[yast-devel] vendor specific module
Hi, please find a first idea of integration of vendor specific modules at: http://en.opensuse.org/YaST/Web/Docu/Navigation#Vendor_Specific_Module The idea would be: Vendor specific modules are represented either with an icon specified by a vendor or by a generic icon (e.g. yast-vendor.png) When clicking on the module the vendor specific configuration starts in fullscreen mode and replaces the webYaST UI completely. If specified by the vendor a separate login screen is shown. Cancelling the login dialog returns the user to webYaST "Home". For changes and navigation within the module the module`s controls are used. After finishing work with the vendor specific module the module is exited by clicking either on logout or any other exit option provided within the vendor specific module. The user then returns to webYaST "Home". Retrieved from "http://en.opensuse.org/YaST/Web/Docu/Navigation" Reasons for this: * running a module inside YaST GUI leads to a confusing look and feel and a lot of unclear functionalities (e.g. how to save settings); see slide 4 on presentation at http://en.opensuse.org/YaST/Web/Docu/Navigation#Try_it_3 * most programms have an exit functionality so why not use it? Looking forward to your comments! Cu, Martin -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate für nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Martin Schmidkunz <Martin.Schmidkunz@gmx.de> [Aug 13. 2009 14:48]:
Hi,
please find a first idea of integration of vendor specific modules at: http://en.opensuse.org/YaST/Web/Docu/Navigation#Vendor_Specific_Module
The idea would be: Vendor specific modules are represented either with an icon specified by a vendor or by a generic icon (e.g. yast-vendor.png)
Well, naming it 'module' is a bit confusing. What Fate#306713 ([webyast] Link to Application-Specific Web UI) asks for is a link to a vendor web ui running on a different port. So this is similar to a normal html 'href' but should open a new browser tab (resp. window) to make the difference apparent. 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
Well, naming it 'module' is a bit confusing.
Right! It was just a working title :-) I renamed it to: http://en.opensuse.org/YaST/Web/Docu/Navigation#Link_to_Application-Specific...
So this is similar to a normal html 'href' but should open a new browser tab (resp. window) to make the difference apparent.
Wouldn`t it be more intuitive to run it in the same window as webYaST? The pros would be: * consistent behaviour with "How to start a module" (and as the vendor specific application is visualized similar to other modules it might be hard for the user to distinguish them from a "real" module) * simplify navigation and work with webYaST when everything runs in one window * consistent with the idea of working with one module at the time Cu, Martin -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Martin Schmidkunz <Martin.Schmidkunz@gmx.de> [Aug 13. 2009 16:42]:
Well, naming it 'module' is a bit confusing.
Right! It was just a working title :-) I renamed it to: http://en.opensuse.org/YaST/Web/Docu/Navigation#Link_to_Application-Specific...
So this is similar to a normal html 'href' but should open a new browser tab (resp. window) to make the difference apparent.
Wouldn`t it be more intuitive to run it in the same window as webYaST?
I do not think so because this UI is completely separate from (and different to) Webyast.
The pros would be: * consistent behaviour with "How to start a module" (and as the vendor specific application is visualized similar to other modules it might be hard for the user to distinguish them from a "real" module) * simplify navigation and work with webYaST when everything runs in one window * consistent with the idea of working with one module at the time
We have absolutely no influence on the look and feel or the navigation properties of the vendor UI. It might even be advisable to pop up a "you're leaving Webyast" warning (configurable). 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
On Thursday 13 August 2009 15:58:11 Klaus Kaempf wrote:
Well, naming it 'module' is a bit confusing. What Fate#306713 ([webyast] Link to Application-Specific Web UI) asks for is a link to a vendor web ui running on a different port.
So this is similar to a normal html 'href' but should open a new browser tab (resp. window) to make the difference apparent.
right now we can link to other application modules using the shortcuts. The missing part would be to also read shortcuts from a more standard location and not only from the plugin directory. But nothing right now prevents for adding a full url path. Now, how to enter the port without saying the host (the host should be the "same" :-) Additionally we can add attributes like: - whether to open in a new window? - .... -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (3)
-
Duncan Mac-Vicar Prett -
Klaus Kaempf -
Martin Schmidkunz