Re: How to check SDK version?

[Graham Cobb]

On Saturday 31 October 2009 00:28:21 Jeremiah Foster wrote:
> On Oct 30, 2009, at 10:58, Graham Cobb wrote:
> > On Friday 30 October 2009 08:11:37 Reshma Prasanna wrote:
> >> Hi,
> >> I'm new to Maemo but I'm using a PC that already has a Maemo SDK
> >> installation (done by someone else). Please tell me how to find out
> >> which
> >> version of the SDK is installed? i.e. Is the SDK version 5.0 alpha,
> >> 5.0
> >> beta or 5.0 stable version?
> >
> > cat /etc/maemo_version
>
> Is /etc/maemo_version canonical?

Probably not.  And in things like configure scripts I always check against 
versions of installed libraries, not against the SDK name.  However, it is 
good enough to answer the question "someone left me an SDK which version is 
it"!

MUD uses it as the default for the SDK name (which it uses to select 
alternative entries in its build file) but the user can override it if it is 
wrong.

Graham
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: The issue of version strings

[Jeremiah Foster]

On Oct 30, 2009, at 12:44, Juha Kallioinen wrote:

> ext Niels Breet wrote:
>> On Thu, October 29, 2009 09:01, Martin Grimme wrote:
>>> Hi,
>>>
>>>
>>> hmm, what's so bad about a simple date for a version number?  
>>> Ubuntu does
>>> it, (Open)Solaris does it, and I started doing it, too, because I  
>>> found it
>>> less confusing than having version numbers such as e.g. 0.96.5.
>>
>> Sane version numbers should at least not look like this:
>> 2.0.0+cvs20040908+mp4v2+bmp-0ubuntu6maemo1
>>
>> And yes, this is an actual package version number ;)
>
> And a perfectly good one too! :)

I don't agree. :P

> It's useful not to change the upstream
> package version too much so that it's easier to see that a package  
> could use
> updating.

But in this case it has both the ubuntu and maemo strings. The policy  
says that you use the 'maemo' string only if you have modified the  
package in some way for maemo, is this the case with that package? Or  
is in modified for ubuntu? Or is it modified for maemo and the ubuntu  
modifications have been kept?

Furthermore what is 'bmp' and how is that helpful? What is mp4v2? And  
how is that helpful? And why have both a version number _and_ a  
version control system number? Perhaps use one or the other.
>
> The problem is imho the Application manager, not the version numbers.
>
> What's the point of even displaying the version number in the  
> Application
> manager's default view? I personally don't care about the version at  
> all and
> I certainly won't remember if an application's version has been  
> updated by
> looking at the list view. Am I alone with this opinion? Why do you  
> need to
> see the version there? The update manager will gladly tell me if I  
> have an
> older version installed and if I don't, won't I just install  
> whatever the
> Application manager offers me?

Good points, but Ryan's original point is still valid and these issues  
also affect any place you have to use version numbers, not just the  
Application Manager. The string that Niels posted could be shortened  
to: 2.0.0-6maemo1

This leaves you with the version number of the upstream source, the  
version of upstream packaging, and the maemo packaged version. Here  
you have all the trackability you need with simplicity. I think the  
original request is a good one and developers/maintainers ought to  
consider revising their version strings for clarity.

Jeremiah

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: How to check SDK version?

[Jeremiah Foster]

On Oct 30, 2009, at 10:58, Graham Cobb wrote:

> On Friday 30 October 2009 08:11:37 Reshma Prasanna wrote:
>> Hi,
>> I'm new to Maemo but I'm using a PC that already has a Maemo SDK
>> installation (done by someone else). Please tell me how to find out  
>> which
>> version of the SDK is installed? i.e. Is the SDK version 5.0 alpha,  
>> 5.0
>> beta or 5.0 stable version?
>
> cat /etc/maemo_version

Is /etc/maemo_version canonical? I know that /etc/debian_version is  
not but rather one checks against which repo you are pulling down from  
in /etc/apt/sources.list. i.e. deb http://ftp.ee.debian.org/debian/  
lenny main would be an entry in the list and the version would be  
lenny in this case.

Jeremiah

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

OT (hope not too much) N900 FW

[Delfim Machado]

Hi all,
things happen when they shouldn't...

I usually do my upgrades @Nokia, but my N900 decided to "die" some  
hours ago (my mistake, played with rootfs and now he don't boot) and  
they don't work in the weekend :)

I tried NSU but the device was not found, then i tried Nokia Internet  
Tablet Software Update and he detects the mobile but asks me for the  
FW. From what i learned, i should be able to do a recover using the  
NSU or the NITSU, right?
http://www.symbian-master.com/index.php?page=Nokia_N900_RX-51_v1.2009.42.2_Available_On_NSU

Can i do something to recover it so i can play with him in the weekend  
or i must wait for monday?

Sorry the little OT

Best Regards
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Maemo5 on Beagle wiki page updated

[Dirk Behme]

Hi,

I have updated the Maemo5 on Beagle (OMAP) wiki page

http://omappedia.org/wiki/Maemo_Getting_Started

to recent status.

Feel free to update, correct and add everything I missed.

Best regards

Dirk
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Updated DevHelp files for Hildon, PyMaemo, Fremantle ecc....

[Andrea Grandi]

Hi all,

where can I find updated devhelp file to have Hildon, PyMaemo and all
Fremantle libraries help in DevHelp, under Ubuntu?

For some things I still can use normal GTK and PyGtk help, but of
course Fremantle has more libraries+bindings than a normal Linux
distribution, so I'm missing that in this moment.

Thanks for your help! :)

-- 
Andrea Grandi
email: a.grandi [AT] gmail [DOT] com
website: http://www.andreagrandi.it
PGP Key: http://www.andreagrandi.it/pgp_key.asc
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Maemo5 on Beagleboard

[Dirk Behme]

Tuomas Kulve wrote:
>> What's your state? Has anyone actually been able to do something
>> with the mouse?
> 
> No. I can use it to unblank the screen..

Yes, same here (now) :)

