[prev in list] [next in list] [prev in thread] [next in thread] 

List:       netsaintplug-devel
Subject:    Re: [Netsaintplug-devel] plugin parameters etc
From:       Hugo Gayosso <qztf7k () powertrain ! mpg ! gm ! com>
Date:       2000-07-20 14:56:25
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

While doing some cleaning, I found this mail, and because I will try
to upgrade the guidelines today (was going to do it yesterday) I think
I should ask you what is out of sync, and which changes should I
apply?

Karl already sent me an e-mail with some issues, but I haven't
upgraded them yet.

Greetings,

Jacob Lundqvist <jaclu@galdrion.com> writes:

> Now I'm confused.
> 
> >From the doc I was pointed to this link:
> 
> http://netsaintplug.sourceforge.net/doc/developer-guidelines.html
> 
> I did very option exactly as requested there, and it took me some time
> to double-check and debug that every option was working ok. Then you
> yourself disagree on (almost) everything!
> 
> Still, I agree with you that it's a good thing if plugins try to behave
> the same, so I'l change as requested, no problem! Hopefully I'l be able
> to do it today.
> 
> I realy think that the plugin development guidlines should be updated to
> indicate the kind of comments actually expected. 
> 
> In the current state they do more harm than good, and should propably be
> removed. Had they not been around, I had just browsed the code of other
> plugs, and saved myself a few hours :(
> 
> Are they out of date or are you and the maintainer of that page out of
> sync? ;)
> 
> >BTW, when this gets added to core (and that could be soon based on your
> >efforts to comply with the plugin standards, the make process will
> >substitute the correct path for the python execuatble through a rule
> >making <plugin> from <plugin>.py -- so the source should be suffixed
> >.py, rather than unsuffixed, in order to make the unsuffixed file to be
> >installed. Make sense?
> 
> Yes sure!
> 
> I didn't want to scare all you c-coders out there, so I removed the .py
> sufix so that people wouldn't get confused. In the future I'll deliver
> it as a .py
> 
> 
> A request:
> I'd like to extract part of the plugin (like the Task and
> timeout_handler classes) to separate py files. Would it be possible to
> add a 'lib' or similar directory to the distribution, where one could
> put class-files? Maybe even lib/python and lib/perl
> 
> Actually I'm doing some more py-plugs, so I'd really like to have a lib
> or similar for reusable code.
> 
> 	regards /Jacob Lundqvist
> 
> ----
> You can always tell as Swede, but you can't tell him much!
> 
> _______________________________________________
> Netsaintplug-devel mailing list
> Netsaintplug-devel@lists.sourceforge.net
> http://lists.sourceforge.net/mailman/listinfo/netsaintplug-devel
> 

- -- 
Hugo Gayosso
Support the Free Software Movement!
GNU Project <http://www.gnu.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE5dxMZx2JZtTN6co8RAijJAJ9EpW+BJoYsmkFTBBx++4RNArDenQCg70BN
nhOdY8wPN2FaIqxmNq61VZg=
=4lHH
-----END PGP SIGNATURE-----

[prev in list] [next in list] [prev in thread] [next in thread]