2009/2/28 Sebastien Lelong <[email protected]>:
> "project" is good. Yes, "project" without a "s". Makes sens. Maybe more than
> "jalapp" ;)
project is good and projects is better, see below ;)

>
> How do we decide something should go to projects or not ? Should this be
> 100% jallib related ? Can we say that, if there's something external needed
> (like a script, an app, etc...) it shouldn't go there ? My worry is this
> "project" map shouldn't become a place where we could put every piece of jal
> code (something a like a carryall or a junk room -- well, I needed
> wordreference.com on these --). Or maybe that would be good ? What's your
> opinion guys ?

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.
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).
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.
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.


My 2c
Joep

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to