Hi Amila, Thanks for the comments, and sorry for the late reply.
> This is something I have mentioned earlier as well. I am not sure any one > have paid a real attention to it. > > The problem with current DSS is that it try to provide every thing from one > wizard. Rather you can have > different set of menus like data first, data service, contract first etc .. > as a top menu and show only the relevant > things at the wizard which make less confuse to the user. Yes, we have been paying attention to your ideas very much :) .. And this was also suggested by Sumedha sometime back, and at the moment, we do have separate menus for the classical data services wizard, the contract first approach, and the data first approach, and also scheduled tasks for data services, these functionalities are clearly broken down. And our next aim is to add more functionalities specially for the data first and the contract first approaches to be used to rapidly create data services based on some predefined use cases. Cheers, Anjana. > > In CEP also we had a wizard like structure. But what we found there was it > does not show the big picture to the user and > he is lost in going forward and back word. If you can break down the DSS > functionalities in terms of use cases then you can have more compact views > with each use cases rather than long wizards. > > thanks, > Amila. >> >> If you compare DSS to some other large data integration products which >> has a richer UI, you will notice that DSS have the most simple UI, >> which provides the most functionality/customisability. Hope you wont >> see this as me giving excuses for not making the current UI better :), >> rather, we will definitely look into your ideas and consider the >> improvements. >> >> Thanks and Regards, >> Anjana. >> >> On Sat, Jan 29, 2011 at 12:24 AM, Afkham Azeez <[email protected]> wrote: >> > When it comes to a wizard, there is an expected flow. You should be able >> > to >> > move forward or back, and screen that take you out of the wizard should >> > be >> > avoided. Those are something you should avoid according to the wizard >> > paradigm. If you go through the DS wizard, it is obvious to the >> > developers >> > who wrote it, not to the users. One way in which people improve >> > usability is >> > give a set of things to be done by new users, and watch what they do. >> > Perhaps you guys can watch me doing something and learn from the >> > mistakes I >> > make. >> > Thanks >> > Azeez >> > >> > >> > >> > On Fri, Jan 28, 2011 at 11:48 AM, Anjana Fernando <[email protected]> >> > wrote: >> >> >> >> Hi Azeez, >> >> >> >> On Fri, Jan 28, 2011 at 1:34 AM, Afkham Azeez <[email protected]> wrote: >> >> > The wizard is not really a wizard since it does not necessarily >> >> > follow a >> >> > flow. Also, if you do things in the wrong order, bad things happen & >> >> > NPEs >> >> > fly. These things normally happen at the wrong time; during demos :) >> >> >> >> I do agree on the UI issues, the DSS UI is very fragile, and we've >> >> been planning on rewriting the DSS UI soon. As in, some validations >> >> are missing I guess, for instance, if you just enter an url of a >> >> specific page by hand - something in the middle of the wizard, most >> >> probably it'll give some unexpected errors. >> >> >> >> But, when you said, 'not following a flow', can you elaborate on that >> >> a bit more? .. Because, I was having the impression, the current DS >> >> wizard is pretty simple in a way that, it follows the below flow for >> >> the normal service creation. >> >> >> >> Start Service Creation -> Create Data Source(s) -> Create Queries -> >> >> Create Operation(s) / Resource(s). >> >> >> >> What kind of a flow are you suggesting? .. >> >> >> >> Cheers, >> >> Anjana. >> >> >> >> > >> >> > -- >> >> > Afkham Azeez >> >> > Senior Software Architect & Senior Manager; WSO2, Inc.; >> >> > http://wso2.com, >> >> > >> >> > Member; Apache Software Foundation; http://www.apache.org/ >> >> > email: [email protected] cell: +94 77 3320919 >> >> > blog: http://blog.afkham.org >> >> > twitter: http://twitter.com/afkham_azeez >> >> > linked-in: http://lk.linkedin.com/in/afkhamazeez >> >> > >> >> > Lean . Enterprise . Middleware >> >> > >> >> > _______________________________________________ >> >> > Carbon-dev mailing list >> >> > [email protected] >> >> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > >> >> > >> >> >> >> >> >> >> >> -- >> >> Anjana Fernando >> >> Software Engineer >> >> WSO2, Inc.; http://wso2.com >> >> lean.enterprise.middleware >> >> _______________________________________________ >> >> Carbon-dev mailing list >> >> [email protected] >> >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> > >> > >> > -- >> > Afkham Azeez >> > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >> > >> > Member; Apache Software Foundation; http://www.apache.org/ >> > email: [email protected] cell: +94 77 3320919 >> > blog: http://blog.afkham.org >> > twitter: http://twitter.com/afkham_azeez >> > linked-in: http://lk.linkedin.com/in/afkhamazeez >> > >> > Lean . Enterprise . Middleware >> > >> > _______________________________________________ >> > Carbon-dev mailing list >> > [email protected] >> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> > >> >> >> >> -- >> Anjana Fernando >> Software Engineer >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> _______________________________________________ >> 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 > > -- Anjana Fernando Software Engineer WSO2, Inc.; http://wso2.com lean.enterprise.middleware _______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
