Re: [fossil-users] Improving Fossil's Look
On Wed, 18 Feb 2015 09:12:37 +0100, Roy Marples r...@marples.name wrote: On 2015-02-17 23:43, Richard Hipp wrote: I have switched the default Fossil repo over to using the San Francisco Modern skin. Everybody seems to think it looks a lot better, and I agree. I like the look, but why the fixed width? I like the flexible width of the original skin more. +1. If possible, this might also be changed in the side-by-side diffs (which, I believe, always had fixed width ...). Roy ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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] Improving Fossil's Look
On 2015-02-17 23:43, Richard Hipp wrote: I have switched the default Fossil repo over to using the San Francisco Modern skin. Everybody seems to think it looks a lot better, and I agree. I like the look, but why the fixed width? I like the flexible width of the original skin more. Roy ___ 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] Improving Fossil's Look
On Wed, 18 Feb 2015 00:43:15 +0100, Richard Hipp d...@sqlite.org wrote: I have switched the default Fossil repo over to using the San Francisco Modern skin. Everybody seems to think it looks a lot better, and I agree. execpt, maybe the fixed-width layout ... I think the next step of the ongoing Fossil makeover should be to improve the homepage: https://www.fossil-scm.org/fossil/doc/trunk/www/index.wiki Suggestions and especially mockups of how this front page should look are welcomed. What are the most important features of Fossil that should be front-and-center on the homepage? I feel like the front page is providing Too Much Information and that eyes gloss over when first-time readers see all that text. (Maybe I'm wrong - let me know!) So what information can be removed from the front-page and what are the essential elements that need to be retained? I've always felt the homepage is quite OK. at the very least, it will not put off prospective users, I'd say. but to guide a cursory visitor around, yes, it might be better to restructure it a bit. in this case I would stress these points in the `why use fossil` list points 1, 2, and 4 as the most distinguishing ones. the others need to be mentioned elsewhere, sure, but they are prob. not relevant for first time visitors. I think the zero-config/(near)-zero-dependencies/single exec point might be especially relevant for first-time visitors/users. one could also contemplate to just list them with a much shortened explanatory text in parenthesis and convert the items to links where the full explanation can be found (the present list, that is). then a statement `the full list of properties can be found here' or similar. and immediately thereafter a paragraph containing pregnant links to `quick start' and `concepts'. one might also try to restructure the `list for fossil users' by discriminating between casual user and advanced user, especially isolating highly technical material from understanding concepts and how to use fosill stuff. just my 2c What else can be done to make Fossil easier? FWIW: I've made some improvements to the techniques available to skin designers, and tried to write up a brief introduction to how to design new skins at https://www.fossil-scm.org/fossil/doc/trunk/www/customskin.md - hopefully this will make it a little easier to design new skins for Fossil, will lower the barrier to entry slightly, and encourage more people to come up with innovative new designs. Please read the document, suggest improvements to the document, and give a try at designing a new look if you have talents in that area. That said: as soon as 1.31 goes out the door, I'm going to start a branch for Fossil 2.0, which will be completely 100% compatible with Fossil 1.x in terms of repository and check-ins, but will likely have a modified DOM for the web interface and thus may break any new skins you come up with today. Nevertheless, I want designers to try to make skins using 1.31 so that they can suggest ways of improving the DOM to make skinning and theming easier in 2.0. I will help you convert 1.31 skins into 2.0 skins upon request. Thank you all for your attention and your contributions. -- 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] Improving Fossil's Look
On 17 February 2015 at 15:43, Richard Hipp d...@sqlite.org wrote: I think the next step of the ongoing Fossil makeover should be to improve the homepage: https://www.fossil-scm.org/fossil/doc/trunk/www/index.wiki Suggestions and especially mockups of how this front page should look are welcomed. What are the most important features of Fossil that should be front-and-center on the homepage? I feel like the front page is providing Too Much Information and that eyes gloss over when first-time readers see all that text. (Maybe I'm wrong - let me know!) So what information can be removed from the front-page and what are the essential elements that need to be retained? I discovered there are many duplicate links on /index.wiki: FAQ FAQ --- Quick Start Quick Start guide to using fossil --- Bug Tracking And Wiki The concepts behind fossil This entire website (except the download page) is just a running instance of Fossil. The pages you see here are all wiki or embedded documentation. When you clone Fossil from one of its self-hosting repositories, you get more than just source code - you get this entire website. Fossil supports embedded documentation that is versioned along with project source code. --- Robust Reliable - Fossil stores content using an enduring file format Fossil uses an enduring file format that is designed to be readable, searchable, and extensible by people not yet born. The file format used by every content file stored in the repository. --- Autosync: branching A tutorial on branching, what it means and how to do it using fossil. -- Robust Reliable: selfcheck.wiki The automatic self-check mechanism helps insure project integrity. -- Bug Tracking And Wikiwikitheory pages you see here are all wiki Fossil contains a built-in wiki. -- distributed blog mechanism all in a single integrated package.: event.wiki An Event is a special kind of wiki page associated with a point in time rather than a name. -- CGI/SCGI Enabled: server.wiki How to set up a server for your repository. -- The file format used by every content file stored in the repository. content using an enduring file format Most of the duplicates are found under 'Links For Fossil Users', which are in the 'why use fossil' section. pages to update: https://www.fossil-scm.org/fossil/doc/trunk/www/stats.wiki https://www.fossil-scm.org/fossil/doc/trunk/www/password.wiki https://www.fossil-scm.org/fossil/doc/trunk/www/index.wiki An Event is a special kind of wiki page associated with a point in time rather than a name. --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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] Improving Fossil's Look
Hi Michai, On 17 February 2015 at 16:24, Michai Ramakers m.ramak...@gmail.com wrote: Talking of documentation, and just out of curiosity: does anyone know if there are plans to update Jim Schimp's Fossil book (by himself or anyone else)? I'm somehow comparing this to the FreeBSD Handbook w.r.t. FreeBSD project. I think the source of the book is available so anyone could update it. It looks like there was one update in December: http://www.fossil-scm.org/schimpf-book/timeline I'd be willing to assist in updating it and reviewing updates, if needed. -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Bug in command line help?
Hello, I have the latest fossil on my system: $ fossil version This is fossil version 1.30 [1df1b41c86] 2015-01-19 11:29:00 UTC and the `fossil help timeline` shows the following: Usage: fossil timeline ?WHEN? ?CHECKIN|DATETIME? ?OPTIONS? snip The BASELINE can be any unique prefix of 4 characters or more. snip There's no BASELINE mentioned in Usage header, it's CHECKIN now, so I'm sure this is a leftover from the previous version, and probably this should be fixed (BASELINE to CHECKIN in the details text). ___ 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] Generating links in tickets reports
I haven't specified any mime-type (I'm not sure how or where to set this), I only added a new field to the tickets schema, of type text. I managed to customize the View Ticket page to create links from the text found in this field, but for reports, there's only the query, and I'm not sure if I have access to the logic that is rendering the result of this query. Can I find this somewhere? Thanks On Mon, Feb 16, 2015 at 1:29 PM, Richard Hipp d...@sqlite.org wrote: On 2/16/15, Fadi Mansour fadi.redeemer.mans...@gmail.com wrote: Dear all, I'm trying to customize the ticketing system to be able to include as part of ticket information, a reference to another issue tracking system. The reference is an issue ID from another system, and I have two options: 1. Either store the whole link as part of the ticket attributes, I need to be able to display it as a link in the tickets report. 2. Or, I could just store the ID as normal text and automatically build the link in the report logic. I went with the second option, but in the report query, it seems to me that the fields are only text, and not html. Is there a way to do that? Need more details to solve your problem. Ticket fields can be any of text/plain, text/html, text/x-fossil-wiki, or test/x-markdown. What are you using? -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ 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] Generating links in tickets reports
On Wed, Feb 18, 2015 at 4:11 PM, Fadi Mansour fadi.redeemer.mans...@gmail.com wrote: I managed to customize the View Ticket page to create links from the text found in this field, but for reports, there's only the query, and I'm not sure if I have access to the logic that is rendering the result of this query. Once upon a time, I considered the possibility of an enhancement to Ticket Reports to specify TH1/TCL filter code that would be called once for each ticket The filter could modify the named fields in place and possibly return status to indicate whether the ticket should be included or skipped. While I still think it would be useful, our reports are currently New Tickets, My Tickets, Export Open and Export Closed. The 2 export reports are used via the CLI to produce CSV files for managers to look at in Excel (which seems to be their preferred UI for everything). ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] fossil search on cli
Hello All,
From this page, it looks like I can run a fossil search on the cli for
timeline check-in comments:
https://www.fossil-scm.org/index.html/help?cmd=search
My test repo has only five check-ins with very short comments:
2015-02-18
01:48
[9b6c6c17020e] Leaf: remove line (user: sean, tags: trunk)
01:47
[53df06b80def] entering commit message (user: sean, tags: trunk)
2015-02-13
15:37
[309e02cb5108] aliases are cnames (user: sean, tags: trunk)
2015-02-12
23:38
[adc2ab8412df] updated domain list (user: sean, tags: trunk)
23:10
[7deef6fb78ed] adding domain list for integration (user: sean, tags: trunk)
% fossil search domain
SQLITE_ERROR: no such function: score
fossil: no such function: score: {INSERT INTO
srch(rid,uuid,date,comment,x) SELECT blob.rid, uuid,
datetime(event.mtime), coalesce(ecomment,comment),
score(coalesce(ecomment,comment)) AS y FROM event, blobWHERE
blob.rid=event.objid AND y0;}
Doesn't return any of the timeline check-in comments.
Is there a prerequisite to run this search?
--
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
___
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] incorrect repository schema version:
Thus said j. van den hoff on Tue, 17 Feb 2015 09:44:47 +0100: doing the exact same cloning command after login to the server (i.e. via a ssh connection to itself) the clone is just fine. whether an accidental coincidence or not: this happened today and just one day after I updated fossil on the server and my local machine to fossil version 1.31 [47bb6432a1] 2015-02-16 11:33:04 UTC. I run into occasional glitches like these. Usually it turns out to be a problem with updating, building and linking in old object files. Try running ``make clean'' before building and see if it doesn't go away. Andy -- TAI64 timestamp: 400054e57c8a ___ 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] Generating links in tickets reports
Thank you for the suggestion, exporting reports from the CLI has it's uses, but what I was trying to do is to provide links to an external system. I noticed that using an _ at the start of a column name makes it possible to use wiki strings, which would successfully create links, but the problem is that this will break the columnar format of the report, as these fields will be on rows by themselves. Useful, but not what I needed right now. Regards On Wed, Feb 18, 2015 at 11:51 PM, Ron W ronw.m...@gmail.com wrote: On Wed, Feb 18, 2015 at 4:11 PM, Fadi Mansour fadi.redeemer.mans...@gmail.com wrote: I managed to customize the View Ticket page to create links from the text found in this field, but for reports, there's only the query, and I'm not sure if I have access to the logic that is rendering the result of this query. Once upon a time, I considered the possibility of an enhancement to Ticket Reports to specify TH1/TCL filter code that would be called once for each ticket The filter could modify the named fields in place and possibly return status to indicate whether the ticket should be included or skipped. While I still think it would be useful, our reports are currently New Tickets, My Tickets, Export Open and Export Closed. The 2 export reports are used via the CLI to produce CSV files for managers to look at in Excel (which seems to be their preferred UI for everything). ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ 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] Fossil 2.0 (reprise)
Thus said Ashwin Hirschi on Tue, 17 Feb 2015 21:32:57 +0100: Yeah, it feels a bit counter-intuitive: monospaced fonts are usually associated with old things [;-)]. But using them for the check-in links really helps make the timeline easier to read. I prefer monospaced fonts for most things that I do with text. My email client is configured to use a fixed font, my terminals, just about everything, except the browser and other similar tools. However, even in the browser, when it comes to code, I prefer a fixed font. Maybe that makes me one of those ``old things?'' Andy -- TAI64 timestamp: 400054e57d08 ___ 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] Bug in command line help?
Thus said =?koi8-r?B?7cnOxNLP1yDl18fFzsnK?= on Wed, 18 Feb 2015 22:32:02 +0300: There's no BASELINE mentioned in Usage header, it's CHECKIN now, so I'm sure this is a leftover from the previous version, and probably this should be fixed (BASELINE to CHECKIN in the details text). Thanks for the report: http://www.fossil-scm.org/index.html/info/8006c6ddf25d3f53 Andy -- TAI64 timestamp: 400054e580f1 ___ 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] Fossil 2.0 (reprise)
On Feb 18, 2015, at 11:04 PM, Andy Bradford amb-fos...@bradfords.org wrote: I prefer monospaced fonts for most things that I do with text. We have hundreds of years of evidence that it is easier to read prose in a proportional font than in a monospace font. It’s been studied to death. However, not everything is prose, and there are special cases where prose should be in a monospace font regardless. One such place, which I hope gets fixed while all this attention is being given to the stock skins is to make the wiki composition textbox monospace, at least if you’ve chosen Markdown formatting. Formatting a Markdown table with proportional fonts is a minor nightmare. Here are some screenshots for those who haven’t already recognized the problem, perhaps by past experience with ASCII art wreckage in email or Usenet postings: http://imgur.com/zKtnLVA,xlAs1gS The first screenshot shows a table that is properly formatted in a monospace font when viewed in my browser’s choice of proportional font. The second shows my doomed attempt to fix this. Both render the same way because Fossil currently doesn’t care if the pipe characters are aligned. Yes, I know, I can fix this in my skin CSS. In fact, I’m going to do that right now. What I’m proposing here is that the code that currently emits class=“wikiedit” be changed to something that reflects the document language, so that different CSS can be applied for the different cases. I propose class=“wikiedit markdown”. I’ve gone with a 2-class solution instead of something like class=“mdedit” for backwards compatibility with existing customized skin CSS. This works on all major browsers going back many years, and on IE going back to…wait for it…IE7, because IE6 is B-R-O-K-E-N. ___ 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] Improving Fossil's Look
Thus said Richard Hipp on Tue, 17 Feb 2015 18:43:15 -0500: I have switched the default Fossil repo over to using the San Francisco Modern skin. Everybody seems to think it looks a lot better, and I agree. It does look better, but it lacks a background color. :-) Andy -- TAI64 timestamp: 400054e57d8f ___ 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] Fossil repos 2 3
On 2/18/15, jungle Boogie jungleboog...@gmail.com wrote: Hi, I noticed this article today: https://www.fossil-scm.org/fossil/doc/trunk/www/selfhost.wiki And visited the two repos; both are very much in sync but are running bf681039e2. Is it usually the case to keep those on the equivalent of -release and update as new releases are made? www2 and www3 normally are a behind www, because a do not log into www2 and www3 to recompile as frequently. But there is no deliberate strategy of keeping www2 and www3 on release. -- D. Richard Hipp d...@sqlite.org ___ 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] Fossil 2.0 (reprise)
Hello All, On 15 February 2015 at 20:49, Richard Hipp d...@sqlite.org wrote: Adjustments have been made to the new look. Prototypes: https://www.fossil-scm.org/skin2 http://52.10.34.196/fossil The latter is a transient AC2 instance used for prototyping. It has the two new menu items Docs and Search and omits Tags and is not necessarily synced up with the latest check-ins. The first link above is the canonical repository using the default San Francisco Modern skin, as it exist on trunk. In other words, the first URL is the default look and is what newly created projects will look like (before they are customized) and the second URL contains a couple of simple customizations specific to the Fossil project itself. Please continue to offer suggestions for improvement. I was reading the archives a little today to see what I can find out about my fossil search and came across a fossil v2 thread from July 2013. It starts roughly here: http://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg12357.html Stephan made a Google doc for some of his thoughts, too: https://docs.google.com/document/d/12g0s5A2TPX7-y47Nsw235rvsjcuh49TnHfMDB4ASvlo/view#heading=h.djew3kr7njit Just bringing this up to as it may have content a committer may like, and it looks like markdown and search were highly request--both of which now exist. -- D. Richard Hipp d...@sqlite.org -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