I was able to solve my "USB is not detected" issues by connecting a 
(powered) hub to Beagle rev C USB host port P7 (#8 in [1]). Having a 
mouse and keyboard connected to the hub while starting (powering) make 
USB work then. Pressing a keyboard key makes the screen unblank, too.

Having the powered hub connected to OTG port (#12 in [1]) doesn't work 
for me at all. It worked for Angstrom, though.

Cheers

Dirk

[1] http://elinux.org/BeagleBoard#Components

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: The issue of version strings / improving Application manager view

[Andrew Flegg]

On Fri, Oct 30, 2009 at 15:15, David Greaves  wrote:
>>
>> So, the example of 2.0.0+cvs20040908+mp4v2+bmp-0ubuntu6maemo1 would
>> just appear as 2.0.0 in the view.
>
> /me would be confused.
>
> Why is it upgrading 2.0.0 to 2.0.0 *again* ?

You know what version you've got installed of something already? I'm
talking only about the grid view, the details can show whatever
weirdity fits.

Cheers,

Andrew

-- 
Andrew Flegg -- mailto:and...@bleb.org  |  http://www.bleb.org/
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: The issue of version strings / improving Application manager view

[Luca Donaggio]

Why not simply telling "minor release update" whenever the version upgrade
is in the epoch part only?

Luca Donaggio

On Fri, Oct 30, 2009 at 4:15 PM, David Greaves  wrote:

> On Fri, 2009-10-30 at 13:20 +, Andrew Flegg wrote:
> > On Fri, Oct 30, 2009 at 12:55, Graham Cobb 
> > >
> wrote:
> > > On Friday 30 October 2009 11:44:17 Juha Kallioinen wrote:
> > >> And a perfectly good one too! :) It's useful not to change the
> upstream
> > >> package version too much so that it's easier to see that a package
> could
> > >> use updating.
> > >
> > > I agree with all Juha's points (but I would, wouldn't I!).
> >
> > Simplest solution I can see, whilst still giving the user some
> > indication of version number (3.4.1 tells you something over 0.0.1):
> > the Application Manager only shows things of the form (\d+)(\.\d+)*?
> >
> > So, the example of 2.0.0+cvs20040908+mp4v2+bmp-0ubuntu6maemo1 would
> > just appear as 2.0.0 in the view.
>
> /me would be confused.
>
> Why is it upgrading 2.0.0 to 2.0.0 *again* ?
>
> David
> (Who presumably wouldn't see the -local_bugfix1 and -local_bugfix2
> suffixes)
>
>
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: The issue of version strings / improving Application manager view

[David Greaves]

On Fri, 2009-10-30 at 13:20 +, Andrew Flegg wrote:
> On Fri, Oct 30, 2009 at 12:55, Graham Cobb  wrote:
> > On Friday 30 October 2009 11:44:17 Juha Kallioinen wrote:
> >> And a perfectly good one too! :) It's useful not to change the upstream
> >> package version too much so that it's easier to see that a package could
> >> use updating.
> >
> > I agree with all Juha's points (but I would, wouldn't I!).
> 
> Simplest solution I can see, whilst still giving the user some
> indication of version number (3.4.1 tells you something over 0.0.1):
> the Application Manager only shows things of the form (\d+)(\.\d+)*?
> 
> So, the example of 2.0.0+cvs20040908+mp4v2+bmp-0ubuntu6maemo1 would
> just appear as 2.0.0 in the view.

/me would be confused.

Why is it upgrading 2.0.0 to 2.0.0 *again* ?

David
(Who presumably wouldn't see the -local_bugfix1 and -local_bugfix2
suffixes)


___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: How to get a transparent GtkWindow (fremantle)

[Luca Donaggio]

Thanks Kimmo, somehow I haven't seen it in the manual page!
But... I found it's not necessary: the thing which was preventing the
transparency effect to work as expected was this instruction:

gdk_window_reparent(myapp->imgparamwin->window,gtk_widget_get_window(GTK_WIDGET
(myapp->mainwin)),offset,offset);

Without it I can get the transparent background just as Conny suggested, BUT
... without it the HildonAppMenu stops working: it shows up and immediately
disappear!

Luca Donaggio

2009/10/30 Kimmo Hämäläinen 

