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
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
