> > This is really, really something you guys should consider before moving to > OO documents. Having documentation in ASCII format is why it's possible to > put it under version control, with diff'ing and merging feature, etc... > Imagine jal code couldn't be diff'ed and merged... >
Well, that is a good reason for other solutions than OpenOffice. Still, the one who created the jallib blog and have a google account, can have access at Google Docs and can create the desired Jallib book in OpenOffice format and can share it. It can invite people to edit and can be made public for reading. Is online available and can be edited online. I think this is the only approach regarding to OpenOffice docs... Once is good enough as a 0.x version, can be exported (locally) in pdf and as OpenOffice native format and made available for download in jallib code or discussion group. Regards, Vasi --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