> On Fri, 2009-10-30 at 14:36 +0100, ext Luca Donaggio wrote:
> > Thanks Conny and Kimmo,
> >
> > here are my progresses:
> >
> > I'm able to draw to the GtkWindow using Cairo only if I do it in a
> > callback attached to the expose event of the window itself, but I'm
> > still getting no transparency!
> > I'm sure this is the problem with the window manager that Kimmo
> > pointed out, but I don't know how to set the override-redirect flag
> > apart from passing the correct value inside a GdkWindowAttr struct
> > when manually creating a GdkWindow with gdk_window_new(), but I'm not
> > doing this manually, so I'm lost here!
>
> gdk_window_set_override_redirect () sets it. You need to set it after
> realizing (gtk_widget_realize ()) your window but before showing it.
> gtk_widget_get_window () returns GdkWindow of your widget.
>
> -Kimmo
>
> >
> > Luca Donaggio
> >
> > 2009/10/30 Kimmo Hämäläinen 
> > On Thu, 2009-10-29 at 17:29 +0100, ext Luca Donaggio wrote:
> > > I'm trying to create a transparent, non-decorated popup
> > GtkWindow on
> > > top af my app HildonWindow and draw something on its
> > underlying
> > > GdkWindow object using cairo.
> > > All I was able to obtain so far is a black (or whatever is
> > the
> > > background colour of the selected theme) rectangle -ie it's
> > not
> > > transparent and everything I paint in its GdkWindow with
> > Cairo is not
> > > showed at all.
> >
> >
> > You may hit (at least) this hard-coded limitation:
> > http://maemo.gitorious.org/fremantle-hildon-
> > desktop/libmatchbox2/blobs/master/matchbox/core/mb-wm-
> > client.c#line173
> >
> > Currently alpha in dialogs and application windows is ignored
> > because it
> > allows for optimisations in the compositor. But if you set the
> > override-
> > redirect flag for the window, that should go around that
> > (because the
> > type of your window would be MBWMClientTypeOverride).
> >
> > -Kimmo
> >
> >
> > > Here is the code I'm using:
> > >
> > > void create_image_details(GtkWidget *callerobj,app_data_t
> > *myapp) {
> > > PangoLayout *textbuff;
> > > cairo_t *cr;
> > > gint x0, y0, r, txtwidth, txtheight;
> > >
> > > /* For the widget itself let's use a GtkWindow */
> > > if ((myapp->imgparamwin != NULL) & GTK_IS_WINDOW(myapp-
> > > >imgparamwin)) gtk_widget_destroy(myapp->imgparamwin);
> > > myapp->imgparamwin = gtk_window_new(GTK_WINDOW_POPUP);
> > > gtk_window_set_decorated(GTK_WINDOW (myapp-
> > >imgparamwin),FALSE);
> > > gtk_window_set_opacity(GTK_WINDOW (myapp-
> > >imgparamwin),0);
> > > gtk_widget_set_app_paintable(myapp->imgparamwin,TRUE);
> > > gtk_widget_realize(myapp->imgparamwin);
> > > /* gdk_window_set_back_pixmap(myapp->imgparamwin-
> > > >window,NULL,FALSE); */
> > > /* Get the Cairo context */
> > > cr = gdk_cairo_create(GDK_DRAWABLE (myapp->imgparamwin-
> > >window));
> > > textbuff = pango_cairo_create_layout(cr);
> > > pango_layout_set_markup(textbuff,myapp->imgparam,-1);
> > > pango_layout_get_pixel_size
> > (textbuff,&txtwidth,&txtheight);
> > > /* Draw a rounded rectangle */
> > >
> > > [cairo stuff is here]
> > >
> > > cairo_destroy(cr);
> > > g_object_unref(textbuff);
> > > /* Show the widget */
> > > gtk_window_resize(GTK_WINDOW (myapp-
> > >imgparamwin),txtwidth + (r *
> > > 2),txtheight + (r * 2));
> > > gtk_window_move(GTK_WINDOW (myapp->imgparamwin),30,30);
> > > gdk_window_reparent(myapp->imgparamwin->window,myapp-
> > >image-
> > > >window,30,30);
> > > gtk_widget_show_all(myapp->imgparamwin);
> > > }
> > >
> > > The window dimension after the gtk_window_resize() are
> > correct -ie the
> > > dimension of the PangoLayout containing the text to be
> > rendered, so
> > > something is definitely going on under the hood... but
> > nothing is
> > > displayed!
> > > If I add som

Re: How to get a transparent GtkWindow (fremantle)

[Kimmo Hämäläinen]

On Fri, 2009-10-30 at 14:36 +0100, ext Luca Donaggio wrote:
> Thanks Conny and Kimmo,
> 
> here are my progresses:
> 
> I'm able to draw to the GtkWindow using Cairo only if I do it in a
> callback attached to the expose event of the window itself, but I'm
> still getting no transparency!
> I'm sure this is the problem with the window manager that Kimmo
> pointed out, but I don't know how to set the override-redirect flag
> apart from passing the correct value inside a GdkWindowAttr struct
> when manually creating a GdkWindow with gdk_window_new(), but I'm not
> doing this manually, so I'm lost here!

gdk_window_set_override_redirect () sets it. You need to set it after
realizing (gtk_widget_realize ()) your window but before showing it.
gtk_widget_get_window () returns GdkWindow of your widget.

-Kimmo

> 
> Luca Donaggio
> 
> 2009/10/30 Kimmo Hämäläinen 
> On Thu, 2009-10-29 at 17:29 +0100, ext Luca Donaggio wrote:
> > I'm trying to create a transparent, non-decorated popup
> GtkWindow on
> > top af my app HildonWindow and draw something on its
> underlying
> > GdkWindow object using cairo.
> > All I was able to obtain so far is a black (or whatever is
> the
> > background colour of the selected theme) rectangle -ie it's
> not
> > transparent and everything I paint in its GdkWindow with
> Cairo is not
> > showed at all.
> 
> 
> You may hit (at least) this hard-coded limitation:
> http://maemo.gitorious.org/fremantle-hildon-
> desktop/libmatchbox2/blobs/master/matchbox/core/mb-wm-
> client.c#line173
> 
> Currently alpha in dialogs and application windows is ignored
> because it
> allows for optimisations in the compositor. But if you set the
> override-
> redirect flag for the window, that should go around that
> (because the
> type of your window would be MBWMClientTypeOverride).
> 
> -Kimmo
> 
> 
> > Here is the code I'm using:
> >
> > void create_image_details(GtkWidget *callerobj,app_data_t
> *myapp) {
> > PangoLayout *textbuff;
> > cairo_t *cr;
> > gint x0, y0, r, txtwidth, txtheight;
> >
> > /* For the widget itself let's use a GtkWindow */
> > if ((myapp->imgparamwin != NULL) & GTK_IS_WINDOW(myapp-
> > >imgparamwin)) gtk_widget_destroy(myapp->imgparamwin);
> > myapp->imgparamwin = gtk_window_new(GTK_WINDOW_POPUP);
> > gtk_window_set_decorated(GTK_WINDOW (myapp-
> >imgparamwin),FALSE);
> > gtk_window_set_opacity(GTK_WINDOW (myapp-
> >imgparamwin),0);
> > gtk_widget_set_app_paintable(myapp->imgparamwin,TRUE);
> > gtk_widget_realize(myapp->imgparamwin);
> > /* gdk_window_set_back_pixmap(myapp->imgparamwin-
> > >window,NULL,FALSE); */
> > /* Get the Cairo context */
> > cr = gdk_cairo_create(GDK_DRAWABLE (myapp->imgparamwin-
> >window));
> > textbuff = pango_cairo_create_layout(cr);
> > pango_layout_set_markup(textbuff,myapp->imgparam,-1);
> > pango_layout_get_pixel_size
> (textbuff,&txtwidth,&txtheight);
> > /* Draw a rounded rectangle */
> >
> > [cairo stuff is here]
> >
> > cairo_destroy(cr);
> > g_object_unref(textbuff);
> > /* Show the widget */
> > gtk_window_resize(GTK_WINDOW (myapp-
> >imgparamwin),txtwidth + (r *
> > 2),txtheight + (r * 2));
> > gtk_window_move(GTK_WINDOW (myapp->imgparamwin),30,30);
> > gdk_window_reparent(myapp->imgparamwin->window,myapp-
> >image-
> > >window,30,30);
> > gtk_widget_show_all(myapp->imgparamwin);
> > }
> >
> > The window dimension after the gtk_window_resize() are
> correct -ie the
> > dimension of the PangoLayout containing the text to be
> rendered, so
> > something is definitely going on under the hood... but
> nothing is
> > displayed!
> > If I add some widget to the popoup window (for example a
> GtkLabel with
> > some text in it), it's rendered correctly, but, of course
> it's not
> > transparent!
> >
> > Any help, as always, is much appreciated!
> >
> > Luca Donaggio
> 
> 
> 

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: How to get a transparent GtkWindow (fremantle)

