From: Johan K. <joh...@id...> - 2003-01-31 09:46:29
|
I would like to see a clearly visible link to the online manual, preferably directly from the cvs-tree. Is that possible? Johan |
From: Maarten B. <sou...@ds...> - 2011-08-29 18:47:43
|
Hi, I seem to remember that the website gets automatically updated (after a day) if I change some file in the sdcc-web SVN tree. Yesterday I added an HTTP header to snap_header.php but I don't see any change. Do I need to do something to force a publish action? Maarten |
From: Borut R. <bor...@gm...> - 2011-08-29 19:43:59
|
On 08/29/2011 08:47 PM, Maarten Brock wrote: > Hi, > > I seem to remember that the website gets automatically updated (after a > day) if I change some file in the sdcc-web SVN tree. Yes, it should be so. > Yesterday I added > an HTTP header to snap_header.php but I don't see any change. Do I need > to do something to force a publish action? This could be a consequence of broken build on cf-x86... Borut |
From: Bernhard H. <Ber...@be...> - 2003-01-31 10:52:01
|
> I would like to see a clearly visible link to the online manual, preferably > directly from the cvs-tree. Is that possible? We could checkout the html-documentation to the web-site with a cronjob on e.g. daily basis. That's easy. It's no longer possible to access cvs via php or cgi. Bernhard |
From: Bernhard H. <Ber...@be...> - 2003-01-31 11:16:05
|
> We could checkout the html-documentation to the web-site with a cronjob on > e.g. daily basis. That's easy. http://sdcc.sourceforge.net/doc/ |
From: Johan K. <joh...@id...> - 2003-01-31 11:42:31
|
> http://sdcc.sourceforge.net/doc/ Whoooo, Paul! Now we only need a generated ht...oc/sdccman.pdf and sdccman.html.tgz (for off-line browsing) and we can remove these redundancies from CVS. Johan |
From: Bernhard H. <Ber...@be...> - 2003-01-31 13:22:03
|
> > http://sdcc.sourceforge.net/doc/ > > Whoooo, Paul! I'm not yet happy, because we've still to define a place for the other documentation (as, ucsim). > Now we only need a generated ht...oc/sdccman.pdf and sdccman.html.tgz (for > off-line browsing) and we can remove these redundancies from CVS. Fortunately latex2html is available at the shell server. If I can make this beast working, it should be easy to rebuild the output autmatically. At the moment I've problems with latex2html. I'll check it later, until then any hint is welcome. Bernhard |
From: Johan K. <joh...@id...> - 2003-01-31 11:18:03
|
> > I would like to see a clearly visible link to the online manual, > preferably > > directly from the cvs-tree. Is that possible? > We could checkout the html-documentation to the web-site with a cronjob on > e.g. daily basis. That's easy. Also generating the html/pdf documents if the master document (sdccman.lyx) has changed (and maybe even check them in again)? Johan |
From: Bernhard H. <ber...@be...> - 2003-01-31 20:07:28
|
12:17 > Also generating the html/pdf documents if the master document (sdccman.lyx) > has changed (and maybe even check them in again)? 12:42 > Now we only need a generated ht...oc/sdccman.pdf and sdccman.html.tgz (for > off-line browsing) and we can remove these redundancies from CVS. Could you please make up your mind? Delete or commit? Bernhard P.S.: ;-) |
From: Johan K. <joh...@id...> - 2003-01-31 20:41:05
|
> 12:17 > > Also generating the html/pdf documents if the master document (sdccman.lyx) > > has changed (and maybe even check them in again)? > > 12:42 > > Now we only need a generated ht...oc/sdccman.pdf and sdccman.html.tgz (for > > off-line browsing) and we can remove these redundancies from CVS. > > Could you please make up your mind? Delete or commit? :) Everything is going so fast now, fun!. If we could have a realtime online document tree, than those is CVS would be obsolete (apart from the master doc ofcourse). Johan |
From: Bernhard H. <ber...@be...> - 2003-02-01 00:50:09
|
> :) Everything is going so fast now, fun!. If we could have a realtime > online document tree, than those is CVS would be obsolete (apart from the > master doc ofcourse). After a little hacking to get lyx running (it's not installed at SF): http://sdcc.sourceforge.net/doc/node62.html Next step: move the script from the shell-server to the CF-server. There's dvips available for creating the PDF file. Bernhard |
From: Johan K. <joh...@id...> - 2003-02-01 01:28:57
|
> > Could you please make up your mind? Delete or commit? > > :) Everything is going so fast now, fun!. If we could have a realtime > online document tree, than those is CVS would be obsolete (apart from the > master doc ofcourse). In the middle of the night I woke up with the idea that the website and the documentation should be identical! I can't think of anything on the website that shouldn't be in the documentation and vice versa. So, why maintaining them both? One source document (tree) could generate the home page, in fact being the online manual, and the offline manuals (.html.tgz, .pdf, and why not, the M$ .hlp) just in the same run. If some one e.g. adds or removes an --option, it would be reflected in all of them (assuming the master doc is edited accordingly; we should make that as easy as possible). Just a thought, now I'm going back to sleep. Johan |