Re: [fossil-users] Limiting HTTP/1.1 host

[Andy Goth]

On 5/1/2015 8:12 PM, Ron W wrote:
> I somehow got the impression you wanted to limit the sources of incoming
> requests, thus my idea to limit the addresses from which the requests
> would be accepted.

Nah, usernames and passwords are better for that.  I can't know in
advance which addresses each user will use.  But I do know no legitimate
user will send "Host: 5.61.43.116" when that's not even my IP address!

-- 
Andy Goth | 



signature.asc
Description: OpenPGP digital signature
___
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] Limiting HTTP/1.1 host

[Ron W]

On Fri, May 1, 2015 at 8:56 PM, Andy Goth  wrote:

>
> My point is that any attempt to access my repository other than through
> one of the few expected hostnames is clearly illegitimate, and I wish to
> block it.  Because this is an application-layer thing, this cannot be
> done with iptables, only inside the HTTP server.
>

I somehow got the impression you wanted to limit the sources of incoming
requests, thus my idea to limit the addresses from which the requests would
be accepted.
___
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] Limiting HTTP/1.1 host

[Andy Goth]

On 4/30/2015 12:36 PM, Ron W wrote:
> On Thu, Apr 30, 2015 at 10:36 AM, Andy Goth  wrote:
>> Seems I have a lot of people trying to access my repository who have
>> no business doing so:
>>
>> I'd like to limit access based on the HTTP/1.1 Host: header.  If
>> Host: isn't un.is-a-geek.com  or
>> un.is-a-geek.com . (note final period) then
>> just drop the connection.
> 
> The HTTP Host header field is the name of "targeted" server, not the
> client's host. This field is used to support virtual hosting.

I know, and in my original email I went on to say that a refinement of
my simple request would be to implement virtual hosting.

My point is that any attempt to access my repository other than through
one of the few expected hostnames is clearly illegitimate, and I wish to
block it.  Because this is an application-layer thing, this cannot be
done with iptables, only inside the HTTP server.

-- 
Andy Goth | 



signature.asc
Description: OpenPGP digital signature
___
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] Merge operation not merging newly created files.

[Fossil User]

I think it is a bug in fossil. Bellow git work flow for compassion.

Best,
Anofos


 git init .
Initialized empty Git repository in /tmp/git_test/.git/
 echo "a" > a
 echo "b" > b
 git add a b
 git commit -m "a b"
[master (root-commit) aa9af4a] a b
 2 files changed, 2 insertions(+)
 create mode 100644 a
 create mode 100644 b
 git checkout -b branch2
Switched to a new branch 'branch2'
 git mv b c
 ls
a  c
 git commit -m "b -> c"
[branch2 32afd71] b -> c
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename b => c (100%)
 echo "b2" > b
 git add b
 git commit -m "b2"
[branch2 e72cfde] b2
 1 file changed, 1 insertion(+)
 create mode 100644 b
 git checkout master
Switched to branch 'master'
 git merge branch2
Updating aa9af4a..e72cfde
Fast-forward
 b | 2 +-
 c | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)
 create mode 100644 c
 ls -al
razem 12
drwxr-xr-x  3 as   as120 maj  2 00:10 .
drwxrwxrwt 49 root root 2420 maj  2 00:08 ..
-rw-r--r--  1 as   as  2 maj  2 00:09 a
-rw-r--r--  1 as   as  3 maj  2 00:10 b
-rw-r--r--  1 as   as  2 maj  2 00:10 c
drwxr-xr-x  8 as   as280 maj  2 00:10 .git



2015-05-01 18:59 GMT+02:00 Richard Hipp :

