[rox-devel] OroboROX options GUI

[Jonatan Liljedahl <than@ho...>]

I'm writing a simple python script for editing the OroboROX rcfile...
I'm using the Options.xml system in ROX-Lib2.

Questions:

Is it possible to get the toggles (checkboxes) to return 'true' and
'false' instead of '1' and '0' ?

How do I add buttons in the option GUI to call my own funcs? (I would
like a button that opens APP_DIR/themes in a filer window). I would also
like a DnD area where you can drop the themedirectory.

Is it possible to convert the result from the font-button widget, from
the "new" fontnames like "Luxi Sans 12" to the traditional oldschool
names like 
-*-lucida-medium-r-normal-*-12-*-*-*-*-*-iso8859-* ?


/Jonatan
__
  |   __                 ____        _          ____
  |__/__         _____  _____||___  (_) ____   _____|
  |     )(_____|(  |  )(_____||_____ | (______(_____|
===============|=====================================
             __| http://kymatica.com

[rox-devel] OroboROX options GUI

[Jonatan Liljedahl <than@ho...>]

I'm writing a simple python script for editing the OroboROX rcfile...
I'm using the Options.xml system in ROX-Lib2.

Questions:

Is it possible to get the toggles (checkboxes) to return 'true' and
'false' instead of '1' and '0' ?

How do I add buttons in the option GUI to call my own funcs? (I would
like a button that opens APP_DIR/themes in a filer window). I would also
like a DnD area where you can drop the themedirectory.

Is it possible to convert the result from the font-button widget, from
the "new" fontnames like "Luxi Sans 12" to the traditional oldschool
names like 
-*-lucida-medium-r-normal-*-12-*-*-*-*-*-iso8859-* ?


/Jonatan
__
  |   __                 ____        _          ____
  |__/__         _____  _____||___  (_) ____   _____|
  |     )(_____|(  |  )(_____||_____ | (______(_____|
===============|=====================================
             __| http://kymatica.com

Re: [rox-devel] OroboROX options GUI

[Ken Hayber <khayber@so...>]

On Mar 29, 2004, at 11:19 AM, Jonatan Liljedahl wrote:

> I'm writing a simple python script for editing the OroboROX rcfile...
> I'm using the Options.xml system in ROX-Lib2.
>
> Questions:
>
> Is it possible to get the toggles (checkboxes) to return 'true' and
> 'false' instead of '1' and '0' ?
Not that I know of.  Python shouldn't care.

> How do I add buttons in the option GUI to call my own funcs? (I would
> like a button that opens APP_DIR/themes in a filer window). I would 
> also
> like a DnD area where you can drop the themedirectory.
The new way is via the widget registry in 1.9.13.  I never tried it the 
old way which is to subclass the OptionsBox class and add your own 
handlers.  The very top of the OptionsBox documentation page on the 
wiki has examples of the new way.

>
> Is it possible to convert the result from the font-button widget, from
> the "new" fontnames like "Luxi Sans 12" to the traditional oldschool
> names like
> -*-lucida-medium-r-normal-*-12-*-*-*-*-*-iso8859-* ?
Why would you want this?  Isn't everything using the new style stuff 
now.  I'd think you'd want to do the opposite.

Re: [rox-devel] OroboROX options GUI

[Jonatan Liljedahl <than@ho...>]

On Mon, 29 Mar 2004 13:05:40 -0800
Ken Hayber <khayber@...> wrote:

> On Mar 29, 2004, at 11:19 AM, Jonatan Liljedahl wrote:
> 
> > I'm writing a simple python script for editing the OroboROX
> > rcfile... I'm using the Options.xml system in ROX-Lib2.
> >
> > Questions:
> >
> > Is it possible to get the toggles (checkboxes) to return 'true' and
> > 'false' instead of '1' and '0' ?
> Not that I know of.  Python shouldn't care.

The thing is that OroboROX cares, one solution is to add a check for
'true' or '1' in OroboROX of course... Anyhow I solved it at last, with
a custom checkbox widget.

> > How do I add buttons in the option GUI to call my own funcs? (I
> > would like a button that opens APP_DIR/themes in a filer window). I
> > would also
> > like a DnD area where you can drop the themedirectory.
> The new way is via the widget registry in 1.9.13.  I never tried it
> the old way which is to subclass the OptionsBox class and add your own
> 
> handlers.  The very top of the OptionsBox documentation page on the 
> wiki has examples of the new way.

Yes, I succeeded at last. Don't know if I've done everything the right
way but it works.
(I have never written python or gtk-apps in my whole life before this)

> > Is it possible to convert the result from the font-button widget,
> > from the "new" fontnames like "Luxi Sans 12" to the traditional
> > oldschool names like
> > -*-lucida-medium-r-normal-*-12-*-*-*-*-*-iso8859-* ?
> Why would you want this?  Isn't everything using the new style stuff 
> now.  I'd think you'd want to do the opposite.

Currently OroboROX wants the oldstyle... And since I have no
experience/knowledge about writing gtk-stuff I don't know how to make it
handle the new style... Guido?

/Jonatan
__
  |   __                 ____        _          ____
  |__/__         _____  _____||___  (_) ____   _____|
  |     )(_____|(  |  )(_____||_____ | (______(_____|
===============|=====================================
             __| http://kymatica.com

Re: [rox-devel] OroboROX options GUI

[Guido Schimmels <gushi@ar...>]

Am 29.03.2004 01:46:17 schrieb(en) Jonatan Liljedahl:
> On Mon, 29 Mar 2004 13:05:40 -0800
> Ken Hayber <khayber@...> wrote:

> > > Is it possible to convert the result from the font-button widget,
> > > from the "new" fontnames like "Luxi Sans 12" to the traditional
> > > oldschool names like
> > > -*-lucida-medium-r-normal-*-12-*-*-*-*-*-iso8859-* ?
> > Why would you want this?  Isn't everything using the new style =20
> stuff
>=20
> > now.  I'd think you'd want to do the opposite.
>=20
> Currently OroboROX wants the oldstyle... And since I have no
> experience/knowledge about writing gtk-stuff I don't know how to make
> it
> handle the new style... Guido?

No gtk-stuff needed.
libxft has functions dealing with both font naming schemes. Currently =20
OroboROX detects libxft at comile time and compiles without xft font =20
support when the system doesn't have it. Therefore I left it at the =20
old-style font names in the rc file for the moment.

OroboROX now reads the old-style names from the rc via
XftFontOpenXlfd()

'man Xft' has this example for new-style names:

font =3D XftFontOpen (dpy, scr,  XFT_FAMILY,  Xft-TypeString,   	=09
		"charter",  XFT_SIZE,  XftTypeDouble, 12.0);

Here is the respective option from XFwm4:
<option name=3D"Xfwm/TitleFont" type=3D"string" value=3D"Sans Bold 12"/>

We could either drop support for non-xft builds or add e.g. an xftfont =20
option. For XFT builds we would read option xftfont first and fall back =20
to option font when xftfont is not set (or loading fails).=20

Re: [rox-devel] OroboROX options GUI

[Jonatan Liljedahl <than@ho...>]

On Tue, 30 Mar 2004 10:16:34 +0200
Guido Schimmels <gushi@...> wrote:

> > Currently OroboROX wants the oldstyle... And since I have no
> > experience/knowledge about writing gtk-stuff I don't know how to
> > make it
> > handle the new style... Guido?
> 
> No gtk-stuff needed.
> libxft has functions dealing with both font naming schemes. Currently 
> 
> OroboROX detects libxft at comile time and compiles without xft font  
> support when the system doesn't have it. Therefore I left it at the  
> old-style font names in the rc file for the moment.
> 
> OroboROX now reads the old-style names from the rc via
> XftFontOpenXlfd()
> 
> 'man Xft' has this example for new-style names:
> 
> font = XftFontOpen (dpy, scr,  XFT_FAMILY,  Xft-TypeString,   		
> 		"charter",  XFT_SIZE,  XftTypeDouble, 12.0);

I found a function named XftFontOpenName() which worked, but it wants
the fontnames in the style: "Times-12:bold" instead of "Times Bold 12".
What to do? Anyone know the trick? I did a "grep -r XftFont *" in my
directory containing all unpacked source tarballs but found nothing. It
seems no one is using Xft? ;)

> We could either drop support for non-xft builds or add e.g. an xftfont
> option. For XFT builds we would read option xftfont first and fall
> back  to option font when xftfont is not set (or loading fails). 

I would vote to drop non-xft builds.

/Jonatan
__
  |   __                 ____        _          ____
  |__/__         _____  _____||___  (_) ____   _____|
  |     )(_____|(  |  )(_____||_____ | (______(_____|
===============|=====================================
             __| http://kymatica.com

Re: [rox-devel] OroboROX options GUI

[Guido Schimmels <gushi@ar...>]

Am 29.03.2004 13:10:30 schrieb(en) Jonatan Liljedahl:
> On Tue, 30 Mar 2004 10:16:34 +0200
> Guido Schimmels <gushi@...> wrote:
>
> I found a function named XftFontOpenName() which worked, but it wants
> the fontnames in the style: "Times-12:bold" instead of "Times Bold
> 12".
> What to do? Anyone know the trick?

Such string processing is easy with Python. Of course we could just =20
store it the way XftFontOpenName expects it. I don't know why XFwm4 =20
stores it the way it does. Maybe the pango wrapper function expects it =20
that way and converts it before passing over to xft. I'm not familiar =20
with the pango API.

> I did a "grep -r XftFont *" in my
> directory containing all unpacked source tarballs but found nothing.
> It
> seems no one is using Xft? ;)

You normally don't uses thoses functions directly, but through the =20
toolkit abstractions.
You should find something in the pango sources.

> > We could either drop support for non-xft builds or add e.g. an
> xftfont
> > option. For XFT builds we would read option xftfont first and fall
> > back  to option font when xftfont is not set (or loading fails).
>=20
> I would vote to drop non-xft builds.

When it becomes a nuicance we will.

Re: [rox-devel] OroboROX options GUI

[Jonatan Liljedahl <than@ho...>]

On Tue, 30 Mar 2004 17:12:57 +0200
Guido Schimmels <gushi@...> wrote:

> > I found a function named XftFontOpenName() which worked, but it
> > wants
>  > the fontnames in the style: "Times-12:bold" instead of "Times Bold
>  > 12".
>  > What to do? Anyone know the trick?
> 
>  Such string processing is easy with Python. Of course we could just  
>  store it the way XftFontOpenName expects it. I don't know why XFwm4  
>  stores it the way it does. Maybe the pango wrapper function expects
>  it  that way and converts it before passing over to xft. I'm not
>  familiar  with the pango API.

Yes, ok. My python skills are very very low, how do I do that? 

>  > I did a "grep -r XftFont *" in my
>  > directory containing all unpacked source tarballs but found
>  > nothing. It
>  > seems no one is using Xft? ;)
> 
>  You normally don't uses thoses functions directly, but through the  
>  toolkit abstractions.
>  You should find something in the pango sources.

Ah, okey. I'll take a look there.
 
/Jonatan
__
  |   __                 ____        _          ____
  |__/__         _____  _____||___  (_) ____   _____|
  |     )(_____|(  |  )(_____||_____ | (______(_____|
===============|=====================================
             __| http://kymatica.com

Re: [rox-devel] OroboROX options GUI

[Steve Cooper <stevencooper@is...>]

On Mon, 2004-03-29 at 13:31, Jonatan Liljedahl wrote:
> > > I found a function named XftFontOpenName() which worked, but it
> > > wants
> >  > the fontnames in the style: "Times-12:bold" instead of "Times Bold
> >  > 12".
> >  > What to do? Anyone know the trick?
<snip>
> Yes, ok. My python skills are very very low, how do I do that? 

Try something like this...

fontX = 'Times Bold 12'
(name, style, size) = fontX.split()
fontXft = '%s-%s:%s' % (name, size, style.lower())

cheers,
Steve

Re: [rox-devel] OroboROX options GUI

[Jonatan Liljedahl <than@ho...>]

On Mon, 05 Apr 2004 19:33:46 -0700
Steve Cooper <stevencooper@...> wrote:

> On Mon, 2004-03-29 at 13:31, Jonatan Liljedahl wrote:
> > > > I found a function named XftFontOpenName() which worked, but it
> > > > wants
> > >  > the fontnames in the style: "Times-12:bold" instead of "Times
> > >  > Bold 12".
> > >  > What to do? Anyone know the trick?
> <snip>
> > Yes, ok. My python skills are very very low, how do I do that? 
> 
> Try something like this...
> 
> fontX = 'Times Bold 12'
> (name, style, size) = fontX.split()
> fontXft = '%s-%s:%s' % (name, size, style.lower())

Python is elegant. =) 

But, the problem is that it could as well be "Times 12" or "Luxi Sans
12", "Bitstream Vera Sans Mono 12", etc...

I looked in the Edit source and it does "font =
pango.FontDescription(name)" to convert this to a fontdescription that
is used by "gtk.Widget.modify_font(font)". The pygtk2 reference does not
say
what kind of fontdescription this method takes...

I've tried pango.FontDescription(name).to_string() but it only returns
the name again.

/Jonatan
__
  |   __                 ____        _          ____
  |__/__         _____  _____||___  (_) ____   _____|
  |     )(_____|(  |  )(_____||_____ | (______(_____|
===============|=====================================
             __| http://kymatica.com