It appers that GtkFixed is not really designed for stacking widgets as
it does not have
a concept of a z-axis. What gets drawn on top is purely a matter of what
child comes last when drawing, and a similar story is with input.
If you need to stack things, how is this best accomplished?
Imagine
On 5/11/06, Sean Kelley [EMAIL PROTECTED] wrote:
It appers that GtkFixed is not really designed for stacking widgets as
it does not have
a concept of a z-axis. What gets drawn on top is purely a matter of what
child comes last when drawing, and a similar story is with input.
GTK does not have
I saw this question asked elsewhere but couldn't find an answer for it.
I've got a window that contains:
window
+vbox
+menubar
+toolbar
+frame
+drawing_area
The frame is packed to expand and fill, the menubar and toolbar are not.
During
Hi,
I would like to write the gnome help for a little application that I'm
developing, but I can't find any tutorials.
At developer.gnome.org I only found routines for displaying help, but... how
should I write the help? Is it XML or HTML?
Thanks in advance.
Johan Dahlin wrote:
Over the last couple of weeks Henrique Romano and I have been working on
GtkBuilder, a UI constructor intended for inclusion in GTK+.
I'd like to discuss the API and some of the decisions before making the
code available for public review.
I went ahead and attached
On 5/11/06, Yevgen Muntyan [EMAIL PROTECTED] wrote:
Why remove custom properties? They are still needed by applications,
Out of curiosity, for what kind of functionality do _applications_ use
custom properties for? I can understand if they are used in creation
of the widgets by the loading
On Thu, 11 May 2006, Yevgen Muntyan wrote:
Johan Dahlin wrote:
Over the last couple of weeks Henrique Romano and I have been working on
GtkBuilder, a UI constructor intended for inclusion in GTK+.
I'd like to discuss the API and some of the decisions before making the
code available
On Wed, 2006-05-10 at 11:51 -0300, Johan Dahlin wrote:
We've made a couple of important decisions:
* GMarkup based parser which parses and creates the object tree in one step
go instead of saprving a whole tree in memory.
* breaking xml format compatibility with libglade
* not supporting
On Mon, 8 May 2006, Paolo Maggi wrote:
Hi,
Adding a specific print current selection feature should be quite
easy, although it will require some work to implement the win32 side i
think. However, how do you propose a generic mechanism for this would
work? (That also would work in
On Wed, 10 May 2006, John (J5) Palmieri wrote:
I'm implementing the preview code in gtkprint. I have decided to use an
external helper (default is evince) to do print preview. The idea was
to write out to a pdf in /tmp and launch the external helper when the
user hits the preview button.
On Mon, 2006-05-08 at 15:43 -0400, John (J5) Palmieri wrote:
Larry Ewing caught me on irc this morning to ask why an element in the
print dialog notebook widget (namely the printer list) affect the tabs
in the notebook itself. I agree with him that it can be confusing and
the general
o first of all, GtkBuilder GtkBuildable is a nice api and seemingly
covers
the api that in libglade allowed you to provide a constructor
function and
a build_children function... this will be important for people to
port any
custom libglade extentions that were using these
Over the last couple of weeks Henrique Romano and I have been working on
GtkBuilder, a UI constructor intended for inclusion in GTK+.
I'd like to discuss the API and some of the decisions before making the
code available for public review.
I went ahead and attached the patch to
On Tue, 2006-05-09 at 13:39 +0200, Christian Persch wrote:
Hi,
Larry Ewing caught me on irc this morning to ask why an element in the
print dialog notebook widget (namely the printer list) affect the tabs
in the notebook itself. I agree with him that it can be confusing and
the general
Behdad Esfahbod wrote:
On Thu, 11 May 2006, Yevgen Muntyan wrote:
Johan Dahlin wrote:
Over the last couple of weeks Henrique Romano and I have been working on
GtkBuilder, a UI constructor intended for inclusion in GTK+.
I'd like to discuss the API and some of the decisions before making
Kalle Vahlman wrote:
On 5/11/06, Yevgen Muntyan [EMAIL PROTECTED] wrote:
Why remove custom properties? They are still needed by applications,
Out of curiosity, for what kind of functionality do _applications_ use
custom properties for? I can understand if they are used in creation
of the
Yevgen Muntyan wrote:
Johan Dahlin wrote:
Over the last couple of weeks Henrique Romano and I have been working on
GtkBuilder, a UI constructor intended for inclusion in GTK+.
I'd like to discuss the API and some of the decisions before making the
code available for public review.
I
Johan Dahlin wrote:
o My real concern is about supporting menus and toolbars built by
UIManager.
- Is the motivation here only a time-to-market thing ?
- If so, do you have any plan or stratagy to take baby-steps and
eventually get
all the ui building code into the IBuildable ?
Morten Welinder wrote:
When Glade is used with a recent gtk+, it will write lots of
properties that old gtk+ will not understand. Now if those
properties were non-default that is unavoidable, but it is
irritating that one cannot readily edit a glade file on a
new system without hand-patching
Yevgen Muntyan wrote:
Johan Dahlin wrote:
o My real concern is about supporting menus and toolbars built by
UIManager.
- Is the motivation here only a time-to-market thing ?
- If so, do you have any plan or stratagy to take baby-steps and
eventually get
all the ui building code
[snip]
There should be only one obvious way of doing a specific task.
GtkUIManager is the currently the obvious way of creating menus and
toolbars
Here you go, python programmer in action :)
Seriously speaking, GtkUIManager is not and may not be perfect. The
single fact that it
Damon Chaplin wrote:
On Wed, 2006-05-10 at 11:51 -0300, Johan Dahlin wrote:
We've made a couple of important decisions:
* GMarkup based parser which parses and creates the object tree in one step
go instead of saprving a whole tree in memory.
* breaking xml format compatibility with
I never claimed GtkUIManager was perfect. I just said it was the obvious way
of creating menus and toolbars. It might be overkill in smaller
applications, but if they use gtkbuilder they won't even notice.
Johan
Probably I've missed something but can someone give a link where a decision to
It'll be fairly easy to add support for this in the signal tag,
so you can specify the data argument. It would require two attributes
one for the data and one for the type, then you'd do:
signal name=activated handler=quit_cb data=window1
data-type=GObject/
void quit_cb (GtkAction
Damon Chaplin wrote:
On Wed, 2006-05-10 at 11:51 -0300, Johan Dahlin wrote:
We've made a couple of important decisions:
* GMarkup based parser which parses and creates the object tree in one step
go instead of saprving a whole tree in memory.
* breaking xml format compatibility with
Johan Dahlin wrote:
Over the last couple of weeks Henrique Romano and I have been working on
GtkBuilder, a UI constructor intended for inclusion in GTK+.
I'd like to discuss the API and some of the decisions before making the
code available for public review.
I went ahead and attached the
On Thu, 2006-05-11 at 09:47 -0500, Yevgen Muntyan wrote:
Johan Dahlin wrote:
o My real concern is about supporting menus and toolbars built by
UIManager.
- Is the motivation here only a time-to-market thing ?
- If so, do you have any plan or stratagy to take baby-steps and
On Wed, 2006-05-10 at 16:51 -0500, Federico Mena Quintero wrote:
On Wed, 2006-05-10 at 17:42 -0400, John (J5) Palmieri wrote:
I'm implementing the preview code in gtkprint. I have decided to use an
external helper (default is evince) to do print preview. The idea was
to write out to a pdf
Alexander Larsson wrote:
I think the best way to do this is to rely on an external helper. For a
couple of reasons:
* Running something as complicated as a document viewer in the same
process as the application scares me for stability reasons. Its easy for
a bug in the viewer to bring the whole
On 5/11/06, Alexander Larsson [EMAIL PROTECTED] wrote:
On unix we could use evince (or another pdf viewer of your choice), on
OSX we could use preview.app, and on Windows we could generate a .emf
file (easy with cairo) and use the emf viewer that ships with windows.
So what happens if you try
On Thu, 2006-05-11 at 10:23 -0400, Jody Goldberg wrote:
On Thu, May 11, 2006 at 09:19:57AM -0500, Norm Jacobs wrote:
why not put the printers (+ status
and location if you like) in a dropdown list?
That list can get very big. Whether it is in a dropdown or a list
we should only show a
On Thu, 2006-05-11 at 12:29 -0500, Travis Watkins wrote:
On 5/11/06, Alexander Larsson [EMAIL PROTECTED] wrote:
On unix we could use evince (or another pdf viewer of your choice), on
OSX we could use preview.app, and on Windows we could generate a .emf
file (easy with cairo) and use the emf
Having most recently used shown somewhere would be nice though I am not
sure I like having a 'more' button. What do you show when there were no
printers ever used? One of the nice thing about the current structure
is you can search by typing in a printer name and you can sort. What
might be
Dan Winship wrote:
Johan Dahlin wrote:
Over the last couple of weeks Henrique Romano and I have been working on
GtkBuilder, a UI constructor intended for inclusion in GTK+.
I'd like to discuss the API and some of the decisions before making the
code available for public review.
I went
Owen Taylor wrote:
It's, err, wrong to claim that another piece of soft is perfect, and
make this piece of soft perfect assuming that's perfect,
and say is that's not perfect, complain about it, but this piece of
soft will still assume that piece of soft is perfect.
Are we living in ideal
On Thu, 2006-05-11 at 15:55 -0500, Yevgen Muntyan wrote:
Owen Taylor wrote:
It's, err, wrong to claim that another piece of soft is perfect, and
make this piece of soft perfect assuming that's perfect,
and say is that's not perfect, complain about it, but this piece of
soft will still
36 matches
Mail list logo
