Hi Matt, Having multiple books doesn't seem like a bad idea to me, provided it's consistent. Separating practice (tutorials) and theory (intro, ref) allows readers to focus on what they need.
That said, I can obviously create a "big book". In theory, I could even pick some pages from Jaluino (external URLs) if needed. In practice, this feature seems not implemented in current DITA-OT. So, it's possible. Question now is: what would be the Table Of Content ? Cheers, Seb 2009/11/24 mattschinkel <[email protected]> > My suggestion I guess is that we have many small books (jallib > tutorials, extended jal ref, jaluino tutorials, etc). Also however, we > should compile them all into one "Big book of jal". Does this sound > good? > > Seb, can you create a blank extended reference book on SVN so it can > slowly be created. maybe copy the other book and change the name to > something like "JAL+jallib Extended Code Reference", I am assuming we > may have some small jallib examples within this reference?? > > Matt. > > On Nov 23, 8:34 am, Rob Hamerling <[email protected]> wrote: > > Hi Matt, > > > > mattschinkel wrote: > > > I suppose ALIAS is only a jallib prefrence over var volitile. > > > > Hmmm, sound to me as if you think one is an 100% alternative for the > > other? That is not the case. I'm afraid you haven't fully understood the > > meaning of 'volatile'. The device files have many occurences of var > > volatile, where alias is totally inappropriate! Chapter 7 of the JalV2 > > manual describes the purpose of volatile. > > > > [Joep] > > > > > However, an extensive reference, with examples and tricks is an other > story! > > > > Programming may look like (black) magic for many people, but it is an > > ordinary craft. I would prefer the word 'techniques' in stead of > > 'tricks' when describing perfectly normal/legal ways to perform > > operations in a certain programming language. > > > > > What is the right way to go about building this extensive ref? through > > > kyle, or on our own? > > > > You have probably in mind a "JalV2 Programmer's Guide", which is > > something else than a "JalV2 Language Reference Manual". The latter > > describes the rules, the first describes how to apply rules (write a > > program that obeys the rules). > > And I think a Programmer's Guide should preferrably written by another > > author! But of course it can be in co-operation. > > > > Regards, Rob. > > > > -- > > Rob Hamerling, Vianen, NL (http://www.robh.nl/) > > -- > > 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]<jallib%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/jallib?hl=en. > > > -- 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.
