> > > > "project" is good. Yes, "project" without a "s". Makes sens. Maybe more > than > > "jalapp" ;) > project is good and projects is better, see below ;)
"project" follows what's already there: everything in singular. But I can live with "projects" too... > > We have the compiler, jaledit, the libs and examples as part of the > release. For us, we also have tools, board files and test files. > What we are looking for is a place for stuff that airlines call > odd-shape luggage - stuff worth having but not fitting in an other > category. OK :) > > My suggestion is to create a projects folder and in there a subfolder > for each project. This subfolder should contain all files releated to > this project (except for the jallib libs etc.) and the distribution > should maintain this structure (or convert the subdirs into zips or > alike). OK here too ! > > So yes, it should be jal related. Mostly it would contain a jal > source, along with other files (like schematics, pcb design, pc > program source & exec etc. And it should have documentation! > I can imagine there could be projects without jal code, related to > tooling. Like using eclipse with jal. By extend, there could be many, many things. Which is good. But... remember this is under our SVN. Only jallib committers can upload their code. I think this kind of projects concern a larger public, I mean lots of people can share their work, far easier than building libraries. If many should go there (which is good, again), we may need to give access to SVN for lots of people. I wonder if this is good ! (this is a real question, I've no definitive answer here) > > For my editor (ultraedit) I also have some jal-specifc stuff, but I > doubt that this has enough added value to qualify as a project. Let's take another example. I'm currently working on interfacing my DC motor controller board, building a GUI with Pure Data. This is fun, btw. So, there's jallib inside, I could upload my board/code to this project map. But what about other related tools, namely the GUI ? It's an important part, but can't be put in project, because there's a lot of dependencies, this time not related to jallib. Hope you've guess what I mean: this is about related tools/executable that comes with each project, which may not have their place in this repos, just because it's not pure jallib, and because this will become a junk room. Do we need another repos, open to everyone ? Or, again how do we decide which project is eligible to this "project(s)" map ? Next thing to come: servo controller board (I hope to have soon time for this). Typically, this project will produce schematics & code. But also a GUI, I hope, to control and configure the whole. Schematics & code can surely go to "project" map. What about the GUI ? Should it also go there ? Should we never provide external tools/execs ? Who will find the truth in this secret mystery ? Cheers, Seb -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
