Re: [fossil-users] Lots of web interface changes

2017-12-06 Thread John P. Rouillard 
Hello Richard:

I have to say I like the new changes. Especially making the diff
format sticky. It was a real pain to have to keep shifting fron side
to side diff to unidiff format. Now onto the issue.

In message

Re: [fossil-users] Lots of web interface changes

2017-12-06 Thread Stephan Beal 
On Wed, Dec 6, 2017 at 10:59 PM, Richard Hipp  wrote:

> On 12/6/17, Stephan Beal  wrote:
> > On Wed, Dec 6, 2017 at 8:33 PM, Richard Hipp  wrote:
> >
> >> know.)  Are you still having the same problem with the latest
> >> code, even after hitting multiple "Reloads"?
> >>
> >
> > Just tested: no :)
>
> I just brought up chrome here on my desktop and on a Win7 laptop and
> they both seems to be working fine.  Can you give me more information
> on how to repro the problem?


Sorry, i could have been more explicit: no, i don't have the problem
anymore - it may have been a transient problem. :)

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
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] Lots of web interface changes

2017-12-06 Thread jungle Boogie 
On 6 December 2017 at 11:22, Richard Hipp  wrote:
> There have been lots of changes (hopefully, "improvements") to the web
> interface of Fossil over the past few days.  If you have not be
> following the developments, I encourage you to visit a few of the main
> sites running the latest code and let me know what you think.  Your
> suggestions and comments are very important.
>
> If you can, please download the latest trunk sources, compile on your
> own systems, and run the tip of trunk there.  Let me know if you run
> into any problems.
>
> If you want to contribute your CSS skills for better styling, that
> would be really great.  Let me know and I will set you up.
>
> Here are some links to try:
>
>  https://www.fossil-scm.org/fossil/timeline

For a comparison:
http://www2.fossil-scm.org/fossil/timeline

I really do like the tags and properties section of a check-in not
being displayed by default. And the reorganization of what's displayed
in the Overview section.

Nice job and thanks for the constant improvements.
___
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] Lots of web interface changes

2017-12-06 Thread Scott Robison 
I read that as no, he isn't having the same problem.

On Dec 6, 2017 2:59 PM, "Richard Hipp"  wrote:

> On 12/6/17, Stephan Beal  wrote:
> > On Wed, Dec 6, 2017 at 8:33 PM, Richard Hipp  wrote:
> >
> >> know.)  Are you still having the same problem with the latest
> >> code, even after hitting multiple "Reloads"?
> >>
> >
> > Just tested: no :)
>
> I just brought up chrome here on my desktop and on a Win7 laptop and
> they both seems to be working fine.  Can you give me more information
> on how to repro the problem?
>
> --
> 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] Lots of web interface changes

2017-12-06 Thread Stephan Beal 
On Wed, Dec 6, 2017 at 8:33 PM, Richard Hipp  wrote:

> know.)  Are you still having the same problem with the latest
> code, even after hitting multiple "Reloads"?
>

Just tested: no :)

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
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] Lots of web interface changes

2017-12-06 Thread The Tick 

On 12/6/2017 1:22 PM, Richard Hipp wrote:

There have been lots of changes (hopefully, "improvements") to the web
interface of Fossil over the past few days.  If you have not be
following the developments, I encourage you to visit a few of the main
sites running the latest code and let me know what you think.  Your
suggestions and comments are very important.


I have been reading the posts concerning the proposed CSS changes. I 
also am not by any means a CSS guru -- I have only a rudimentary 
knowledge of CSS.


I like to use longer commit comments and so I have used (which I found 
via this mailing list):


  span.timelineComment {
font-family: Consolas; /* optional */
white-space: pre;
  }

for my timeline. One thing I noticed is that other pages that display 
the commit comments (such as the overview on the info/ page for a 
particular commit) do not use the same (or any unique class or id that I 
could easily reference -- perhaps my CSS knowledge is just not 
sufficient) for the comment.


I would suggest that the html generated by fossil be consistent and use 
the same id= or class= tags for the elements on each page. This would 
allow one to more consistently change the look of specific elements 
displayed by fossil.


___
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] Lots of web interface changes

2017-12-06 Thread Warren Young 
On Dec 6, 2017, at 12:34 PM, Sean Woods  wrote:
> 
> https://www.fossil-scm.org/index.html/doc/trunk/www/index.wiki
> 
> See that ugly "index.html" in the URL?  Was that always there?