[Cornelius Hald]

Hi Luca,

have a look at this file:
https://garage.maemo.org/plugins/scmsvn/viewcvs.php/trunk/conboy/src/fullscreenmanager.c?revision=517&root=conboy&view=markup

The creation of the overlay window is done in fullscreen_ui_create() and
the cairo drawing on the window is in on_expose_event().

This code works. It creates a small semi-transparent window which is
shown over the main window. I first clear the surface, then I draw a
semi-transparent rectangle with a rounded upper-left corner and then I
add a pixmap with an alpha channel.

I think the most important parts are:

- Setting the color map of the window.
  gtk_widget_set_colormap (widget, gdk_screen_get_rgba_colormap
(screen));

- Clearing the cairo surface.
  cairo_set_operator (ctx, CAIRO_OPERATOR_CLEAR);
  cairo_paint (ctx);


Hope that helps!
Conny


On Fri, 2009-10-30 at 14:36 +0100, Luca Donaggio wrote:
> Thanks Conny and Kimmo,
> 
> here are my progresses:
> 
> I'm able to draw to the GtkWindow using Cairo only if I do it in a
> callback attached to the expose event of the window itself, but I'm
> still getting no transparency!
> I'm sure this is the problem with the window manager that Kimmo
> pointed out, but I don't know how to set the override-redirect flag
> apart from passing the correct value inside a GdkWindowAttr struct
> when manually creating a GdkWindow with gdk_window_new(), but I'm not
> doing this manually, so I'm lost here!
> 
> Luca Donaggio
> 
> 2009/10/30 Kimmo Hämäläinen 
> On Thu, 2009-10-29 at 17:29 +0100, ext Luca Donaggio wrote:
> > I'm trying to create a transparent, non-decorated popup
> GtkWindow on
> > top af my app HildonWindow and draw something on its
> underlying
> > GdkWindow object using cairo.
> > All I was able to obtain so far is a black (or whatever is
> the
> > background colour of the selected theme) rectangle -ie it's
> not
> > transparent and everything I paint in its GdkWindow with
> Cairo is not
> > showed at all.
> 
> 
> You may hit (at least) this hard-coded limitation:
> http://maemo.gitorious.org/fremantle-hildon-
> desktop/libmatchbox2/blobs/master/matchbox/core/mb-wm-client.c#line173
> 
> Currently alpha in dialogs and application windows is ignored
> because it
> allows for optimisations in the compositor. But if you set the
> override-
> redirect flag for the window, that should go around that
> (because the
> type of your window would be MBWMClientTypeOverride).
> 
> -Kimmo
> 
> 
> > Here is the code I'm using:
> >
> > void create_image_details(GtkWidget *callerobj,app_data_t
> *myapp) {
> > PangoLayout *textbuff;
> > cairo_t *cr;
> > gint x0, y0, r, txtwidth, txtheight;
> >
> > /* For the widget itself let's use a GtkWindow */
> > if ((myapp->imgparamwin != NULL) & GTK_IS_WINDOW(myapp-
> > >imgparamwin)) gtk_widget_destroy(myapp->imgparamwin);
> > myapp->imgparamwin = gtk_window_new(GTK_WINDOW_POPUP);
> > gtk_window_set_decorated(GTK_WINDOW
> (myapp->imgparamwin),FALSE);
> > gtk_window_set_opacity(GTK_WINDOW
> (myapp->imgparamwin),0);
> > gtk_widget_set_app_paintable(myapp->imgparamwin,TRUE);
> > gtk_widget_realize(myapp->imgparamwin);
> > /* gdk_window_set_back_pixmap(myapp->imgparamwin-
> > >window,NULL,FALSE); */
> > /* Get the Cairo context */
> > cr = gdk_cairo_create(GDK_DRAWABLE
> (myapp->imgparamwin->window));
> > textbuff = pango_cairo_create_layout(cr);
> > pango_layout_set_markup(textbuff,myapp->imgparam,-1);
> >
> pango_layout_get_pixel_size(textbuff,&txtwidth,&txtheight);
> > /* Draw a rounded rectangle */
> >
> > [cairo stuff is here]
> >
> > cairo_destroy(cr);
> > g_object_unref(textbuff);
> > /* Show the widget */
> > gtk_window_resize(GTK_WINDOW
> (myapp->imgparamwin),txtwidth + (r *
> > 2),txtheight + (r * 2));
> > gtk_window_move(GTK_WINDOW (myapp->imgparamwin),30,30);
> >
> gdk_window_reparent(myapp->imgparamwin->window,myapp->image-
> > >window,30,30);
> > gtk_widget_show_all(myapp->imgparamwin);
> > }
> >
> > The window dimension after the gtk_window_resize() are
> correct -ie the
> > dimension of the PangoLayout containing the text to be
> rendered, so
> > something is definitely going on under the hood... but
> nothing is
> > displayed!
> > If I add some widget to the popoup window (for example a
> GtkLabel with
> > some 

Re: How to get a transparent GtkWindow (fremantle)

[Luca Donaggio]

Thanks Conny and Kimmo,

here are my progresses:

I'm able to draw to the GtkWindow using Cairo only if I do it in a callback
attached to the expose event of the window itself, but I'm still getting no
transparency!
I'm sure this is the problem with the window manager that Kimmo pointed out,
but I don't know how to set the override-redirect flag apart from passing
the correct value inside a GdkWindowAttr struct when manually creating a
GdkWindow with gdk_window_new(), but I'm not doing this manually, so I'm
lost here!

Luca Donaggio

2009/10/30 Kimmo Hämäläinen 

> On Thu, 2009-10-29 at 17:29 +0100, ext Luca Donaggio wrote:
> > I'm trying to create a transparent, non-decorated popup GtkWindow on
> > top af my app HildonWindow and draw something on its underlying
> > GdkWindow object using cairo.
> > All I was able to obtain so far is a black (or whatever is the
> > background colour of the selected theme) rectangle -ie it's not
> > transparent and everything I paint in its GdkWindow with Cairo is not
> > showed at all.
>
> You may hit (at least) this hard-coded limitation:
> http://maemo.gitorious.org/fremantle-hildon-
> desktop/libmatchbox2/blobs/master/matchbox/core/mb-wm-client.c#line173
>
> Currently alpha in dialogs and application windows is ignored because it
> allows for optimisations in the compositor. But if you set the override-
> redirect flag for the window, that should go around that (because the
> type of your window would be MBWMClientTypeOverride).
>
> -Kimmo
>
> > Here is the code I'm using:
> >
> > void create_image_details(GtkWidget *callerobj,app_data_t *myapp) {
> > PangoLayout *textbuff;
> > cairo_t *cr;
> > gint x0, y0, r, txtwidth, txtheight;
> >
> > /* For the widget itself let's use a GtkWindow */
> > if ((myapp->imgparamwin != NULL) & GTK_IS_WINDOW(myapp-
> > >imgparamwin)) gtk_widget_destroy(myapp->imgparamwin);
> > myapp->imgparamwin = gtk_window_new(GTK_WINDOW_POPUP);
> > gtk_window_set_decorated(GTK_WINDOW (myapp->imgparamwin),FALSE);
> > gtk_window_set_opacity(GTK_WINDOW (myapp->imgparamwin),0);
> > gtk_widget_set_app_paintable(myapp->imgparamwin,TRUE);
> > gtk_widget_realize(myapp->imgparamwin);
> > /* gdk_window_set_back_pixmap(myapp->imgparamwin-
> > >window,NULL,FALSE); */
> > /* Get the Cairo context */
> > cr = gdk_cairo_create(GDK_DRAWABLE (myapp->imgparamwin->window));
> > textbuff = pango_cairo_create_layout(cr);
> > pango_layout_set_markup(textbuff,myapp->imgparam,-1);
> > pango_layout_get_pixel_size(textbuff,&txtwidth,&txtheight);
> > /* Draw a rounded rectangle */
> >
> > [cairo stuff is here]
> >
> > cairo_destroy(cr);
> > g_object_unref(textbuff);
> > /* Show the widget */
> > gtk_window_resize(GTK_WINDOW (myapp->imgparamwin),txtwidth + (r *
> > 2),txtheight + (r * 2));
> > gtk_window_move(GTK_WINDOW (myapp->imgparamwin),30,30);
> > gdk_window_reparent(myapp->imgparamwin->window,myapp->image-
> > >window,30,30);
> > gtk_widget_show_all(myapp->imgparamwin);
> > }
> >
> > The window dimension after the gtk_window_resize() are correct -ie the
> > dimension of the PangoLayout containing the text to be rendered, so
> > something is definitely going on under the hood... but nothing is
> > displayed!
> > If I add some widget to the popoup window (for example a GtkLabel with
> > some text in it), it's rendered correctly, but, of course it's not
> > transparent!
> >
> > Any help, as always, is much appreciated!
> >
> > Luca Donaggio
>
>
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: The issue of version strings / improving Application manager view

[Andrew Flegg]

On Fri, Oct 30, 2009 at 12:55, Graham Cobb  wrote:
> On Friday 30 October 2009 11:44:17 Juha Kallioinen wrote:
>> And a perfectly good one too! :) It's useful not to change the upstream
>> package version too much so that it's easier to see that a package could
>> use updating.
>
> I agree with all Juha's points (but I would, wouldn't I!).

