Mailinglist Archive: yast-devel (177 mails)

< Previous Next >
Re: [yast-devel] Direction of YaST Architecture?
* Gabriele Mohr <gs@xxxxxxx> [Feb 09. 2011 10:22]:
Am 28.01.2011 16:50, schrieb Arvin Schnell:
Hi,

in a recent telco the question about the direction of the YaST
architecture was raised.

I miss an important fact when reading the discussion here. For me it's
not clearly pointed out how WebYaST and YaST will work together nicely
in future.

Thanks for bringing this up.

I think they should share as much code as possible, e.g. an
interface which provides the logic for system access (something like
Klaus has proposed?).
I think it's a very important goal to bring WebYaST and YaST together
and this aspect should be more respected in the discussion.

This reveals a key problem in the current discussion - treating YaST
and WebYaST as separate projects.

I believe this is wrong.

What's needed is a common infrastructure/backend resp. API to do management
tasks on a Linux system.

This forms the low-level development API for the various user
interfaces.

What we currently know/discuss as 'YaST' would be the (rich) Qt user
interface.
What we currently know/discuss as 'WebYaST' would be the (limited) Web user
interface.
Additionally, a CLI interface for scripting is needed.

All those user interfaces are using the common backend, exposing
different details and functionality.


Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG N├╝rnberg)

--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
List Navigation
This Thread
References