Connecting GTK application to a database

2010-02-23 Thread sruti
Hi,
Can somebody help me with connecting a gtk interface with a backend
database, say, Posgres? How does one embed SQL queries in the C code.?

Thanks in advance
Sruti
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Re: Connecting GTK application to a database

2010-02-23 Thread Tor Lillqvist
 Can somebody help me with connecting a gtk interface with a backend
 database, say, Posgres? How does one embed SQL queries in the C code.?

GTK+ has nothing to do with that.

--tml
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Re: Connecting GTK application to a database

2010-02-23 Thread Vivien Malerba
On 23 February 2010 17:16, Tor Lillqvist t...@iki.fi wrote:
 Can somebody help me with connecting a gtk interface with a backend
 database, say, Posgres? How does one embed SQL queries in the C code.?


The Libgda library provides an uniform access to databases using a
GObject oriented API. See http://www.gnome-db.org.

Note that the stable version only contains non UI features and the
unstable (read: being worked on) features some GTK+ based UI widgets.

Vivien
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Re: Connecting GTK application to a database

2010-02-23 Thread Basile Starynkevitch

sruti wrote:

Hi,
Can somebody help me with connecting a gtk interface with a backend
database, say, Posgres? How does one embed SQL queries in the C code.?


I would believe that you handle this issue as in any C program. GTK is 
not relevant (except that you probably don't want to issue SQL queries 
from several threads).


So, first learn to embed SQL inside a plain (command line) simple program.

There might be perhaps libraries related to GTK to help about that. I 
don't know them.


Regards.


--
Basile Starynkevitch http://starynkevitch.net/Basile/
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


putting combobox in toolbar

2010-02-23 Thread walter tallent
Hi.
I'm trying to add a combobox to my toolbar.  I get as far as embedding it into 
a GtkToolButton with gtk_tool_button_set_label_widget but it seems the button 
itself is intercepting the mouse clicks and I can't come up with what I need to 
do to get the clicks through to the combobox so it will open up and show me my 
options.
I've tried playing with the clicked signal, but there's something I'm 
missing.  I can't find any references to using this function on google or in 
the list search box.
Please.  Help.
thanks
walter



  
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


GTK+ 2.19.6 released

2010-02-23 Thread Matthias Clasen
GTK+ 2.19.6 is now available for download at:

 ftp://ftp.gtk.org/pub/gtk/2.19/
 http://download.gnome.org/sources/gtk+/2.19/

md5 sums:
524021c965a0e1a4ebadd58c576926a5  gtk+-2.19.6.tar.bz2
1311c99903e4dd28bf42a352b05788db  gtk+-2.19.6.tar.gz

sha1 sums:
0a4267fe2f3022f39fdf1a2a3817e520c0ff  gtk+-2.19.6.tar.bz2
0e1d0329f2aad4d7aa9fd127c9b393db79dc6746  gtk+-2.19.6.tar.gz

This is a development release leading up to GTK+ 2.20.

Notes:

 * This is an unstable development release.
   It has had only little testing and there are unfinished
   features and plenty of bugs in this release. It should
   definitively not be used in production.

 * Installing this version will overwrite your existing
   copy of GTK+ 2.18. If you have problems, you'll need
   to reinstall GTK+ 2.18.

 * GTK+ 2.20 will be source and binary compatible with
   the GTK+ 2.18 series; however, the new API additions
   are not yet finalized, so there may be incompatibilities
   between this release and the final 2.20 release.

 * Bugs should be reported to http://bugzilla.gnome.org.


What is GTK+


GTK+ is a multi-platform toolkit for creating graphical user
interfaces. Offering a complete set of widgets, GTK+ is suitable for
projects ranging from small one-off tools to complete application
suites.

GTK+ has been designed from the ground up to support a range of
languages, not only C/C++. Using GTK+ from languages such as Perl and
Python (especially in combination with the Glade GUI builder) provides
an effective method of rapid application development.

GTK+ is free software and part of the GNU Project. However, the
licensing terms for GTK+, the GNU LGPL, allow it to be used by all
developers, including those developing proprietary software, without
any license fees or royalties.


Where to get more information about GTK+


Information about GTK+ including links to documentation can be
found at:

http://www.gtk.org/

