I18 Standard button and dcop

Hi,

Some questions...

I have seen we can use i18n in kommander but for a text
propertie already set 
in editor, must we redefine text in the init slot from
dialog form like this:  
Widget.setText( i18( "Please traduce that"))
or is it automatic ?

An other cosmetic problem is I'm not able to have standard
buttons( wich 
doesn't change of size when window resizing)? Standard
button have an 
attribute 'Block GUI' but no way in editor to edit this.
Must we use Qt 
designer ?

And finally I found in dcop that there are
"functions" with QSignal exported. 
Can with use them ? ( connect a widget with this signals ?)

( More generally, does qt export all signals and slots
automagically or must 
we export functions like it is described in the kommander
plugins 
documentation ?)

Thanks for response.

Fréderic LECONTE <fred.leconte2wanadoo.fr>

_______________________________________________
Kommander mailing list
Kommanderkdewebdev.org

http://mail.kdewebdev.org/mailman/listinfo/kommander

On Wednesday 30 April 2008 7:02:03 am LECONTE Frédéric
wrote:
> Hi,
>
> Some questions...
>
> I have seen we can use i18n in kommander but for a text
propertie already
> set in editor, must we redefine text in the init slot
from dialog form like
> this: Widget.setText( i18( "Please traduce
that"))
> or is it automatic ?

i8n() always signifie text to be translated and must be
used.
>
> An other cosmetic problem is I'm not able to have
standard buttons( wich
> doesn't change of size when window resizing)? Standard
button have an
> attribute 'Block GUI' but no way in editor to edit
this. Must we use Qt
> designer ?

GUI blocking has to do with blocking any other input while
an operation is in 
process. Sizing is handled by layouts and properties. Check
the property 
editor. You can set maximum size as well as policies like
prefer or ignore.
>
> And finally I found in dcop that there are
"functions" with QSignal
> exported. Can with use them ? ( connect a widget with
this signals ?)

Signals and slots are available and explained in the docs. 
>
> ( More generally, does qt export all signals and slots
automagically or
> must we export functions like it is described in the
kommander plugins
> documentation ?)

Some slots are filtered in the signal slot editor, but as of
1.3 there is a 
slots category in the Function Browser enabling scripts to
directly call any 
slot. Not all of the QWidget stuff is exported or it would
be very busy. 
That's why I added geometry and hasFocus in 1.3.1.

Plugins are another matter. If you write a plugin you can do
anything you can 
code, but you have to name the widget differently from any
existing.
>
> Thanks for response.
>
> Fréderic LECONTE <fred.leconte2wanadoo.fr>
>


-- 
Eric Laffoon
Project Lead - kdewebdev module
_______________________________________________
Kommander mailing list
Kommanderkdewebdev.org

http://mail.kdewebdev.org/mailman/listinfo/kommander

On Wednesday 30 April 2008 18:15:16 Eric Laffoon wrote:
> > Some questions...
> >
> > I have seen we can use i18n in kommander but for a
text propertie already
> > set in editor, must we redefine text in the init
slot from dialog form
> > like this: Widget.setText( i18( "Please
traduce that"))
> > or is it automatic ?
>
> i8n() always signifie text to be translated and must be
used.

That's true, but for the text you add to
buttons/widgets/etc. in the editor, 
this is not the case. Those should be extracted
automatically.

Andras

-- 
 
Quanta Plus developer - http://quanta.kdewebdev.o
rg
K Desktop Environment - http://www.kde.org
_______________________________________________
Kommander mailing list
Kommanderkdewebdev.org

http://mail.kdewebdev.org/mailman/listinfo/kommander