gtk-doc resolution-independen branch

[Stefan Kost]

hi,

saw your changes for res-indep gtk branch for gtk-doc. I'd like to discuss how
we can handle this better in gtk-doc by using some sort of plugins. gtk+ itself
has some gtk-specific support in gtk-doc, but e.g. gstreamer has lots of gobject
things that could get some special doc treatment.

Ideally gtk-doc itself only knows about gobject and all the gtk-specific things
go to a module (that could be active by default for backwards compat). gstreamer
things go to a gst module. modules can be activated/deactivated in Makefile.am.

I don't have thought this any deeper though.

Stefan
_______________________________________________
gtk-doc-list mailing list
gtk-doc-list@...
http://mail.gnome.org/mailman/listinfo/gtk-doc-list

[Davyd Madeley]

Hey,

Yeah. I did wonder about adding GTK+ specific code there, but I noticed
there was already a stack of it, so I didn't feel too upset.

I think using plugins is a good idea though.

Maybe the solution is to allow the passing of an optional Perl module
(e.g. --with-plugin=gtk.pm) that can define certain hooks within the
scanner e.g. to fiddle with the type handling etc. We can modify the
gtk-doc.make to provide a WITH_PLUGIN in the Makefile.am.

Thoughts?

--d

On Fri, 2009-05-22 at 22:38 +0300, Stefan Kost wrote:

> hi,
>
> saw your changes for res-indep gtk branch for gtk-doc. I'd like to discuss how
> we can handle this better in gtk-doc by using some sort of plugins. gtk+ itself
> has some gtk-specific support in gtk-doc, but e.g. gstreamer has lots of gobject
> things that could get some special doc treatment.
>
> Ideally gtk-doc itself only knows about gobject and all the gtk-specific things
> go to a module (that could be active by default for backwards compat). gstreamer
> things go to a gst module. modules can be activated/deactivated in Makefile.am.
>
> I don't have thought this any deeper though.
>
> Stefan

--
Davyd Madeley

http://www.davyd.id.au/
08B0 341A 0B9B 08BB 2118  C060 2EDD BB4F 5191 6CDA

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

[Stefan Kost]

Davyd Madeley schrieb:

> Hey,
>
> Yeah. I did wonder about adding GTK+ specific code there, but I noticed
> there was already a stack of it, so I didn't feel too upset.
>
> I think using plugins is a good idea though.
>
> Maybe the solution is to allow the passing of an optional Perl module
> (e.g. --with-plugin=gtk.pm) that can define certain hooks within the
> scanner e.g. to fiddle with the type handling etc. We can modify the
> gtk-doc.make to provide a WITH_PLUGIN in the Makefile.am.
>

Yes, something like that. I think its okay to ship the gtk module with gtk-doc
unless gtk itself wants to take it. I never did a perl module - so I need to
sudy a bit how and where they should be installed.
I should finalize and release 1.12 before though :)

Stefan

> Thoughts?
>
> --d
>
> On Fri, 2009-05-22 at 22:38 +0300, Stefan Kost wrote:
>> hi,
>>
>> saw your changes for res-indep gtk branch for gtk-doc. I'd like to discuss how
>> we can handle this better in gtk-doc by using some sort of plugins. gtk+ itself
>> has some gtk-specific support in gtk-doc, but e.g. gstreamer has lots of gobject
>> things that could get some special doc treatment.
>>
>> Ideally gtk-doc itself only knows about gobject and all the gtk-specific things
>> go to a module (that could be active by default for backwards compat). gstreamer
>> things go to a gst module. modules can be activated/deactivated in Makefile.am.
>>
>> I don't have thought this any deeper though.
>>
>> Stefan

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

[Davyd Madeley]

On Sat, 2009-05-23 at 20:56 +0300, Stefan Kost wrote:

> Yes, something like that. I think its okay to ship the gtk module with gtk-doc
> unless gtk itself wants to take it. I never did a perl module - so I need to
> sudy a bit how and where they should be installed.
> I should finalize and release 1.12 before though :)

We can install them wherever we like, and then set that install path in
the Perl scangobj program via `use lib`.

Alternatively, we could consider GModules.

--
Davyd Madeley

http://www.davyd.id.au/
08B0 341A 0B9B 08BB 2118  C060 2EDD BB4F 5191 6CDA

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

[Matthias Clasen-2]

On Sat, May 23, 2009 at 1:56 PM, Stefan Kost <ensonic@...> wrote:

> Yes, something like that. I think its okay to ship the gtk module with gtk-doc
> unless gtk itself wants to take it. I never did a perl module - so I need to
> sudy a bit how and where they should be installed.


I don't have any particular desire to start shipping perl modules with
gtk. I think it makes a lot more sense to ship gobject and gtk support
with gtk-doc, as it has always been.
_______________________________________________
gtk-doc-list mailing list
gtk-doc-list@...
http://mail.gnome.org/mailman/listinfo/gtk-doc-list

[Stefan Kost]

Matthias Clasen schrieb:

> On Sat, May 23, 2009 at 1:56 PM, Stefan Kost <ensonic@...> wrote:
>
>> Yes, something like that. I think its okay to ship the gtk module with gtk-doc
>> unless gtk itself wants to take it. I never did a perl module - so I need to
>> sudy a bit how and where they should be installed.
>
>
> I don't have any particular desire to start shipping perl modules with
> gtk. I think it makes a lot more sense to ship gobject and gtk support
> with gtk-doc, as it has always been.

Don't worry about the gobject stuff. For gtk specific thing it would be good to
somehow pick the bits and pieces and group them in a module. But again for the
sake of backward compat it should be shipped with gtk-doc. Lets discuss this
again in the future if its done and if we still think it should go elsewhere :)

Stefan
_______________________________________________
gtk-doc-list mailing list
gtk-doc-list@...
http://mail.gnome.org/mailman/listinfo/gtk-doc-list