Mailinglist Archive: yast-devel (177 mails)
| < Previous | Next > |
Re: [yast-devel] Direction of YaST Architecture?
- From: Thomas Goettlicher <thomas.goettlicher@xxxxxxx>
- Date: Tue, 1 Feb 2011 15:01:19 +0100
- Message-id: <201102011501.19754.thomas.goettlicher@suse.de>
On Tuesday, February 01, 2011 12:01:22 pm Stanislav Visnovsky wrote:
[...]
There already exists a project that is a complete new YaST without legacy code
like YCP and it uses a cool and object oriented script language. It's called
webyast. :-)
For YaST I think we shouldn't try to refactor everything for the sake of
refatoring. We already have a robust framework, let's focus on how we can add
benefits for the users to YaST, e.g. the snapper feature. If the
implementation of this feature needs architectural changes I totally fine with
it.
Thomas
--
Thomas Goettlicher
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx
[...]
I fully agree.
I'm fan of small steps, not grand plans for redoing everything from
scratch.
There already exists a project that is a complete new YaST without legacy code
like YCP and it uses a cool and object oriented script language. It's called
webyast. :-)
For YaST I think we shouldn't try to refactor everything for the sake of
refatoring. We already have a robust framework, let's focus on how we can add
benefits for the users to YaST, e.g. the snapper feature. If the
implementation of this feature needs architectural changes I totally fine with
it.
Thomas
--
Thomas Goettlicher
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx
| < Previous | Next > |