An installation guide for GTK+ 2.x is found at:

 http://developer.gnome.org/doc/API/2.0/gtk/gtk-building.html

Common questions:

http://developer.gnome.org/doc/API/2.0/gtk/gtk-question-index.html
http://www.gtk.org/faq/


Contributing


GTK+ is a large project and relies on voluntary contributions.
We are actively searching for new contributors in various areas
and invite everyone to help project development.
If you are willing to participate, please subscribe to the project
mailing lists to offer your help and read over our list of vacant
project tasks:
   http://live.gnome.org/GtkTasks


Overview of Changes from GTK+ 2.19.5 to 2.19.6
==

* Bugs fixed:
 610701 gnome-shell crashes frequently
 604799 Crash when button is pressed.
 609744 crash at parse_data_for_row_pseudocolor
 600789 gdk/gdkwindow.c find_native_sibling_above will crash
 610141 gtk_assistant_get_nth_page() function fails to deliver...
 609952 destroying a notebook window when the last tab got dragged...
 603923 [annotations] gtk_tree_store_newv/set_column_types
 610474 [annotations] Add allow-none
 609650 GtkPlug Embedded signal is not emitted when plug...
 610381 More space between toolbar icon and label
 548026 No accessor for GtkWidget.requisition
 609514 fix introspection comments for gtk_tree_view_get_path_at_pos
 610235 msgid in bad English
 607697 GDK_META_MASK always set on Alt-Enter with gtk+ 2.19.x
 610632 gtk_info_bar_set_default_response problem
 609172 gdk/directfb: little cleanups
 610184 gtk_assistant_set_current_page() segfaults...

* Updated translations
 Bulgarian
 Czech
 Estonian
 German
 Japanese
 Korean
 Lithuanian
 Norwegian bokmål
 Oriya
 Polish
 Romanian
 Slovenian
 Spanish

Thanks to our contributors:
Javier Jardón
Michael Natterer
Christian Dywan
Stefan Kost
Johan Dahlin
Carlos Garcia Campos
Tadej Borovšak
Alan Knowles
Hiroyuki Ikezoe
Andre Draszik


February 23, 2010
Matthias Clasen


___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list

Re: putting combobox in toolbar

2010-02-23 Thread Tadej Borovšak
Hello.

Don't use GtkToolButton for this purpose, use it's parent,
GtkToolItem[1] directly and pack combo box inside it.

Tadej


[1] http://library.gnome.org/devel/gtk/stable/GtkToolItem.html

-- 
Tadej Borovšak
tadeboro.blogspot.com
tadeb...@gmail.com
tadej.borov...@gmail.com
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list

buttons in GtkMenus, and GtkUIManager

2010-02-23 Thread Brian J. Tarricone
So I have a bit of a weird request.

I'm creating a menu based on several merged UI descriptions at
runtime, using GtkUIManager.  This part works great.

The problem is that our user experience guys want a sort of
toggle-button-like radio selector at the top of the menu (this will be
for a touchscreen device).  So the first menu item will actually be
three buttons arranged horizontally.

I created a simple GtkMenuItem subclass that adds a GtkHBox to itself
with 3 GtkToggleButtons, plus some logic to make sure only one is
selected at a time.  I build the GtkMenu with GtkUIManager, and add my
custom menu item to the top.

First problem: I don't want the big prelight when the mouse moves over
it.  Fine, I just override GtkWidget::expose_event and GtkItem::select
in my menu item subclass.

But now the three buttons don't work.  I don't get a prelight
(somewhat important because our device will have a stylus that
supports proximity), and clicking on them does nothing.  I suspect it
has to do with how GtkMenu does its grabs.  However, if I connect to
motion-notify on my GtkMenuItem subclass, I do get motion events --
actually I seem to get *two* motion events for each mouse move over
any of the buttons -- one with coords relative to the button, the
other with coords relative to the menu item -- the odd thing is that
both of these events are delivered to the menu item (or maybe that's
not odd, given the grab?).

Anyway, I'm a bit stumped at this point.  Any pointers would be
appreciated.  I'd rather not have to write my own GtkMenuShell
subclass, but if people here think that's the best (or least-worst)
way to go, I'll do it.

Thanks,
Brian
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


When deprecating, always say what the replacement is.

2010-02-23 Thread Murray Cumming
When we deprecate API, please remember to document what the replacement
is. People forget this quite often.

A small recent example that doesn't do this:
http://git.gnome.org/browse/gtk
+/commit/?id=bb1824c131f247c2ef64f3c5f8b9ffe3885c9d90

-- 
murr...@murrayc.com
www.murrayc.com
www.openismus.com

___
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list


Re: When deprecating, always say what the replacement is.

2010-02-23 Thread Javier Jardón
2010/2/23 Murray Cumming murr...@murrayc.com:
 When we deprecate API, please remember to document what the replacement
 is. People forget this quite often.

 A small recent example that doesn't do this:
 http://git.gnome.org/browse/gtk
 +/commit/?id=bb1824c131f247c2ef64f3c5f8b9ffe3885c9d90

Indeed, the info about the replacements is on the deprecated
functions/macros documentation (inline comments ;)):

http://git.gnome.org/browse/gtk+/diff/gtk/gtkwidget.h?id=bb1824c131f247c2ef64f3c5f8b9ffe3885c9d90

Best Regards,


-- 
Javier Jardón Cabezas
___
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list


Re: When deprecating, always say what the replacement is.

2010-02-23 Thread Claudio Saavedra
El mar, 23-02-2010 a las 19:17 +0100, Javier Jardón escribió:
 2010/2/23 Murray Cumming murr...@murrayc.com:
  When we deprecate API, please remember to document what the replacement
  is. People forget this quite often.
 
  A small recent example that doesn't do this:
  http://git.gnome.org/browse/gtk
  +/commit/?id=bb1824c131f247c2ef64f3c5f8b9ffe3885c9d90
 
 Indeed, the info about the replacements is on the deprecated
 functions/macros documentation (inline comments ;)):
 
 http://git.gnome.org/browse/gtk+/diff/gtk/gtkwidget.h?id=bb1824c131f247c2ef64f3c5f8b9ffe3885c9d90
 
 Best Regards,

What about patching gtk-doc to provide syntax for replacements?

Claudio


___
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list


Re: When deprecating, always say what the replacement is.

2010-02-23 Thread Murray Cumming
On Tue, 2010-02-23 at 19:17 +0100, Javier Jardón wrote:
 2010/2/23 Murray Cumming murr...@murrayc.com:
  When we deprecate API, please remember to document what the replacement
  is. People forget this quite often.
 
  A small recent example that doesn't do this:
  http://git.gnome.org/browse/gtk
  +/commit/?id=bb1824c131f247c2ef64f3c5f8b9ffe3885c9d90
 
 Indeed, the info about the replacements is on the deprecated
 functions/macros documentation (inline comments ;)):

No, Deprecated: 2.20: Do not use it. is not good enough.


-- 
murr...@murrayc.com
www.murrayc.com
www.openismus.com

___
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list


GTK+ 2.19.6 released

2010-02-23 Thread Matthias Clasen
GTK+ 2.19.6 is now available for download at:

 ftp://ftp.gtk.org/pub/gtk/2.19/
 http://download.gnome.org/sources/gtk+/2.19/

md5 sums:
524021c965a0e1a4ebadd58c576926a5  gtk+-2.19.6.tar.bz2
1311c99903e4dd28bf42a352b05788db  gtk+-2.19.6.tar.gz

sha1 sums:
0a4267fe2f3022f39fdf1a2a3817e520c0ff  gtk+-2.19.6.tar.bz2
0e1d0329f2aad4d7aa9fd127c9b393db79dc6746  gtk+-2.19.6.tar.gz

This is a development release leading up to GTK+ 2.20.

Notes:

 * This is an unstable development release.
   It has had only little testing and there are unfinished
   features and plenty of bugs in this release. It should
   definitively not be used in production.

 * Installing this version will overwrite your existing
   copy of GTK+ 2.18. If you have problems, you'll need
   to reinstall GTK+ 2.18.

 * GTK+ 2.20 will be source and binary compatible with
   the GTK+ 2.18 series; however, the new API additions
   are not yet finalized, so there may be incompatibilities
   between this release and the final 2.20 release.

 * Bugs should be reported to http://bugzilla.gnome.org.


What is GTK+


GTK+ is a multi-platform toolkit for creating graphical user
interfaces. Offering a complete set of widgets, GTK+ is suitable for
projects ranging from small one-off tools to complete application
suites.

GTK+ has been designed from the ground up to support a range of
languages, not only C/C++. Using GTK+ from languages such as Perl and
Python (especially in combination with the Glade GUI builder) provides
an effective method of rapid application development.

GTK+ is free software and part of the GNU Project. However, the
licensing terms for GTK+, the GNU LGPL, allow it to be used by all
developers, including those developing proprietary software, without
any license fees or royalties.


Where to get more information about GTK+


Information about GTK+ including links to documentation can be
found at:

http://www.gtk.org/

An installation guide for GTK+ 2.x is found at:

 http://developer.gnome.org/doc/API/2.0/gtk/gtk-building.html

Common questions:

http://developer.gnome.org/doc/API/2.0/gtk/gtk-question-index.html
http://www.gtk.org/faq/


Contributing


GTK+ is a large project and relies on voluntary contributions.
We are actively searching for new contributors in various areas
and invite everyone to help project development.
If you are willing to participate, please subscribe to the project
mailing lists to offer your help and read over our list of vacant
project tasks:
   http://live.gnome.org/GtkTasks


Overview of Changes from GTK+ 2.19.5 to 2.19.6
==

* Bugs fixed:
 610701 gnome-shell crashes frequently
 604799 Crash when button is pressed.
 609744 crash at parse_data_for_row_pseudocolor
 600789 gdk/gdkwindow.c find_native_sibling_above will crash
 610141 gtk_assistant_get_nth_page() function fails to deliver...
 609952 destroying a notebook window when the last tab got dragged...
 603923 [annotations] gtk_tree_store_newv/set_column_types
 610474 [annotations] Add allow-none
 609650 GtkPlug Embedded signal is not emitted when plug...
 610381 More space between toolbar icon and label
 548026 No accessor for GtkWidget.requisition
 609514 fix introspection comments for gtk_tree_view_get_path_at_pos
 610235 msgid in bad English
 607697 GDK_META_MASK always set on Alt-Enter with gtk+ 2.19.x
 610632 gtk_info_bar_set_default_response problem
 609172 gdk/directfb: little cleanups
 610184 gtk_assistant_set_current_page() segfaults...

* Updated translations
 Bulgarian
 Czech
 Estonian
 German
 Japanese
 Korean
 Lithuanian
 Norwegian bokmål
 Oriya
 Polish
 Romanian
 Slovenian
 Spanish

Thanks to our contributors:
Javier Jardón
Michael Natterer
Christian Dywan
Stefan Kost
Johan Dahlin
Carlos Garcia Campos
Tadej Borovšak
Alan Knowles
Hiroyuki Ikezoe
Andre Draszik


February 23, 2010
Matthias Clasen


___
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list


Re: When deprecating, always say what the replacement is.

2010-02-23 Thread Michael Natterer
On Tue, 2010-02-23 at 19:59 +0100, Murray Cumming wrote:
 On Tue, 2010-02-23 at 19:17 +0100, Javier Jardón wrote:
  2010/2/23 Murray Cumming murr...@murrayc.com:
   When we deprecate API, please remember to document what the replacement
   is. People forget this quite often.
  
   A small recent example that doesn't do this:
   http://git.gnome.org/browse/gtk
   +/commit/?id=bb1824c131f247c2ef64f3c5f8b9ffe3885c9d90
  
  Indeed, the info about the replacements is on the deprecated
  functions/macros documentation (inline comments ;)):
 
 No, Deprecated: 2.20: Do not use it. is not good enough.

As a matter of fact, it is. There is not supposed to be any
replacement for the stuff that says Do not use it. Everything
that has a replacement is however documented.

So please, a little research before bashing perfectly good commits.

ciao,
--mitch


___
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list


Re: When deprecating, always say what the replacement is.

2010-02-23 Thread Morten Welinder
 As a matter of fact, it is. There is not supposed to be any
 replacement for the stuff that says Do not use it. Everything
 that has a replacement is however documented.

 So please, a little research before bashing perfectly good commits.

How about a research before bashing perfectly good bashing?
(And look for Do not used it. before calling it a perfectly good
commit.)

But seriously, Do not use it is unhelpful.  Things no longer
compile for someone and all you have to offer is you shouldn't
have been doing that?  We can do better than that!

For GTK_WIDGET_FLAGS, for example, one could point to
a list of the accessors for the individual flags.  That is, as I
understand it, what one is supposed to use instead, even if
it is clearly not a 1-for-1 replacement.

Morten
___
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list


Re: When deprecating, always say what the replacement is.

2010-02-23 Thread Murray Cumming
On Tue, 2010-02-23 at 22:36 +0100, Michael Natterer wrote:
 On Tue, 2010-02-23 at 19:59 +0100, Murray Cumming wrote:
  No, Deprecated: 2.20: Do not use it. is not good enough.
 
 As a matter of fact, it is. There is not supposed to be any
 replacement for the stuff that says Do not use it. Everything
 that has a replacement is however documented.

But Do not use it does not even make that clear. The reader has no
idea whether it is something that should never have been used (and why
not) or something that has a replacement. It shouldn't take much empathy
to realize that, or to realize that documentation _must_ have a problem
if someone says it's unclear. We can do better.

-- 
murr...@murrayc.com
www.murrayc.com
www.openismus.com

___
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list


Re: Remarks on gtk docs

2010-02-23 Thread Joost

This here (the middle paragraph) had been cut by a bug anywhere -
it is in the version in my Sent folder. I send it a second time
from Thunderbird - perhaps i must search for another email client
than Thunderbird, Sylpheed or Pegasus)

And i had found it somewhere on library.gnome.org - yes it is documented.
But not at the prominent place, where it has to. This must be in one
of the first paragraphs on .rc files everywhere.

gtk authors will have had reasons for this ideosyncratic behavior of widget.
From the first  look it appears as nothing as another weakness - and
that is, what i want to state as the second main point here: The documentation
must be more honest to be well usable. These days i begin to make
the User Manual for my commercial OKamba. I will cut off any try of
pseudo-objectivity there and use a lot of is (hopefully not too penetrant)
using it for advertisement with the same move. But i will speak of more than one
weakness of OKamba there - and prevent useless searching of the users so.

The gtk docs - without any need - do so nowhere :(
That is a sure way to loose the battle against QT.

___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Do not use Pegasus for sending to this list (?)

2010-02-23 Thread Joost

Hm,

perhaps i must change my email client another time
(from Thunderbird to Pegasus and now what - unix sendmail ?).
The thread Remarks on gtk docs is terrible - i
must beg you pardon. And a paragraph had been
cut-off from the main entry, the middle paragraph
of these 3 here:


And i had found it somewhere on library.gnome.org - yes it is documented.
But not at the prominent place, where it has to. This must be in one
of the first paragraphs on .rc files everywhere.

gtk authors will have had reasons for this ideosyncratic behavior of widget.
From the first look it appears as nothing as another weakness - and
that is, what i want to state as the second main point here: The documentation
must be more honest to be well usable. These days i begin to make
the User Manual for my commercial OKamba. I will cut off any try of
pseudo-objectivity there and use a lot of is (hopefully not too penetrant)
using it for advertisement with the same move. But i will speak of more than one
weakness of OKamba there - and prevent useless searching of the users so.

The gtk docs - without any need - do so nowhere :(
That is a sure way to loose the battle against QT.

___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Do not use Pegasus for sending to this list (?) - PS to remarks on doc

2010-02-23 Thread Joost

Hm,

perhaps i must change my email client another time
(from Thunderbird with its bad behavior in small
networks to Pegasus and now what - unix sendmail ?).
The thread Remarks on gtk docs is terrible - i
must beg your pardon. And a paragraph had been
cut-off from the main entry (Pegasus has the mail complete
in its Sent folder), the middle paragraph of these 3 here:


And i had found it somewhere on library.gnome.org - yes it is documented.
But not at the prominent place, where it has to. This must be in one
of the first paragraphs on .rc files everywhere.

gtk authors will have had reasons for this ideosyncratic behavior of widget.
From the first look it appears as nothing as another weakness - and
that is, what i want to state as the second main point here: The documentation
must be more honest to be well usable. These days i begin to make
the User Manual for my commercial OKamba. I will cut off any try of
pseudo-objectivity there and use a lot of is (hopefully not too penetrant)
using it for advertisement with the same move. But i will tell more than one
weakness of OKamba there.

The gtk docs - without any need - do so nowhere :(
That is a sure way to loose the battle against QT.


Honesty is also the topic with Read the sources, honesty
to oneself too.

And at Ed James: Many thanks - that was comforting. And i am
elder too, but til now only living from my software as its user.
(1994-1999 TCL/TK for plain TeX on Slackware Linux).

Thanks for reading, Joost

___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


A problem with a treeview header's columns

2010-02-23 Thread MILLEREUX , Sébastien
Hello,

I've posted the bug 610277 on https://bugzilla.gnome.org but I'm not sure I 
will have a quick response and a solution... maybe someone will help me on this 
mailing list.

As i posted, i'm working with directfb 1.4.3 and gtk 2.16.6
I've include a GtkTreeView into a GtkScrolledWindow into a GtkHBox
The Hbox contain 3 elements and the scrolled window is include in the middle 
one.
Two columns compose the treeview's model.
When the first is too large to show the complete data the horizontal scrollbar 
appears in the bottom of the window.

= all is working well for the data in the rows but the first row (the header 
one) is not painted correctly.
The button corresponding to the column header is painted out of the scrolled 
window upper the third hbox element.
Moreover, when I'm scrolling horizontally the labels in the header's columns 
move but not the buttons in the background.
It is like the background buttons are not resized to fit to the 
scrolledwindow and take all the place.

I was working with gtk 2.12 before and I didn't meet this problem.
I can't work with gtk 2.18 because I can't start my application because of a 
bug on directfb not resolved yet !
I think this bug is resolved with the version 2.18 because I've tryed my 
application on ubuntu with gtk2.18 and I didn't meet it.

I've tryed to look at the code in gtk 2.18 to correct my bug but gdk has so 
many changes and i don't know exactly what is the problem.

I need a patch, thanks by advance for any help

MS

___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


GLib-GObject-CRITICAL after make install glib-2.22.4

2010-02-23 Thread UGP
Hi,

I surf to LXDE website and download tarball for compile by myself.

It say need newer version gtk+ library, so I go to download gtk+ tarball too. 
And make install it.

When glib-2.22.4 install finish, I attend LXDE's deb files for install, I add 
lxde apt information and use apt-get install lxde.

Install finish, so I logout gnome and want login LXDE, but it happen this 
problem:
NVIDIA Logo - orange screen, waiting cursor - terminal screen - NVIDIA Logo 
- ...


Linux Environment: Ubuntu 8.04.3


cat /var/log/syslog | grep GLib:

Feb  9 00:19:19 ugplinux gdmgreeter[31250]: GLib-GObject-CRITICAL: 
g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed
Feb  9 00:19:19 ugplinux gdmgreeter[31250]: GLib-GObject-CRITICAL: 
g_object_set_qdata_full: assertion `G_IS_OBJECT (object)' failed

Feb  9 00:32:22 ugplinux gdmgreeter[402]: GLib-GObject-CRITICAL: 
g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed
Feb  9 00:32:22 ugplinux gdmgreeter[402]: GLib-GObject-CRITICAL: 
g_object_set_qdata_full: assertion `G_IS_OBJECT (object)' failed

Feb  9 00:32:27 ugplinux gdm[430]: GLib-GObject-CRITICAL: g_object_get_qdata: 
assertion `G_IS_OBJECT (object)' failed
Feb  9 00:32:27 ugplinux gdm[430]: GLib-GObject-CRITICAL: 
g_object_set_qdata_full: assertion `G_IS_OBJECT (object)' failed


I has tried these to solve this problem, but not work:

1.sudo dpkg-reconfigure gnome-desktop-environment
terminal say nothing after this.

2.sudo apt-get remove lxde openbox lxde-*

3.sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf_backup

4.sudo /etc/init.d/kdm start
terminal say kdm isn't default setting.

5.sudo aptitude remove xserver; sudo aptitude install ubuntu-desktop


How to solve it?
Thanks.
UGP


  

___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Re: GLib-GObject-CRITICAL after make install glib-2.22.4

2010-02-23 Thread Tadej Borovšak
Hello.

 It say need newer version gtk+ library, so I go to download gtk+ tarball too. 
 And make install it.

 When glib-2.22.4 install finish, I attend LXDE's deb files for install, I add 
 lxde apt information and use apt-get install lxde.

How did you install all of this stuff? More exactly, what prefix did
you use for your installation?

Tadej

-- 
Tadej Borovšak
tadeboro.blogspot.com
tadeb...@gmail.com
tadej.borov...@gmail.com
___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Re: Remarks on gtk docs

2010-02-23 Thread Tor Lillqvist
 That is a sure way to loose the battle against QT.

People who like Qt (not QT) use that if they have a choice, people
who like GTK+ use that if they have a choice. Where is the battle?

--tml
___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


All widget are too fat - theming not working properly

2010-02-23 Thread Matthias Fuchs

Hi guys,

imho, all gtk widgets are much to fat/big, especially comboboxes, 
buttons and tabs.
So ok, it's possible to decrease x-/ythickness, some paddings and stuff 
like this. After much hours of tweaking and tuning I managed to create a 
minimal theme. Though some buttons (those without icons) have the 
desired height, buttons that normally have icons, like in dialogs, are 
much higher. Though these icons are not visible/hidden the buttons' 
heights seem to not decrease anymore.


There are also some quirks with comboboxes. Those that are not editable 
are higher as the others.


Look at the screenshot to see what I mean:
1) and 2) are both chomboboxes, but 2) is one pixel higher
(Yes, I know, it's just a pixel and 99,9% of all users won't ever notice 
is -- But I do. And everytime I look at the screen I hate it.


3) and 4) are both buttons. 4) seems to adopt my gtkrc settings, 3) 
doesn't. 3) should normally have an icon. But I disabled all kind of 
icons in menus and on buttons. Somehow they seem to still be there and 
prevent the button from becoming less high.



Is there some way to solve these bugs? Is there a chance that GTK+ 3.0 
doesn't have such fat widgets per default?


Hope, I didn't confuse you too much ;-)

br, ash

attachment: widget_mess.png___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


GTK+ 2.19.6 released

2010-02-23 Thread Matthias Clasen
GTK+ 2.19.6 is now available for download at:

 ftp://ftp.gtk.org/pub/gtk/2.19/
 http://download.gnome.org/sources/gtk+/2.19/

md5 sums:
524021c965a0e1a4ebadd58c576926a5  gtk+-2.19.6.tar.bz2
1311c99903e4dd28bf42a352b05788db  gtk+-2.19.6.tar.gz

sha1 sums:
0a4267fe2f3022f39fdf1a2a3817e520c0ff  gtk+-2.19.6.tar.bz2
0e1d0329f2aad4d7aa9fd127c9b393db79dc6746  gtk+-2.19.6.tar.gz

This is a development release leading up to GTK+ 2.20.

Notes:

 * This is an unstable development release.
   It has had only little testing and there are unfinished
   features and plenty of bugs in this release. It should
   definitively not be used in production.

 * Installing this version will overwrite your existing
   copy of GTK+ 2.18. If you have problems, you'll need
   to reinstall GTK+ 2.18.

 * GTK+ 2.20 will be source and binary compatible with
   the GTK+ 2.18 series; however, the new API additions
   are not yet finalized, so there may be incompatibilities
   between this release and the final 2.20 release.

 * Bugs should be reported to http://bugzilla.gnome.org.


What is GTK+


GTK+ is a multi-platform toolkit for creating graphical user
interfaces. Offering a complete set of widgets, GTK+ is suitable for
projects ranging from small one-off tools to complete application
suites.

GTK+ has been designed from the ground up to support a range of
languages, not only C/C++. Using GTK+ from languages such as Perl and
Python (especially in combination with the Glade GUI builder) provides
an effective method of rapid application development.

GTK+ is free software and part of the GNU Project. However, the
licensing terms for GTK+, the GNU LGPL, allow it to be used by all
developers, including those developing proprietary software, without
any license fees or royalties.


Where to get more information about GTK+


Information about GTK+ including links to documentation can be
found at:

http://www.gtk.org/

An installation guide for GTK+ 2.x is found at:

 http://developer.gnome.org/doc/API/2.0/gtk/gtk-building.html

Common questions:

http://developer.gnome.org/doc/API/2.0/gtk/gtk-question-index.html
http://www.gtk.org/faq/


Contributing


