On 12/6/17, Dominique Devienne wrote:
>
> If there was 1 "modern" view (i.e. with boxes) but with a 2-lines setup,
> with the first line
> for commit message in the "normal" font, and a second for the meta-data and
> links in a
> smaller font with a bit less visibility (to
On Tue, Dec 5, 2017 at 4:27 PM, Richard Hipp wrote:
> On 12/5/17, Reimer Behrends wrote:
> > Richard Hipp wrote:
> >> Which is better?
> >>
> >>A: https://www.fossil-scm.org/a/timeline
> >>B: https://www.fossil-scm.org/b/timeline
> >
> > I don't
On Tue, 05 Dec 2017 16:27:28 +0100, Richard Hipp wrote:
Please keep a close eye on the Fossil website and report any usability
issues.
just a thought: could/should the boxes+checkin messages be indented,
reflecting the horizontal position of the respective branch in the
On 12/5/17, Reimer Behrends wrote:
> Richard Hipp wrote:
>> Which is better?
>>
>>A: https://www.fossil-scm.org/a/timeline
>>B: https://www.fossil-scm.org/b/timeline
>
> I don't see much of a difference,
Thanks for looking. But the original question is old, and the
I agree. Why does the [brief-hash] need to be a hyperlink and bracketed
when the Timeline time stamp has the same link?
On Tue, Dec 5, 2017 at 9:30 AM, Reimer Behrends wrote:
> Richard Hipp wrote:
>
>> Which is better?
>>
>>A: https://www.fossil-scm.org/a/timeline
>>
Richard Hipp wrote:
Which is better?
A: https://www.fossil-scm.org/a/timeline
B: https://www.fossil-scm.org/b/timeline
I don't see much of a difference, to be honest (but that may be because
I'm late to the party and the layouts have changed during the past
days). The
On 2017-11-24 9:35, Richard Hipp wrote:
Which is better?
A: https://www.fossil-scm.org/a/timeline
B: https://www.fossil-scm.org/b/timeline
They both use too much vertical screen space, IMO.
Also:
A: https://www.fossil-scm.org/a/finfo?name=src/search.c
B:
Thus said Jungle Boogie on Tue, 28 Nov 2017 22:08:58 -0800:
> In which mode? I think this is only an issue in the compact mode,
> right?
Yes, after further experimentation, the problem only exists with the
Compact mode.
Andy
--
TAI64 timestamp: 40005a1fa5b8
Focusing on the Compact view:
Is there any chance to limit the click action to just the ellipses?
And to revert, click on the added content, Ex. "check-in:" or "user:".
As others mentioned, it is annoying when selecting text from the comments
to have the background action.
On Wed, Nov 29, 2017 at
On Nov 29, 2017, at 8:26 AM, Richard Hipp wrote:
>
> On 11/29/17, Warren Young wrote:
>>
>>https://imgur.com/a/TEWjA
>
> I think we'd like the selection mechanism to somehow highlight the
> entire row
I don’t think it really helps, but this gets you
On Nov 29, 2017, at 8:27 AM, Martin Gagnon wrote:
>
>> It can be fixed by adding href="#" into the elements
>
> Using "Inspect" on chrome, I found that adding:
>
> cursor: pointer;
>
> inside "element.style" fix the problem.
That feels more heavy-handed to me. My
Hi Andy,
On 29/11/17 00:45, Andy Bradford wrote:
> Thus said Offray Vladimir Luna C?rdenas on Mon, 27 Nov 2017 18:20:44 -0500:
>
>> I agree with Warren's design and improved readability by adding space.
>> Timeline now has more "air to breath" and is more pleasant to the eye.
> If you're talking
On 11/29/17, Warren Young wrote:
>>
>> Still looks goofy in the Modern View, especially using Edge. Your
>> help in fixing that problem will be much appreciated.
>
> It’s applying the style to the containing rather than to the that
> most of the recent changes have been
On Wed, Nov 29, 2017 at 08:10:28AM -0700, Warren Young wrote:
> On Nov 29, 2017, at 7:53 AM, Martin Gagnon wrote:
> >
> > There's a small display glitch, the mouse cursor over the
> > Basic/Advanced button is set to "text selection" mode instead of the
> > usual "hand with the
On Nov 29, 2017, at 8:16 AM, Warren Young wrote:
>
> [*] To be clear, that means the element ends up with two classes.
Even more clear:
...
td.timelineSelected {
border-width: 2px;
background-color: #ffc;
box-shadow: 4px 4px 2px rgba(0, 0, 0, 0.5);
}
On Nov 29, 2017, at 7:26 AM, Richard Hipp wrote:
>
> The "selected entry" highlighting, such as seen here:
>
>https://www.fossil-scm.org/fossil/timeline?c=trunk
>
> Still looks goofy in the Modern View, especially using Edge. Your
> help in fixing that problem will be
On Nov 29, 2017, at 7:53 AM, Martin Gagnon wrote:
>
> There's a small display glitch, the mouse cursor over the
> Basic/Advanced button is set to "text selection" mode instead of the
> usual "hand with the index finger up" for clickable links.
It can be fixed by adding
On Wed, Nov 29, 2017 at 09:26:57AM -0500, Richard Hipp wrote:
> The 4-view-modes timeline change is now on trunk and is the default on
> these sites:
>
> https://sqlite.org/src/timeline
> https://www.fossil-scm.org/fossil/timeline
> http://mirror1.tcl.tk/tcl/timeline
>
The 4-view-modes timeline change is now on trunk and is the default on
these sites:
https://sqlite.org/src/timeline
https://www.fossil-scm.org/fossil/timeline
http://mirror1.tcl.tk/tcl/timeline
https://androwish.org/index.html/timeline
The "selected entry" highlighting, such as
On Tue 28 Nov 2017 10:36 PM, Andy Bradford wrote:
> Thus said Richard Hipp on Mon, 27 Nov 2017 17:41:55 -0500:
>
> > I have installed the new look (temporarily at least) on
> > https://www.fossil-scm.org/fossil so that we can live with it for a
> > while to see how we like it.
>
Thus said Richard Hipp on Tue, 28 Nov 2017 22:33:04 -0500:
> Maybe "Verbose" should be modified to include the hash up front
This was one of the factors that actually lead to my #1 ranking for
Verbose.
Andy
--
TAI64 timestamp: 40005a1e5143
Thus said Richard Hipp on Tue, 28 Nov 2017 22:08:38 -0500:
> Please offer your opinions on:
>
> https://www.fossil-scm.org/b/timeline
I see that you've corrected one of the problems I mentioned previously
which was the melding of different comments in the same branch by
introducing
On Tue 28 Nov 2017 10:40 PM, Andy Bradford wrote:
> Thus said Richard Hipp on Mon, 27 Nov 2017 17:41:55 -0500:
>
> > The big down-side is that less information is visible on a single
> > screen now, so you have to scroll more. But that seems to be the trend
> > with websites these days
>
Thus said Richard Hipp on Mon, 27 Nov 2017 21:01:37 -0500:
> As it was yesterday:
>https://www.fossil-scm.org/fossil/timeline
Hard to stomach (as previously mentioned).
> Warren Young's new approach:
>https://www2.fossil-scm.org/fossil/timeline
Slightly better, but still has the
Thus said Offray Vladimir Luna C?rdenas on Mon, 27 Nov 2017 18:20:44 -0500:
> I agree with Warren's design and improved readability by adding space.
> Timeline now has more "air to breath" and is more pleasant to the eye.
If you're talking about what is currently visible on
Thus said Richard Hipp on Mon, 27 Nov 2017 17:41:55 -0500:
> The big down-side is that less information is visible on a single
> screen now, so you have to scroll more. But that seems to be the trend
> with websites these days
There's another extremely annoying downside to this as
Thus said Richard Hipp on Mon, 27 Nov 2017 17:41:55 -0500:
> I have installed the new look (temporarily at least) on
> https://www.fossil-scm.org/fossil so that we can live with it for a
> while to see how we like it.
I tend to prefer having more information to less, but
Richard Hipp wrote:
>
> "Verbose" mode now looks like legacy.
>
Thank you, much appreciated.
--
Joe Mistachkin @ https://urn.to/r/mistachkin
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
A view of the dbpage branch of SQLite on the GitHub mirror:
https://github.com/mackyle/sqlite/commits/dbpage
The same information from the latest experimental Fossil:
http://www.sqlite.org/srcxb/timeline?ss=n=34=dbpage=ci
--
D. Richard Hipp
d...@sqlite.org
I like it. Thanks
On 29 Nov 2017, 10:17 AM +0800, Warren Young , wrote:
> On Nov 27, 2017, at 7:04 PM, Steve Landers wrote:
> >
> > Note that I would retain the rounded corners on Warren’s backgrounds, they
> > make the visuals “softer”.
>
> You
On 11/28/17, Joe Mistachkin wrote:
>
> Yeah, something like that would be cool. Also, having the "Leaf" indicator,
> et al, up front as well (like before)?
"Verbose" mode now looks like legacy.
--
D. Richard Hipp
d...@sqlite.org
On 11/28/17, Richard Hipp wrote:
>
> Limitations:
>
(5) The selected-entry highlighting is messed up for MS-Edge. Ex:
https://www.fossil-scm.org/b/timeline?ss=n=2017-07-07 - suggestions
for how to fix this are welcomed.
--
D. Richard Hipp
d...@sqlite.org
Richard Hipp wrote:
>
> Maybe "Verbose" should be modified to include the hash up front
>
Yeah, something like that would be cool. Also, having the "Leaf" indicator,
et al, up front as well (like before)?
--
Joe Mistachkin @ https://urn.to/r/mistachkin
On 11/28/17, Joe Mistachkin wrote:
>
> Richard Hipp wrote:
>>
>> (1) You have a selection of styles: Normal, Compact, Verbose,
>> Columnar. Each can be styled separately.
>>
>
> Pretty please, can we have a "Legacy" style that gives the old look?
>
Maybe "Verbose" should
Richard Hipp wrote:
>
> (1) You have a selection of styles: Normal, Compact, Verbose,
> Columnar. Each can be styled separately.
>
Pretty please, can we have a "Legacy" style that gives the old look?
I think not having the check-in at the front of the line is going to
be a huge pain for me
On 11/28/17, Richard Hipp wrote:
> Please offer your opinions on:
>
> https://www.fossil-scm.org/b/timeline
Other comparison repositories:
http://mirror1.tcl.tk/tcl-b/timeline
https://sqlite.org/b/timeline
>
> Changes:
>
> (1) You have a selection of styles:
Please offer your opinions on:
https://www.fossil-scm.org/b/timeline
Changes:
(1) You have a selection of styles: Normal, Compact, Verbose,
Columnar. Each can be styled separately.
(2) The style selection, the number of elements in the timeline, and
whether the timeline shows just
On Nov 28, 2017, at 3:12 AM, Johan Kuuse wrote:
>
> I think the one important thing is that all involved HTML elements have a
> 'class' or 'id' tag.
Yes. Several times in making my last custom Fossil skin, I’ve had to employ
some rather clever CSS selector trickery to target
On Nov 27, 2017, at 7:04 PM, Steve Landers 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;
On 11/28/17, Johan Kuuse wrote:
> I think it is impossible to get "one style fits all"...
>
Indeed. So my latest strategy is to provide a combobox in the submenu
that lets the user selected between a small number of formats:
"Compact", "Relaxed", "Detailed" (new name suggestions
On 25 November 2017 at 08:53, Richard Hipp wrote:
> Send me your ideas of what you think timelines should look like. Even
> better: send me mock-ups.
Since we’re at it, I’m going ahead with some other CSS suggestions. Here I’ve
mostly focused on “calendar” demarcations which
On Tue, Nov 28, 2017 at 3:07 AM, David Mason wrote:
> I would like yesterdays with a bit of whitespace between commit comments.
>
> Also someone liked the original because the checkin tag was in a
> predictable place. If you put the tag last in the extra information it
>
I would like yesterdays with a bit of whitespace between commit comments.
Also someone liked the original because the checkin tag was in a
predictable place. If you put the tag last in the extra information it
would be predictably at the right margin.
On 27 November 2017 at 21:01, Richard Hipp
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 , wrote:
> On 11/27/17, Steve Landers wrote:
> > Nice work.
> >
> > Have you considered dropping the
On 11/27/17, Steve Landers 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
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
On 27/11/17 18:02, Warren Young wrote:
> On Nov 27, 2017, at 3:46 PM, Warren Young wrote:
>> On Nov 27, 2017, at 3:41 PM, Richard Hipp wrote:
>>> The big down-side is that less
>>> information is visible on a single screen now, so you have to scroll
>>>
On Nov 27, 2017, at 3:46 PM, Warren Young wrote:
>
> On Nov 27, 2017, at 3:41 PM, Richard Hipp wrote:
>>
>> The big down-side is that less
>> information is visible on a single screen now, so you have to scroll
>> more. But that seems to be the trend with
On Nov 27, 2017, at 3:41 PM, Richard Hipp wrote:
>
> The big down-side is that less
> information is visible on a single screen now, so you have to scroll
> more. But that seems to be the trend with websites these days….
The design ideas I tapped into this were old when
On 11/27/17, Warren Young wrote:
>
> table.timelineTable {
> border-collapse: separate;
> }
> td.timelineTableCell {
> vertical-align: top;
> text-align: left;
> padding: 0.75em;
> border: 1px #ccc solid;
> border-radius: 1em;
> }
> span.timelineDetail {
>
On 27 November 2017 at 14:13, Warren Young wrote:
> On Nov 24, 2017, at 7:35 AM, Richard Hipp wrote:
>>
>> Which is better?
>>
>> A: https://www.fossil-scm.org/a/timeline
>> B: https://www.fossil-scm.org/b/timeline
>
> I prefer A because I don’t like
On Nov 24, 2017, at 7:35 AM, Richard Hipp wrote:
>
> Which is better?
>
> A: https://www.fossil-scm.org/a/timeline
> B: https://www.fossil-scm.org/b/timeline
I prefer A because I don’t like having to dig for details. Hiding details
isn’t the answer to clutter. Drawing
Thus said Jacob MacDonald on Fri, 24 Nov 2017 18:52:41 +:
> Seems like I'm in the minority, but I prefer the A version. I tend to
> like compact UIs and having all the relevant information close
> together and the commit hash prominently displayed is nice.
The only reason why I
Thus said Richard Hipp on Fri, 24 Nov 2017 11:12:14 -0500:
> Now fixed.
Verified.
> Other changes on https://www.fossil-scm.org/b/timeline since the
> original comparison request:
>
> (1) The "details" section is shown on a separate line below the
> check-in comment.
I just
On Fri 24 Nov 2017 7:25 PM, sky5w...@gmail.com wrote:
> Wow, #5 is super clean and easy on the eyes!
> And #12 is interesting if I can see it with Per-Item Time Format = (off)?
>
> Thanks for the changes!
#5 is nice, and especially with the easy option to switch back to
advanced. Perhaps the
Wow, #5 is super clean and easy on the eyes!
And #12 is interesting if I can see it with Per-Item Time Format = (off)?
Thanks for the changes!
On Fri, Nov 24, 2017 at 7:12 PM, Richard Hipp wrote:
> On 11/24/17, Zakero wrote:
> >
> > tldr; This new change of
On 11/24/17, Zakero wrote:
>
> tldr; This new change of the timeline makes it harder to find useful links.
>
There is now a per-repository configuration option under
Setup/Timeline that lets you choose which timeline format you prefer.
https://www.fossil-scm.org/fossil/ is
Looking at the commit message data, it has a 4 types of information:
- The check-in link
- The commit message
- Leaf, Closed-Leaf
- Detail (user, tags)
For me, the most important piece of information is the check-in link. Now,
l have to search for the link because it is no longer in a consistent
On Fri, Nov 24, 2017 at 06:52:41PM +, Jacob MacDonald wrote:
> Seems like I'm in the minority, but I prefer the A version. I tend to like
> compact UIs and having all the relevant information close together and the
> commit hash prominently displayed is nice.
Same for me.
With B
Seems like I'm in the minority, but I prefer the A version. I tend to like
compact UIs and having all the relevant information close together and the
commit hash prominently displayed is nice.
On Fri, Nov 24, 2017 at 12:32 PM David Mason wrote:
> I like the B cases... in fact
I like the B cases... in fact I'd indent the details a bit so that the
comments are easier to find visually.
On 24 November 2017 at 11:53, wrote:
> I understand the need for links, but do users really need truncated hashes
> for every line?
> Can the link be applied more
I understand the need for links, but do users really need truncated hashes
for every line?
Can the link be applied more subtly?
Can there be a similar "quiet" setting for the Timeline like *Per-Item Time
Format = (off) *to conserve space?
My commits prepend a simple timestamp in the comment and
On 11/24/17, bch wrote:
>>
>> (1) The "details" section is shown on a separate line below the
>> check-in comment.
>> (2) The "details" are in the same font-color as the comment-text
>> but have a slightly reduced font size.
>>
>
> I don’t see that reflected on the
On Fri, Nov 24, 2017 at 8:12 AM Richard Hipp wrote:
> On 11/24/17, Richard Hipp wrote:
> > On 11/24/17, Andy Bradford wrote:
> >> I still miss the Leaf, which I do find useful.
> >
> > Ugh. I didn't intend to omit the "Leaf" and
On 11/24/17, Richard Hipp wrote:
> On 11/24/17, Andy Bradford wrote:
>> I still miss the Leaf, which I do find useful.
>
> Ugh. I didn't intend to omit the "Leaf" and "Closed-Leaf" marks,
> though I did want to move them to the end, rather than before
On 11/24/17, Andy Bradford wrote:
> I still miss the Leaf, which I do find useful.
Ugh. I didn't intend to omit the "Leaf" and "Closed-Leaf" marks,
though I did want to move them to the end, rather than before the
check-in comment. The omission of that information is
On 11/24/17, Andy Bradford wrote:
> Thus said Richard Hipp on Fri, 24 Nov 2017 09:35:55 -0500:
>
>> The change here is to emphasis the check-in comment and de-emphasize
>> the links to the check-in details and other information.
>
> Hopefully this change is simply
Thus said Richard Hipp on Fri, 24 Nov 2017 10:13:22 -0500:
> Alternative CSS that causes the "details" to appears on a separate
> line from the comment:
>
> A: https://sqlite.org/src/timeline
> B: https://sqlite.org/b/timeline
I think it looks slightly cleaner with the ``details''
Thus said Richard Hipp on Fri, 24 Nov 2017 09:35:55 -0500:
> The change here is to emphasis the check-in comment and de-emphasize
> the links to the check-in details and other information.
Hopefully this change is simply accomplished with some CSS. That way
those who prefer their UI to
Thus said Richard Hipp on Fri, 24 Nov 2017 09:35:55 -0500:
> Which is better?
>
> A: https://www.fossil-scm.org/a/timeline
> B: https://www.fossil-scm.org/b/timeline
I prefer A. I don't like muted colors for text. I prefer seeing text
than to have to look for text that begins to
Am 24.11.17 um 16:17 schrieb Richard Hipp:
> If the entire check-in comment is a hyperlink, that would make it
> difficult to have hyperlinks embedded within the check-in comment.
I totally agree. So far I only use ticket IDs that are automatically
linked but this is very important to me. If the
On 11/24/17, j. van den hoff wrote:
>
> personally, I rather like the tidiness of the timeline graph available in
> mercurial via `hg serve' ... so one might think about doing something similar
> (remove hash display and link the commit message itself to the 'chekin'
>
On 11/24/17, Richard Hipp wrote:
> Which is better?
>
> A: https://www.fossil-scm.org/a/timeline
> B: https://www.fossil-scm.org/b/timeline
>
Alternative CSS that causes the "details" to appears on a separate
line from the comment:
A: https://sqlite.org/src/timeline
On Fri, 24 Nov 2017 15:35:55 +0100, Richard Hipp wrote:
Which is better?
A: https://www.fossil-scm.org/a/timeline
B: https://www.fossil-scm.org/b/timeline
Also:
A: https://www.fossil-scm.org/a/finfo?name=src/search.c
B:
Hi,
I'd like to object the default use of low-contrast type in
professional software :)
I use displays that are adjusted for low eye strain by reducing
contrast and brightness. Having type and typography do the same thing
again has the opposite effect and legibility starts to suffer.
Regards,
Which is better?
A: https://www.fossil-scm.org/a/timeline
B: https://www.fossil-scm.org/b/timeline
Also:
A: https://www.fossil-scm.org/a/finfo?name=src/search.c
B: https://www.fossil-scm.org/b/finfo?name=src/search.c
Surf about from any of the links above for additional views.
The
76 matches
Mail list logo