Hi Leslie, On 11/28/09 10:15, Leslie P. Polzer wrote: > Venkat, you've posted a link showing that you've integrated the > current HTML draft of the documentation into the Weblocks wiki hosted > by you. > > Do you intend to add new content and edit it there? If yes then we > should probably agree on a good way to have a common base format for > the manual. > > At the moment we have two approaches: > > * the one I've used so far has the canonical content in source text > files annotated with some formatting understood by the stx2any > document processor. > > * HTML as source format in your Wiki > > I explicitly invite all other readers to participate in this > discussion.
I've just copied and pasted into the WYSIWIG editor in Tikiwiki. Which, imo, sucks in many ways. There is the wiki structure and syntax that it supposedly works with - you can create a /structure/ that acts like a table of contents and then fill it back out. The last layout system that I used that I liked was LaTeX. Its been a while :) That said, on the CMS that runs the Rayservers site that we wrote, HTML edited by Tinymce works well for the simple content in it. http://tinymce.moxiecode.com/ There is a new version of the WYSIWYG editor that Tikiwiki uses that is out. I have not yet tried to see if it will work with the current install of Tikiwiki. http://ckeditor.com/ It seems that the fckeditor is specialized to comprehend wiki syntax. I would say that we should just use the Tikiwiki structure in their WYSIWYG editor which means that content can be simply generated. >From using it for a few articles the content in the editor when saved appears >to become doublespaced. This is annoying. The GBBopen hyperdoc is easy to use. The summary of what I guess I'm trying to say is that we should just post HTML to the wiki and then work out a better documentation method later, perhaps writing a lisp based system. We need content first, the structure will evolve from there. Sort of like extreme programming.... and I love the way you have the auto-generated documentation. Off-topic, but relevant is our economic security. The world as we know it will change dramatically in the next two years. I've known this for many years: http://www.rayservers.com/blog/the-dow-gold-ratio---the-most-reliable-prognosticator-of-our-time Why I'm doing what I am doing and how I'm going about it touches every aspect of computer programming - databases, lisp, DHTs, crypto. The biggest monopoly of our time is not Windows - it is SAP. To replace centralized database centric programming with a distributed system where the network is the database is my goal. The system has to be capable of reasoning. Ambitious, yes. So what does this have to do with documentation - lets put up whatever we think on to the wiki, I can instantiate a forum so discussions get indexed. The Gentoo forums, and Ubuntu forums were great ways to get problems sorted into threads. Lets write article and post. Put up a blog. I know there are some freedom thinking lisp programmers. Perhaps there are more of them than I know. Business and making money - there is the entire crashing centralized economy to take over. People who can program Lisp are capable of abstract thinking. There should be plenty to go around. https://freedom.rayservers.com/forum10 - a forum for Weblocks. Cheers, ---Venkat. -- You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en.
