Re: [fossil-users] Why no EXE+DLL like SQLite?

[Steve Landers]

On 6 Aug 2018, 9:19 AM +0800, Steve Landers , wrote:
> Put differently, what can’t you do with “fossil ui” that you can do with a 
> native client?
>
> Drag and drop is the only one I can think of and I suspect that’s a good 
> thing.

And also push notifications. While it can be done with web tech I don’t 
advocate it for fossil.

Steve

> On 6 Aug 2018, 9:17 AM +0800, Richard Hipp , wrote:
> > On 8/5/18, Gilles  wrote:
> > > 2. There's no maintained GUI for Fossil.
> >
> > I would argue that running "fossil ui" is your GUI.
> >
> > --
> > 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
___
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] Why no EXE+DLL like SQLite?

[Steve Landers]

Put differently, what can’t you do with “fossil ui” that you can do with a 
native client?

Drag and drop is the only one I can think of and I suspect that’s a good thing.


-- Steve
On 6 Aug 2018, 9:17 AM +0800, Richard Hipp , wrote:
> On 8/5/18, Gilles  wrote:
> > 2. There's no maintained GUI for Fossil.
>
> I would argue that running "fossil ui" is your GUI.
>
> --
> 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] About to merge the forum-v2 branch

[Steve Landers]

On 31 Jul 2018, 9:47 PM +0800, Richard Hipp , wrote:
> I am about ready to merge the forum-v2 branch into trunk. If there
> are any objections, voice them quickly.

An observation (not a criticism) is that (at its current state of development) 
the forum does not work too well on mobile devices. And so IMO it isn’t yet a 
replacement for the mailing list.


Steve
___
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] Perception of Fossil

[Steve Landers]

fossil submit

Steve

On 16 Jun 2018, 9:30 PM +0800, Tony Papadimitriou , wrote:
> -Original Message-
> From: Richard Hipp
>
> > Other ideas for what to name this (hypothetical and unimplemented) command:
> >
> > fossil contribute
> > fossil bequest
> > fossil bestow
> > fossil proffer
>
> Some more ideas (in random order):
>
> fossil chip-in (shortest possible is ch)
> fossil enqueue (shortest: en) and it could be matched by a fossil queue
> (shortest: q) command to quickly check the pending queue
> fossil inbound (shortest: inb)
> fossil try-request (shortest: tr)
> fossil consider (shortest: cons)
> fossil evaluate (shortest: ev)
>
> ___
> 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] Show time...

[Steve Landers]

Too snarky, IMHO.

State the positive, let the reader figure the negative.

Steve

On 4 Jun 2018, 9:33 AM +0800, Richard Hipp , wrote:
> On 6/3/18, Richard Hipp  wrote:
> >
> > So, if anybody sees any last minute tidying up that we need to do...
>
> For example, on the front page
> (https://fossil-scm.org/index.html/doc/trunk/www/index.wiki), what if
> I add some text to item 8 to talk about how Fossil is "Independent and
> not beholden to venture capitalists". Too snarky?
>
> --
> 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] Metadata in Timeline Verbose View

[Steve Landers]

The slightly lighter gray has the downside of not being visible by many folk 
with diminished contrast perception.

Old geezers in other words :)

My vote would be to stick with the current color and also to ensure no 
generated branch colors ever come close to matching it.

On 12 Dec 2017, 11:47 AM +0800, Warren Young , wrote:
> On Dec 11, 2017, at 5:03 PM, Richard Hipp  wrote:
> >
> > A new version of Fossil is up with some minor UI tweaks:
> >
> > (1) No more box around comments in the Modern and Columnar views.
> > Instead, the background color is a light gray.
>
> Works for me, though maybe a slightly lighter gray, barely perceptible?
>
> Just a thought.
> ___
> 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] Help improve the Fossil CSS

[Steve Landers]

That’ll definitely help, and be more likely to work across the various web 
browsers we need to support.

On 12 Dec 2017, 7:07 AM +0800, Richard Hipp <d...@sqlite.org>, wrote:
> On 12/11/17, Steve Landers <st...@digitalsmarties.com> wrote:
> > i haven’t had the time to figure the correct CSS to make the background on
> > the row override the background on the div.
>
> I was thinking I need to change the generated HTML a little to give
> you better class tags to work with. That is on-queue.
> --
> 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] Help improve the Fossil CSS

[Steve Landers]

i haven’t had the time to figure the correct CSS to make the background on the 
row override the background on the div.


On 11 Dec 2017, 11:03 PM +0800, Richard Hipp , wrote:
> On 12/11/17, Martin Gagnon  wrote:
> >
> > > The llnk for draft1 is https://www.fossil-scm.org/fossil/draft1/timeline
> >
> > This one is by far my favorite one. Separate Checkins are well defined
> > and the overall still smooth on the eyes without the horizontal lines.
> >
> > If Same changes can be applied to the "Columnar View", this skin would
> > be complete.
> >
> > I would vote for this one as the default skin.
>
> The "selected check-in" display is a little wonky on that skin:
> https://www.fossil-scm.org/fossil/draft1/timeline?c=9f9ed
>
> --
> 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] Help improve the Fossil CSS

