[cssed-devel] =?ISO-8859-1?Q?Re:_[cssed-devel]_Re:_[cssed-devel]_Re:_[cssed-de?= =?ISO-8859-1?Q?vel]_New_plugin:_developer_doc_plugin_=28Modifi?= =?ISO-8859-1?Q?=E9_par_Mich=E8le_Garoche=29?=

[<mic...@ea...>]

Le 20 sept. 2004, =E0 9:22, Iago Rubio a =E9crit :

> On Mon, 2004-09-20 at 00:28, Mich=E8le Garoche wrote:
>> which is only for mac in cvs, so that I can have it in the port? Then
>> when the other way to do it is done, I'll drop the code.
>
> :???
> Why?
Because, basically it's the same call as for the API plugin doc, if you=20=

add the possibility to have browser, the code is not needed, only for=20
sure the location of the web site and on the online doc. So once the=20
structure for the browser is here, I use it to go to the web site or=20
the online doc.

>>> The plugin API is open for people to do whatever plugin they wants,=20=

>>> and
>>> can be platform dependant and shiped only in one platform.
>> That's not possible, since it requires for the plugin doc for example
>> to incorporate the html files in it. Hence, it should be put on cvs,
>> otherwise it is not possible to port it. Or you will end up with a
>> bunch of plugins you have no control on them.
> Surely it will end with a bunch of plugins I'll have no control over
> them :)
> That's what I want, more people implied, more people coding and
> mantaining their own plugins.
Oh, that's a strange idea. But well, we'll see.

> We should build a documentation package that follows the fink guide
> lines.
The one I've made follow it, except that you should change the location=20=

of the menu, should be under help. And normally, should be supply with=20=

the main package. Then porters can choose to install it or not, I=20
personally always install the developers doc. As for the location of=20
the doc itself it all depends if it uses gnome help or not and which=20
version of gnome it uses. But generally when using gnome, the makefile=20=

already has the right routine to install it. And for the Mac I patch,=20
to respect special post/pre install/remove scripts.

> If he wants to be bound to the package manager, he have no need to
> install something out of fink. If he want to develop or install a =
third
> party plugin, I have little to do with that.
Yes, of course. But then, you have no idea what exists outside of=20
cssed, no?
Or do you mean, it would be useful I develop some plugins I put on=20
sourceforge in my project page, then you can pick up what you find=20
useful or something like that? Anyway at the moment, I don't feel as=20
skilled as to develop something useful myself.

Mich=E8le
<http://micmacfr.homeunix.org>