> Tnx.  I'm busy chasing unrelated issues in SQLite at the moment.  I'll
> look into this when I get a chance.
>
> On 5/1/15, Fossil User  wrote:
> >This  is a bash prompt.
> >
> >
> > fossil init repo
> >project-id: fb0c7719bbe9fa2723a658b8f729cf287c2d3df7
> >server-id:  608b8566ad457edc073e16a3cd7175f7b36a8bd0
> >admin-user: as (initial password is "702370")
> > fossil open repo
> >project-name: 
> >repository:   /tmp/merge/repo
> >local-root:   /tmp/merge/
> >config-db:/home/as/.fossil
> >project-code: fb0c7719bbe9fa2723a658b8f729cf287c2d3df7
> >checkout: 380ff0133ab47f54d71a7aa8cbb0a67d708bc8ec 2015-05-01
> 16:07:
> >15 UTC
> >leaf: open
> >tags: trunk
> >comment:  initial empty check-in (user: as)
> >check-ins:1
> > echo "a" > a
> > echo "b" > b
> > fossil add a b
> >ADDED  a
> >ADDED  b
> > fossil commit
> >vi "./ci-comment-476E1CDF606A.txt"
> >New_Version: 641e11cd2c5990dd5817284f81da2035449d7d08
> > fossil branch new b trunk
> >New branch: 8e3aa59de9a7c1427d901e4ebe4cac60b963e889
> > fossil co b
> >a
> >b
> > fossil branch
> >* b
> >  trunk
> > mv b c
> > fossil mv b c
> >RENAME b c
> > fossil commit
> >vi "./ci-comment-940692954A7B.txt"
> >New_Version: 56e70776f4a435e4fb81a42ca5033811cf6c07da
> > ls
> >a  c  repo
> > echo "??" > b
> > ls
> >a  b  c  repo
> > fossil add b
> >ADDED  b
> > fossil commit
> >vi "./ci-comment-F6312B62FC0A.txt"
> >New_Version: dc8246bfe50b243aaf9e69a1c18146db29829031
> > fossil co trunk
> >a
> >b
> > fossil merge b
> >RENAME b -> c
> > "fossil undo" is available to undo changes to the working checkout.
> > ls
> >a  c  repo
> > fossil timeline
> >=== 2015-05-01 ===
> >16:10:06 [dc8246bfe5] new b (user: as tags: b)
> >16:09:32 [56e70776f4] b -> c (user: as tags: b)
> >16:08:56 [8e3aa59de9] Create new branch named "b" (user: as tags: b)
> >16:08:36 [641e11cd2c] *CURRENT* a b (user: as tags: trunk)
> >16:07:15 [380ff0133a] initial empty check-in (user: as tags: trunk)
> >+++ no more data (5) +++
> > fossil branch
> >  b
> >* trunk
> > fossil commit
> >vi "./ci-comment-B0BE822ED2B5.txt"
> >New_Version: e3662c7508e1bd3a725a36eff0e3416dbf363ce7
> > fossil close
> >
> >
> > 2015-05-01 18:29 GMT+02:00 Richard Hipp :
> >
> >> On 5/1/15, Fossil User  wrote:
> >> > 3 should be create and switch to branch b
> >> >
> >> > Please see attached file, it is full console text dump.
> >> >
> >>
> >> This mailing list strips attachments.  Please paste in-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
> >>
> >
>
>
> --
> 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] Skin almost finished.

[Richard Hipp]

On 5/1/15, John Found  wrote:
>
> I missed the point here. Probably my English... It is open source.
> Why I have to sign this CA document? In addition, I can't sign it
> because I don't use PGP and don't have private/public key at all.
>

We need the signed Contributors Agreement (CA) so that we can prove
that your code is open source if that fact is ever disputed.  All CAs
are kept in a (physical) file in the firesafe here at the SQLite.org
headquarters.

The CA says, in essence, "yes my contributions to this project are
open-source too".  CAs are common practice for all (non-GPL)
open-source software.  You must sign a CA before contributing to any
apache foundation project, for example.

Print the document onto paper, then sign the piece of paper, then scan
the paper and email me the scan.

-- 
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] Skin almost finished.

[John Found]

On Fri, 1 May 2015 12:46:46 -0400
Richard Hipp  wrote:

> If you will just sign and send in a Fossil CA, I can then pull your
> code.  Then we can figure out what enhancements are needed in Fossil
> to make it convenient to use your skin without using dirty tricks like
> putting images in Wiki attachments.
> -- 
> D. Richard Hipp
> d...@sqlite.org

I missed the point here. Probably my English... It is open source. 
Why I have to sign this CA document? In addition, I can't sign it
because I don't use PGP and don't have private/public key at all.

-- 
http://fresh.flatassembler.net
http://asm32.info
John Found 
___
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] Merge operation not merging newly created files.

[Richard Hipp]

Tnx.  I'm busy chasing unrelated issues in SQLite at the moment.  I'll
look into this when I get a chance.

On 5/1/15, Fossil User  wrote:
>This  is a bash prompt.
>
>
> fossil init repo
>project-id: fb0c7719bbe9fa2723a658b8f729cf287c2d3df7
>server-id:  608b8566ad457edc073e16a3cd7175f7b36a8bd0
>admin-user: as (initial password is "702370")
> fossil open repo
>project-name: 
>repository:   /tmp/merge/repo
>local-root:   /tmp/merge/
>config-db:/home/as/.fossil
>project-code: fb0c7719bbe9fa2723a658b8f729cf287c2d3df7
>checkout: 380ff0133ab47f54d71a7aa8cbb0a67d708bc8ec 2015-05-01 16:07:
>15 UTC
>leaf: open
>tags: trunk
>comment:  initial empty check-in (user: as)
>check-ins:1
> echo "a" > a
> echo "b" > b
> fossil add a b
>ADDED  a
>ADDED  b
> fossil commit
>vi "./ci-comment-476E1CDF606A.txt"
>New_Version: 641e11cd2c5990dd5817284f81da2035449d7d08
> fossil branch new b trunk
>New branch: 8e3aa59de9a7c1427d901e4ebe4cac60b963e889
> fossil co b
>a
>b
> fossil branch
>* b
>  trunk
> mv b c
> fossil mv b c
>RENAME b c
> fossil commit
>vi "./ci-comment-940692954A7B.txt"
>New_Version: 56e70776f4a435e4fb81a42ca5033811cf6c07da
> ls
>a  c  repo
> echo "??" > b
> ls
>a  b  c  repo
> fossil add b
>ADDED  b
> fossil commit
>vi "./ci-comment-F6312B62FC0A.txt"
>New_Version: dc8246bfe50b243aaf9e69a1c18146db29829031
> fossil co trunk
>a
>b
> fossil merge b
>RENAME b -> c
> "fossil undo" is available to undo changes to the working checkout.
> ls
>a  c  repo
> fossil timeline
>=== 2015-05-01 ===
>16:10:06 [dc8246bfe5] new b (user: as tags: b)
>16:09:32 [56e70776f4] b -> c (user: as tags: b)
>16:08:56 [8e3aa59de9] Create new branch named "b" (user: as tags: b)
>16:08:36 [641e11cd2c] *CURRENT* a b (user: as tags: trunk)
>16:07:15 [380ff0133a] initial empty check-in (user: as tags: trunk)
>+++ no more data (5) +++
> fossil branch
>  b
>* trunk
> fossil commit
>vi "./ci-comment-B0BE822ED2B5.txt"
>New_Version: e3662c7508e1bd3a725a36eff0e3416dbf363ce7
> fossil close
>
>
> 2015-05-01 18:29 GMT+02:00 Richard Hipp :
>
>> On 5/1/15, Fossil User  wrote:
>> > 3 should be create and switch to branch b
>> >
>> > Please see attached file, it is full console text dump.
>> >
>>
>> This mailing list strips attachments.  Please paste in-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
>>
>


-- 
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] Skin almost finished.

[John Found]

On Fri, 1 May 2015 10:10:36 -0400
Richard Hipp  wrote:

> Off-list reply.
> 
> Do we have a CA for you on file?  If not, can you send one in
> (https://www.fossil-scm.org/fossil/doc/trunk/www/copyright-release.html)
> so that we can add your new skin as one of the options in standard
> Fossil builds?
> 
> -- 
> D. Richard Hipp
> d...@sqlite.org

The skin itself is open-source, so you can freely use it. I am not sure where I
have to write the license, but it is permissive and compatible with BSD.

But there are some technical problems. I used some tricks that will make 
it hard to pack the skin as a stand alone skin for Fossil. For example, 
it uses images attached to a wiki article. Embedding these images to the 
CSS will not be convenient, because of their size.

-- 
http://fresh.flatassembler.net
http://asm32.info
John Found 
___
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] Merge operation not merging newly created files.

[Fossil User]

   This  is a bash prompt.


    fossil init repo
   project-id: fb0c7719bbe9fa2723a658b8f729cf287c2d3df7
   server-id:  608b8566ad457edc073e16a3cd7175f7b36a8bd0
   admin-user: as (initial password is "702370")
    fossil open repo
   project-name: 
   repository:   /tmp/merge/repo
   local-root:   /tmp/merge/
   config-db:/home/as/.fossil
   project-code: fb0c7719bbe9fa2723a658b8f729cf287c2d3df7
   checkout: 380ff0133ab47f54d71a7aa8cbb0a67d708bc8ec 2015-05-01 16:07:
   15 UTC
   leaf: open
   tags: trunk
   comment:  initial empty check-in (user: as)
   check-ins:1
    echo "a" > a
    echo "b" > b
    fossil add a b
   ADDED  a
   ADDED  b
    fossil commit
   vi "./ci-comment-476E1CDF606A.txt"
   New_Version: 641e11cd2c5990dd5817284f81da2035449d7d08
    fossil branch new b trunk
   New branch: 8e3aa59de9a7c1427d901e4ebe4cac60b963e889
    fossil co b
   a
   b
    fossil branch
   * b
 trunk
    mv b c
    fossil mv b c
   RENAME b c
    fossil commit
   vi "./ci-comment-940692954A7B.txt"
   New_Version: 56e70776f4a435e4fb81a42ca5033811cf6c07da
    ls
   a  c  repo
    echo "??" > b
    ls
   a  b  c  repo
    fossil add b
   ADDED  b
    fossil commit
   vi "./ci-comment-F6312B62FC0A.txt"
   New_Version: dc8246bfe50b243aaf9e69a1c18146db29829031
    fossil co trunk
   a
   b
    fossil merge b
   RENAME b -> c
"fossil undo" is available to undo changes to the working checkout.
    ls
   a  c  repo
    fossil timeline
   === 2015-05-01 ===
   16:10:06 [dc8246bfe5] new b (user: as tags: b)
   16:09:32 [56e70776f4] b -> c (user: as tags: b)
   16:08:56 [8e3aa59de9] Create new branch named "b" (user: as tags: b)
   16:08:36 [641e11cd2c] *CURRENT* a b (user: as tags: trunk)
   16:07:15 [380ff0133a] initial empty check-in (user: as tags: trunk)
   +++ no more data (5) +++
    fossil branch
 b
   * trunk
    fossil commit
   vi "./ci-comment-B0BE822ED2B5.txt"
   New_Version: e3662c7508e1bd3a725a36eff0e3416dbf363ce7
    fossil close


2015-05-01 18:29 GMT+02:00 Richard Hipp :

> On 5/1/15, Fossil User  wrote:
> > 3 should be create and switch to branch b
> >
> > Please see attached file, it is full console text dump.
> >
>
> This mailing list strips attachments.  Please paste in-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
>
___
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] Merge operation not merging newly created files.

[Richard Hipp]

On 5/1/15, Fossil User  wrote:
> 3 should be create and switch to branch b
>
> Please see attached file, it is full console text dump.
>

This mailing list strips attachments.  Please paste in-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

Re: [fossil-users] Merge operation not merging newly created files.

[Fossil User]

3 should be create and switch to branch b

Please see attached file, it is full console text dump.

2015-05-01 18:21 GMT+02:00 Richard Hipp :

> On 5/1/15, Fossil User  wrote:
> > Hello.
> >
> > I'm using version 1.32 [6c40678e91] and I can't understand how merge
> > operation works.
> > Here is example of what I'm try to do:
> >
> > 1. branch: trunk
> > 2. commit: add file a and add file b
> >
> > 3. switch to branch b:
> > 4. commit: move b to c
>
> How is that possible since you just added file b to the repository on
> trunk and so it does not yet exist on branch b?
>
> > 5 commit: add new file b
> >
> > 6. merge b into trunk
> > but, in this step file b is not present, why?
> >
> > Example session: http://pastebin.com/cYTjMXeb
> > Repo file: http://s000.tinyupload.com/?file_id=81023289595312112568
> > 
> >
> > Best,
> > Anofos
> >
>
>
> --
> 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] Merge operation not merging newly created files.

[Richard Hipp]

On 5/1/15, Fossil User  wrote:
> Hello.
>
> I'm using version 1.32 [6c40678e91] and I can't understand how merge
> operation works.
> Here is example of what I'm try to do:
>
> 1. branch: trunk
> 2. commit: add file a and add file b
>
> 3. switch to branch b:
> 4. commit: move b to c

How is that possible since you just added file b to the repository on
trunk and so it does not yet exist on branch b?

> 5 commit: add new file b
>
> 6. merge b into trunk
> but, in this step file b is not present, why?
>
> Example session: http://pastebin.com/cYTjMXeb
> Repo file: http://s000.tinyupload.com/?file_id=81023289595312112568
> 
>
> Best,
> Anofos
>


-- 
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] Merge operation not merging newly created files.

[Fossil User]

Hello.

I'm using version 1.32 [6c40678e91] and I can't understand how merge
operation works.
Here is example of what I'm try to do:

1. branch: trunk
2. commit: add file a and add file b

3. switch to branch b:
4. commit: move b to c
5 commit: add new file b

6. merge b into trunk
but, in this step file b is not present, why?

Example session: http://pastebin.com/cYTjMXeb
Repo file: http://s000.tinyupload.com/?file_id=81023289595312112568


Best,
Anofos
___
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] Skin almost finished.

[John Found]

On Fri, 01 May 2015 08:49:30 -0400
Doug Franklin  wrote:

> On 2015-05-01 4:43, Martin S. Weber wrote:
> 
> > This is more user-friendly than deciding an optimal
> > reading width for them (that may or may not pay attention to user-styles,
> > user-selected fonts, one of the ways a document can be scaled on the
> > user-end, etc.), so here's a tip to the hat for you: *.
> 
> +100
> 
> People have different hardware; use their systems differently; configure 
> their systems differently; run different sets of applications.  Let 
> users decide how big the window should be for their usage and 
> preferences, both for browsers and for GUI apps.
> 
> -- 
> Thanks,
> DougF (KG4LMZ)
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

I agree and you can see that my skin scales pretty good for the different 
window sizes. 

But my observations are that the majority of the users use the browser in
one single mode - maximized. This way, it is good for the web designer to
take into consideration this fact, instead to blame his visitors to not
use the computer in a "proper way".

-- 
http://fresh.flatassembler.net
http://asm32.info
John Found 
___
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] Skin almost finished.

[Doug Franklin]

On 2015-05-01 4:43, Martin S. Weber wrote:


This is more user-friendly than deciding an optimal
reading width for them (that may or may not pay attention to user-styles,
user-selected fonts, one of the ways a document can be scaled on the
user-end, etc.), so here's a tip to the hat for you: *.


+100

People have different hardware; use their systems differently; configure 
their systems differently; run different sets of applications.  Let 
users decide how big the window should be for their usage and 
preferences, both for browsers and for GUI apps.


--
Thanks,
DougF (KG4LMZ)
___
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] Skin almost finished.

[Martin S. Weber]

On 2015-05-01 11:58:30, John Found wrote:
> (...)
> Well, maybe it is a bad practice, but my browser is always maximized.
> Also, all people I know maximize their browsers...

Which is why I was saying, one keystroke and you're ready for
prose-reading-mode, but the other way around, there's no way for you to
reach that. If your windowing environment STILL doesn't support at least
basic tiling, it's time to change ;)

Regards,
-Martin
___
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] Skin almost finished.

[paul]

On 30/04/15 22:12, John Found wrote:

On Fri, 1 May 2015 00:03:01 +0300
John Found  wrote:


Well, the first version of my new skin is ready and uploaded. I named it 
"ProgrammingClassic".


And the URL is: http://fresh.flatassembler.net/fossil/repo/fresh

It is published below, but I decided to post it explicitly.




Wow, that is fab, I like it a lot. Thanks for posting the link.
___
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] Skin almost finished.

[John Found]

On Fri, 1 May 2015 10:43:45 +0200
"Martin S. Weber"  wrote:

> By giving the user the control over the width of the rendered page back
> by making it a function of the browser's client width, the user can
> easily adjust the width of the browser for prose reading, often with a
> single keystroke (e.g. on windows, win+{left,right}, for me on awesome
> it mostly is one keystroke, sometimes two, depending on my active tags
> etc., but I digress). This is more user-friendly than deciding an optimal
> reading width for them (that may or may not pay attention to user-styles,
> user-selected fonts, one of the ways a document can be scaled on the
> user-end, etc.), so here's a tip to the hat for you: *.
> 

Well, maybe it is a bad practice, but my browser is always maximized.
Also, all people I know maximize their browsers...


-- 
http://fresh.flatassembler.net
http://asm32.info
John Found 
___
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] Skin almost finished.

[Martin S. Weber]

On 2015-05-01 10:09:46, John Found wrote:
> (...)
> On the one hand, increasing the width, you are increasing the use of the 
> screen area which is good.
> On the other hand, the readability of the plain text articles decreases for 
> very wide texts. 
> 
> Anyway, for the purposes of source code management, the screen use is more 
> important, so I removed 
> the max-width and now the paper will occupy the whole screen. 

By giving the user the control over the width of the rendered page back
by making it a function of the browser's client width, the user can
easily adjust the width of the browser for prose reading, often with a
single keystroke (e.g. on windows, win+{left,right}, for me on awesome
it mostly is one keystroke, sometimes two, depending on my active tags
etc., but I digress). This is more user-friendly than deciding an optimal
reading width for them (that may or may not pay attention to user-styles,
user-selected fonts, one of the ways a document can be scaled on the
user-end, etc.), so here's a tip to the hat for you: *.

Thanks & Regards,
-Martin
___
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] Skin almost finished.

[John Found]

On Thu, 30 Apr 2015 15:05:57 -0700
jungle Boogie  wrote:

> On 30 April 2015 at 14:57, Ron W  wrote:
> >
> > I like it. The maximum width of the main text area (the "paper") is a little
> > low, so I see a lot of border background. (my browser width is "set" for
> > websites with sidebars on both sides, like Gmail)
> >
> 
> It's a cool skin but I agree with Ron:
> http://fresh.flatassembler.net/fossil/repo/fresh/wdiff?name=Fresh+IDE&a=6759
> 

The problem with the above example was a missing "overflow: auto" style. It is 
fixed now.

But the problem with the "paper width" still exists. 
But this is a very common problem in the web design with the wide screen 
displays. 

On the one hand, increasing the width, you are increasing the use of the screen 
area which is good.
On the other hand, the readability of the plain text articles decreases for 
very wide texts. 

Anyway, for the purposes of source code management, the screen use is more 
important, so I removed 
the max-width and now the paper will occupy the whole screen.   

Regards

-- 
http://fresh.flatassembler.net
http://asm32.info
John Found 
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users