[Steve Landers]

Done .. I just copied the bulk of Warren’s Draft2 and added my few lines at 
then.

On 5 Dec 2017, 9:38 AM +0800, Richard Hipp <d...@sqlite.org>, wrote:
> On 12/3/17, Steve Landers <st...@digitalsmarties.com> wrote:
> > If the entire highlighted commit should be yellow then the background CSS
> > can be made conditional
> >
> >  td.timelineModernCell : not (.timelineSelected) {
> >  background-color: #f8f8f8;
> >  }
> >
>
> You had this working, Steve. Then I attempted to "improve" it without
> making a backup, ended up breaking it, and now I can't seem to fix it.
> Can you please work your magic again?
>
> --
> 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] Help improve the Fossil CSS

[Steve Landers]

On 4 Dec 2017, 11:12 AM +0800, Richard Hipp <d...@sqlite.org>, wrote:
> On 12/3/17, Steve Landers <st...@digitalsmarties.com> wrote:
> > The llnk for draft1 is https://www.fossil-scm.org/fossil/draft1/timeline
>
> At https://www.fossil-scm.org/fossil/draft1/timeline?c=106fe6 the
> yellow highlight color only covers the date and the graph, not the comment.

That’s right, I like every commit in the branch to have the same color for 
consistency.  I also don’t like suits with horizontal pin-stripes, but each to 
their own. https://imgur.com/6ClhiKR

If the entire highlighted commit should be yellow then the background CSS can 
be made conditional

 td.timelineModernCell : not (.timelineSelected) {
   background-color: #f8f8f8;
 }

I’ve done this on draft1 for now, clear cache + refresh.

Steve

___
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] Help improve the Fossil CSS

[Steve Landers]

The llnk for draft1 is https://www.fossil-scm.org/fossil/draft1/timeline

On 4 Dec 2017, 11:07 AM +0800, Steve Landers <st...@digitalsmarties.com>, wrote:
> Draft1 omits the borders around checkins in the Modern View, and adds a 
> subtle background color for any commits that are not already colored.
>
> The rationale is that horizontal lines are “visual noise” that draw the eye 
> from the content of the check-in.   Removing the horizontal lines also gives 
> a slightly better use of vertical space.
>
> Steve
>
> On 3 Dec 2017, 10:26 AM +0800, Richard Hipp <d...@sqlite.org>, wrote:
> > New enhancements to the "skin" mechanism of Fossil allow up to 9
> > separate "draft" skins that can be independently edited and viewed,
> > for easier A/B comparisons.
> >
> > For the moment, I have assigned "draft1" to Steve Landers and "draft2"
> > to Warren Young, since both individuals have contributed CSS change
> > suggestions recently. I will send them specific instructions on how
> > to edit their assigned drafts by private email.
> >
> > If any other readers are interested in contributing CSS changes,
> > please send me private email and I will assign a draft skin to you and
> > give you edit permissions on that draft as well.
> >
> > To view Fossil using a draft skin, simply insert the draft skin name
> > in front of the URL element that determines the page. For example, if
> > the page you are interested in is:
> >
> > https://www.fossil-scm.org/fossil/timeline
> >
> > Then to view the draft2 skin, go to:
> >
> > https://www.fossil-scm.org/fossil/draft2/timeline
> >
> > There should be no difference between the default and "draft2" at this
> > time, though perhaps Warren will change that soon are report back on
> > this list... :-)
> >
> > --
> > 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] Help improve the Fossil CSS

[Steve Landers]

Draft1 omits the borders around checkins in the Modern View, and adds a subtle 
background color for any commits that are not already colored.

The rationale is that horizontal lines are “visual noise” that draw the eye 
from the content of the check-in.   Removing the horizontal lines also gives a 
slightly better use of vertical space.

Steve

On 3 Dec 2017, 10:26 AM +0800, Richard Hipp <d...@sqlite.org>, wrote:
> New enhancements to the "skin" mechanism of Fossil allow up to 9
> separate "draft" skins that can be independently edited and viewed,
> for easier A/B comparisons.
>
> For the moment, I have assigned "draft1" to Steve Landers and "draft2"
> to Warren Young, since both individuals have contributed CSS change
> suggestions recently. I will send them specific instructions on how
> to edit their assigned drafts by private email.
>
> If any other readers are interested in contributing CSS changes,
> please send me private email and I will assign a draft skin to you and
> give you edit permissions on that draft as well.
>
> To view Fossil using a draft skin, simply insert the draft skin name
> in front of the URL element that determines the page. For example, if
> the page you are interested in is:
>
> https://www.fossil-scm.org/fossil/timeline
>
> Then to view the draft2 skin, go to:
>
> https://www.fossil-scm.org/fossil/draft2/timeline
>
> There should be no difference between the default and "draft2" at this
> time, though perhaps Warren will change that soon are report back on
> this list... :-)
>
> --
> 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] A-B comparison of proposed timeline changes