Simplest solution I can see, whilst still giving the user some
indication of version number (3.4.1 tells you something over 0.0.1):
the Application Manager only shows things of the form (\d+)(\.\d+)*?

So, the example of 2.0.0+cvs20040908+mp4v2+bmp-0ubuntu6maemo1 would
just appear as 2.0.0 in the view.

Cheers,

Andrew

-- 
Andrew Flegg -- mailto:and...@bleb.org  |  http://www.bleb.org/
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

maemo-optify - files < 4 kb aren't moved

[Valerio Valerio]

Hi,

from the "maemo-optify" readme[1]:

"Maemo-optify has a heuristic for selecting which files to move.  By
default, it will never move files that are less than 2kb and it will
only move directories that have the same name as the package."

Does the size of the files changed ?
An user noticed that the "supertux" game has about 1.6mb in the /usr
(15mb under /opt) , the files there are mainly a bunch of files with <
4kb (according to 'du -hs'). I'm using the upstream debian/rules (not
the best ones I've seen so far). I'll write a new rules file and put
everything directly under /opt, but I would like to dig a bit one it,
might be a bug or some special weird case.


[1] - http://maemo.gitorious.org/maemo-af/maemo-optify/blobs/master/README


Best regards,

-- 
Valério Valério

http://www.valeriovalerio.org
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: RE: Re: Maemo5 on Beagleboard

[Till Harbaum]

Hi,

> It's in the alpha patch
Found it. Unfortunately it doesn't help.

I think i need some help of an x-server expert here. The problems with my
touchscreen are related to this:
(**) eGalax Inc. USB TouchController: Device: "/dev/input/event3"
(**) eGalax Inc. USB TouchController: Calibration factors: 200 3910 3761 180 0 0
(II) eGalax Inc. USB TouchController: Found x and y absolute axes

The calibration factors are completely nonsense and in fact the behaviour
of the touch makes sense when taking these numbers into account. But my touch 
needs
100 1900 100 1900 0 0

