Re: [fossil-users] Asciidoc(tor) Fossil
On Sun, 17 Aug 2014 13:49:01 -0400 Ron W ronw.m...@gmail.com wrote: And it could be even easier than it is, now, per my suggested enhancement to Fossil. Where can one read about it? Sincerely, Gour -- In this endeavor there is no loss or diminution, and a little advancement on this path can protect one from the most dangerous type of fear. http://www.atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Mon, Aug 18, 2014 at 4:46 PM, Gour g...@atmarama.net wrote: On Sun, 17 Aug 2014 13:49:01 -0400 Ron W ronw.m...@gmail.com wrote: And it could be even easier than it is, now, per my suggested enhancement to Fossil. Where can one read about it? In my message in this thread on Thu, 14 Aug 2014 18:47:54 -0400 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Fri, Aug 15, 2014 at 12:55 AM, Gour g...@atmarama.net wrote: My intention was not to suggest using AsciiDoc as 'alternative' to the Fossil's Nor mine. wiki (I had enough in the past when asking for markdown support), but only if there is some simple way to make it render AsciiDoc documents (for those already using such markup) via Asciidoctor.js. And it could be even easier than it is, now, per my suggested enhancement to Fossil. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Asciidoc(tor) Fossil
Hello, the topic of the markup in Fossil is quite an old one and in the past there was a thread about using AsciiDoc markup which can be rendered with https://github.com/srackham/asciidoc-fossil-backend. Recently I've became interested (again) into using AsciiDoc feeling that markdown is simply not capable enough for our needs and that led me to discovery of Asciidoctor (http://asciidoctor.org/). Now the interesting part in regard to is is Asciidoctor.js - a fully-functional version of Asciidoctor that works in any JavaScript environment, such as a web browser or Node.js., so I wonder whether there is some possibility to make it integrate it with Fossil in order to enjoy combination of Asciidoc markup + Fossil? I also see that Asciidoc is now deployed on Github: http://asciidoctor.org/news/2013/01/30/asciidoc-returns-to-github/ and hope that mentioning it will not produce negative effects here. :-) Sincerely, Gour -- An intelligent person does not take part in the sources of misery, which are due to contact with the material senses. O son of Kuntī, such pleasures have a beginning and an end, and so the wise man does not delight in them. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, 14 Aug 2014 09:56:32 +0200 Stephan Beal sgb...@googlemail.com wrote: You can in fact do that with the JSON API. i've been serving Google Code-format wiki pages this way for a a couple years now: Very interersting! Does it mean there is nothing interesting in Asciidoctor.js to make Fossil 'speak' AsciiDoc? Sincerely, Gour -- One who sees inaction in action, and action in inaction, is intelligent among men, and he is in the transcendental position, although engaged in all sorts of activities. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, Aug 14, 2014 at 10:14 AM, Gour g...@atmarama.net wrote: Does it mean there is nothing interesting in Asciidoctor.js to make Fossil 'speak' AsciiDoc? Correct, but it also means that if you try to view those pages in the fossil wiki, they will be mangled. For those 3 sites i use only my custom front-end for the wiki and store only GoCo-format docs in the wiki. If you like, as a repayment for saving me weeks of work writing/debugging another ncurses script binding (by introducing me to termbox), we can try to get one set up for you with Asciidoc. What we'll need: First, i need to go get reacquainted with that code. i haven't touched it in... [stephan@host:~/cvs/fossil/fwiki/js/fijet]$ f-timeline -n 2 checkin [c2546ff7595d] @ 2013-01-02 16:18:00 by [stephan] branch [trunk] *CURRENT* fix(?) for wrong friendly time calculation for =26 weeks in the past. checkin [187257d5123b] @ 2012-05-05 09:50:31 by [stephan] branch [trunk] removed some debug output. in a long time. IIRC, it is capable of dispatching to renderers depending on rules (page name patterns, IIRC), but i can't seem to find proof of that at the moment. If indeed it does support that, then we can plug asciidoc in with little work. i _know_ somewhere i have an example which dispatches to a different renderer based on file type, but that might have been in a different source tree (i can't see to find an example of it in this one). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, 14 Aug 2014 10:32:20 +0200 Stephan Beal sgb...@googlemail.com wrote: Correct, but it also means that if you try to view those pages in the fossil wiki, they will be mangled. That's clear, but originally I was thinking about https://github.com/srackham/asciidoc-fossil-backend which says: https://github.com/srackham/asciidoc-fossil-backend; If you like, as a repayment for saving me weeks of work writing/debugging another ncurses script binding (by introducing me to termbox), we can try to get one set up for you with Asciidoc. You're very generous, but let's wait a bit if there is some more interest to integrate/use Asciidoc(tor) with Fossil by using Asciidoctor.js. If indeed it does support that, then we can plug asciidoc in with little work. i _know_ somewhere i have an example which dispatches to a different renderer based on file type, but that might have been in a different source tree (i can't see to find an example of it in this one). That would be really cool...the more I play with Asciidoc I see it's really capable even to the extent of writing books using it. (I read somewhere that these days it's possible for author writing book in AsciiDoc and submit it to O'Reilly.) So, rich markup + Fossil for keeping it under DVCS sounds as great combo for writers, isn't it? Sincerely, Gour -- You have a right to perform your prescribed duty, but you are not entitled to the fruits of action. Never consider yourself the cause of the results of your activities, and never be attached to not doing your duty. http://www.atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, Aug 14, 2014 at 12:24 PM, Gour g...@atmarama.net wrote: https://github.com/srackham/asciidoc-fossil-backend which says: https://github.com/srackham/asciidoc-fossil-backend; Sorry, i missed that part. i'm glad to see someone gets some use out of the wiki CLI commands (IIRC those were my first contributions to Fossil). You're very generous, but let's wait a bit if there is some more interest to integrate/use Asciidoc(tor) with Fossil by using Asciidoctor.js. Just let me know. If indeed it does support that, then we can plug asciidoc in with little work. i _know_ somewhere i have an example which dispatches to a different renderer based on file type, but that might have been in a different source tree (i can't see to find an example of it in this one). That would be really cool... _Somewhere_ (in a fossil repo, nonetheless) i've got an example of it, possibly in another source tree. It can be done, i just don't know if it's in that particular tree or not. i explicitly remember adding renderers for shell code and plain text at one point. the more I play with Asciidoc I see it's really capable even to the extent of writing books using it. (I read somewhere that these days it's possible for author writing book in AsciiDoc and submit it to O'Reilly.) So, rich markup + Fossil for keeping it under DVCS sounds as great combo for writers, isn't it? Indeed. It's called LaTeX ;). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, Aug 14, 2014 at 12:39 PM, Stephan Beal sgb...@googlemail.com wrote: i'm glad to see someone gets some use out of the wiki CLI commands (IIRC those were my first contributions to Fossil). Fossil says otherwise, though: http://fossil-scm.org/index.html/timeline?ym=2008-02n=35y=au=stephan They came soon after, though: http://fossil-scm.org/index.html/timeline?ym=2008-05n=26y=au=stephan -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, 14 Aug 2014 12:24:24 +0200, Gour g...@atmarama.net wrote: On Thu, 14 Aug 2014 10:32:20 +0200 Stephan Beal sgb...@googlemail.com wrote: Correct, but it also means that if you try to view those pages in the fossil wiki, they will be mangled. That's clear, but originally I was thinking about https://github.com/srackham/asciidoc-fossil-backend which says: https://github.com/srackham/asciidoc-fossil-backend; If you like, as a repayment for saving me weeks of work writing/debugging another ncurses script binding (by introducing me to termbox), we can try to get one set up for you with Asciidoc. You're very generous, but let's wait a bit if there is some more interest to integrate/use Asciidoc(tor) with Fossil by using Asciidoctor.js. If indeed it does support that, then we can plug asciidoc in with little work. i _know_ somewhere i have an example which dispatches to a different renderer based on file type, but that might have been in a different source tree (i can't see to find an example of it in this one). That would be really cool...the more I play with Asciidoc I see it's really capable even to the extent of writing books using it. (I read somewhere that these days it's possible for author writing book in AsciiDoc and submit it to O'Reilly.) So, rich markup + Fossil for keeping it under DVCS sounds as great combo for writers, isn't it? asciidoc sure is a very good markup language and much more capable than markdown. so it would be very nice to see it supported for wiki markup in fossil. books: I wouldn't do that, probably, since while it is quite easy to get decent pdf-formatted output it is a pain to customize it (both with the FOP and the dblatex backends) beyond very basic things. I thus quite probably still would prefer the LaTeX route for serious typesetting. but overall asciidoc is really great. just my 2c... Sincerely, Gour -- Using Opera's revolutionary email client: http://www.opera.com/mail/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, Aug 14, 2014 at 09:56:32AM +0200, Stephan Beal wrote: On Thu, Aug 14, 2014 at 9:27 AM, Gour [1]g...@atmarama.net wrote: Now the interesting part in regard to is is Asciidoctor.js � - a fully-functional version of Asciidoctor that works in any JavaScript environment, such as a web browser or Node.js., so I wonder whether there is some possibility to make it integrate it with Fossil in order to enjoy combination of Asciidoc markup + Fossil? You can in fact do that with the JSON API. i've been serving Google Code-format wiki pages this way for a a couple years now: [2]http://fossil.wanderinghorse.net/wikis/ all of those use the JSON API to serve GoCo-format pages, which then get rendered on the client side. May be it would be more simple (if possible) to just modify fossil skins related configuration (header, footer, css, ...) to use Asciidoctor.js. If it is possible for google-code-prettify for syntax highlighting, I guess it could be for Asciidoctor.js. It's only my 2 cents since I don't know much about Asciidoctor.js. note: For google-code-prettify, I use my own skin based on the google-code skin from here: http://fossil.include-once.org/fossil-skins/index That I modify to don't have to link to google-code-prettify js script from google, I've integrated it to my repository instead so it can be use on a local network without internet access.. I've also removed dependency on jquery. Regards, -- Martin G. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, 14 Aug 2014 12:39:06 +0200 Stephan Beal sgb...@googlemail.com wrote: Indeed. It's called LaTeX ;). I like LaTeX's output and used it for printed books along with LyX, but it's simply not very readable. Sincerely, Gour -- The humble sages, by virtue of true knowledge, see with equal vision a learned and gentle brāhmana, a cow, an elephant, a dog and a dog-eater. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, 14 Aug 2014 12:50:21 +0200 j. van den hoff veedeeh...@googlemail.com wrote: I thus quite probably still would prefer the LaTeX route for serious typesetting. but overall asciidoc is really great. Don't forget there is Pandoc. ;) Sincerely, Gour -- One who is not disturbed in mind even amidst the threefold miseries or elated when there is happiness, and who is free from attachment, fear and anger, is called a sage of steady mind. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, Aug 14, 2014 at 3:39 AM, Stephan Beal sgb...@googlemail.com wrote: On Thu, Aug 14, 2014 at 12:24 PM, Gour g...@atmarama.net wrote: https://github.com/srackham/asciidoc-fossil-backend which says: https://github.com/srackham/asciidoc-fossil-backend; Sorry, i missed that part. i'm glad to see someone gets some use out of the wiki CLI commands (IIRC those were my first contributions to Fossil). You're very generous, but let's wait a bit if there is some more interest to integrate/use Asciidoc(tor) with Fossil by using Asciidoctor.js. Just let me know. If indeed it does support that, then we can plug asciidoc in with little work. i _know_ somewhere i have an example which dispatches to a different renderer based on file type, but that might have been in a different source tree (i can't see to find an example of it in this one). That would be really cool... _Somewhere_ (in a fossil repo, nonetheless) i've got an example of it, possibly in another source tree. It can be done, i just don't know if it's in that particular tree or not. i explicitly remember adding renderers for shell code and plain text at one point. the more I play with Asciidoc I see it's really capable even to the extent of writing books using it. (I read somewhere that these days it's possible for author writing book in AsciiDoc and submit it to O'Reilly.) So, rich markup + Fossil for keeping it under DVCS sounds as great combo for writers, isn't it? Indeed. It's called LaTeX ;). I think asciidoc is a lowest common denominator, reasonable for many use cases, 80/20 rule compliant substitute for LaTeX with the massive benefit that the source document is usable as text documentation as-is where LaTeX source is absolutely NOT readable as stand-alone documentation by anyone other than the author. I would use an asciidoc(tor) plugin or a recipe for using asciidoc(tor) from within fossil. I already have a lot of documentation in asciidoc format. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Matt -=- 90% of the nations wealth is held by 2% of the people. Bummer to be in the majority... ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
Personally, I don't see much need for fossil to have built-in support for rendering anything much richer than its own wiki or the vanilla markdown we have now. I happily use fossil as-is for storing writing projects. Lately I write in a combination of markdown and LaTeX (usually LuaLaTeX, specifically), using Pandoc to do the needed transformation and either replacing its stock template or supplying my own outer .tex file to assemble the finished product. On 8/14/2014 5:41 AM, Gour wrote: On Thu, 14 Aug 2014 12:50:21 +0200 j. van den hoff veedeeh...@googlemail.com wrote: I thus quite probably still would prefer the LaTeX route for serious typesetting. but overall asciidoc is really great. Don't forget there is Pandoc. ;) I tried to like ASCIIDoc, but the whole FOP framework and its assumption that a giant Java application is ok just in my way too often. I do wish for finer control over tables and figures from time to time, so far I've done what I needed by at worst post-processing the TeX emitted by Pandoc and often just be dropping literal TeX in the markdown source. -- Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, Aug 14, 2014 at 3:27 AM, Gour g...@atmarama.net wrote: the topic of the markup in Fossil is quite an old one and in the past there was a thread about using AsciiDoc markup which can be rendered with I looked at AsciiDoc. In theory, it's nice, but it appears to have gathered a huge number of features over the years. It really appears to try to be LaTeX Light. Also, it uses [ and ] for purposes other than wiki links (as many wiki mark-ups use) , so using it as an alternative to either Fossil's native wiki mark-up or to mark-down would be awkward for many users. Last I checked (2 years ago?), other than the JASON API, Fossil's web interface did not provide an easy means for a client side mark-up renderer to identify the file content. While the JSON API is very nice, I still think there would be value in Fossil's generated HTML putting a clearly identifiable div around the content. Maybe like: div class=user_content filename=filename.ext Then a client side handler could easily extract both the content and the filename/extension with which it could dispatch the appropriate renderer. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, 14 Aug 2014 18:47:54 -0400 Ron W ronw.m...@gmail.com wrote: I looked at AsciiDoc. In theory, it's nice, but it appears to have gathered a huge number of features over the years. It really appears to try to be LaTeX Light. As it was already said, readability counts here. Also, it uses [ and ] for purposes other than wiki links (as many wiki mark-ups use) , so using it as an alternative to either Fossil's native wiki mark-up or to mark-down would be awkward for many users. My intention was not to suggest using AsciiDoc as 'alternative' to the Fossil's wiki (I had enough in the past when asking for markdown support), but only if there is some simple way to make it render AsciiDoc documents (for those already using such markup) via Asciidoctor.js. Sincerely, Gour -- From wherever the mind wanders due to its flickering and unsteady nature, one must certainly withdraw it and bring it back under the control of the self. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, 14 Aug 2014 14:29:55 -0700 Ross Berteig r...@cheshireeng.com wrote: Personally, I don't see much need for fossil to have built-in support for rendering anything much richer than its own wiki or the vanilla markdown we have now. I agree and as I already replied the idea is just to be able to *render* documentation written in AsciiDoc markup using Asciidoctor.js, not adding AsciiDoc as another 'built-in' markup. I happily use fossil as-is for storing writing projects. Lately I write in a combination of markdown and LaTeX (usually LuaLaTeX, specifically), using Pandoc to do the needed transformation and either replacing its stock template or supplying my own outer .tex file to assemble the finished product. The possible advantage of being able to directly render AsciiDoc documents via AsciiDoctor.js is that I could happily use my (relatively cheap) hosting and have nicely looking documents in my repo *without* the need to have/install the usual toolchain used to built html from e.g. LaTeX. I believe you agree that built-in wiki markup as well as plain markdown are not suitable for more complex docs. Sincerely, Gour -- Therefore, without being attached to the fruits of activities, one should act as a matter of duty, for by working without attachment one attains the Supreme. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] asciidoc
One of the things I would like from the documentation is that it can be provide in other formats. I haven been playing with asciidoc and a utility called pandoc. A converter from many things to many things. HTML to asciidoc is one of the possibilities. I converted 3 embedded documentation files tech_overview.wiki, delta_encoder_algorithm.wiki en delta_format.wiki and created a docbook manifest which looks like: = Several documents combined Joe Bloggs v1.0, 12-Aug-03 :numbered: :doctype: book include::tech_overview.txt[] include::delta_format.txt[] include::delta_encoder_algorithm.txt[] and a reasonable document was generated. Reasonable because 1) obvious the conversion wasn't 100 % 2) these documents were not made with an eye for book integration 3) Links were difficult to reproduce. I had to make them absolute referencing I have been playing with lyx and docbook but those solutions are using extern generated docs and allow you to show them in fossil. This could work from the embedded html documentation. Although one document had mixed html with wiki syntax and that caused some grief in the conversion. :-) A goal for me is to have an updated lyx fossil manual in fossil and be able to use that to produce a pdf. I'll ponder a bit more about that. -- Rene ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] asciidoc-fossil-backend
On Sun, Mar 25, 2012 at 03:47:00AM +0200, Stephan Beal wrote: On Sun, Mar 25, 2012 at 1:05 AM, Christopher Berardi cbera...@natoufa.com wrote: I don't see why Fossil can't use any markup engine. For example, there are a number of settable commands, such as pgp command, diff command, editor, gmerge command, etc. Would it really be that difficult to basically add a markup command so a user could use whatever markup language/engine they wanted? While the principal is a good one, i think, it would come with the cost of portability. All people who clone the repo would have to install and configure that back-end for their clone (and their platform). That is very true. However, is it really that different of a scenario than the choice of programming language used in a repo (I'm assuming the majority of Fossil users are using it for source code versioning). Anyone who clones the repo or who wishes to contribute to the project will have to install whatever compiler, interpreter, and/or buildtools that are required to make the project. -- Christopher Berardi http://www.natoufa.com/ May grace and peace by yours in abundance. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] asciidoc-fossil-backend
I don't see why Fossil can't use any markup engine. For example, there are a number of settable commands, such as pgp command, diff command, editor, gmerge command, etc. Would it really be that difficult to basically add a markup command so a user could use whatever markup language/engine they wanted? -- Christopher Berardi http://www.natoufa.com/ May grace and peace by yours in abundance. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] asciidoc-fossil-backend
On Sun, Mar 25, 2012 at 1:05 AM, Christopher Berardi cbera...@natoufa.comwrote: I don't see why Fossil can't use any markup engine. For example, there are a number of settable commands, such as pgp command, diff command, editor, gmerge command, etc. Would it really be that difficult to basically add a markup command so a user could use whatever markup language/engine they wanted? While the principal is a good one, i think, it would come with the cost of portability. All people who clone the repo would have to install and configure that back-end for their clone (and their platform). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] asciidoc-fossil-backend
Hello! In our search for adequate markup to be used for our upcoming open-source project, we stumbled upon AsciiDoc (http://www.methods.co.nz/asciidoc/) and, so far, like it very much and decided to use it instead of reST/Sphinx, markdown etc. However, the best part is that there is asciidoc-fossil-backend (https://github.com/srackham/asciidoc-fossil-backend) which enables one to write his/her documentation in AsciiDoc and still display it nicely on the site using Fossil's wiki mechanism. I was not able to add new page following documentation @github, but the following works: asciidoc -b fossil -o - asciidoc.txt | fossil wiki create AsciiDoc to add new page to the wiki, while: fossil wiki export AsciiDoc AsciiDoc.wiki created embedded doc (which seems to be favoured nowadaysa). Remembering that I was complaining a lot about Fossil' not using some 'standard' markup (reST/markdown/...), I did accept this design choise believing that Fossil offer so much more, but now I was graced by even better solution. :-) AsciiDoc is very rich semantically and able to cope with the whole books, it produces excellent PDF output (we use dblatex toolchain), generates several flavours of HTML (html4, xhtml, html5) and can be used for generating man pages as well as EPUB, DocBook output etc., but it is still possible to get decent Fossil wiki output without putting too much weight on the server by installing DocBook toolchain tools. I did not find any post about this backend here, but only in the AsciiDoc mailing list, so hope it might be of some use for Fossil users. Sincerely, Gour -- One who knows the transcendental nature of My appearance and activities does not, upon leaving the body, take his birth again in this material world, but attains My eternal abode, O Arjuna. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 signature.asc Description: PGP signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] asciidoc-fossil-backend
On Thu, Mar 22, 2012 at 03:12, Gour g...@atmarama.net wrote: Hello! In our search for adequate markup to be used for our upcoming open-source project, we stumbled upon AsciiDoc (http://www.methods.co.nz/asciidoc/) and, so far, like it very much and decided to use it instead of reST/Sphinx, markdown etc. However, the best part is that there is asciidoc-fossil-backend (https://github.com/srackham/asciidoc-fossil-backend) which enables one to write his/her documentation in AsciiDoc and still display it nicely on the site using Fossil's wiki mechanism. Gour, could you, please, provide a demo so that one can see AsciiDoc + Fossil in action. --Leo-- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] asciidoc-fossil-backend
On Thu, 22 Mar 2012 09:01:17 -0400 Leo Razoumov slonik...@gmail.com wrote: Gour, could you, please, provide a demo so that one can see AsciiDoc + Fossil in action. http://fossil.atmarama.net/cgi-bin/ascii-fossil.fsl Sincerely, Gour -- One is understood to be in full knowledge whose every endeavor is devoid of desire for sense gratification. He is said by sages to be a worker for whom the reactions of work have been burned up by the fire of perfect knowledge. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 signature.asc Description: PGP signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] asciidoc-fossil-backend
Am 22.03.2012 15:39, schrieb Gour: On Thu, 22 Mar 2012 09:01:17 -0400 Leo Razoumovslonik...@gmail.com wrote: Gour, could you, please, provide a demo so that one can see AsciiDoc + Fossil in action. http://fossil.atmarama.net/cgi-bin/ascii-fossil.fsl I'm also very interested in a demonstration backend for using a different wiki markup language. There is a blog post about the AsciiDoc-fossil-backend which describes it in more detail: http://srackham.wordpress.com/2011/08/30/fossil-backend-for-asciidoc/ It seems, though, that the AsciiDoc-Backend simply translates text from AsciiDoc-Markup to Fossil-Markup. There is no real integration in fossil, and it seems that it can not be used from within fossil as a markup substitute. @Gour: Is that correct, or did I miss something here? So far, fossil is the almost perfect distributed wiki and note collection system (distributed, portable, integrated HTTP-Server, offline, MathJax-compatible, stable, supported). The only drawback is the wiki syntax, which is somewhat limited. Some way of changing that markup would be very, very appreciated. I'm currently trying my luck with editing the fossil source code, but this is a less then optimal solution (as forking breaks portability a bit, and doesn't sync the markup between the repositories). Maybe including some (sandboxed) scripting language interpreter in fossil would help - one could then change the markup script similar to the Header/Footer/CSS. Of course, I might be missing some obvious solution, so correct me if I'm wrong :) Cheers Eph ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] asciidoc-fossil-backend
On Thu, Mar 22, 2012 at 9:52 AM, Ephrim Khong dr.khong+fos...@gmail.comwrote: Am 22.03.2012 15:39, schrieb Gour: On Thu, 22 Mar 2012 09:01:17 -0400 Leo Razoumovslonik...@gmail.com wrote: Gour, could you, please, provide a demo so that one can see AsciiDoc + Fossil in action. http://fossil.atmarama.net/**cgi-bin/ascii-fossil.fslhttp://fossil.atmarama.net/cgi-bin/ascii-fossil.fsl I'm also very interested in a demonstration backend for using a different wiki markup language. There is a blog post about the AsciiDoc-fossil-backend which describes it in more detail: http://srackham.wordpress.com/**2011/08/30/fossil-backend-for-**asciidoc/http://srackham.wordpress.com/2011/08/30/fossil-backend-for-asciidoc/ It seems, though, that the AsciiDoc-Backend simply translates text from AsciiDoc-Markup to Fossil-Markup. There is no real integration in fossil, and it seems that it can not be used from within fossil as a markup substitute. @Gour: Is that correct, or did I miss something here? So far, fossil is the almost perfect distributed wiki and note collection system (distributed, portable, integrated HTTP-Server, offline, MathJax-compatible, stable, supported). The only drawback is the wiki syntax, which is somewhat limited. Some way of changing that markup would be very, very appreciated. I'm currently trying my luck with editing the fossil source code, but this is a less then optimal solution (as forking breaks portability a bit, and doesn't sync the markup between the repositories). Maybe including some (sandboxed) scripting language interpreter in fossil would help - one could then change the markup script similar to the Header/Footer/CSS. Of course, I might be missing some obvious solution, so correct me if I'm wrong :) What about using markdown? https://chiselapp.com/user/zot/repository/fossil-pagedown/doc/pagedown/README.wiki Bill ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] asciidoc-fossil-backend
On Thu, Mar 22, 2012 at 3:52 PM, Ephrim Khong dr.khong+fos...@gmail.comwrote: I'm also very interested in a demonstration backend for using a different wiki markup language. http://fossil.wanderinghorse.net/repos/fwiki/editor/ (click on the README link in the left menu for details) That demo currently uses the fossil wiki parsing back-end, but now that the core is working more or less how i want, the next step is to add a client-side renderer (or multiples - we could use client-side rules to render different wiki pages differently). i hope to get a version done this weekend which uses the Google Code wiki syntax (my personal favourite). AsciiDoc sounds intriguing, though, and i will also be looking for a JS implementation of it. i have all the code to handle the client-side rendering, i just have to plug it in to the fossil back-end (it currently uses a custom back-end using a JSON API very similar to fossil's, and the port will be straightforward). breaks portability a bit, and doesn't sync the markup between the repositories). Maybe including some (sandboxed) scripting language interpreter in fossil would help - one could then change the markup script similar to the Header/Footer/CSS. AFAIK there is a branch which integrates jimtcl into fossil, allowing the full range of tcl features via the built-in th1 script language. i thought this had made its way to the trunk, but i don't remember for certain. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] asciidoc-fossil-backend
On Thu, 22 Mar 2012 15:52:12 +0100 Ephrim Khong dr.khong+fos...@gmail.com wrote: It seems, though, that the AsciiDoc-Backend simply translates text from AsciiDoc-Markup to Fossil-Markup. Correct. There is no real integration in fossil, and it seems that it can not be used from within fossil as a markup substitute. Well, considering that even Fossil itself is moving/moved towards embedded docs, I do not see a problem using AsciiDoc as markup for our documentation, keep 'em as source under Fossil and use ascii-fossil backend to render them on the server without any need for heavy Docbook-based toolchain. Sincerely, Gour -- One who is able to withdraw his senses from sense objects, as the tortoise draws its limbs within the shell, is firmly fixed in perfect consciousness. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 signature.asc Description: PGP signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] asciidoc-fossil-backend
On Thu, 22 Mar 2012 16:15:07 +0100 Stephan Beal sgb...@googlemail.com wrote: AsciiDoc sounds intriguing, though, and i will also be looking for a JS implementation of it. It is indeed...very capable to write complete books with index, bibliography, glossary...plus rich semantic. I like it much more than reST...Markdown is, anyway, not the same league. Otoh, I'm not aware of any JS implementation 'cause it's very much tied to DocBook. Iow, AsciiDoc has very rich markup and it's not, imho, just question of rendering. Sincerely, Gour -- What is night for all beings is the time of awakening for the self-controlled; and the time of awakening for all beings is night for the introspective sage. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 signature.asc Description: PGP signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] asciidoc-fossil-backend
On Thu, March 22, 2012 3:58 pm, Gour wrote: On Thu, 22 Mar 2012 16:15:07 +0100 Stephan Beal sgb...@googlemail.com wrote: AsciiDoc sounds intriguing, though, and i will also be looking for a JS implementation of it. It is indeed...very capable to write complete books with index, bibliography, glossary...plus rich semantic. I like it much more than reST...Markdown is, anyway, not the same league. Otoh, I'm not aware of any JS implementation 'cause it's very much tied to DocBook. Iow, AsciiDoc has very rich markup and it's not, imho, just question of rendering. Asciidoc is written in Python, and seems to depend internally on pattern-matching, templates, and naming conventions. The scope of its markup was (as far as I can tell) determined by the need to produce Docbook output, but structurally, Docbook is just another back-end. I can't see it being easy to rewrite in JS though - Perl or Tcl possibly, but that's not much help. Personally I have no problem with saying, this is my documentation source (in Asciidoc markup), from which I might build html or PDF or manpage, but also Fossil-compatible markup so that the same documentation from the same source can also be nicely-formatted embedded documentation. Even though I am normally against checking in built files. I think this is about embedded documentation more than about wiki pages, i.e. the latter are not documentation, just information exchange among developers. Eric -- ms fnd in a lbry ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] asciidoc-fossil-backend
On Thu, Mar 22, 2012 at 11:16, Gour g...@atmarama.net wrote: On Thu, 22 Mar 2012 15:52:12 +0100 Ephrim Khong dr.khong+fos...@gmail.com wrote: It seems, though, that the AsciiDoc-Backend simply translates text from AsciiDoc-Markup to Fossil-Markup. Correct. I think it would be better to produce HTML from AsciiDoc and set fossil wiki to Use HTML as wiki markup language from Admin-Configuration. Full HTML is so much more powerful than what fossil wiki syntax allows. --Leo-- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] asciidoc-fossil-backend
On Thu, March 22, 2012 11:01 pm, Leo Razoumov wrote: On Thu, Mar 22, 2012 at 11:16, Gour g...@atmarama.net wrote: On Thu, 22 Mar 2012 15:52:12 +0100 Ephrim Khong dr.khong+fos...@gmail.com wrote: It seems, though, that the AsciiDoc-Backend simply translates text from AsciiDoc-Markup to Fossil-Markup. Correct. I think it would be better to produce HTML from AsciiDoc and set fossil wiki to Use HTML as wiki markup language from Admin-Configuration. Full HTML is so much more powerful than what fossil wiki syntax allows. It's already pretty much Asciidoc's html4 backend wrapped in nowiki. Eric -- ms fnd in a lbry ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
