Re: [fossil-users] The case for Markdown (yes, I rtfm)
On Wed, 5 May 2010 14:48:33 +0200, Gour g...@gour-nitai.com wrote: On Wed, 05 May 2010 13:09:34 +0200 renework == renew...@xs4all.nl wrote: renework I'm not clear for what you are going to use this for. I'll try to explain... renework If for writing documentation, say a user manual. Then You renework don't want to use fossil markup. I'd like to use it for user manual. You get into trouble if it is contained in two wiki pages. Basically your are better of to write two markdown files and a Makefile. Which you can do in Darcs anyway. renework (I use markup in a general sense not a specific product) No problem. Product is 'markdown'. ;) renework You might want to use fossil as a scm for storing your renework documentation files. That is possible. renework (Not if you're using native word format :-) Fortunately, I'm not. After having bad experience with Lotus Word Pro many years ago (while using OS/2) I've decided not to use binary format for my writing ever again. renework If you would use say asciidoc renework http://www.methods.co.nz/asciidoc/ as fossil markup. renework Then generating A wikiPAGE could take A long time. Asciidoc renework is overkill for that purpose. I don't like Asciidoc and Docbook toolchain. Otoh, Markdown is quite readable markup, mature, with many implementations etc. I looked up markdown and it is a 35Kb perl source file. But you are in luck there is a c implementation http://www.pell.portland.or.us/~orc/Code/discount/ Now find someone to incorporate it into fossil. renework If you would enhance wiki pages for wiki purposes then a renework markup containing more functions is called for. Yes, I'd also like enhanced capabilities for wiki pages and I see that it's even on Fossil's TODO list: Ability to attach image files (GIFs and JPEGs) and refer to these in wiki pages. Enhance wiki to the point where it can host the existing fossil documentation. (http://www.fossil-scm.org/index.html/wiki?name=To+Do+List) renework Richard wants to keep his past documentation efforts. I fully understand that, but if he would decide to support Markdown, I'd be ready to convert all the Fossil docs from the present wiki to it. renework Assuming that the creole functionality satisfies your needs. No interest for creole since I'm involved with Haskell and there is very nice Pandoc allowing me to use Markdown as single-source markup capable to convert to plethora of end formats (HTML, PDF...) renework However nice it is to ramble along, The question is still renework what do you want to do with the markup? To use (more) 'standard' wiki markup like Markdown which has support in different tools (e.g. Pandoc for processing it, different blog-engines support writing in it, there is Emacs-mode for it etc.) for all my documentation-related needs instead of learning new wiki for every app I need. You do understand that other users have there own preferences for markup implementations and they all claim that theirs is the best and most standard? The present Fossil's markup lacks features in order to be used as single-source markup which is pity and forces one to use another markup for writing other docs. Richard likes HTML markup :-) . But pandoc can convert HTML to markdown (Aha do I see a way out of typing a lot of documents :-) (Before settling on markdown, I was thinking about reST and same reasoning applies there as well.) The solution I presented for creole could just as easy be used for markdown e.g. ** bold markdown this is markdown fossil and back in fossil That would spare you a lot of typing :-) also But it might bring you into trouble with pandoc because pandoc might not understand markdown my advice would be to use DARCS, write your user manual and keep the files in DARCS and use pandoc to your harts content. There is much work involved with what you want and it won't happen overnight if ever. Sincerely, Gour ___ 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] The case for Markdown (yes, I rtfm)
On 05/05/2010 10:53 AM, Twylite wrote: That said, if you really want Markdown, why don't you use something like Attacklab's Showdown (http://attacklab.net/showdown/), which is a Markdown implementation in JavaScript. Write your Wiki pages in plain text, include Showdown in the site header, and with a little fiddling you should be able to have the Markdown rendered into HTML on the browser. That's the plan, though my intention is to render the markdown to HTML at post time and store both the markdown and HTML text. -- Joshua Paine LetterBlock: Web applications built with joy http://letterblock.com/ 301-576-1920 ___ 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] The case for Markdown (yes, I rtfm)
On Wed, 05 May 2010 16:53:27 +0200 Twylite == Twylite wrote: Twylite Plugins are of limited value. The repository becomes Twylite non-portable except to other Fossil installations with the Twylite same plugins. The end of that road is that everyone has to Twylite have all the markup plugins, and a significant part of the Twylite value of Fossil is lost. Yeah, you're right. Let's forget plugin idea. Twylite The only thing Markdown offers is a claim of being easier for Twylite authors to work with than HTML. I say a claim because there Twylite are plenty of people who disagree, in particular those who are Twylite blessed by having to work with five different markup languages Twylite in a day. Hmm, maybe I'm spoiled by Pandoc's extensions...check http://johnmacfarlane.net/pandoc/README.html#pandocs-markdown-vs.standard-markdown) Twylite Markdown does NOT have automation features that are common to Twylite most Wikis, and essential for creating complex documents (e.g. Twylite Table of Contents, notices callouts, numbered headings). Heh, Pandoc has -N or --number-sections option which causes sections to be numbered in LaTeX, ConTeXt, or HTML output. By default, sections are not numbered. :-) Twylite That said, if you really want Markdown, why don't you use Twylite something like Attacklab's Showdown Twylite (http://attacklab.net/showdown/), which is a Markdown Twylite implementation in JavaScript. Write your Wiki pages in plain Twylite text, include Showdown in the site header, and with a little Twylite fiddling you should be able to have the Markdown rendered into Twylite HTML on the browser. This sounds like something which Joshua wants to do. Thanks for the input. Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 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] The case for Markdown (yes, I rtfm)
On Wed, 05 May 2010 16:32:29 +0200 renework == renework wrote: renework You get into trouble if it is contained in two wiki pages. renework Basically your are better of to write two markdown files and renework a Makefile. Which you can do in Darcs anyway. Well, the more I think about it, it seems that it's better to forget about fossil's wiki as solution for documentation and use it only according to the DRH's intention. :-) renework I looked up markdown and it is a 35Kb perl source file. But renework you are in luck there is a c implementation renework http://www.pell.portland.or.us/~orc/Code/discount/ renework Now find someone to incorporate it into fossil. Still, it won't be accepted in the core, so better to forget about it. renework You do understand that other users have there own preferences renework for markup implementations and they all claim that theirs is renework the best and most standard? Sure. I understand, but I posted since this thread is labelled as: The case for Markdown. ;) renework my advice would be to use DARCS, write your user manual and renework keep the files in DARCS and use pandoc to your harts renework content. There is much work involved with what you want and renework it won't happen overnight if ever. I understand your suggestion to write user-manual with markdown and use pandoc, but why are you suggesting to use darcs instead of fossil as scm? Maybe there are too many users already? :-D Well, it is a topic for a new post... Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 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
[fossil-users] collaborating with other SCMs
Hello, I'll leave the Markdown/Fossil_wiki topic on the side and try to focus on evaluating some more thrilling features of Fossil... I'm using darcs for quite a long time (since 0.9.x), and like its cherry-picking features, selective record etc. Moreover, there is need to track different projects using other SCM systems (bzr, git, hg, svn), I am able to cope with it by e.g. using bzr and its bzr-svn bzr-git plugins (bzr-hg is a little bit behind the rest) along with fast-export/import utilities which enable one to (even) do 2-way sync between bzr darcs. This makes one feel more secure that it's easily possible to migrate from one system to the other. Now, considering that Fossil seems to have bus-factor of 1, I'm curious if all the Fossil users are exclusively use Fossil and what to do if you want to collaborate with other systems and/or move to/from Fossil/some_other_system? Sincerely, Gour (who continues to read all the available Fossil-related docs) -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 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
[fossil-users] What he danger of allowing all Html
While discussing markup and markdown i looked over wikiformat.c and notice the case of selectively allowing HTML elements. I wonder what the threat is in allowing all HTML elements. 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] Integration into Emacs Version Control
On Wed, 28 Oct 2009 14:49:31 -0700 Venkat == Venkat Iyer wrote: Hiya, Venkat I'm trying to integrate fossil into emacs vc I'm still in the evaluating phase for Fossil, but being an Emacs user, I'm curious why you're integrating into VC and not DVC? (http://www.xsteve.at/prg/emacs_dvc/dvc.html) Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 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
[fossil-users] ticket assignment
I have developed a simple patch to introduce ticket assignment. I have yet to
add an assigned to column in all places that may be necessary. Is this
something people would be interested in seeing included with the standard
fossil distribution?
diff -rupN fossil_src_orig/src/schema.c fossil_new/src/schema.c
--- fossil_src_orig/src/schema.c2010-03-18 10:20:53.0 -0400
+++ fossil_new/src/schema.c 2010-05-05 21:00:11.762884455 -0400
@@ -175,6 +175,27 @@ const char zRepositorySchema1[] =
@ title
@ FROM ticket');
@
+@ INSERT INTO reportfmt(title,cols,sqlcode) VALUES('My Tickets','#ff Key:
+@ #f2dcdc Active
+@ #e8e8e8 Review
+@ #cfe8bd Fixed
+@ #bde5d6 Tested
+@ #cacae5 Deferred
+@ #c8c8c8 Closed','SELECT
+@ CASE WHEN status IN (''Open'',''Verified'') THEN ''#f2dcdc''
+@WHEN status=''Review'' THEN ''#e8e8e8''
+@WHEN status=''Fixed'' THEN ''#cfe8bd''
+@WHEN status=''Tested'' THEN ''#bde5d6''
+@WHEN status=''Deferred'' THEN ''#cacae5''
+@ELSE ''#c8c8c8'' END AS ''bgcolor'',
+@ substr(tkt_uuid,1,10) AS ''#'',
+@ datetime(tkt_mtime) AS ''mtime'',
+@ type,
+@ status,
+@ subsystem,
+@ title
+@ FROM ticket WHERE assignedto=user()');
+@
@ -- Some ticket content (such as the originators email address or contact
@ -- information) needs to be obscured to protect privacy. This is achieved
@ -- by storing an SHA1 hash of the content. For display, the hash is
@@ -359,6 +380,7 @@ const char zRepositorySchema2[] =
@ severity TEXT,
@ foundin TEXT,
@ private_contact TEXT,
+@ assignedto TEXT,
@ resolution TEXT,
@ title TEXT,
@ comment TEXT
diff -rupN fossil_src_orig/src/tktsetup.c fossil_new/src/tktsetup.c
--- fossil_src_orig/src/tktsetup.c 2010-03-18 10:20:53.0 -0400
+++ fossil_new/src/tktsetup.c 2010-05-05 21:11:33.683636050 -0400
@@ -290,6 +290,13 @@ static const char zDefaultNew[] =
@ /tr
@
@ tr
+@ td align=rightAssigned To:
+@ input type='text' name='assignedto' size='20' value=$assignedto
+@ /td
+@ tdShould this issue be assigned to a particular developer?/td
+@ /tr
+@
+@ tr
@ td align=rightEMail:
@ input type=text name=private_contact value=$private_contact
size=30
@ /td
___
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] ticket assignment
On Wed, 05 May 2010 21:25:51 -0400 Joshua == Joshua Paine wrote: Joshua Put me down as a big don't care one way or the other. It wasn't Joshua hard to add it on the repos where I needed it. May I suggest to add it to the wiki's Cookbook section? Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 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] ticket assignment
On Thursday 06 May 2010 04:18:20 zacht...@cis-partners.com wrote: I have developed a simple patch to introduce ticket assignment. I have yet to add an assigned to column in all places that may be necessary. Is this something people would be interested in seeing included with the standard fossil distribution? Did you look at this link (which is on the Fossil main page)? http://www.fossil-scm.org/index.html/doc/tip/www/custom_ticket.wiki -- Sending me something private? Use my GPG public key: AD29415D signature.asc Description: This is a digitally signed message part. ___ 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] Integration into Emacs Version Control
From: Gour g...@gour-nitai.com I'm still in the evaluating phase for Fossil, but being an Emacs user, I'm curious why you're integrating into VC and not DVC? (http://www.xsteve.at/prg/emacs_dvc/dvc.html) Two answers. 1. I had to make it as painless as possible for my users (who unfortunately are more used to traditional VCS). I'm currently tracking fossil head with minor changes to 2 files, so it's been a relatively successful project for me. 2. I had never heard of dvc. I'm sure I can make it work with fossil. But if the user experience is much different, then I'm not helping my users. I really didn't have a choice. I wanted fossil, my users absolutely needed it to work with emacs vc. Would you recommend DVC over VC? Why? - Venkat ___ 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] ticket assignment
On Thu, 6 May 2010 06:44:21 +0300 Ron == Ron Aaron wrote: Ron Did you look at this link (which is on the Fossil main page)? Ron Ron http://www.fossil-scm.org/index.html/doc/tip/www/custom_ticket.wiki Heh, as it usually happens, I've discovered it 15mins after posting. :- I had to read some other docs which were open on the earlier tabs in FF... Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 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] Integration into Emacs Version Control
On Wed, 5 May 2010 21:16:39 -0700 Venkat == Venkat Iyer wrote: Venkat 1. I had to make it as painless as possible for my users (who Venkatunfortunately are more used to traditional VCS). I'm Venkat currently tracking fossil head with minor changes to 2 files, Venkat so it's been a relatively successful project for me. OK. Venkat 2. I had never heard of dvc. I'm sure I can make it work with Venkat fossil. But if the user experience is much different, then I'm Venkat not helping my users. I see. Venkat Would you recommend DVC over VC? Why? Simpy because it says: DVC: Distributed Version Control for Emacs, i.e. I consider that Fossil is in the category of DVCS and therefore having support in DVC seems more natural, especially if users ahve to deal with more than one system, then DVC (simlar to VC) brings some useful abstraction. Otoh, I still wait to receive some reply on my post to find out whether Fossil's users are living in isolated universe or not. :-D Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 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