Where do these default numbers come from? Adding some section like described
here http://www.conan.de/touchscreen/evtouch.html does not have any impact 
on these wrong numbers.

Till

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: The issue of version strings / improving Application manager view

[Graham Cobb]

On Friday 30 October 2009 11:44:17 Juha Kallioinen wrote:
> And a perfectly good one too! :) It's useful not to change the upstream
> package version too much so that it's easier to see that a package could
> use updating.

I agree with all Juha's points (but I would, wouldn't I!).  

Maybe we need to decouple the package versions (which are very useful to link 
to the upstream versions, and have to be monotonically increasing to make 
sure builds and installs work) from user-visible versions.  If we had a 
separate field for the user-visible version (like we do for name) I would 
probably use something like: "2.7 2009/10/30" instead of the long version 
string I use in the package.

Graham
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Tentative: UX meets Code hackfest in December @ Barcelona

[Quim Gil]

Re-post made at http://talk.maemo.org/showthread.php?t=33719 - please
reply there if you are interested in order to track the feedback in one
place.


Hi, an idea we are cooking these days:

Maemo community developers and user experience professionals meet 3 days
with 3 main goals:

- Improve the usability and visual appeal of great Maemo apps.

- Improve the UX documentation for Maemo developers.

- Get a critical mass of people interested in pushing forward UX meets
Code activities online and face to face.

Idea: December 4-6, Barcelona. About 50 people invited.

We are lining up the right UX professionals from the Maemo team, Forum
Nokia and developer partners.

Who is interested?

Please provide in this thread

- Your maemo.org profile making sure that there one can find info about
or links to your current projects and your interests in Code or UX.

- If you are more into Code, a link to the app hosted in maemo.org,
either under Fremantle packages or OS2008 Downloads.

- If you are more into UX, a link to wherever your work can be seen.

If we have a good response we will confirm the event. Forward this to
your colleagues working on great stuff!

For budgeting and also practical purposes we will keep the number of
participants around 50 people even if we get more requests. The criteria
will be defined more or less by fast response, travel costs, community
involvement and of course Maemo excellence in Code or UX.

General feedback about the hackfest itself is also welcome. We will
share here more news.

-- 
Quim Gil
open source advocate
Maemo Devices @ Nokia
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: maemo-developers Digest, Vol 54, Issue 30

[Doug Steel]

> Message: 16
> Date: Thu, 29 Oct 2009 14:16:59 +0100 (MET)
> From: "Till Harbaum" 
> Subject: Re: Re: Maemo5 on Beagle
>
> For me currently a mystery is the source of the default video mode the device
> comes up with: It definitely uses the panel driver in panel-generic. But this
> only contains a single mode of 640x480 pixels. Yet the device comes up with
> 800x600 pixels. Where does this mode come from?

Hi Till

I think the 800x600 mode comes from the TI X-loader bootargs, interrupt the boot
and type
  printenv
to see what mode is in the bootargs line.

I tweaked mine using
  setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw
rootfstype=ext3 rootwait omapfb.mode=dvi:640x480mr...@60
  saveenv

X seems to pick this up and you can check by looking in /tmp/Xorg.0.log

However I still have a blank screen to look at, so I can't confirm
this actually does what it claims

Cheers
Doug

PS take a copy of your old bootargs so you can re-instate it should
things go wrong...
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

RE: Re: Maemo5 on Beagleboard

[tero.kojo]

> -Original Message-
> From: maemo-developers-boun...@maemo.org 
> [mailto:maemo-developers-boun...@maemo.org] On Behalf Of ext 
> Till Harbaum
> Sent: 30 October, 2009 13:27
> To: Tuomas Kulve; Till Harbaum
> Cc: maemo-developers@maemo.org
> Subject: Re: Re: Maemo5 on Beagleboard
> 
> Hi,
> 
> Thomas Kulve wrote:
> > I don't get the cursor with tuxpaint. Did you modify the 
> libmatchbox2 
> > and rebuild hildon-desktop?
> Nope, i didn't change anything. If you just start tuxpaint 
> without touching the mouse at all, you should see the cursor 
> in the screen center. Once you touch it, it nearly immedtialy 
> jumps of to the border.
> 
> The mouse really behaves weird and nearly immediately jumps 
> into one of the screen corners/borders. Have you ever used a 
> mouse with wrong protocol settings (e.g. ps2 with an imps2 mouse)?
> The current situation looks pretty much the same. Perhaps it 
> is even something like that. I know the alpha port used a 
> seperate xorg.conf which had to be invoked this way:
> -:~# Xorg -config /etc/xorg.conf-beagle &
> 
> I don't have a alpha setup anymore. Has one of you access to 
> this old xorg.conf-beagle?
> If yes, can you please post it so we can use it as a replacement?

It's in the alpha patch
http://maemo-beagle.garage.maemo.org/files/maemo5-alpha/event-diff.patch
Last file in the patch, easy to extrack manually, as it's a new file.

Tero // waiting for the post to bring a beagle C2/3...

> > No. I can use it to unblank the screen..
> Me too :-)

I can do that on a B5, but I don't have the image that should appear :-)

> Till
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers
> 
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: The issue of version strings / improving Application manager view

[Juha Kallioinen]

ext Niels Breet wrote:
> On Thu, October 29, 2009 09:01, Martin Grimme wrote:
>> Hi,
>>
>>
>> hmm, what's so bad about a simple date for a version number? Ubuntu does
>> it, (Open)Solaris does it, and I started doing it, too, because I found it
>> less confusing than having version numbers such as e.g. 0.96.5.
> 
> Sane version numbers should at least not look like this:
> 2.0.0+cvs20040908+mp4v2+bmp-0ubuntu6maemo1
> 
> And yes, this is an actual package version number ;)

And a perfectly good one too! :) It's useful not to change the upstream 
package version too much so that it's easier to see that a package could use 
updating.

The problem is imho the Application manager, not the version numbers.

What's the point of even displaying the version number in the Application 
manager's default view? I personally don't care about the version at all and 
I certainly won't remember if an application's version has been updated by 
looking at the list view. Am I alone with this opinion? Why do you need to 
see the version there? The update manager will gladly tell me if I have an 
older version installed and if I don't, won't I just install whatever the 
Application manager offers me?