[Steve Landers]

I like it. Thanks

On 29 Nov 2017, 10:17 AM +0800, Warren Young <war...@etr-usa.com>, wrote:
> On Nov 27, 2017, at 7:04 PM, Steve Landers <st...@digitalsmarties.com> wrote:
> >
> > Note that I would retain the rounded corners on Warren’s backgrounds, they 
> > make the visuals “softer”.
>
> You can have that without the stroked borders:
>
> td.timelineTableCell {
> border-radius: 10px;
> background-color: #f8f8f8;
> }
>
> That is, don’t define a border style, just apply the border radius to the td 
> element, which rounds the corners of the background color. Set a very pale 
> background color as a default for the “normal” case, then let Fossil override 
> that for branches and such.
>
> With this, I’d suggest increasing padding to 0.75 em. It gets a bit crowded 
> in the corners otherwise.
>
> Preview:
>
> https://imgur.com/a/a7nlN
> ___
> 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] A-B comparison of proposed timeline changes

[Steve Landers]

Note that I would retain the rounded corners on Warren’s backgrounds, they make 
the visuals “softer”.

On 28 Nov 2017, 10:01 AM +0800, Richard Hipp <d...@sqlite.org>, wrote:
> On 11/27/17, Steve Landers <st...@digitalsmarties.com> wrote:
> > Nice work.
> >
> > Have you considered dropping the borders on the commits? They do add
> > definition to the commit, but at the expense of repetition and possibly
> > “noise” when the branch isn’t colored
>
> Here are comparison links:
>
> As it was yesterday:
> https://www.fossil-scm.org/fossil/timeline
> https://www.fossil-scm.org/fossil/timeline?dp=d95f712=4
> https://www.fossil-scm.org/fossil/timeline?b=2017-09-01
> https://www.fossil-scm.org/fossil/finfo?name=src/db.c
>
> Warren Young's new approach:
> https://www2.fossil-scm.org/fossil/timeline
> https://www2.fossil-scm.org/fossil/timeline?dp=d95f712=4
> https://www2.fossil-scm.org/fossil/timeline?b=2017-09-01
> https://www2.fossil-scm.org/fossil/finfo?name=src/db.c
>
> Steve Landers' modifications to Warren's approach:
> https://www3.fossil-scm.org/site.cgi/timeline
> https://www3.fossil-scm.org/site.cgi/timeline?dp=d95f712=4
> https://www3.fossil-scm.org/site.cgi/timeline?b=2017-09-01
> https://www3.fossil-scm.org/site.cgi/finfo?name=src/db.c
>
> Please do not restrict yourself to just the links shown. Look at
> various timelines to see what works well and what does not.
>
> --
> 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] A-B comparison of proposed timeline changes

[Steve Landers]

Nice work.

Have you considered dropping the borders on the commits?  They do add 
definition to the commit, but at the expense of repetition and possibly “noise” 
when the branch isn’t colored

Screenshot at https://www.dropbox.com/s/o4sa29q8i0dv7r3/timeline.png?dl=0

—Steve

On 28 Nov 2017, 7:02 AM +0800, Warren Young , wrote:
> My proposed design changes do not waste space, they buy readability.
>
> Also, I just want to emphasize that I do not think this is the paragon of web 
> site design. I hope someone riffs on it and does something even better with 
> it.
___
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] Random thoughts on Fossil v2

[Steve Landers]

On 28/07/2013, at 8:53 AM, Paolo Bolzoni paolo.bolzoni.br...@gmail.com wrote:

 Marketing I am afraid ... 
...
 Of course whoever is interested in selling other languages will mark the C++ 
 way as older. 

I respectfully disagree, strongly.

Some OO languages support greater degrees of introspection and dynamic type 
checking than others.  Some encourage delegation,  dynamic binding and 
dispatch, whether classes are part of the object system, whether the class of 
classes can be subclassed, etc., these differences are really fundamental 
things.

One thing I appreciate about Tcl is that I can choose which type of OO suits my 
needs, or none at all (sometimes an OO system gets in the way of a clean 
solution). 

But, in summary, the main difference in OO systems is the degree to which they 
support dynamic stuff and whether they support delegation.

___
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] Inofficial naming contest...

[Steve Landers]

libfossil, that's what it is. 

But if you want to go down the living fossil path, Coelacanth. Just be careful 
it doesn't become a coprolith.


On 30/07/2013, at 8:36 AM, Stephan Beal sgb...@googlemail.com wrote:



 On Tue, Jul 30, 2013 at 3:33 PM, David Given d...@cowlark.com wrote:
 Stephan Beal wrote:
  - libname of some specific dinosaur species
 
 I really want to suggest 'archeoraptor', being a famously fake fossil,
 
 LOL! If i was working on a fork, THAT would be the name :).
  
 but it's a bit of a mouthful. 'Piltdown', perhaps?
 
 i don't get the reference.
 
 -- 
 - 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 mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] error code 28: multiple links to file (on OSX 10.8)

[Steve Landers]

Same problem here.  I'm not going to touch the TimeMachine links  either but a 
simple workaround is to exclude the Fossil repositories from the Time Machine 
backups.

-- Steve

On 09/06/2013, at 1:58 PM, Dominic Lemire gramo...@hotmail.com wrote:

 Thank you Richard,
 
 Turns out the other links were automatically created by TimeMachine under 
 /.MobileBackups
 
  sudo find / -x -samefile /Users/me/myclone.fossil 2/dev/null
  Password:
  /.MobileBackups/Computer/2013-06-08-161153/Volume/Users/me/myclone.fossil
  /.MobileBackups/Computer/2013-06-09-105603/Volume/Users/me/myclone.fossil
 
 I don't want to mess with my backups, so I'll just live with the warnings.
 
 Regards,
 Dominic
 ___
 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] How to set-up multiple-repo CGI-based server? (fossil: d...@sqlite.org exclusive)

[Steve Landers]

Richard,

Agree with all you say, it reflects my frustrations about a profession where 
simple, stable and reliable is so readily dismissed as outdated.

Re your specific comment I'm not sure why the one-process-per-task model has 
fallen out of favor..  It may be because early  web servers (and Apache in 
particular) struggled to scale on the then available hardware.  That and (as 
you mention) the startup cost of the languages being used.

Re SCGI, while I agree with all you say my experience is that it isn't 
difficult at all (at least, from Tcl).  In the Einstein Brain Atlas project we 
use NGINX + SCGI and it works just fine and is relatively simple to integrate 
with Tcl.  

Not that I'm advocating SCGI for Fossil, but if you do have needs that go 
beyond what simple CGI can provide then Nginx/SCGI is a relatively small 
incremental complexity cost.

Steve

On 29/05/2013, at 10:01 AM, Richard Hipp d...@sqlite.org wrote:

 
 
 On Wed, May 29, 2013 at 10:09 AM, Stephan Beal sgb...@googlemail.com wrote:
 On Wed, May 29, 2013 at 3:59 PM, fossil@9ox.net wrote:
 Despite my error, I find the simplicity of setting up a Fossil repo
 (or better a set of repos) under cgi fantastic.
 
 +1
 
 @Richard: out of historical interest, what was the motivation behind adding 
 CGI support initially? (Despite CGI being archaic, it was _the_ feature which 
 caused my initial addiction to fossil.)
 
 
 Well, I suppose I don't consider CGI to be archaic.  CGI is simple, concise, 
 easy to administer, easy to implement (on both ends), efficient, and is 
 supported by all web-servers (except nginx).
 
 CGI grows out of the historic development model where you spin up a new 
 process to handle each specific task.  Unix was built around this model.  It 
 is an older model, but just because it is old doesn't make it bad.  There is 
 really quite a lot to recommend it:
 
 (1) No need to worry about resource leaks because the operating-system 
 automatically and efficiently reclaims resources when the short-lived working 
 process dies.
 
 (2) Programming is much simpler because you can almost always run 
 single-threaded and you can often get away with using global variables.
 
 (3) Unit testing and debugging is easier since the worker task is now an 
 independent process that can be run from a command-line prompt and/or in gdb 
 or valgrind.
 
 (4) Bugs in the application are well-contained.  One worker task might 
 segfault due to a bug, but other independent tasks continue happily running 
 without impact.
 
 (5) There are no background processes that an administrator needs to monitor 
 and keep running.  The worker tasks are launched on-demand.  Thus the 
 administrative overhead is reduced.
 
 I'm not sure why the one-process-per-task model has fallen out of favor.  One 
 cause might be a quest to squeeze every last ounce of performance out of 
 systems by avoiding the process creation and breakdown overhead.  Another 
 reason might be people growing up in a windows-oriented world where process 
 creation and breakdown is significantly more complex and costly compared to 
 unix where fork() and exit() are easy and cheap.
 
 I like things to have low administrative, development, and maintenance 
 overhead.  CGI fits that requirement nicely.  Other similar technologies 
 (FCGI or SCGI come first to mind) require a lot more effort to program, to 
 set up, and to maintain.  Those others might be slightly faster on a busy 
 site, but CGI is fast enough for most applications, especially for small 
 and light-weight applications.  For something like Fossil, FCGI/SCGI would be 
 no faster.  (FCGI/SCGI might well be much faster if your CGI script starts 
 with #!/usr/bin/perl or #!/usr/bin/php, but that is a function of the 
 start-up overhead of your scripting language, not of the interprocess 
 communication protocol.  Fossil, being native code, starts up very quickly 
 and so CGI startup time is minimized and the performance advantages of 
 FCGI/SCGI are lost in the noise of the added complexity.)
 
 The Fossil and SQLite websites spin up about 4 or 5 new worker processes per 
 second on a debian linux VM at Linode.com that is a 1/24th slice of an actual 
 server.  And yet the load average stays down around 5%.  People say Oh, you 
 could go so much faster using $COOL_NEW_TECHNOLOGY.  But I doubt it.  And 
 even if we could, with the load average holding steady at 5%, it isn't worth 
 the trouble.  Better to keep things simple and reliable.
 
 -- 
 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] Did you know that Fossil could do...

[Steve Landers]

On 28/05/2013, at 8:38 AM, Mark Janssen mpc.jans...@gmail.com wrote:

 I did not know this, but find it very useful. 

+1

Steve
___
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] Rename --limit to --count and --test to --nochange

[Steve Landers]

On 20/04/2013, at 2:46 AM, Richard Hipp d...@sqlite.org wrote:

 
 
 On Fri, Apr 19, 2013 at 1:19 PM, Stefan Bellon sbel...@sbellon.de wrote:
 On Fri, 19 Apr, Jan Nijtmans wrote:
 
  Yes, that would work fine. My question was not meant technical, but
  regarding the documentation: If --test|-n is the new 'official'
  option, and --nochange is deprecated, the documentation should be
  adapted accordingly as well.
 
 If changing (and possibly breaking existing scripts), why not change it
 to something *really* meaningful and use something other tools use,
 e.g. make:
 
   -n, --just-print, --dry-run, --recon
   Don't actually run any commands; just
   print them.
 
 -n as short and --dry-run as long option seem like a good choice.
 
 I can go with --dryrun (I think without the - between dry and run, but 
 that is a minor point that I won't insist on.)

I'm all for re-inventing square wheels, but given svn, rsync, git (and perhaps 
others) use -n and --dry-run it would be worth using those

Steve
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Changed tickets report - getting previous values of a field

[Steve Landers]

I'm implementing a Changed Tickets report similar to that in Fossil's ticket 
system, the main difference is I want to show who made the change. I do this by 
joining ticket and ticketchg

SELECT DISTINCT
date(ticket.tkt_mtime), 
substr(tkt_uuid,1,10) AS '#',
status, 
login,
title
FROM ticket LEFT OUTER JOIN ticketchng
ON ticket.tkt_id = ticketchng.tkt_id
ORDER BY ticket.tkt_mtime desc

I'd like to do is show the status value for the particular ticket change 
(rather than the current value) so the report would return something like: 

DateStatus  ModifiedTitle
2013-01-12  Closed  Dick
2013-01-12  Tested  DickSome task
2013-01-11  DoneHarry   Some task
2013-01-10  Started Harry   Some task
2013-01-10  OpenDickSome task
2013-01-09  New Tom Some task

In this example, assume Tom is an end user, Dick is the tester and Harry is the 
developer.

The above example returned Status Closed for all rows. Can anyone think of a 
convenient way to achieve the above report?

Thanks

Steve
___
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] Changed tickets report - getting previous values of a field

[Steve Landers]

On 11/01/2013, at 9:44 PM, Richard Hipp d...@sqlite.org wrote:

 The status field is coming from the ticket table and thus shows the latest 
 status.  To show the latest status at some point in the past, you need a (I 
 think) to first add a status field to your ticketchng table definition.  
 Then modify the query to be something like this (untested):
 
 
 SELECT DISTINCT
 date(ticket.tkt_mtime),
 substr(tkt_uuid,1,10) AS '#',
 (SELECT status FROM tkt_chng AS chng2
WHERE chng2.tkt_id = ckc1.tkt_id
 AND chng2.tkt_time = chng1.tkt_time
 AND chng2.status IS NOT NULL
 ORDER BY chng2.tkt_time DESC LIMIT 1),
 login,
 title
 FROM ticket AS tkt1 LEFT OUTER JOIN ticketchng AS chng1
 ON tkt1.tkt_id = chng1.tkt_id
 ORDER BY tkt1.tkt_mtime desc

Excellent, thx. That shows me a way forward.

 Later today, I'll try to find time to enhance Fossil so that you can 
 accomplish the above merely by creating a status column in the TICKETCHNG 
 table and omitting the subquery.

Even better.

 On Fri, Jan 11, 2013 at 3:07 AM, Steve Landers st...@digitalsmarties.com 
 wrote:
 I'm implementing a Changed Tickets report similar to that in Fossil's 
 ticket system, the main difference is I want to show who made the change. I 
 do this by joining ticket and ticketchg
 
 How is the /timeline?y=t page is insufficient for this?

It's not tabular and not easily configurable (color, number of entries or 
recent entries by time, order/sorting/format of columns, etc).  Plus, I've 
added sortable columns via javascript.  So, the information is there but not as 
accessible.

Thanks again Richard. As always, much appreciated.

Steve
___
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] Support for Win9x?

[Steve Landers]

On 13/09/2012, at 9:02 AM, Richard Hipp d...@sqlite.org wrote:

 Is there any reason to try to keep Fossil working on windows9x?

Only if  you are a technonecrophiliac

Steve
___
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] Postmortum: DRH in Munich

[Steve Landers]

On 04/07/2012, at 5:43 AM, Bill Burdick wrote:

 On Tue, Jul 3, 2012 at 4:08 PM, Stephan Beal sgb...@googlemail.com wrote:
 On Tue, Jul 3, 2012 at 11:04 PM, Bill Burdick bill.burd...@gmail.com wrote:
 On Tue, Jul 3, 2012 at 3:58 PM, Stephan Beal sgb...@googlemail.com wrote:
 @DRH: the proof is in the pudding (though i've never really understood 
 where that phrase comes from)
 
 Heh, well, that's because it doesn't make sense.  The actual saying is: The 
 proof of the pudding is in the eating. :)
 
 LOL! Well, it certainly tastes better than my foot ;).
 
 It's a very misquoted quotation.  Like, money is the root of all kinds of 
 evil, is usually quoted as, money is the root of all evil.  

Actually, the correct quote is For the love of money is a root of all kinds of 
evil.  - 
http://www.biblegateway.com/passage/?search=1+Timothy+6%3A10version=NIV

 It's just par for the course.  Most people say, the proof is in the 
 pudding,  but, unlike you, they just don't realize that they just said 
 something that doesn't really make very much sense.  I mean, if the proof is 
 in the pudding and you're making pudding, then the pudding doesn't exist yet. 
  Maybe they should say, the proof will be in the pudding.
 
 Anyway -- I guess this is turning into a thread-jack :).

Ditto

Steve

___
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] problem with illegal characters

[Steve Landers]

On 09/03/2012, at 8:22 AM, Matt Welland wrote:

 I'm in the mood for some long winded editorializing
 
 Bob Coder is moving his development team off of AntiquatedSCM and on to one 
 of the fancy new distributed SCMs that are all the rage. They look at git but 
 it seems kinda complicated and one of the devs suggests Fossil. Wow, nice, 
 simple, elegant, reliable, data storage design that looks trustworthy, solves 
 multiple problems with one executable. Cool. But in the evaluation it comes 
 to light that some legacy files with funky characters can't be checked in and 
 the only two solutions are to throw away or rewrite multiple megs of test 
 cases or to maintain a private branch of the Fossil source. Neither option is 
 tenable and Fossil is eliminated.
 
 So Fossil loses another potential advocate due to being devoted to a 
 philosophy of enforcing adherence to the lowest common denominator and the 
 ever pragmatic (albeit, bloody complicated) git gains another user.
 
 Sure, it is a silly story and who cares, fossil was not written to be 
 everything to everyone. But still, we've seen at least one real world variant 
 of this story reported to the list 
 
 A strongly worded warning makes sense but I personally think a no-alternative 
 enforcement does not.
 
 IMHO a more viable philosophy is to use documentation and methodology to make 
 seamless interoperability between Windows and Unix/Linux possible for teams 
 that need it. Otherwise where possible and where the code cost is not too 
 high, independently make fossil work perfectly on Unix and perfectly on 
 Windows.

+1

In my experience, good software tools embody best practice out of the box, 
while accommodating existing non ideal practice (and leading the user gently 
from the latter to the former).

Steve

 
 On Wed, Mar 7, 2012 at 3:16 PM, Leo Razoumov slonik...@gmail.com wrote:
 On Wed, Mar 7, 2012 at 14:30,  sky5w...@gmail.com wrote:
  because of the hassle of re-working their multitudes of files or
  create/maintain Fossil branches using Richard's suggestion.
 
 
 If square bracket limitation is the only thing that make fossil
 unacceptable to you then, please, consider making your own fossil
 branch as Richard suggested.
 
 Actually, I found maintaining my own fossil branch quite easy. And my
 changes are larger and more intrusive that commenting out couple of
 lines of code.
 
 --Leo--
 ___
 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

___
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] Why do people create branches as a separate step? Was: Unable to sign manifest

[Steve Landers]

On 11/08/2011, at 8:02 AM, Stephan Beal wrote:

 On Thu, Aug 11, 2011 at 1:35 AM, Will Duquette w...@wjduquette.com wrote:
 ...development context.  If I create the new branch explicitly, then I've 
 changed my development context in my head AND in my work area.
 
 
 Thank you for so elegantly describing what i was unable to express nearly as 
 well :).

+1

--Steve___
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] Needed: volunteer to autoconf Fossil

[Steve Landers]

On 07/07/2011, at 3:03 PM, Stephan Beal wrote:

 On Thu, Jul 7, 2011 at 8:31 AM, Steve Bennett ste...@workware.net.au wrote:
 On 07/07/2011, at 2:22 PM, Matt Welland wrote:
 Does the cross compilation really work?
 
 ... 
 $ ./configure --host=mips-unknown-nto-qnx6.5.0
 Host System...mips-unknown-nto-qnx6.5.0
 ...
 $ file fossil
 fossil: ELF 32-bit MSB executable, MIPS, MIPS-II version 1, dynamically 
 linked (uses shared libs), with unknown capability 0x4100 = 0xf676e75, 
 not stripped
 
 i'm convinced :). That would certainly greatly simplify the release of the 
 pre-built fossil binaries.
 
 i spent about half an hour reading through autosetup's docs last night and i 
 will certainly be trying it out on a tree or three of mine. i don't know tcl, 
 but a tool like this one provides a good motivator for learning it.

It's actually quite simple if you forget formal grammars and think command arg 
arg arg .   Simple but not simplistic,  you get sophisticated features 
like event driven I/O, threads (if you want them, but mostly you don't need 
to), co-routines,  full I18N and localization, single file deployment via 
starkits, etc.

And there's plenty of Tcler's on this list who will help you :)

A good place to start is the Tclers Wiki at http://wiki.tcl.tk ... perhaps 
starting at http://wiki.tcl.tk/20789

Steve___
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] branch colour

[Steve Landers]

On 29/06/2011, at 4:49 PM, Christopher Vance wrote:

 I've seen the --bgcolor option for 'fossil branch new', but was
 wondering if I can change the colour on an existing branch?

Yep, via the web interface.  Look for the Edit link.

Oh, and g'day Chris, good to have you on board and fossilising :)

Steve

___
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 status coloring

[Steve Landers]

As an aside, I use the ticket coloring extensively and it works as advertised.  
Start with the default and configure as you feel the need.

One thing I'd like to see some time is support for fgcolor as well as bgcolor 
(but not enough that I'd start hacking the code just at the moment :))

Steve

On 12/01/2011, at 10:26 AM, Richard Hipp wrote:

 
 
 On Tue, Jan 11, 2011 at 9:19 PM, Ron Wilson ronw.m...@gmail.com wrote:
 Did as requested. Status came back as Implemented.
 
 The raw output was:
 bgcolor #   mtime   typestatus  subsystem   title
 #c8c8c8 9445d15aae  2011-01-12 01:02:51 Problem Implemented   
   Invalid
 partnumber in response to query
 
 Does the Implemented string have spaces on one side or the other?
  
 
 On Tue, Jan 11, 2011 at 9:11 PM, Richard Hipp d...@sqlite.org wrote:
 
  Add here:
 
   status AS status,
 
  To see what is really in your status field.
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
 
 
 
 -- 
 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] Enhancement: ssh:// sync method

[Steve Landers]

On 25/08/2010, at 3:46 PM, Brian Smith wrote:

 On Wed, Aug 25, 2010 at 1:25 PM, Richard Hipp d...@sqlite.org wrote:
 The latest version of Fossil (in the self-hosting Fossil repository - not
 the precompiled binaries which are a little too old) supports a new method
 of pushing, pulling, cloning, and syncing using SSH.  Examples:
 
  fossil clone ssh://usern...@hostname.com/local/path/repo.fossil
 ex1.fossil
 
  fossil clone ssh://usern...@hostname.com//full/path/name/repo.fossil
 ex2.fossil
 
 Notice that with a single / between the hostname and the beginning of the
 repository path, the repository path is relative to the home directory of
 the user.  With two // characters, the pathname to the repository is an
 absolute pathname.
 
 I'd vote for changing this notation to a more standard scp style reference.
 I.e.: usern...@hostname.com:local/path or 
 usern...@hostname.com:/full/path.
 I've got no strong opinions as to whether or not ssh:// is at the
 front of those.

+1

 This new feature currently only works on unix.  As part of the
 implementation, I needed a bidirectional popen() function.  (The standard
 library popen() only works in one direction.)  I implemented this for unix
 in the popen.c source file.  But I do not know how to do the same on
 windows.  If someone cares to contribute ideas on how to implement a
 bidirection popen() for windows, that will help me get the new ssh://
 functionality working on windows.
 
 On the other hand, no many windows machines that I have seen support ssh.
 So maybe the ssh:// method is not useful there.  What do you think, gentle
 readers?
 
 
 Putty provides a command line tool for doing such operations. Also, both
 cygwin and mingw provide ssh builds. Windows users desiring SSH functionality
 are probably used to having to jump through some hoops. Having some
 default lookups
 for Putty, cygwin, and mingw with an option to specify a custom path
 should be sufficient.
 
 While I don't personally use Windows, I think having near identical feature 
 sets
 on all platforms is important.

+1

Albeit I'm not in a position to contribute to making it happen

Steve

___
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] CGI issues

[Steve Landers]

On 20/05/2010, at 8:30 AM, Richard Hipp wrote:

 
 
 On Wed, May 19, 2010 at 8:00 PM, Michal Suchanek hramr...@centrum.cz wrote:
 
 Is the cgi feature well tested?
 
 The whole fossil website at http://www.fossil-scm.org/ is an instance of 
 fossil running as CGI.  (But not off of Apache 1.3.) 

I use it extensively, proxied behind Apache2 (to enforce ssl access) and before 
Fossil supported ssl I used stunnel fror the same purpose.

Steve

___
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] Didn't someone mention working on a fossil GUI (like Tortoise)?

[Steve Landers]

On 25/04/2010, at 4:07 PM, Ron Aaron wrote:

 I seem to recall something like that, but can't find the reference.
 
 I'm interested in that, maybe in helping out.

I mentioned that there was a proposed Google Summer of Code student project, 
which is detailed at http://wiki.tcl.tk/23186 (search for fossil).

Unfortunately, the student withdraw the application during the evaluation 
phase. If anyone is interested I can provide guidance and direction (aka 
mentoring) but I'm not in a position to do a lot of the work at the moment.

Steve
___
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] unittest Regression Testing

[Steve Landers]

On 10/04/2010, at 2:55 AM, Rob Powell wrote:

 I have been looking into various tools used for unit testing and regression 
 testing, thinking on how to approach the goal of having a regression test 
 framework for fossil.
 
 I want to use something that is fairly cross-platform, running on all 
 environments that fossil runs, windows, linux, mac.
 I want to have something that is mostly contained within itself, as few 
 external dependencies as possible.
 I want to be able to edit and add tests without going through a development 
 process of re-compiling and building the test framework.  
 Anyone (on any system) should be able to work on the framework without
 requiring specialized tools/packages to be installed.

I suggest you seriously look at the tcltest facility, used by the Tcl/Tk test 
suite. There are lots of links from the Tclers Wiki Tcltest page at 
http://wiki.tcl.tk/tcltest

It can be run by a stand-alone Tcl interpreter (single file - tclkit), is 
mature and extremely capable, with lots of examples.

Given that many in the fossil community are capable Tclers, I'd also anticipate 
a lot of support is available.

I'm all for reinventing square wheels, but on this occassion I suggest that it 
would be better to use something proven, capable, well supported and evolving :)

Steve


___
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 GUI for local source tree operations

[Steve Landers]

Folks,

Re a Fossi GUI, please note I've suggested a Tk Fossil GUI in the Google Summer 
of Code (GSOC) Tcl/TK projects. Search for Fossil in http://wiki.tcl.tk/23186

If you know of any students who would like to earn $5k over the summer whilst 
learning about GUI design and development (not to mention DVCS), please 
encourage them to visit the Tclers Wiki at http://wiki.tcl.tk/_/recent and note 
the links to the GSOC at the top of the Recent Changes page.

Steve
___
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] Autosync hangs

[Steve Landers]

On 14/11/2009, at 9:38 AM, D. Richard Hipp wrote:

 Fossil is designed in such a way that someone could decide to  
 reimplement the whole thing from scratch using a different technology  
 and the new Fossil would be able to synchronize with the old.  (There  
 are some people who have been threatening to reimplement Fossil using  
 Tcl/Tk, for example, but no results on that front yet, at least not  
 that I've heard of.)

Was that Mark or me?

Actually, we were talking about creating a Tcl/Tk binding using Critcl - 
essentially just turning Fossil into a library that can be called from Tcl 
rather than by exec'ing the Fossil command for each operation.

That might be the gateway to richer user interfaces (perhaps even sitting GitTk 
on top of Fossil, albeit that might be a bridge too far), plus also a form of 
megawidgets - scripted encapsulation of workflow.

But, as you say, no results yet.

Cheers

Steve
___
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] QLFossil - Quick Look plugin for Mac OS X

[Steve Landers]

On Oct 26, 2009, at 10:35 PM, Dmitry Chestnykh wrote:

 Hello,

 Today I wrote a Quick Look plugin for Mac OS X to quickly view
 timeline of repositories.

 You can check it out here:

 http://dev.codingrobots.org/cgi-bin/o/qlfossil/

 I hope Mac users will like it ;-)

This one does :)

Very cool - thanks for the work

Steve
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users