From: Francesco M. <f18...@ya...> - 2006-02-12 20:30:42
|
Hi, since build system is now quite stable I'd like to write a few notes about it for users. I see that there are some .txt files in docs\ but before updating them (I would touch only building.txt anyway), I think we should decide if we want to keep them as plain TXT file or choose HTML (wxArt2d has a nice install.html: http://cvs.sourceforge.net/viewcvs.py/*checkout*/wxart2d/wxArt2D/install.html)... Just let me know, Francesco |
From: klaas.holwerda <kho...@xs...> - 2006-02-12 21:21:11
|
Francesco Montorsi wrote: > Hi, > since build system is now quite stable I'd like to write a few notes > about it for users. > > I see that there are some .txt files in docs\ but before updating them > (I would touch only building.txt anyway), I think we should decide if > we want to keep them as plain TXT file or choose HTML (wxArt2d has a > nice install.html: > http://cvs.sourceforge.net/viewcvs.py/*checkout*/wxart2d/wxArt2D/install.html)... > > > Just let me know, please please HTML, it is so much better. And for editing www.nvu.com is free and good. Klaas |
From: John L. <jla...@gm...> - 2006-02-13 05:13:54
|
On 2/12/06, klaas.holwerda <kho...@xs...> wrote: > Francesco Montorsi wrote: > > > Hi, > > since build system is now quite stable I'd like to write a few notes > > about it for users. > > > > I see that there are some .txt files in docs\ but before updating them > > (I would touch only building.txt anyway), I think we should decide if > > we want to keep them as plain TXT file or choose HTML (wxArt2d has a > > nice install.html: > > http://cvs.sourceforge.net/viewcvs.py/*checkout*/wxart2d/wxArt2D/instal= l.html)... > > > > > > Just let me know, > > please please HTML, it is so much better. And for editing www.nvu.com is > free and good. I dunno, I think everyone else always just uses text files, in fact I can't remember ever using a project that has them in any other form. They're a lot easier to read on the command line. I don't envision a large amount of documentation for wxLua, just build, install, usage, and differences to the wxWidgets c++ docs. -John Labenski |
From: k. h. <kla...@nl...> - 2006-02-13 07:08:37
|
John Labenski wrote: >On 2/12/06, klaas.holwerda <kho...@xs...> wrote: > > >>Francesco Montorsi wrote: >> >> >> >>>Hi, >>> since build system is now quite stable I'd like to write a few notes >>>about it for users. >>> >>>I see that there are some .txt files in docs\ but before updating them >>>(I would touch only building.txt anyway), I think we should decide if >>>we want to keep them as plain TXT file or choose HTML (wxArt2d has a >>>nice install.html: >>>http://cvs.sourceforge.net/viewcvs.py/*checkout*/wxart2d/wxArt2D/install.html)... >>> >>> >>>Just let me know, >>> >>> >>please please HTML, it is so much better. And for editing www.nvu.com is >>free and good. >> >> > >I dunno, I think everyone else always just uses text files, in fact I >can't remember ever using a project that has them in any other form. > > I can, you are working to much on Linux. On windows it is hlp/chm or html. But i went through my tool dir, even many linux orginating tools use often html or redirect through a readme file to docs/index.html. We can not do hlp/chm but for platfrom independent tooling html is no problem. >They're a lot easier to read on the command line. > > Like i say ;-) >I don't envision a large amount of documentation for wxLua, just >build, install, usage, and differences to the wxWidgets c++ docs. > > I wish there was some more. Like how it is organized internal , source documentation in doxygen. I still vote for HTML. Regards, Klaas -- Unclassified |
From: John L. <jla...@gm...> - 2006-02-14 04:52:49
|
On 2/13/06, k. holwerda <kla...@nl...> wrote: > >>please please HTML, it is so much better. And for editing www.nvu.com i= s > >>free and good. > > > >I dunno, I think everyone else always just uses text files, in fact I > >can't remember ever using a project that has them in any other form. > > > I can, you are working to much on Linux. > On windows it is hlp/chm or html. > But i went through my tool dir, even many linux orginating tools use > often html or redirect > through a readme file to docs/index.html. > We can not do hlp/chm but for platfrom independent tooling html is no > problem. > > >They're a lot easier to read on the command line. > > > Like i say ;-) > > >I don't envision a large amount of documentation for wxLua, just > >build, install, usage, and differences to the wxWidgets c++ docs. > > > I wish there was some more. Like how it is organized internal , source > documentation in doxygen. > > I still vote for HTML. Allright, I'll try nvu. I've tried in the past to use a WYSIWYG to write really simple, clean, readable HTML and found that the Mozilla editor was the best, but every now and then it would really garble things up. I think they can get very confused and stick in millions of   and trash the layout of tables. The HTML they generate is fine, but it's completely unreadable as text. Regards, John Labenski |
From: Francesco M. <f18...@ya...> - 2006-02-14 12:07:25
|
Hi, John Labenski ha scritto: > Allright, I'll try nvu. I've tried in the past to use a WYSIWYG to > write really simple, clean, readable HTML and found that the Mozilla > editor was the best, but every now and then it would really garble > things up. I think they can get very confused and stick in millions of >   and trash the layout of tables. The HTML they generate is fine, > but it's completely unreadable as text. you're right; I've no good experience with XHTML WYSIWYG editors, at least on windows; that's why I usually prefer writing XHTML by hand. However I'm trying to use NVU on my linux... I've added a first draft of install.html to the DOCS directory; it doesn't look bad... Francesco |