Hi guys, A discussion started at jal website group, talking about jal product names. I derived from product names to a kind of description of a "jal stack". I move this discussion here, the better place I guess.
[Seb] >> I'm in favor of using jal* derived names, I guess this is something about marketing. jallist, jallib, jaluino, jaledit, >> jalpack, etc... "jaluino" is more sexy than "protoboard", even if protoboard is more meaningful. But once you've clicked >> on jaluino, you know what this is about. >> >> Idea: jal-* => jalstar (or jalstack), a full stack used to have fun with PIC microcontroller Here I explain more about what I have in mind. As I said to Matt in the origianl discussion, it's brainstorming with myself so don't expect meaningful things :) So... - jalv2 is the compiler - on top of jalv2, you have libraries to handle any PICs and hardware configuration. This is jallib. - on top of jallib (and because it's highly flexible, let's say that again :)), you can start specialization, and provide more hardware specific libraries, where hardware configuration is setup for you. This is the frontier between jallib and software part of jaluino: providing jaluino libs, so users don't have to know what's going on under. - now you leave the software world and dive into the hardware one. Jaluino board. - with shields, you continue to specialize by providing application specific shields. And also application/software code to run these applications. - all of this can be accessed through an IDE. This is jaledit (I hope it'll be cross-platform). - simulation is done using picshell (crap ! this one doesn't start with "jal" !) - beside jaluino libraries, you can also imagine dynamic interpreters (search "jalstamp" into jallib group). Using a command line interface (CLI), through serial, you can dynamically access your PIC, act on it, set parameters, read values (dive into its guts). - on top on this CLI, you can now build a GUI, to control and monitor PIC state (I have some ideas here, using Pure Date for instance. Search for Arduino and Pure data too. Also involved is a very nice protocol easy to implement I think: OSC -- Open Sound Control --). This GUI should actually be a toolkit: you can dynamically build it, and add elements, connect them, to retrieve data from your PIC and send commands. I've prototyped this with Pure Data (to control an RC tank), this is very fun and extremely powerful I think. All of this is build with layers, one layer using the other layer below. Just like a stack. Web Services specifications are often refered as WS-* (WS-<anything>), people sometime name this WS-deathstar (because of WS complexity). So jal-*, "jalstar", is a stack (hopefully less complex than WS). You choose where you want to start from: lower layer, or higher. This is an overview of how things interact with other. And also a nice marketing name ? Also a kind of roadmap I guess... If you have more brainstorming juice, please mix ! 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 -~----------~----~----~----~------~----~------~--~---
