We need a app store or cpan !

[winger]

We need to submit code and search script code in a very convenient place.

These codes can be very easily applied to the actual work.

Now everyone each write their own.

I think we need a CPAN or an appstore.

http://search.cpan.org/">//http://search.cpan.org/

[cormullion]

When you say that "everyone is writing their own", are you hoping to see a central repository for individual contributions, or for some (more) collaboration on shared projects, or both?



In the past newLISP code has been developed mainly by individuals and shared publicly in different places, rather than developed collaboratively.  A few have made it into the official release. There are a few newLISP projects on GitHub, which is ideal for collaboration, although also ideal for fragmentation.

[winger]

No accumulation No Future

[TedWalther]

I think you are right, winger.  What would a newLISP CPAN include?  What would it look like?  Lutz already links to third party modules.  But people write what works, then the language evolves, and old stuff breaks.  There needs to be a versioning system for modules/programs I guess.  Or a convention for versioning.



Also, the existing modules need more intelligence about loading libraries.  Every time a dynamic library in Linux gets bumped in version number, the newLISP module has to be updated to know about it.

[kanen]

I'm massively in favor of this.



Something that would allow newLisp install modules into the current "NEWLISPDIR" + /modules directory if they didn't already exist there.



While I'm wishing, I'd add versioning to the modules, so we know if one has been updated.

[TedWalther]

Yeah, and modules could check the version of newLISP when they load,  and stop loading if the newLISP version is too high or too low for that module.



For there is the library versioning problem



And the module versioning problems

a: version of newlisp the module works with

b: version of the module itself



This "NPAN" framework should be easy enough to do in newLISP itself.



Maybe ~/.newlisp/modules should be a directory default to check for modules?  I have a custom "mime.lsp" module I use for various things.  Because MIME is such a handy serial data exchange format, beats the pants off XML.