UI Service Components
Sun, 2008-08-31 19:35 — tamhas
This category will be used to discuss principles of building UI service components, sample UI service component code, and helper classes for UI services.
UI services are components which run on the server and provide an interface between clients and the business logic layer. They contain no UI themselves. It is likely that some will be specific to a given UI and will serve to isolate the business logic layer from the specifics of the particular UI. Some may be UI independent.
- Printer-friendly version
- Login to post comments
Comments
fielf definition
In our old clientserver app we defined a structure in the private data of the field, with properties of the field. example: Is it a mandatoryfield, how should the field be presented: a combo-box, a search-field, suggest-field etc. Also the parameters for this presentation were located.
Is this the aim of this component. If so i think it usefull to define a type with holds these properties. It will be defined on the server and contains all domain properties. So i you use on of these fields say: CountryCode it will inherit its properties from tis structure. The UI should than translate these properties in the proper widgets.
Of course the program can override this definition with his own.
Right now, there aren't
Right now, there aren't really any specific components proposed for this group ... it is just a logical category into which proposals can go. I have to confess to not having thought a lot about this category since I have a bias toward WUI clients, i.e., no ABL UI.
Off the top of my head, I'm not sure that I see a need for what you are proposing, but perhaps I just don't have it clear. It seems to me that some of the properties are properties in the business entity object itself while others are properties of the specific UI.