> > > >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. >
>From what I understand & read, Eagle and Kicad are the ones being mostly used. Eagle isn't open source but free, widely used, lots of source of information, a must. That said, Richard uses Orcad & Layo PCB for Jaluino boards. These are the tools he knows the best, and he produces high quality schematics and boards (can you say more about not being able to read pin names ? I can zoom 400%, it displays perfectly). So why would we bother him learning a new tool right now ? This is not a priority for now IMHO. > > >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 > That seems to be DITA. > > 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. > This BOOK_TORELEASE file would actually be one or more ditamap files (a way to aggregate different content, highly flexible. See the tutorial book, work in progress: doc/dita/tutorials/*) About compiling doc, that's the idea, and that's why we need a documentation tool, and not just word. Write some content in one place (a XML file, using DITA format), and produce different output, one being the website (I still need to figure out what is the standard way to put content on Drupal , automatically using a script). > Currently we have no way of contributing to the book. Or do we? > First, everybody should raise his hand and say "yes I agree to use DITA" (or "no DITA sucks, here's what I suggest: ..."). Then, once we have the doc tool, we can start. As this is a huge (again, huge) task, things have to be organized, all things are very fuzzy, just like SVN at jallib first days. So, I suggest to "just" produce content, like I'm currently doing with tutorials I wrote from jallib blog. With DITA, we can organize content the way we want. Sure things will have re-organized, again and again, until we can reach a balance. We'll also have to refactor documentation, just like we refactor code. But for now, I'd say doc & content needs to be centralized in jallib SVN, using a format, DITA. You could, for instance, write a tutorial (maybe several parts) explaining how to drive a hard disk with jallib. With schematics, and photos (this is important to show how it looks like). This could be integrated to the "Tutorial Book" (see http://jallib.googlecode.com/svn/trunk/doc/dita/tutorials/tutorials.pdf) 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 -~----------~----~----~----~------~----~------~--~---
