I've hacked in a change so that the file tree viewer shows the age (how
long ago the last change occurred) for each file. Or for directories it
shows youngest age of all contented files and subdirectories.
Example:
https://www.fossil-scm.org/fossil/tree?ci=trunk
I'm not yet convinced that
On Tue, Dec 16, 2014 at 5:42 PM, Richard Hipp d...@sqlite.org wrote:
I'm not yet convinced that this change is actually useful, though. It is
still on a branch. Suggestions for improving it are welcomed.
It's consistent with various hosting services, e.g. (IIRC) the old CVS/SVN
browser in
What platform is it running on, and what version of Fossil have you got?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
NetBSD, [a0cc614326]
-bch
On 12/16/14, Warren Young w...@etr-usa.com wrote:
What platform is it running on, and what version of Fossil have you got?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
On Tue, Dec 16, 2014 at 11:57 AM, Stephan Beal sgb...@googlemail.com
wrote:
On Tue, Dec 16, 2014 at 5:42 PM, Richard Hipp d...@sqlite.org wrote:
I'm not yet convinced that this change is actually useful, though. It is
still on a branch. Suggestions for improving it are welcomed.
It's
On Tue, Dec 16, 2014 at 8:06 PM, Richard Hipp d...@sqlite.org wrote:
The problem was it was difficult to follow the line from the filename
across to its age. We need some leading. Rather than that, I highlight
the li element on mouse-over. See the latest on the website.
The mouseover is
On Tue, Dec 16, 2014 at 5:42 PM, Richard Hipp d...@sqlite.org wrote:
https://www.fossil-scm.org/fossil/tree?ci=2008-01-01expand
you're obviously in an experimental mood, so here's something which clearly
falls into the interesting to try out, but might turn out ugly category:
add a heat
On Tue, Dec 16, 2014 at 2:11 PM, Stephan Beal sgb...@googlemail.com wrote:
It also begs the question: how can we sort on that column (using JS) if we
prettify the times?
Maybe have the epoc time as a hidden field? Possibly less overhead that
running the prettify JS in the browser, though that
On Tue, Dec 16, 2014 at 8:15 PM, Ron W ronw.m...@gmail.com wrote:
On Tue, Dec 16, 2014 at 2:11 PM, Stephan Beal sgb...@googlemail.com
wrote:
It also begs the question: how can we sort on that column (using JS) if
we prettify the times?
Maybe have the epoc time as a hidden field? Possibly
On Tue, Dec 16, 2014 at 2:11 PM, Stephan Beal sgb...@googlemail.com wrote:
The latest code now shows the time of the check-in and file times relative
to the main check-in time, as a negative interval. I think that works
better.
i think i'd rather see something like the mouseover than the
On Tue, Dec 16, 2014 at 8:27 PM, Richard Hipp d...@sqlite.org wrote:
That's all controlled by CSS so it is easy to customize. I added
overrides in the CSS for the canonical Fossil site. But I don't think I
like them. Take a look and see what you think.
Much nicer - toning down the lines
Hi Richard,
On 16 December 2014 at 11:27, Richard Hipp d...@sqlite.org wrote:
On Tue, Dec 16, 2014 at 2:11 PM, Stephan Beal sgb...@googlemail.com wrote:
The latest code now shows the time of the check-in and file times
relative to the main check-in time, as a negative interval. I think
On Tue, Dec 16, 2014 at 2:27 PM, Stephan Beal sgb...@googlemail.com wrote:
(i'm thinking of the sort mechanism we already have in place. i think a
hidden field might require extending that.)
As best I understand, CSS can hide the extra column, just need to make sure
the sort button for the
On Tue, Dec 16, 2014 at 2:42 PM, Ron W ronw.m...@gmail.com wrote:
On Tue, Dec 16, 2014 at 2:27 PM, Stephan Beal sgb...@googlemail.com
wrote:
(i'm thinking of the sort mechanism we already have in place. i think a
hidden field might require extending that.)
As best I understand, CSS can
Hi Richard,
On 16 December 2014 at 11:52, Richard Hipp d...@sqlite.org wrote:
On Tue, Dec 16, 2014 at 2:42 PM, Ron W ronw.m...@gmail.com wrote:
On Tue, Dec 16, 2014 at 2:27 PM, Stephan Beal sgb...@googlemail.com
wrote:
(i'm thinking of the sort mechanism we already have in place. i think a
On Tue, Dec 16, 2014 at 3:11 PM, jungle Boogie jungleboog...@gmail.com
wrote:
Sorting by age is doable, but I think (at least for the initial
implementation) it will be a new page request - in other words a server
round-trip.
Take a look at this: http://tablesorter.com/docs/
Since the
On Tue, Dec 16, 2014 at 9:15 PM, Richard Hipp d...@sqlite.org wrote:
I think tablesorter simply sorts a single linear table. That's not what
is going on here. We are sorting a tree. That's a little different.
i was only thinking of sorting for this one:
Hi Stephen,
On 16 December 2014 at 12:20, Stephan Beal sgb...@googlemail.com wrote:
On Tue, Dec 16, 2014 at 9:15 PM, Richard Hipp d...@sqlite.org wrote:
I think tablesorter simply sorts a single linear table. That's not what
is going on here. We are sorting a tree. That's a little
On Tue, Dec 16, 2014 at 3:53 PM, jungle Boogie jungleboog...@gmail.com
wrote:
Additionally/alternatively, some search feature around the checkin
link to help filter results better. (similar to control F in the
browser but have it actually remove non-matched items). ;)
You can add a query
Hi Richard,
On 16 December 2014 at 13:04, Richard Hipp d...@sqlite.org wrote:
You can add a query parameter re=REGEXP where REGEXP is a regular
expression and it will only show the files that match that regular
expression.
So, for example, to see just the files (and their folders) that
Thus said jungle Boogie on Tue, 16 Dec 2014 13:47:32 -0800:
I'm curious what unhiding here:
https://www.fossil-scm.org/fossil/timeline actually does.
Try it here:
https://www.fossil-scm.org/index.html/timeline?c=2014-11-06+21:46:01
Andy
--
TAI64 timestamp: 40005490ab17
Hello,
I discovered something strange when moving repositories (I wanted to
consolidate the location of some of mine). After some searching I came
up with three possibilities for a repository relocation:
1) Simple moving the file and then updating the location both in the
global
There is now an mtime query parameter on the /tree page which orders the
contents of each directory from mostly recently modified down to least
recently. Example:
https://www.fossil-scm.org/fossil/tree?ci=trunkmtime
I still need to add controls so that the user can click to select the sort
Please try with trunk.
On Tue, Dec 16, 2014 at 6:19 PM, Robert Engelhardt
m...@robert-engelhardt.de wrote:
Hello,
I discovered something strange when moving repositories (I wanted to
consolidate the location of some of mine). After some searching I came up
with three possibilities for a
Given the much improved tree-view functionality
https://www.fossil-scm.org/fossil/tree?ci=trunkmtime
Is there really any reason to keep the legacy Flat-View on the menu bar?
https://www.fossil-scm.org/fossil/tree?ci=trunktype=flat
I think the flat-view functionality should be
On Wed, Dec 17, 2014 at 2:05 AM, Richard Hipp d...@sqlite.org wrote:
Given the much improved tree-view functionality
https://www.fossil-scm.org/fossil/tree?ci=trunkmtime
Is there really any reason to keep the legacy Flat-View on the menu bar?
On Wed, Dec 17, 2014 at 2:16 AM, Stephan Beal sgb...@googlemail.com wrote:
Actually... i use the flat view more often than not. That's probably just
historical momentum (and the way my old menus are all set up). i wouldn't
whine about loss of flat view, but also won't argue for its removal.
On Tue, Dec 16, 2014 at 8:17 PM, Stephan Beal sgb...@googlemail.com wrote:
On Wed, Dec 17, 2014 at 2:16 AM, Stephan Beal sgb...@googlemail.com
wrote:
Actually... i use the flat view more often than not. That's probably just
historical momentum (and the way my old menus are all set up). i
On Dec 16, 2014, at 6:05 PM, Richard Hipp d...@sqlite.org wrote:
But I don't see a reason to have it using up valuable menu-bar space.
Screen real estate is precious. Nuke that sucker.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
I'm curious about the coding convention in fossil with respect to
variable naming. It seems that the code follows something like the
following convention:
- integers have no prefix
- strings have a z prefix e.g. zParam
- pointers have a p prefix e.g. pSomething
- function pointers have an x
On Tue, Dec 16, 2014 at 9:20 PM, Sean Woods s...@seanwoods.com wrote:
I'm curious about the coding convention in fossil with respect to
variable naming. It seems that the code follows something like the
following convention:
- integers have no prefix
Sometime they have i for integer. Or
Thus said Sean Woods on Tue, 16 Dec 2014 21:20:51 -0500:
- integers have no prefix
I believe there is an exception for when they represent something that
may be ``boolean'' in which case:
- boolean integers have a b prefix e.g. bBlame
Andy
--
TAI64 timestamp: 40005490ed29
On Wed, Dec 17, 2014 at 3:40 AM, Andy Bradford amb-fos...@bradfords.org
wrote:
Thus said Sean Woods on Tue, 16 Dec 2014 21:20:51 -0500:
- integers have no prefix
I believe there is an exception for when they represent something that
may be ``boolean'' in which case:
- boolean
I think the key thing is that symbol names convey what they are used for.
Dr. Simonyi, nominal originator of Hungarian Notation, seems to agree in
his paper about naming conventions. Microsoft has republished that paper:
http://msdn.microsoft.com/en-us/library/aa260976%28v=vs.60%29.aspx
My key
On Dec 16, 2014, at 7:37 PM, Richard Hipp d...@sqlite.org wrote:
But they are useful at times.
Yes. It’s not as useful as a type system that simply doesn’t let you do
questionable things,[*] but when you have to write in C or C++, it’s good to
buttress the type system with some notation.
Hi Richard,
On 16 December 2014 at 17:05, Richard Hipp d...@sqlite.org wrote:
Given the much improved tree-view functionality
https://www.fossil-scm.org/fossil/tree?ci=trunkmtime
Is there really any reason to keep the legacy Flat-View on the menu bar?
This is excellent.
On Dec 16, 2014 9:31 PM, Warren Young w...@etr-usa.com wrote:
On Dec 16, 2014, at 7:37 PM, Richard Hipp d...@sqlite.org wrote:
But they are useful at times.
Yes. It's not as useful as a type system that simply doesn't let you do
questionable things,[*] but when you have
Hello All,
Just to make sure I'm not missing something rather obvious, it's not
yet possible to edit code / source within fossil, correct?
I can see that it's possible to make changes to attributes of a
specific check-in like the comments, color, and branching.
This is from September 2011 so
On Tue, Dec 16, 2014 at 10:29 PM, Warren Young w...@etr-usa.com wrote:
On Dec 16, 2014, at 7:37 PM, Richard Hipp d...@sqlite.org wrote:
But they are useful at times.
Yes. It’s not as useful as a type system that simply doesn’t let you do
questionable things,[*] but when you have to write
39 matches
Mail list logo