The package version can anyways be found from the package details page, 
where there's more space available for it too.

A much more interesting bit of data instead of the package version to be 
shown by default might be the date when the package was uploaded. Also the 
Application manager could use a 'show new packages' view.

But these of course require changes to the Application manager and maybe 
even to apt/dpkg database to be able to show the package's date and are more 
difficult to implement than just making nicer version numbers.

Maybe a nice version number could really just be the date the package was 
created. That would fulfill my first wish, but we'd lose the upstream 
version trackability :)

Juha


-- 
Juha Kallioinen
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Re: Maemo5 on Beagleboard

[Till Harbaum]

Hi,

Thomas Kulve wrote:
> I don't get the cursor with tuxpaint. Did you modify the libmatchbox2
> and rebuild hildon-desktop?
Nope, i didn't change anything. If you just start tuxpaint without touching the
mouse at all, you should see the cursor in the screen center. Once you 
touch it, it nearly immedtialy jumps of to the border.

The mouse really behaves weird and nearly
immediately jumps into one of the screen corners/borders. Have you ever
used a mouse with wrong protocol settings (e.g. ps2 with an imps2 mouse)?
The current situation looks pretty much the same. Perhaps it is even something
like that. I know the alpha port used a seperate xorg.conf which had to be 
invoked
this way:
-:~# Xorg -config /etc/xorg.conf-beagle &

I don't have a alpha setup anymore. Has one of you access to this old 
xorg.conf-beagle?
If yes, can you please post it so we can use it as a replacement?

> No. I can use it to unblank the screen..
Me too :-)

Till
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Maemo5 on Beagleboard

[Tuomas Kulve]

Till Harbaum wrote:

> tuxpaint. Starting tuxpaint from the console immediately gives you a 
> visible mouse pointer. So this is a simple way to actually see what
> your inout devices are doing. 

I don't get the cursor with tuxpaint. Did you modify the libmatchbox2
and rebuild hildon-desktop?

> What's your state? Has anyone actually been able to do something
> with the mouse?

No. I can use it to unblank the screen..

-- 
Tuomas

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: How to check SDK version?

[Graham Cobb]

On Friday 30 October 2009 08:11:37 Reshma Prasanna wrote:
> Hi,
> I'm new to Maemo but I'm using a PC that already has a Maemo SDK
> installation (done by someone else). Please tell me how to find out which
> version of the SDK is installed? i.e. Is the SDK version 5.0 alpha, 5.0
> beta or 5.0 stable version?

cat /etc/maemo_version

The final version is "5.0", the beta is "5.0-beta".

Graham
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Maemo5 on Beagleboard

[Till Harbaum]

Hi,

here's my current status:

The board is booting and i get a 800x600 image (on my 800x480 display :-( )
USB works, but neither touchscreen nor mouse are really doing what 
i expect them to do. I am able to establish a WLAN connection to my home
network. In order to make this work three things have to be done:

1) Install everything necessary to use our particular WLAN stick
(e.g. incl. wpa_supplicant if your are using wpa in your home network
as in my case)

2) Change in /etc/udhcpc/default.bound
  RESOLV_CONF="/var/run/resolv.conf"
to
  RESOLV_CONF="/etc/resolv.conf"

in order to make udhcp change the main resolv.conf as we
are not running a local name server

3) Copy the sources.list used to build the rootfs into the
 rootfs at /etc/apt

You should now be able to do such things like "apt-get update" and the
like.

Now for the problem: I haven't yet been able to work with the mouse 
or the touchscreen in a useful manner. The most useful tool i found 
so far to test the mouse/touchscreen input is "tuxpaint". If you have a 
working network connection as stated above you can just apt-get install
tuxpaint. Starting tuxpaint from the console immediately gives you a 
visible mouse pointer. So this is a simple way to actually see what
your inout devices are doing. 

Sometimes (e.g. if you rebooted while tuxpaint was running, it won't
restart as it thinks it's already running. In that case delete the file
/media/mmc1/tuxpaint/lockfile.dat

What's your state? Has anyone actually been able to do something
with the mouse?

Till
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

How to check SDK version?

[Reshma Prasanna]

Hi,
I'm new to Maemo but I'm using a PC that already has a Maemo SDK installation 
(done by someone else).
Please tell me how to find out which version of the SDK is installed? i.e. Is 
the SDK version 5.0 alpha, 5.0 beta or 5.0 stable version?

Thanks & regards!!
Reshma.
SASKEN BUSINESS DISCLAIMER
-
This message may contain confidential, proprietary or legally privileged 
information. In 
case you are not the original intended Recipient of the message, you must not, 
directly or 
indirectly, use, Disclose, distribute, print, or copy any part of this message 
and you are 
requested to delete it and inform the sender. Any views expressed in this 
message are 
those of the individual sender unless otherwise stated. Nothing contained in 
this message 
shall be construed as an offer or acceptance of any offer by Sasken 
Communication 
Technologies Limited ("Sasken") unless sent with that express intent and with 
due 
authority of Sasken. Sasken has taken enough precautions to prevent the spread 
of 
viruses. However the company accepts no liability for any damage caused by any 
virus 
transmitted by this email
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Disable portrait support for dialog with Hildon

[Cornelius Hald]

On Fri, 2009-10-30 at 09:56 +0200, Kimmo Hämäläinen wrote:
> I guess it's not possible via libhildon API right now (libhildon dudes
> can (un)confirm), but here is an example of how to do it directly with
> GDK.
> http://maemo.gitorious.org/fremantle-hildon-desktop/hildon-desktop/blobs/master/tests/test-portrait-win.c#line29

Thanks Kimmo, I'll give it a try!


___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Disable portrait support for dialog with Hildon

[Kimmo Hämäläinen]