GTK+ is a large project and relies on voluntary contributions.
We are actively searching for new contributors in various areas
and invite everyone to help project development.
If you are willing to participate, please subscribe to the project
mailing lists to offer your help and read over our list of vacant
project tasks:
   http://live.gnome.org/GtkTasks


Overview of Changes from GTK+ 2.19.5 to 2.19.6
==

* Bugs fixed:
 610701 gnome-shell crashes frequently
 604799 Crash when button is pressed.
 609744 crash at parse_data_for_row_pseudocolor
 600789 gdk/gdkwindow.c find_native_sibling_above will crash
 610141 gtk_assistant_get_nth_page() function fails to deliver...
 609952 destroying a notebook window when the last tab got dragged...
 603923 [annotations] gtk_tree_store_newv/set_column_types
 610474 [annotations] Add allow-none
 609650 GtkPlug Embedded signal is not emitted when plug...
 610381 More space between toolbar icon and label
 548026 No accessor for GtkWidget.requisition
 609514 fix introspection comments for gtk_tree_view_get_path_at_pos
 610235 msgid in bad English
 607697 GDK_META_MASK always set on Alt-Enter with gtk+ 2.19.x
 610632 gtk_info_bar_set_default_response problem
 609172 gdk/directfb: little cleanups
 610184 gtk_assistant_set_current_page() segfaults...

* Updated translations
 Bulgarian
 Czech
 Estonian
 German
 Japanese
 Korean
 Lithuanian
 Norwegian bokmål
 Oriya
 Polish
 Romanian
 Slovenian
 Spanish

Thanks to our contributors:
Javier Jardón
Michael Natterer
Christian Dywan
Stefan Kost
Johan Dahlin
Carlos Garcia Campos
Tadej Borovšak
Alan Knowles
Hiroyuki Ikezoe
Andre Draszik


February 23, 2010
Matthias Clasen


___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Re: Remarks on gtk docs

2010-02-23 Thread Tor Lillqvist
 That is a sure way to loose the battle against QT.

People who like Qt (not QT) use it if they have a choice, people
who like GTK+ use it if they have a choice. Where is the battle?

--tml
___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Re: Remarks on gtk docs

2010-02-23 Thread 1

Hello Thor,

after this mishap probably caused by Pegasus (or a misconfiguration by me -
but so far i never heard from problems other addressees had) i'll use my
ISP's webmailer for this mailbox for a while.

Battle was an adoption from wikipedia's browser war - a bit superficial
of course. But there is chitchat about an uprising economy of attention - in
such an economy the concurrency of Gnome versus KDE is a bit more severe
than any academic pastime. Of course we already have advertisement as the
main income of google for instance - but many protagonists of the advertising
business are having doubts about the effectiveness of advertisement at all.
And the first task in establishing such an economy were to sanction  
advertising

lies severely. And their grips below the belt. As spam is dealt with already
today (and this is a feature of such an economy).

I guess moreover, that the common open source programmer is convinced  
of his work's quality. At least i am for my little Python tool  
thrases. And that she
wants to be read like any author of poetry - of course read means  
used here.


By the way: Thanks for your work with the Windows update. I didn't have those
great problems John Stowers reported. But a bad bug: When leaving an entry's
window from a drag for selection, the cursor remains the text  
insertion cursor

and doesn't work no more - only an arbitrary extra click reestablishes the
normal functions of the pointer. A bug 2.16.6 didn't have.

Yes - there are maintainance problems with gtk+ - serious maintainance  
problems.
Providing connect() in depikt i studied the standard method of gtk+ of  
course -

learning, that the use of closures and marshallers is only providing hooks in
comparision with g_signal_connect() and GCallback. And signatures we currently
do not need. Hooks - that means side-effects. Why not have the actions of
these hooks in the using code around my_object.connect() ? And - if needed
multiply - write a function around g_signal_connect() ? That is always
better readable, 100%. I won't probably support that with depikt, only  
if the simpler GCallback will be dismissed also. As the well-done  
simplicity of the

old Tooltips, which are deprecated now (which didn't show correct colours
though, as GtkTreeView::base[NORMAL] didn't too). And apparently we only got
bars as containers for widgets with tooltips instead (i might have missed
something here - i will still use the deprecated methods).

Thanks for reading, Joost





___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list