On Tue, Dec 23, 2014 at 5:28 PM, Joerg Sonnenberger wrote:
> On Tue, Dec 23, 2014 at 03:15:41PM +0200, Baruch Burstein wrote:
> > I just discovered that the JS I used is not supported in IE<=9. What is
> the
> > policy on supporting older browsers?
>
> I would normally draw the line at IE 8. Depe
On Tue, Dec 23, 2014 at 03:15:41PM +0200, Baruch Burstein wrote:
> I just discovered that the JS I used is not supported in IE<=9. What is the
> policy on supporting older browsers?
I would normally draw the line at IE 8. Depending on the specific code,
IE 7 can be reasonable, older normally is no
On Tue, Dec 23, 2014 at 3:52 PM, Richard Hipp wrote:
>
>
>
> On Tue, Dec 23, 2014 at 8:43 AM, Baruch Burstein
> wrote:
>
>>
>>
>> On Tue, Dec 23, 2014 at 3:23 PM, Richard Hipp wrote:
>>>
>>>
>>> On Tue, Dec 23, 2014 at 8:15 AM, Baruch Burstein
>>> wrote:
>>>
On Thu, Dec 18, 2014 at 1:22 A
On Tue, Dec 23, 2014 at 8:43 AM, Baruch Burstein
wrote:
>
>
> On Tue, Dec 23, 2014 at 3:23 PM, Richard Hipp wrote:
>>
>>
>> On Tue, Dec 23, 2014 at 8:15 AM, Baruch Burstein
>> wrote:
>>
>>> On Thu, Dec 18, 2014 at 1:22 AM, Baruch Burstein
>>> wrote:
>>>
I just pushed a rough try at d
On Tue, Dec 23, 2014 at 3:23 PM, Richard Hipp wrote:
>
>
> On Tue, Dec 23, 2014 at 8:15 AM, Baruch Burstein
> wrote:
>
>> On Thu, Dec 18, 2014 at 1:22 AM, Baruch Burstein
>> wrote:
>>
>>>
>>> I just pushed a rough try at doing this filtering client-side
>>> as-you-type. Needs polish, but works.
On Tue, Dec 23, 2014 at 8:15 AM, Baruch Burstein
wrote:
> On Thu, Dec 18, 2014 at 1:22 AM, Baruch Burstein
> wrote:
>
>>
>> I just pushed a rough try at doing this filtering client-side
>> as-you-type. Needs polish, but works. It does only a simple text match, but
>> it would be trivial to chang
On Thu, Dec 18, 2014 at 1:22 AM, Baruch Burstein
wrote:
>
> I just pushed a rough try at doing this filtering client-side as-you-type.
> Needs polish, but works. It does only a simple text match, but it would be
> trivial to change this to case-insensitive and/or regex matching by
> changing whic
Thus said Joel Bruick on Sat, 20 Dec 2014 21:51:31 -0500:
> Sorry I haven't been able to contribute anything in quite a while, but
> this should be fixed on trunk now.
Thanks, the change is much appreciated, especially on high resolution
displays.
Andy
--
TAI64 timestamp: 40005496680c
Richard Hipp wrote:
(1) Adjust the CSS so that the age is not all the way over on the
right margin
Sorry I haven't been able to contribute anything in quite a while, but
this should be fixed on trunk now.
___
fossil-users mailing list
fossil-users
On Tue, Dec 16, 2014 at 11:04 PM, Richard Hipp wrote:
>
>
>
> On Tue, Dec 16, 2014 at 3:53 PM, jungle Boogie
> 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 rem
On Wed, Dec 17, 2014 at 8:06 PM, Ashwin Hirschi
wrote:
>
> It seems to me that the display of file ages would be improved by removing
> the minus signs.
>
> People would then read e.g. "64.7 days" as: this file is 64.7 days *old*
> (or, older than the reference point).
>
> Another way to look at i
Dear Tonyp,
From: to...@acm.org
Sent: Wed, 17 Dec 2014 21:47:58 +0200
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] File age in the tree view
>
Just to note that on Win7 (Firefox browser – if it matters), the
mouse-overshadi
Just to note that on Win7 (Firefox browser – if it matters), the mouse-over
shading is so faint that if I hadn’t read about it here I wouldn’t have noticed
it at all.
Can you make it a little more visible?___
fossil-users mailing list
fossil-users@list
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
It seems to me that the
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=trunk&mtime
I still need to add controls so that the user can click to select the sor
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
_
Hi Richard,
On 16 December 2014 at 13:04, Richard Hipp 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 contain the
>
On Tue, Dec 16, 2014 at 3:53 PM, jungle Boogie
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 parameter "re=REGEX
Hi Stephen,
On 16 December 2014 at 12:20, Stephan Beal wrote:
> On Tue, Dec 16, 2014 at 9:15 PM, Richard Hipp 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
On Tue, Dec 16, 2014 at 9:15 PM, Richard Hipp 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:
https://www.fossil-scm.org/fossil/fileage?name=
On Tue, Dec 16, 2014 at 3:11 PM, jungle Boogie
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 data that
Hi Richard,
On 16 December 2014 at 11:52, Richard Hipp wrote:
>
>
> On Tue, Dec 16, 2014 at 2:42 PM, Ron W wrote:
>>
>> On Tue, Dec 16, 2014 at 2:27 PM, Stephan Beal
>> wrote:
>>>
>>> (i'm thinking of the sort mechanism we already have in place. i think a
>>> hidden field might require extending
On Tue, Dec 16, 2014 at 2:42 PM, Ron W wrote:
>
> On Tue, Dec 16, 2014 at 2:27 PM, Stephan Beal
> 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 ne
On Tue, Dec 16, 2014 at 2:27 PM, Stephan Beal 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 age column refers
Hi Richard,
On 16 December 2014 at 11:27, Richard Hipp wrote:
>
>
> On Tue, Dec 16, 2014 at 2:11 PM, Stephan Beal 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.
>>
>
On Tue, Dec 16, 2014 at 8:27 PM, Richard Hipp 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 makes all th
On Tue, Dec 16, 2014 at 2:11 PM, Stephan Beal 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 lines aroun
On Tue, Dec 16, 2014 at 8:15 PM, Ron W wrote:
>
> On Tue, Dec 16, 2014 at 2:11 PM, Stephan Beal
> 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
On Tue, Dec 16, 2014 at 2:11 PM, Stephan Beal 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 would be an optio
On Tue, Dec 16, 2014 at 5:42 PM, Richard Hipp wrote:
>
> https://www.fossil-scm.org/fossil/tree?ci=2008-01-01&expand
>
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 map (like a
On Tue, Dec 16, 2014 at 8:06 PM, Richard Hipp 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 element on mouse-over. See the latest on the website.
>
The mouseover is great :).
T
On Tue, Dec 16, 2014 at 11:57 AM, Stephan Beal
wrote:
>
> On Tue, Dec 16, 2014 at 5:42 PM, Richard Hipp 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 host
On Tue, Dec 16, 2014 at 5:42 PM, Richard Hipp 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 Sourceforge a
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
34 matches
Mail list logo
