15 Feb
2011
15 Feb
'11
08:33
* Jiri Srain
Actually, this leads to one requirement on the overal architecture, which was mentioned couple of times already: To have a back-end providing the business logic with a reasonable high-level API, on top of which both YaST and WebYaST can provide their UIs.
Yes.
Afterwards, porting a module form classical YaST to WebYaST will mean only creating the screen layout.
Sounds like easy. But it isn't. Getting the UI design and usability right is *hard*. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org