Yes, it was:


https://web.archive.org/web/20151225132659/http://www.fossil-scm.org/index.html/doc/trunk/www/index.wiki

It’s something specific to the way fossil-scm.org is set up.  It will not 
happen on your Fossil instances.
___
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] Lots of web interface changes

2017-12-06 Thread Warren Young 
On Dec 6, 2017, at 12:22 PM, Richard Hipp  wrote:
> 
> (6) CSP headers says:  "default-src 'self' 'unsafe-inline’".

Don’t undersell the advantages.  That’s a significant improvement already:

1. It disallows all eval() cases, which closes off a whole class of attacks.

2. It disallows active content from third-party sites even if someone manages 
to inject a reference to such into the page itself.

It’s one of those 90/10 things: the first 90% of the work took 90% of the 
development time, and the remaining 10% of the work will take the other 90% of 
the development time. :)
___
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] Lots of web interface changes

2017-12-06 Thread Sean Woods 

On Wed, Dec 6, 2017, at 02:22 PM, Richard Hipp wrote:
> There have been lots of changes (hopefully, "improvements") to the web
> interface of Fossil over the past few days.  If you have not be
> following the developments, I encourage you to visit a few of the main
> sites running the latest code and let me know what you think.  Your
> suggestions and comments are very important.

One thing I notice is that when I type fossil-scm.org into my browser it
redirects me to the following URL:

https://www.fossil-scm.org/index.html/doc/trunk/www/index.wiki

See that ugly "index.html" in the URL?  Was that always there?  I feel
like it wasn't.  Should it be there?

I noticed this a few days ago but thought someone would see it; perhaps
not...
___
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] Lots of web interface changes

2017-12-06 Thread Richard Hipp 
On 12/6/17, Stephan Beal  wrote:
>
> FYI: i noticed two days ago that on my tablet (Chrome browser) that the
> various timeline links all point to the honeypot page. It seems the bot
> detection got unduly stringent (i know that's an ongoing war).
>

I didn't change the algorithm any.  I just moved all of the javascript
code out of in-line and into a separate file.  I also turned on CSP,
which may have broken some "setTimeout()" calls, though I think I have
now fixed that.  (I'm learning more about JS than I really wanted to
know.)  Are you still having the same problem with the latest
code, even after hitting multiple "Reloads"?

-- 
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] Lots of web interface changes

2017-12-06 Thread Stephan Beal 
On Wed, Dec 6, 2017 at 8:22 PM, Richard Hipp  wrote:

> There have been lots of changes (hopefully, "improvements") to the web
> interface of Fossil over the past few days.  If you have not be
> following the developments, I encourage you to visit a few of the main
> sites running the latest code and let me know what you think.  Your
> suggestions and comments are very important.
>

