Mailinglist Archive: yast-devel (177 mails)

< Previous Next >
Re: [yast-devel] Direction of YaST Architecture?
  • From: Birger Kollstrand <birger.kollstrand@xxxxxxxxxxxxxx>
  • Date: Wed, 9 Feb 2011 22:54:08 +0100
  • Message-id: <AANLkTimCMWJOV8s=bLxA1pu9r4o0yadRmqnvnNOTFy7K@mail.gmail.com>
2011/2/9 Robert Schweikert <rschweikert@xxxxxxxxxx>:
OK, here is one proposal.

Uses Python with the idea that individual modules are implemented as
Python packages. This would allow us to package each module separately
in a straight forward fashion. Nice granularity which would also benefit
integration with WebYaST.

This also follows the idea Klaus had about being domain specific (which
I like). The domain specific functions are implemented in __init__.py
and the details are hidden from the user. In this case (only rudimentary
implementation) the storage of the information for an NFS share is
hidden in the nfsShare object, while the user setting up a share via
createShare() does not need to worry about these details.

import yast3.nfs_client
yast3.nfs_client.createShare(.....)

Advantages:
- Everything is in Python thus this meets the common language
 criteria that appears to be emerging in the discussion
- Implementation via Python packages provides granularity and easy
 packaging, facilitates small "footprint" for integration with WebYaST
- Domain specific interface allows us to be very expressive
- Easy to use in setup scripts
- It should be relatively easy to put a GUI on top of this while
 maintaining MVC paradigm


ie: one group/pair/individual could present a "prototype" module done
with lang X, tools Y, and show how a module would look like, what
possibilities this bring etc. Another group/pair/individual could do the
same using a different approach.


Or take it even further. Adopt either Ubuntu or Fedoras base and
continue to work with other distros to maximize the effect of the
open-source effort.

Why reinvent when it can be built on an existing stable base? Also the
openSUSE contributions would then benefit a larger audience.
(This is by NO means meant as a flame bait!)

The only reason for not adopting an existing base would be branding. I
can see that openSUSE might get to similar in regards to marketing.
But for open-source I think it would be beneficial. The linux
platforms that are progressing well today are the platforms where the
platform i standardized.

Kind regards

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

< Previous Next >
List Navigation
This Thread