Mailinglist Archive: yast-devel (177 mails)

< Previous Next >
Re: [yast-devel] WebYaST will help the openness
  • From: "Duncan Mac-Vicar P." <dmacvicar@xxxxxxx>
  • Date: Wed, 16 Feb 2011 15:57:12 +0100
  • Message-id: <4D5BE5C8.6080008@suse.de>
On 02/16/2011 09:38 AM, Lukas Ocilka wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dne 15.2.2011 17:19, Duncan Mac-Vicar P. napsal(a):
On 02/15/2011 12:34 PM, Johannes Meixner wrote:
> I would like to describe only the logic of the UI elements
and leave the actual layout to an automatism like:
-------------------------------------------------------------------
Group( Label( "Keywords and values"),
Group( InputField( "First keyword:", keyword1 )
InputField( "First value:", value1 )
),
Group( InputField( "Second keyword:", keyword2 )
InputField( "Second value:", value2 )
),
PushButton( "Store keywords and values" )
)

We could call it HTML, and the styling/positioning part CSS.

Yes, we could :) Except "nobody wants to code HTML&& CSS anymore"™.
Certain level of abstraction is kind of a must nowadays.

a lightweight version of XUL (may be json-ized) may be a good thing. As libyui does not have event loop and you query widgets by id.

Another thing to look is declarative user interfaces, has anyone given a look at Qt Quick?

http://qt.nokia.com/products/qt-quick/

Also we should look more into model binding. Instead of manually maintaining data in the module for each widget, just say... this table is bound to this model and be done.

--
Duncan Mac-Vicar P. - Novell® Making IT Work As One™
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 >