On Fri, 2009-10-30 at 08:45 +0100, ext Cornelius Hald wrote:
> On Fri, 2009-10-30 at 09:39 +0200, Kimmo Hämäläinen wrote:
> > > Try with a 0 instead of ~HILDON_PORTRAIT_MODE_SUPPORT.
> > 
> > The problem here seems to be that passing 0 will cause deletion of the
> > property. That means that since it's missing from the window, it is
> > inherited from the parent window. You would need to keep the SUPPORT
> > property but set the value to 0, to explicitly tell that portrait is not
> > supported and should not be inherited from the parent.
> 
> That sounds reasonable, but can I do that with the Hildon API or do I
> have to set X atoms manually?

I guess it's not possible via libhildon API right now (libhildon dudes
can (un)confirm), but here is an example of how to do it directly with
GDK.
http://maemo.gitorious.org/fremantle-hildon-desktop/hildon-desktop/blobs/master/tests/test-portrait-win.c#line29

-Kimmo

> Thanks!
> Conny
> 
> 

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Disable portrait support for dialog with Hildon

[Cornelius Hald]

On Fri, 2009-10-30 at 09:39 +0200, Kimmo Hämäläinen wrote:
> > Try with a 0 instead of ~HILDON_PORTRAIT_MODE_SUPPORT.
> 
> The problem here seems to be that passing 0 will cause deletion of the
> property. That means that since it's missing from the window, it is
> inherited from the parent window. You would need to keep the SUPPORT
> property but set the value to 0, to explicitly tell that portrait is not
> supported and should not be inherited from the parent.

That sounds reasonable, but can I do that with the Hildon API or do I
have to set X atoms manually?

Thanks!
Conny


___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Disable portrait support for dialog with Hildon

[Kimmo Hämäläinen]

On Thu, 2009-10-29 at 17:31 +0100, ext Piñeiro wrote:
> From: Cornelius Hald 
> 
> > the main window of my app supports portrait mode. Now I have a settings
> > dialog which does not support portrait mode but it inherits those flags
> > from the main window.
> 
> So you'll have the main window in portrait mode, and there is a
> possibility that a dialog in non-portrait mode appear?
> 
> I'm not a expert in usability, but this would be confusing for me, and
> it would force me to rotate 90 degrees the device in order to read
> properly the dialog.
> 
> There isn't any possibility to support the portrait mode in the
> dialog?
> 
> > How can I remove the flags from the dialog window?
> > 
> > I tried the following, but it does not work:
> > 
> > hildon_gtk_window_set_portrait_flags (
> >GTK_WINDOW (dialog), ~HILDON_PORTRAIT_MODE_SUPPORT);
> 
> Try with a 0 instead of ~HILDON_PORTRAIT_MODE_SUPPORT.

The problem here seems to be that passing 0 will cause deletion of the
property. That means that since it's missing from the window, it is
inherited from the parent window. You would need to keep the SUPPORT
property but set the value to 0, to explicitly tell that portrait is not
supported and should not be inherited from the parent.

-Kimmo

> 
> ===
> API (apinhe...@igalia.com)
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: How to get a transparent GtkWindow (fremantle)

[Kimmo Hämäläinen]

On Thu, 2009-10-29 at 17:29 +0100, ext Luca Donaggio wrote:
> I'm trying to create a transparent, non-decorated popup GtkWindow on
> top af my app HildonWindow and draw something on its underlying
> GdkWindow object using cairo.
> All I was able to obtain so far is a black (or whatever is the
> background colour of the selected theme) rectangle -ie it's not
> transparent and everything I paint in its GdkWindow with Cairo is not
> showed at all.

You may hit (at least) this hard-coded limitation:
http://maemo.gitorious.org/fremantle-hildon-
desktop/libmatchbox2/blobs/master/matchbox/core/mb-wm-client.c#line173

Currently alpha in dialogs and application windows is ignored because it
allows for optimisations in the compositor. But if you set the override-
redirect flag for the window, that should go around that (because the
type of your window would be MBWMClientTypeOverride).

-Kimmo

> Here is the code I'm using:
> 
> void create_image_details(GtkWidget *callerobj,app_data_t *myapp) {
> PangoLayout *textbuff;
> cairo_t *cr;
> gint x0, y0, r, txtwidth, txtheight;
> 
> /* For the widget itself let's use a GtkWindow */
> if ((myapp->imgparamwin != NULL) & GTK_IS_WINDOW(myapp-
> >imgparamwin)) gtk_widget_destroy(myapp->imgparamwin);
> myapp->imgparamwin = gtk_window_new(GTK_WINDOW_POPUP);
> gtk_window_set_decorated(GTK_WINDOW (myapp->imgparamwin),FALSE);
> gtk_window_set_opacity(GTK_WINDOW (myapp->imgparamwin),0);
> gtk_widget_set_app_paintable(myapp->imgparamwin,TRUE);
> gtk_widget_realize(myapp->imgparamwin);
> /* gdk_window_set_back_pixmap(myapp->imgparamwin-
> >window,NULL,FALSE); */
> /* Get the Cairo context */
> cr = gdk_cairo_create(GDK_DRAWABLE (myapp->imgparamwin->window));
> textbuff = pango_cairo_create_layout(cr);
> pango_layout_set_markup(textbuff,myapp->imgparam,-1);
> pango_layout_get_pixel_size(textbuff,&txtwidth,&txtheight);
> /* Draw a rounded rectangle */
> 
> [cairo stuff is here]
> 
> cairo_destroy(cr);
> g_object_unref(textbuff);
> /* Show the widget */
> gtk_window_resize(GTK_WINDOW (myapp->imgparamwin),txtwidth + (r *
> 2),txtheight + (r * 2));
> gtk_window_move(GTK_WINDOW (myapp->imgparamwin),30,30);
> gdk_window_reparent(myapp->imgparamwin->window,myapp->image-
> >window,30,30);
> gtk_widget_show_all(myapp->imgparamwin);
> }
> 
> The window dimension after the gtk_window_resize() are correct -ie the
> dimension of the PangoLayout containing the text to be rendered, so
> something is definitely going on under the hood... but nothing is
> displayed!
> If I add some widget to the popoup window (for example a GtkLabel with
> some text in it), it's rendered correctly, but, of course it's not
> transparent!
> 
> Any help, as always, is much appreciated!
> 
> Luca Donaggio

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers