On 02/04/2011 04:00 AM, Duncan Mac-Vicar P. wrote:
On 01/28/2011 04:50 PM, Arvin Schnell wrote:
Hi,
in a recent telco the question about the direction of the YaST architecture was raised.
After seeing this long discussion I think the only way to move forward is that people presents some proposal
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.
Sorry, just a rudimentary implementation, not a complete prototype module, to demonstrate my basic ideas. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Novell-IBM Software Integration Center LINUX Tech Lead rschweikert@novell.com rschweikert@ca.ibm.com 781-464-8147 Novell Making IT Work As One