| Re: [dali-dev] Dali 1.0 UI discussion |
|
The output of this meeting was better definition of the questions at
hand: - What do we want our Java source UI support to look like (beyond the in-source editing assistance) ? (ie Fully functional, rich form based UI versus lighter-weight form based UI) - Should the UI for XML reside in a similar properties form, or should the orm.xml have its own Forms editor? - Is the UI for Java and XML really the same in function, or should it be different? (this is related to the first question) - Where do we want to handle switching (morphing) persistent types and attribute mappings? In the properties page, outline, source, or all of the above? There are arguments to be made for differing answers to the above questions. The basis for these arguments include: what is more platform integrated; what is better for our particular needs and our functionality; what is technically more feasible; what is the likelihood of achieving change across a number of Eclipse projects; what will ultimately make things easier for adopters. At the heart of these arguments is what is ultimately best for our users, adopters, and the community as a whole. The plan to resolve these questions includes requesting guidance from the Eclipse UI Best Practices Working Group, further input from project participants, input from the community, and more discussion to arrive at the best possible solution. Neil Neil Hauge wrote: Webconference info: |