Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Design and Architecture
  4. GUI design for Harware configuration

GUI design for Harware configuration

Scheduled Pinned Locked Moved Design and Architecture
designannouncementc++hardwareregex
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    Praveen Raghuvanshi
    wrote on last edited by
    #1

    Hello, I have been designing a cross-platform GUI application using JUCE framework and need some help in designing it. The GUI will be used for configuring the hardware/device. I did layering for the application as below. - Presentation Layer - Controller Layer - Model Layer - Communcation Layer I’ll explain each of them as below. Model Layer: It contains the actual data that is displayed in the UI and stored in the hardware/device. For e.g Device Information (ID, Name, version number) Presentation Layer: It displays the information present in the Model/Hardware or the information after being manipulated in the Model. Mainly, it acts a View. Controller Layer: It controls the requests coming from presentation layer and hardware/model layer. Communication Layer: It communicates with the actual hardware through some protocol and send/receive from/to controller. So, the basic flow from UI to device will be Presentation -> Controller -> Communication -> H/W -> Receive message from H/W -> Communication -> controller -> Model and Presentation And reverse would be Receive message from H/W -> communication -> controller -> model and presentation. Here are my questions w.r.t design. - Model will have entities such as Employee, Department which will be used inside the controller. Shall I create a EmployeeController and departmentController OR should I have a single controller class only - If I wanted to show information of an emplyee in a department in UI, should I create corresponding views in the UI such as employeeView and departmentView. - What patterns we can apply for different layers, especially for GUI - Where should I write the observer pattern in order to update the UI when there is a change in the value of the Model. - Appreciate if someone can provide me an example for Loosly coupled GUI application in C++ and that interacts with the hardware. Please let me know for any clarification. Thanks in advance for your time and effort.

    Praveen Raghuvanshi Software Developer

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups