RSS/Atom feed Twitter
Site is read-only, email is disabled

where to put widgets for plugins

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

4 of 4 messages available
Toggle history

Please log in to manage your subscriptions.

where to put widgets for plugins Roman Joost 11 Jul 08:23
  where to put widgets for plugins Martin Nordholts 11 Jul 08:30
   where to put widgets for plugins Roman Joost 12 Jul 04:53
    where to put widgets for plugins Martin Nordholts 12 Jul 08:17
Roman Joost
2009-07-11 08:23:40 UTC (over 15 years ago)

where to put widgets for plugins

Hi,

I wonder where I can put and compile a widget I've written for the metadata browser. It's a GtkEntry widget which is "linked" to the XMPModel. The entry takes three parameters in the constructor, the property, the schema and the XMPModel as a data type.

If I put the widget into libgimpwidgets, I probably have to link it against the xmp_model which is defined in a plug-in. If I leave the widget in my metadata plug-in, I need to change the Makefile to use the widget. Any trials I've done so far were not successful.

Maybe the widget should be more general. Because the XMPModel is storing the data in a GtkTreeModel, the widget could be initialized with a GtkTreeModel, rather providing the whole XMPModel.

I'm a bit clueless here what the best solution would be.

Cheers for any suggestions,

Martin Nordholts
2009-07-11 08:30:49 UTC (over 15 years ago)

where to put widgets for plugins

On 07/11/2009 08:23 AM, Roman Joost wrote:

Hi,

I wonder where I can put and compile a widget I've written for the metadata browser. It's a GtkEntry widget which is "linked" to the XMPModel. The entry takes three parameters in the constructor, the property, the schema and the XMPModel as a data type.

If I put the widget into libgimpwidgets, I probably have to link it against the xmp_model which is defined in a plug-in. If I leave the widget in my metadata plug-in, I need to change the Makefile to use the widget.

Hi Roman,

Since we don't want the libgimpwidgets to depend on the metadata plug-in, you should put the widget along with the metadata plug-in source. That the metadata plug-in will depend on a UI library is not a problem. If we can avoid extending our plug-in API we should do that.

BR, Martin

Roman Joost
2009-07-12 04:53:48 UTC (over 15 years ago)

where to put widgets for plugins

On Sat, Jul 11, 2009 at 08:33:11AM +0200, Martin Nordholts wrote:

On 07/11/2009 08:23 AM, Roman Joost wrote:

Hi,

I wonder where I can put and compile a widget I've written for the metadata browser. [...]

Since we don't want the libgimpwidgets to depend on the metadata plug-in, you should put the widget along with the metadata plug-in source. That the metadata plug-in will depend on a UI library is not a problem. If we can avoid extending our plug-in API we should do that.

Thank you!

Not beeing to fuzzy here, but do I need to follow a directory structure? Say, all the widgets - it's currently just one - should be placed into a subdirectory "widgets".

Cheers,

Martin Nordholts
2009-07-12 08:17:00 UTC (over 15 years ago)

where to put widgets for plugins

On 07/12/2009 04:53 AM, Roman Joost wrote:

On Sat, Jul 11, 2009 at 08:33:11AM +0200, Martin Nordholts wrote:

On 07/11/2009 08:23 AM, Roman Joost wrote:

Hi,

I wonder where I can put and compile a widget I've written for the metadata browser. [...]

Since we don't want the libgimpwidgets to depend on the metadata plug-in, you should put the widget along with the metadata plug-in source. That the metadata plug-in will depend on a UI library is not a problem. If we can avoid extending our plug-in API we should do that.

Thank you!

Not beeing to fuzzy here, but do I need to follow a directory structure? Say, all the widgets - it's currently just one - should be placed into a subdirectory "widgets".

No that's not necessary, there are not that many files in total and everything will compiled to a single binary anyway

/ Martin