Re: [cssed-devel] Re: [cssed-devel] Re: [cssed-devel] New plugin: developer doc plugin =?ISO-8859-1?Q?=28Modifi=E9?= par =?ISO-8859-1?Q?Mich=E8le?= Garoche)

[Iago R. <iag...@hi...>]

On Mon, 2004-09-20 at 00:28, Mich=C3=A8le Garoche wrote:
> [snip] open is not portable, it is in the standard lib :-) and
> >> system is on all ports, as far as I know.
> > This does not ensure system will return the same values in all=20
> > platforms
> > and errno values are know to vary between POSIX and non POSIX systems.
> Oh, yes, of course. But here, as it is only for Mac, there is no=20
> problem.

That's why I told you to add it between ifdefs :)

> >>>>> Should we go for this before this release, and "unfreeze" the code=20
> >>>>> to
> >>>>> get docs into a plugin ??
> >>>> Well, all depends if you think you can do that in a reasonable=20
> >>>> delay,
> >>>> otherwise we can just release without it, but well it's so nice to
> >>>> have
> >>>> it...
> >>> It's a time issue. I'd like to release it with a good interface and
> >>> updating the plugin's API acordling. It can take us a couple of weeks
> >>> to
> >>> have all bits in place and there've been a long time with no release.
> >> That's what I suggest put it as is, as it works, and then change it to
> >> gspawn in the next release.
> > It does not work on Linux nor in BSD.
> But, again it's only for Mac.
>=20
> > To hardcde the command is always a bad idea, as it can not be present=20
> > in
> > all systems. Well, it's true - at least - in multi platform
> > applications.
> Yes, but the ifdef or patch are here to do that, to port. You cannot=20
> expect every single bit of the package will work as is on any system.=20
> The port of cssed on mac has little to do with the original package. It=20
> is splitted in two packages and patches are made on some locations,=20
> just to tell some changes.

Ehemmm !!!
That's what I told you to add it between ifdefs :))

> > The find in files plugin, and the file browser plugin will not be
> > shipped in windows as example.
> Yes, but they are in cvs, so why don't you want I put the help part,

:?=20
Michelle, I'm waiting for you to upload those changes to CVS. I've never
said I don't want to put it in CVS.


> which is only for mac in cvs, so that I can have it in the port? Then=20
> when the other way to do it is done, I'll drop the code.

:???
Why?

> > The plugin API is open for people to do whatever plugin they wants, and
> > can be platform dependant and shiped only in one platform.
> That's not possible, since it requires for the plugin doc for example=20
> to incorporate the html files in it. Hence, it should be put on cvs,=20
> otherwise it is not possible to port it. Or you will end up with a=20
> 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.

> > The only think I expect to be in Fink is cssed itself, and the plugins
> > you'll find useful for the Mac community.
> I can put them in fink, if they are in cvs, otherwise I cannot. Then of=20
> course, I can choose to add or not a plugin, but it should be in cvs=20
> before hand, i.e. you should release it.

I see.

> > Right now, I will add the -DDARWING stuff to make your defines to work,
> > so in Mac will be shiped with the help menu.
> > I will add some code to test if the doc is present, but you must=20
> > provide
> > a path to search for it.
> No, you misunderstood me. What I've added is not the doc itself, this=20
> could be done later. I've just added a link to the web site and a link=20
> to the online doc. Because Mac users will never know where and how to=20
> add the doc, besides it has no sense to let them install the doc and=20
> then just provides a link to it in the package. Plus it is completely=20
> against fink policy: fink has a trace of what is installed, then when=20
> you remove a package, all is removed.

Common to all package managers :)

>  If you allow a user to add=20
> something manually or even worse encourage it to do so, fink has no=20
> idea this has been installed, then it cannot remove it later, and the=20
> user ends up with a big mess in his system.

We should build a documentation package that follows the fink guide
lines.

ITOH, I don't encourage the user to add something manually. I give him
the freedom to extend cssed in whatever way he wants.

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.
--=20
Iago Rubio  =20
- Home page    * http://www.iagorubio.com=20
- Last project * http://cssed.sourceforge.net        =20
- GPG Keyserv  * pgp.rediris.es id=3D0x909BD4DD