Re: Auto selection

Essentially, your GUI must be aware of the business objects that
it's
presenting at any time, and which object is in focus is a matter for
the GUI only (not the business model).

Okay. Selection/Focus is a part of the UI. This thightens my
assumption.

So, when you pass your command CreateNewCodeFile to the model, then the
model will eventually send a message to the GUI to say either, "Here's
a new node created," or, "The model's been updated: go figure."

The first approach "Here's a new node created" sounds interesting. Of
course.
Btw, with node you mean an business object, right?

The tree was just an example. It could also be something else. However,
I would like to know how it should be realized with a tree (deep
structure should be also possible). Would you use an event? What would
raise the event? Would you pass the parent business object as a
parameter?

appropriate node highlighted. This also makes navigation of the
graphics easier by user-commands such as arrow-keys (the GUI can expose
an api with such methosd as: Node[] getSelectedNodes[], Node
getNextNode() etc.).

I'm not sure how to understand this in the context. Do you mean this in
a strict MVC design? Please excuse, I'm not that experienced with those
'higher' leveled programming techniques.

Thanks.
Robert

.

Relevant Pages

  • Re: Business Entity Designs
    ... > Tier Roles and Responsibilities (6 assemblies in total) ... > Client user interaction via GUI ... > All business and application logic serviced by .NET remote \ COM+ ... > I've tried to look at existing systems & examples (hence my Duwamish ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: Auto selection
    ... the GUI only. ... Selection/Focus is a part of the UI. ... Btw, with node you mean an business object, right? ... The event that triggers the creation of a folder is the use clicking ...
    (comp.object)
  • Re: Unit testing GUIs
    ... > developing a separate business model and application model. ... it implies having a simpler GUI than you might ... > Now in the final system, all three layers will be sewn together. ... > be defined as adaptors to domain objects and methods. ...
    (comp.object)
  • Re: 3 tier architecture: a lot of questions
    ... here is that your middle layer actually solves some business problem ... and the GUI. ... the RDB access layer. ... Where things get stickier is when the validation data is not yet in the ...
    (comp.object)
  • Re: better way of using XML
    ... The only data going to the Web Service should be business data. ... The GUI can manage itself, and the Web Service doesn't have to know anything ... > I'm using xml file to transfer the GUI information from client to server ...
    (microsoft.public.dotnet.languages.csharp)