Recently I had a look at the DSS event part and here are some mistakes I noticed.
1. There is an Expression filed. I think it mean the Xpath. So it should be Xpath or Xpath Filter 2. If it is Xpath there should be a way to map namespace prefixes to name spaces 3. Subscription filed should rename as Event Sink URL thanks, Amila. On Wed, Feb 23, 2011 at 9:56 PM, Prabath Abeysekera <[email protected]>wrote: > *Meeting Notes:* > > *Participants:* > Azeez, Srinath, Sumedha, Anjana, Saminda, Chathuri, Harshana, Dinusha, > Dakshitha, PrabathA > > * > * > *Suggested Improvements:* > > *Service Details Page* > 1. Introduce an alternative option over true/false inputs. > 2. Change "Disable Streaming" Parameter to "Enable Streaming" and modify > the default values appropriately. > 3. Introduce appropriate names for parameters (eg: terms such as TS should > be removed or used with proper descriptions) > 4. Add proper explainations for technical terms such as XA,etc. > > *XA Data Source Page* > 1. Remove arrows in "Save" buttons. > 2. Change the flow of UI transitions. The reason is, at a give moment, the > existing wizard does not indicate what steps a particular user has already > completed and what needs to be done. > > *Query Definition Page* > 1. Proper Alignment of buttons should be done. > 2. Remove "Finish" button from the initial stages of the wizard such as > "create data source" phase, etc. > (But the existance of Finish button might be important when editing a data > service. That fact should be considered before modifying it.) > 3. A pop up window, a floating div or a similar kind of approach should be > introduced against the existing SQLDialect window to insert required > parameters. > 5. Remove plus/minus icons to hide/show items corresponding to some options > since, in general plus/minus means adding/removing something, which is more > appropriate to be used in a tree type structure. > > *Generation Page* > 1. "Database name" should be changed as "Datasource name" and the > corresponding datasources should be represented using a drop down list box. > > *Things to be done* > 1. Finalize the flow functionalities that should be there in the wizard. > 2. Introduce appropriate grouping of items to achieve clarity. > 3. Do a brainstorming session and prepare a flow diagram which represents > all the necessary steps. > 4. Consider the approach of using Tabbed UIs. > 5. Use Ajax to make the wizard more interactive. > 6. Try some UI frameworks such as JSF to find a better alternative against > the existing approach. > > > > Regards, > -- > Prabath Abeysekara > Software Engineer > WSO2 Inc. > Email: [email protected] <[email protected]> > Mobile: +94774171471 > > <http://harshana05.blogspot.com/> > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
