Re: [platform-swt-dev] SWT.EMBEDDABLE on gtk is not reusable

[Joonas Koivunen <joonas.koivunen@xxxxxxxxx>]

2011/4/15 Silenio Quarti <Silenio_Quarti@xxxxxxxxxx>
>
> Sorry about the state of the web site.

If you help me with the below ones I can send a patch for that cvs
page :) It'd be great to have up-to-date info so that this first step
towards patch wouldnt be so hard. I also tried asking #eclipse @
freenode.net, but it'd seem that swt devs don't irc, at least on my
timezone.

> The task "replace.32.to.64" is in "org.eclipse.swt/tasks/build.xml now along with other tasks to build the native libraries, etc.

Aah, I couldn't read the ".../tasks/..", well. I'll reply to this if I
can get it up and running, otherwise the questions below still stand.

> Just install the SWT tools plugin. See
>
> http://www.eclipse.org/swt/jnigen.php
>
> The tools plugin is only necessary if you have new natives. It auto generates the C code for OS.java.

I've got the jnigen installed ok, could you give me the most important
ant targets I need when I:
 - add new native function
 - want to develop on 64-bit linux-gtk?

The little I understood from buildFragment et al was that I might need
to configure some ant/build properties beforehand, but I do not have
them right now (still at work), nor could I immediatedly see what
values should which property get (or are those automatically
generated).

Could you shed some light on the required props and the relevant build targets?

> I do not know how to get a copy of the whole CVS history. You could put the code you checkout from the eclipse repo into a local CVS to speed up things, but you would not have the whole history.
>
> Silenio
>
>
> From:
> Joonas Koivunen <joonas.koivunen@xxxxxxxxx>
> To: "Eclipse Platform SWT component developers list." <platform-swt-dev@xxxxxxxxxxx>
> Date: 04/15/2011 02:26 PM
> Subject: Re: [platform-swt-dev] SWT.EMBEDDABLE on gtk is not reusable
> Sent by: platform-swt-dev-bounces@xxxxxxxxxxx
> ________________________________
>
>
> 2011/4/15 Silenio Quarti <Silenio_Quarti@xxxxxxxxxx>
> >
> > I believe you are on the right direction. Please, once you have something implemented, attach a patch to the bug report and will review it. Thanks!
>
> Great. Will attach the patch to issue; however I'm having a bit of
> trouble with the dev environment setup.. I wonder if swt homepage
> about fixing bugs is anywhere current or am I just failing at it? I
> just checked out the latest:
>  - o.e.swt
> - o.e.swt.examples
> - o.e.swt.gtk.linux.x86_64
> - o.e.swt.tools
>
> ... just like in http://eclipse.org/swt/fixbugs.php with the extra
> step from FAQs. There's no longer any "replace.32.to.64" and so how to
> get a workable setup is not quite clear.
>
> I'm not quite a fan of cvs but I was able to piece together that a lot
> of things changed when o.e.swt/buildFragment.xml was introduced;
> perhaps a website update was forgotten?
>
> Is it be possible to get a copy of the whole cvs (with history) for
> the swt projects? For me, the anon cvs server is really slow, so I
> can't really work on history through eclipse or the web ui.
>
> > I am not sure there is any way to make the client centered using GtkSocket. If I am not mistaken the client is always as big as the socket.
>
> Oki, thanks for this one; I'll look into client code then.
>
> > Let's keep the technical discussion on the bug.
> >
> > Silenio
> >
> >
> > From: Joonas Koivunen <joonas.koivunen@xxxxxxxxx>
> > To: platform-swt-dev@xxxxxxxxxxx
> > Date: 04/13/2011 12:08 PM
> > Subject: [platform-swt-dev] SWT.EMBEDDABLE on gtk is not reusable
> > Sent by: platform-swt-dev-bounces@xxxxxxxxxxx
> > ________________________________
> >
> >
> > Hi there!
> >
> > I made a bug about this earlier [1] and I'd be interested in
> > implementing a fix. Short summary is that the GtkWidget backing the
> > Composite gets disposed (without Composite getting disposed) when the
> > XEmbed client goes away after being attached.
> >
> > I tried to look around for required blocks but could someone verify
> > I'm not going to the entirely wrong way? For example, are all signals
> > defined in Widget.java for consistency or should the socket signals be
> > in for example Composite as it is the first subclass of widget capable
> > of receiving one.
> >
> > Also, not sure if this is a feature of XEmbed and/or Win32 but under
> > windows, if you have a subwindow (WS_CHILD and maximized I believe) on
> > your SWT.EMBEDDABLE composite it stays centered and grows from there
> > whereas in linux (gtk) the embedded component is anchored to the left
> > top corner, expanding towards right and bottom. Any ideas how I could
> > replicate the windows behaviour on gtk?
> >
> > 1 = https://bugs.eclipse.org/bugs/show_bug.cgi?id=342253
> >
> > --
> > -- Joonas Koivunen
> > _______________________________________________
> > platform-swt-dev mailing list
> > platform-swt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/platform-swt-dev
> >
> >
> >
> >
> > _______________________________________________
> > platform-swt-dev mailing list
> > platform-swt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/platform-swt-dev
> >
>
>
>
> --
> -- Joonas Koivunen
> _______________________________________________
> platform-swt-dev mailing list
> platform-swt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/platform-swt-dev
>
>
>
> _______________________________________________
> platform-swt-dev mailing list
> platform-swt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/platform-swt-dev
>



--
-- Joonas Koivunen