> Putting MAX232 & friends on a breadboard is too complex IMO. Now I have a USB-to-serial converter, I'll use it on tutorials, instead of a whole main board.
of course there can be exceptions like this one. I also use a small board for max232. Since this will be needed in quite a few of the projects, we can make a max232 how-to, and mention that a board can be purchased on the net. >(and again, nothing to pay from getting schematics & PCB from my site). everything needed in the book should be in the book matt On Sep 25, 5:09 am, Sebastien Lelong <[email protected]> wrote: > > book cover will be either some text + an image, or maybe just an > > image. Image in png format. I will supply the image, it can be edited > > easily with .png > > Some text has to be kept in textual format: year, authors, even title and > subtitle. I've been able to add an image, and even a background image > (repeated in tile). Depending on what you want, I may be able to help. > > > > > >Did you also tried to write few things with it ? Using which editor ? I > > used > > Serna, multiplatform, works quite nice. > > > I am trying Serna, and I see there is a steep learning curve, I'll go > > to the tutorials. I don't think new users will ever be able to add > > pages to the book, we will have to do it for them. However, the end > > result is awsome, and I see the html is good for our website (this is > > why I am now interested in this book) > > I think it's first good to look at one tutorial, say GP2D02, to see how > sections, titles, image, etc... are done. It's then always the same, so I > guess it's not that hard... There also few tricks I'll explain in more > details if we go with DITA (xref pointing to DITA file or other type of > files, image break/inline, ...) > > > > > Another big issue I have about this book is weather or not we are > > allowed to sell or promote our own products within it. Already I see > > some at I2C part 3. As a newbie, i would look at that section and say > > "I can't make that becuase I have to buy the board". If we do not > > limit these products, the book will end out to be a big "sales pitch" > > instead of free documentation. > > I agree 100%. I did use on my board (free & open source) because I needed to > use serial. I hesitated a lot before putting photos & links (really) but by > the time I decided to use it, readers have to know where it comes from. > > My suggestion is that all projects should be based on a breadboard, > > > unless a PCB is required because of speed limitations. If a PCB is > > needed, there should be a schematic diagram of the PCB (as well as the > > PCB layout if possible). A new user should be able to read and > > understand the projects without thinking they have to buy something > > from one of us. > > Putting MAX232 & friends on a breadboard is too complex IMO. Now I have a > USB-to-serial converter, I'll use it on tutorials, instead of a whole main > board. > > (and again, nothing to pay from getting schematics & PCB from my site). > > > All other projects that require a product, or have an image of a > > product should be in it's own section near the end of the book. > > > Jaluino can have it's own section, I do believe jaluino should be in > > the book since it jallib group works on it together, however it should > > not be mixed in with the other projects. > > I consider Jaluino independent, one layer above the whole. Jal code won't > actually be the same ("include jaluino" for instance, defining pin aliases, > making things easier). Tutorials in this book are for jallib users, still a > Jaluino user (if I'm not alone) could use them. > > > > > I suppose we will need to make rules for the book, we can work out > > details like this later. If we write the book correctly, we may even > > be able to publish the book someday! > > Well I think this kind of things should be taken into account as earlier as > possible, as we did with JSG. So, the Tutorial Style Guide (TSG...) could > begin like this: > > Rule #1: don't put and promote your own products when describing a tutorial. > If really needed, this product has to be free and open source. Readers don't > have to think they'll have to buy something from us. At most, they should be > able to build it for free. > > I add these ones I consider very important, please advise > > Rule #2: put photos, and when relevant videos. It's very important for > readers to figure out how it looks like for real. Showing detailed photos > will make being able to check they have quite the same. > > Rule #3: put a schematic as needed, even if very simple. It gives an > overview of the project, and readers will constantly refer to it. > > Cheers, > Seb > -- > Sébastien Lelonghttp://www.sirloon.nethttp://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 -~----------~----~----~----~------~----~------~--~---
