Mailinglist Archive: yast-devel (66 mails)

< Previous Next >
Re: [yast-devel] YaST in ruby and UI terms
On Tue, 25 Jun 2013 12:28:19 +0200
Klaus Kaempf <kkaempf@xxxxxxx> wrote:

* Josef Reidinger <jreidinger@xxxxxxx> [Jun 25. 2013 11:35]:
I would like to discuss one think that is related to creating UI in
YaST in ruby. In YCP it uses terms. In ruby generic terms looks


but it is not much nice for me, so I create few shortcuts for known
UI elements and it looks like this:


Agreed, the latter one looks so much nicer.

There is a problem. In UI is often used terms `id and `opts, but it
doesn't start with uppercase and there is high chance to collide
with existing methods ( beside id collide with ruby id method ).

Usage of object#id is not a problem if 'id' is defined in object's

So I
propose to translate it to
ID(:id) and OPTS(:strechable,:notify)

Ugh, all caps is reserved for constants in Ruby.

OK, good argument.

alternative can be Opts and Id.
what is your opinion?

libyui-bindings has more complete examples
which could help guiding a decision.

To be honest, I don't like this examples, it looks like old C gtk where
create every element is pain. Compare this examples with elegance of
translated YCP code -

I just want to get rid of annoying id, header and opt term. So after
your comments I propose to create shortcuts
Id, Opt and Header that creates such terms.

Any objections?



To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups