> each chip to blink a led is the extreme. It may be extreme, but, you will be able to build a blink a led circuit in a matter of minutes for any pic. We do not need to focus on this however. Whenever someone wants to contribute a blink a led schematic, they may, and the same goes for other schematics.
>We decided that we shouldn't force people to choose one > single tool, everybody being used to use one specific. Nobody is forced into using anything, you can continue to use your fav program. However, the only circuit schematics that would be included in the pack are those that use an open source software of our choosing. At least this will give an option for people to contribute to schematic drawings. For those who want to continue using there other software, they will be able to open the file in the open source software and manually copy it to there software without having to design it from scratch. PDF schematic files are not clear, it is very hard to read pin names & lettering. I was looking at the Jaluino PDF, I cannot read pin names, therefore I cannot build circuit. I need to read the ICSP port pins since my programmer has these pins in a different order. >Yes that would be nice, and that would be even greater if we provide full > tutorials, step by step approach. I'm trying to this on jalliblog, and now > moving this stuff on a PDF book, as part of the release. That way users have > dedicated content they can follow when starting (or continuing) to > experiment with jalv2 and jallib. If there is a jallib standard for scematics, updating them would be easy and will help keep the book up to date. Tutorials are also a must and should be written in a document language of jallib’s choice All schematics can have an example in the schematic program, all tutorials can be written in a document software (one tutorial for each project type). Then schematics and tuturials of our choosing can be compiled together in the book & on the website each week and every time a new jallib is released. They can be organized in the book by difficulty level. We can have a BOOK_TORELEASE file. Currently we have no way of contributing to the book. Or do we? >Richard uses Orcad and Layo PCB and produces high quality > schematics & PCBs, and the end this is the most important. Open source software outputs netlists, netlists can be opened by any layout software for making PCB’s. I don’t see any need for choosing a PCB software as PCB layouts are not used as often as schematics. Matt --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
