Hi,
> * The includes are definitely different. As Joep said, for starterpack, one include gives all libraries/features. Serial, delay, ADC, etc... This has a consequence: this "super-include" automagically sets some defaults. For instance, before including serial_software, you need to define which pins will act as TX, RX, what will be the baudrate (also set before include serial_hardware), etc... jallib doesn't provide such a super-include, because we don't want to set defaults. "Make it as simple as possible, but not simpler" as someone said... The user has to set them himself, according to what he needs. Of course, with starterpack, you could edit and modify libraries to change those defaults. But if you have several projects with different baudrates (for instance), you'll have to duplicate the lib. Now, what will happen when the lib is updated ? Lots of maintainance... Modifying libraries' code really should be avoided IMO and should be reserved for debugging or development of the lib itself. I'd say "consider librarie files as read-only". > > * enable_digital_io() is not used either (included in the target pic > library ?) enable_digital_io() is a procedure which can be found in jallib device files, designed by Rob. This procedure set all the pins as digital. Why such a procedure ? Because of the holy datasheet :) The idea with jallib is you get what's described in datasheet. And datasheet says "all pins are analog on reset". So when you "include 16f88", you get a PIC in a state as described in datasheet. You then have to decide if you want to them digital (and use enable_digital_io()) or not. > > * The delay() library is completely different, for example you don't > have a delay_1s() anymore starterpack use an extra delay lib, which add several delay procedures. Not available in jallib, but that's something we can add. > > Are there any other major differences ? And is there any way to help > make a startersguide for newbies (English and Dutch). > I was looking at the arduino.cc site, and noticed that their > 'learning' section is really good! Off coarse, in this case it get's > somewhat harder to provide a guide for - let's say - >200 µC. Yeah Arduino resources usually rocks ! :) The fact there's a common hardware makes the whole things easier. That's why we have to provide a "jaluino" board ! This is something I want to do for quite a long time, I'm sure this can be fun ! (and after all, the Arduino's ancestor was PIC-based, and used jal ! It was named something like Programma2003 or the like, designed by Massimo Banzi: http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1222887499/5). What I like with Arduino's hardware is the board is flexible: you can plug whatever you want to it (shields). We could provide a jallib shield, dedicated to prototyping and getting started, for instance. Or a servo controller shield, or a breadboard shield, or... I think such a jaluino board should embed a big fat PIC, like a 18F4550, providing enough memory, lots of pins, and amongst classical stuffs, USB features... Just some thoughts, hoping they'll turn to reality... Any suggestions ? 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 -~----------~----~----~----~------~----~------~--~---
