Hi Vasile,
> Sorry, maybe the word complex is better. It was just an admirative remark. > > For a better understanding, the initial Jal purpose was to > start with microcontrollers with a minimum programming experience, for > people of which programming is not the fist job. It was in 1999. > I'm following the jal evolution (with some pauses) since 2000. > I have created many projects in jal (I guess more than 100), including some > in jalV2 with I'm struggling right now with a large project (60pcs after > prototyping). I've noticed is easier to design and prototyping directly with > SMD's as long you can see with your own eyes. This last project is the first > one after 10 years with through holes, the rest was SMD. > > Just few words about SMD, quite out of topic: the only time I tried to solder SMD was when trying to build a USB-to-serial adaptor. I had to solder a FTDI. That was a complete disaster. I may not have the right tool (soldering iron too hot or not hot enough), my soldering wire (?) was too hard to melt (Pb-free), well a disaster... > > My opinion, as a hardware engineer ( playing with software in his spare > time) the essence of a good library pack is not the speed of upgrading but > the completion of documentation and examples about using those. Even some > bugs aren't so important as long you catch them once. > > For example, some people are still learning old jal, just because the > compiler is deeply explained and there are available a lot of examples, even > JALV2 is one class above. > Documentation issues are a big topic these days, we all know we have to be better on this side. We actually did write documentation, sure not enough, but most importantly, not well organized, dispatched here and there. We're also working on building a dedicated website, when things are well centralized and well organized, easy to access and follow by beginner. (I also think we need to select the appropriate tool to write documentation, so it's not a pain to maintain, and one won't write a thing twice. For instance one article can be used in a blog, but also in a tutorial and in a book. Yet there can be only one version, the pristine source. Doc also has to be versionned, just like code. End of parenthesis) For detailed tutorials, which I think is accessible for a beginner, see also jalliblog (http://jallib.blogspot.com/) > > I hope I didn't upset anyone, it wasn't my intention. Maybe the Jaluino > developers will take something from this experience about designing the > board and mostly, describing how it works and howcan be used with a library > pack.. > This is the goal of Jaluino: providing a common yet flexible hardware, everyone can build, as a "educational"/learning board, following detailed tutorials. And (provide a way to) share hardware design, as we now have a way to share software efficiently. > Cheers, Seb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