FYI: i noticed two days ago that on my tablet (Chrome browser) that the
various timeline links all point to the honeypot page. It seems the bot
detection got unduly stringent (i know that's an ongoing war).

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Lots of web interface changes

2017-12-06 Thread Richard Hipp 
There have been lots of changes (hopefully, "improvements") to the web
interface of Fossil over the past few days.  If you have not be
following the developments, I encourage you to visit a few of the main
sites running the latest code and let me know what you think.  Your
suggestions and comments are very important.

If you can, please download the latest trunk sources, compile on your
own systems, and run the tip of trunk there.  Let me know if you run
into any problems.

If you want to contribute your CSS skills for better styling, that
would be really great.  Let me know and I will set you up.

Here are some links to try:

 https://www.fossil-scm.org/fossil/timeline
 https://sqlite.org/src/timeline
 http://mirror1.tcl.tk/tcl/timeline

Summary of changes:

(1) The new choice-of-style option on timelines.  Your most recent
choice is remembered in a cookie and becomes the new default.

(2) Other display choices are also remembered in the same cookie, so
that you don't have to constantly change your view to your
preferences.

   (a)  Number of rows in a timeline graph
   (b)  Show just check-ins or everything in a timeline
   (c)  Unified or side-by-side diffs

(3) Changes to the check-in information page (ex:
https://www.fossil-scm.org/fossil/ci/f8bc3ce8) to put more useful
information near the top, and omit seldom used information.  The "Tags
& Properties" are split out into a separate screen (ex:
https://www.fossil-scm.org/fossil/ci_tags/f8bc3ce8c7142435)

(4) When linking to a file timeline, it jumps to the specific version
of the file you referenced.

Behind-the-scenes changes:

(5) Lots of in-line javascript has been split out into separate
javascript files.  This is a work in progress.  There is still some
in-line javascript, but not nearly as much as there once was.  There
is still lots of work to do in omitting in-line CSS.

(6) CSP headers says:  "default-src 'self' 'unsafe-inline'".  The goal
is to be able to remove the unsafe-inline qualifier, but as I pointed
out in (5), I am not there yet.

-- 
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] How to disable crlf warning permanently

2017-12-06 Thread Warren Young 
On Dec 6, 2017, at 2:03 AM, Scott Doctor  wrote:
> 
> I do not get why that warning even exists.

Because people working on cross-platform projects often have one user (there’s 
always one) who opens a text file with Unix line endings on a Windows box and 
commits it with DOS line endings, thus potentially causing downstream damage.

You may say, “But all decent tools these days understand both styles!”  And 
you’d be either wrong or at least incomplete while being mostly right.

Case in point, if you use autosetup — as the Fossil and SQLite source code 
bases do, among others — and commit any *.in file with DOS line endings, the 
next time autosetup processes that file to produce the .in-free output version, 
you’ll get a mix of DOS and Unix line endings: Unix on those lines where 
autosetup made a substitution, and DOS on all the other lines.  This in turn 
can break other software.  (Ask me how I know.)

Another case in point, this time for the opposite case: you might have software 
that insists on DOS line endings.  Let’s pick as a completely random example 
U/W FOCAL. [1]  Even though that software runs under Linux, the input files to 
U/W FOCAL for that project need to have DOS line endings.

And yet another case in point, other Linux software in that same project uses 
DOS line endings because that’s what the upstream project uses, so if we change 
them all to Unix style, it complicates merging upstream changes into our source 
base.

So yeah, some of us appreciate Fossil catching unintended line ending 
conversions for us and would actually like to see an “lf-glob” feature to catch 
the inverse problem from the one it currently checks for.



[1]: https://tangentsoft.com/pidp8i/artifact/15a27bbf29ef6cd9
___
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 disable crlf warning permanently

2017-12-06 Thread Warren Young 
On Dec 6, 2017, at 2:12 AM, Jan Nijtmans  wrote:
> 
> 2017-12-06 10:03 GMT+01:00 Scott Doctor:
>> 
>> How can I permanently turn off the crlf warning that occurs when I do I do a
>> commit without having to use the crlf-glob command each time?  I do not get
>> why that warning even exists.
> 
> Just create a directory ".fossil-settings”

…at the project root.  It won’t work anywhere else.

> and put a file named
> "crlf-glob" in it.

…with the content you were passing to “fossil set crlf-glob”.

Then “fossil unset crlf-glob” to avoid the warning about overlapping settings.
___
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 disable crlf warning permanently

2017-12-06 Thread Jan Nijtmans 
2017-12-06 10:03 GMT+01:00 Scott Doctor:
>
> How can I permanently turn off the crlf warning that occurs when I do I do a
> commit without having to use the crlf-glob command each time?  I do not get
> why that warning even exists.

Just create a directory ".fossil-settings", and put a file named
"crlf-glob" in it.
 .fossil-settings/crlf-glob

Fossil itself has an example:


Then do
 fossil add .fossil-settings/crlf-glob
 fossil commit

The warning will be gone once and for all.

Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] How to disable crlf warning permanently

2017-12-06 Thread Scott Doctor 


How can I permanently turn off the crlf warning that occurs when 
I do I do a commit without having to use the crlf-glob command 
each time?  I do not get why that warning even exists.



--

-
Scott Doctor
sc...@scottdoctor.com
-

___
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

2017-12-06 Thread Richard Hipp 
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 allow reading the commit
> messages top to bottom
> without interfering visually too much), it would fit wide screen much
> better IMHO.
>
> We could call it "modern wide-screen" for example. My $0.02. --DD
>

Good idea.  I have assigned the "draft5" skin to you on the main
Fossil website, so that you can experiment with this approach and show
us what you have in mind.  If you come up with a good look, I'll add
it as a new "Wide Screen" option.

You'll need to login as user "ddevie...@gmail.com" in order to edit
the draft5 skin.  I'll send you your password by private email.

A quick web search suggests that using "overflow: hidden; white-space:
nowrap;" might serve to keep the comment text all on one line.

-- 
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