[yast-devel] UI documentation
Hi, please find some UI documentation on: http://en.opensuse.org/YaST/Web/Docu/Style_Guide The documentation includes: * generic webYaST layout * generic module layout * overview dialog * add wizard * edit * delete Looking forward to your comments, Martin --- Martin Schmidkunz User Experience Specialist mschmidkunz@novell.com +49 (0) 911 740 53-346 --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --- Novell® Making IT Work As One™ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On 08/27/2009 04:10 PM, Martin Schmidkunz wrote:
Hi,
please find some UI documentation on: http://en.opensuse.org/YaST/Web/Docu/Style_Guide
The documentation includes: * generic webYaST layout * generic module layout * overview dialog * add wizard * edit * delete
Looking forward to your comments,
Martin
Yeah, it looks good. Just one note. Web service should be stateless as you cannot restrict what user do (all attempt more or less fail). So example that setting sound in three steps or adding DNS in three steps is not good. It is common, that user set part and that part is immediately save. If we don't do this in this step we could have serious problems during unexpected user actions. So if we need add something in more steps, then I think we should prefer have necessary settings in one screen and set rest after add on separate page which immediately save. So I hope that only wizard is base system settings, which save settings after each step, so it is not real wizard as we know from yast, it is just settings of necessary steps. -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hi, thanks for your comment! On 27.08.2009, at 16:21, Josef Reidinger wrote:
Yeah, it looks good. Just one note. Web service should be stateless as you cannot restrict what user do (all attempt more or less fail). So example that setting sound in three steps or adding DNS in three steps is not good. It is common, that user set part and that part is immediately save. If we don't do this in this step we could have serious problems during unexpected user actions. So if we need add something in more steps, then I think we should prefer have necessary settings in one screen and set rest after add on separate page which immediately save.
Mhm. Couldn`t the values be cached somehow? Maybe someone with more detailed technical knowledge than me can comment this? In general I think, skipping wizards completely would decrease usability a lot :-(
So I hope that only wizard is base system settings, which save settings after each step, so it is not real wizard as we know from yast, it is just settings of necessary steps.
It seems so :-) Cu, Martin --- Martin Schmidkunz User Experience Specialist mschmidkunz@novell.com +49 (0) 911 740 53-346 --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --- Novell® Making IT Work As One™
participants (2)
-
Josef Reidinger -
Martin Schmidkunz