Mailinglist Archive: yast-devel (168 mails)
| < Previous | Next > |
Re: [yast-devel] web based YaST
- From: Klaus Kaempf <kkaempf@xxxxxxx>
- Date: Fri, 11 Apr 2008 14:24:39 +0200
- Message-id: <20080411122439.GA12678@xxxxxxxxxxxxx>
* Michal Zugec <mzugec@xxxxxxx> [Apr 11. 2008 13:46]:
Yes, nice !
I can see REST (http://www.infoq.com/articles/rest-introduction) and MVC
(http://en.wikipedia.org/wiki/Model-view-controller) there.
Both very useful for a web based YaST architecture. Together with a
set of dialog templates to ensure UI consistency (and offload
developers from dialog details).
But using SQL statements (see the video) is ugly. Lets see when Google
adds the active record pattern
(http://en.wikipedia.org/wiki/Active_record_pattern) ;-)
Active record is probably a good pattern to access backend information
(aka 'SCR'). Not sure yet.
Klaus
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx
When we discussed about web frontend, just look how Google do their staff
with
Python (for inspiration):
http://www.youtube.com/watch?v=bfgO-LXGpTM
http://code.google.com/appengine/docs/whatisgoogleappengine.html
Yes, nice !
I can see REST (http://www.infoq.com/articles/rest-introduction) and MVC
(http://en.wikipedia.org/wiki/Model-view-controller) there.
Both very useful for a web based YaST architecture. Together with a
set of dialog templates to ensure UI consistency (and offload
developers from dialog details).
But using SQL statements (see the video) is ugly. Lets see when Google
adds the active record pattern
(http://en.wikipedia.org/wiki/Active_record_pattern) ;-)
Active record is probably a good pattern to access backend information
(aka 'SCR'). Not sure yet.
Klaus
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx
| < Previous | Next > |