Re: [fossil-users] Windows make fail: mkcss.c

[jungle Boogie]

On 29 November 2017 at 15:35, jungle Boogie  wrote:
> On 29 November 2017 at 15:06, jungle Boogie  wrote:
>> Hi All,
>>
>> First time to compile Fossil on Windows in awhile, so this might me a
>> fault of my own doing.
>>
>>  ..\src\../skins/original/header.txt
>> ..\src\../skins/plain_gray/css.txt  ..\src\../skins/plain_gr
>> ../skins/plain_gray/header.txt  ..\src\../skins/rounded1/css.txt
>> ..\src\../skins/rounded1/details
>> nded1/header.txt  ..\src\../skins/xekri/css.txt
>> ..\src\../skins/xekri/details.txt  ..\src\../skin
>> iff.tcl  ..\src\markdown.md  ..\src\wiki.wiki > builtin_data.h
>> cl /nologo /MT /O2 ..\src\mkcss.c
>> mkcss.c
>> ..\src\mkcss.c(79): warning C4129: '%': unrecognized character escape 
>> sequence
>> mkcss.exe ..\src\default_css.txt ..\src\default_css.txt default_css.h
>> Usage: .\mkcss.exe INPUTFILE OUTPUTFILE
>> NMAKE : fatal error U1077: '.\mkcss.exe' : return code '0x1'
>> Stop.
>>
>
>
> nmake /f Makefile.msc clean
> nmake /f Makefile.msc I get this now:
>
> khaki/footer.txt  ..\src\../skins/khaki/header.txt
> ..\src\../skins/original/css.txt  ..\src\../skins/original/details.txt
>  ..\src\../skins/original/footer.txt
>  ..\src\../skins/original/header.txt
> ..\src\../skins/plain_gray/css.txt
> ..\src\../skins/plain_gray/details.txt
> ..\src\../skins/plain_gray/footer.txt  ..\src\
> ../skins/plain_gray/header.txt  ..\src\../skins/rounded1/css.txt
> ..\src\../skins/rounded1/details.txt
> ..\src\../skins/rounded1/footer.txt  ..\src\../skins/rou
> nded1/header.txt  ..\src\../skins/xekri/css.txt
> ..\src\../skins/xekri/details.txt  ..\src\../skins/xekri/footer.txt
> ..\src\../skins/xekri/header.txt  ..\src\d
> iff.tcl  ..\src\markdown.md  ..\src\wiki.wiki > builtin_data.h
> mkcss.exe ..\src\default_css.txt ..\src\default_css.txt default_css.h
> Usage: .\mkcss.exe INPUTFILE OUTPUTFILE
> NMAKE : fatal error U1077: '.\mkcss.exe' : return code '0x1'
> Stop.

Still failing with latest changes and nmake /f Makefile.msc and with
buildmsvc.bat:

    mkbuiltin.exe --prefix ..\src/ ..\src\../skins/aht/details.txt
 ..\src\../skins/black_and_white/css.txt
..\src\../skins/black_and_white/details.txt  ..
\src\../skins/black_and_white/footer.txt
..\src\../skins/black_and_white/header.txt
..\src\../skins/blitz/css.txt  ..\src\../skins/blitz/details.txt
..\src\.
./skins/blitz/footer.txt  ..\src\../skins/blitz/header.txt
..\src\../skins/blitz/ticket.txt
..\src\../skins/blitz_no_logo/css.txt  ..\src\../skins/blitz_no_lo
go/details.txt  ..\src\../skins/blitz_no_logo/footer.txt
..\src\../skins/blitz_no_logo/header.txt
..\src\../skins/blitz_no_logo/ticket.txt  ..\src\../skins/bo
otstrap/css.txt  ..\src\../skins/bootstrap/details.txt
..\src\../skins/bootstrap/footer.txt
..\src\../skins/bootstrap/header.txt  ..\src\../skins/default/css.
txt  ..\src\../skins/default/details.txt
..\src\../skins/default/footer.txt  ..\src\../skins/default/header.txt
 ..\src\../skins/eagle/css.txt  ..\src\../skins
/eagle/details.txt  ..\src\../skins/eagle/footer.txt
..\src\../skins/eagle/header.txt  ..\src\../skins/enhanced1/css.txt
..\src\../skins/enhanced1/details.txt
  ..\src\../skins/enhanced1/footer.txt
..\src\../skins/enhanced1/header.txt  ..\src\../skins/khaki/css.txt
..\src\../skins/khaki/details.txt  ..\src\../skins/
khaki/footer.txt  ..\src\../skins/khaki/header.txt
..\src\../skins/original/css.txt  ..\src\../skins/original/details.txt
 ..\src\../skins/original/footer.txt
 ..\src\../skins/original/header.txt
..\src\../skins/plain_gray/css.txt
..\src\../skins/plain_gray/details.txt
..\src\../skins/plain_gray/footer.txt  ..\src\
../skins/plain_gray/header.txt  ..\src\../skins/rounded1/css.txt
..\src\../skins/rounded1/details.txt
..\src\../skins/rounded1/footer.txt  ..\src\../skins/rou
nded1/header.txt  ..\src\../skins/xekri/css.txt
..\src\../skins/xekri/details.txt  ..\src\../skins/xekri/footer.txt
..\src\../skins/xekri/header.txt  ..\src\d
iff.tcl  ..\src\markdown.md  ..\src\wiki.wiki > builtin_data.h
cl /nologo /MT /O2 ..\src\mkcss.c
mkcss.c
mkcss.exe ..\src\default_css.txt default_css.h
..\src\default_css.txt:1: syntax error
NMAKE : fatal error U1077: '.\mkcss.exe' : return code '0x1'
Stop.

Build failure, errors were encountered.



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] Fossil version 1.31 testing

[Joe Prostko]

On Mon, Feb 23, 2015 at 1:16 PM, Richard Hipp  wrote:
> New tarball with the missing files has been uploaded.

Are you sure about that?  I tried buliding on two separate OS's now
(Manjaro Linux and Haiku) and it fails to build with either with the
same error as previously mentioned.  This is the source tar.gz in
question: https://www.fossil-scm.org/download/fossil-src-20150223162734.tar.gz

Here is the build failure which occurs after ./configure and make:

cc -o bld/mkbuiltin ./src/mkbuiltin.c
bld/mkbuiltin --prefix ./src/ ./src/../skins/black_and_white/css.txt
./src/../skins/black_and_white/footer.txt
./src/../skins/black_and_white/header.txt
./src/../skins/default/css.txt ./src/../skins/default/footer.txt
./src/../skins/default/header.txt ./src/../skins/eagle/css.txt
./src/../skins/eagle/footer.txt ./src/../skins/eagle/header.txt
./src/../skins/enhanced1/css.txt ./src/../skins/enhanced1/footer.txt
./src/../skins/enhanced1/header.txt ./src/../skins/etienne1/css.txt
./src/../skins/etienne1/footer.txt ./src/../skins/etienne1/header.txt
./src/../skins/khaki/css.txt ./src/../skins/khaki/footer.txt
./src/../skins/khaki/header.txt ./src/../skins/plain_gray/css.txt
./src/../skins/plain_gray/footer.txt
./src/../skins/plain_gray/header.txt ./src/../skins/rounded1/css.txt
./src/../skins/rounded1/footer.txt ./src/../skins/rounded1/header.txt
./src/diff.tcl ./src/markdown.md >bld/builtin_data.h
cc -o bld/makeheaders ./src/makeheaders.c
make: *** No rule to make target 'src/../manifest.uuid', needed by
'bld/VERSION.h'.  Stop.


- joe
___
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] Windows make fail: mkcss.c

[jungle Boogie]

On 29 November 2017 at 15:06, jungle Boogie  wrote:
> Hi All,
>
> First time to compile Fossil on Windows in awhile, so this might me a
> fault of my own doing.
>
>  ..\src\../skins/original/header.txt
> ..\src\../skins/plain_gray/css.txt  ..\src\../skins/plain_gr
> ../skins/plain_gray/header.txt  ..\src\../skins/rounded1/css.txt
> ..\src\../skins/rounded1/details
> nded1/header.txt  ..\src\../skins/xekri/css.txt
> ..\src\../skins/xekri/details.txt  ..\src\../skin
> iff.tcl  ..\src\markdown.md  ..\src\wiki.wiki > builtin_data.h
> cl /nologo /MT /O2 ..\src\mkcss.c
> mkcss.c
> ..\src\mkcss.c(79): warning C4129: '%': unrecognized character escape sequence
> mkcss.exe ..\src\default_css.txt ..\src\default_css.txt default_css.h
> Usage: .\mkcss.exe INPUTFILE OUTPUTFILE
> NMAKE : fatal error U1077: '.\mkcss.exe' : return code '0x1'
> Stop.
>


nmake /f Makefile.msc clean
nmake /f Makefile.msc I get this now:

khaki/footer.txt  ..\src\../skins/khaki/header.txt
..\src\../skins/original/css.txt  ..\src\../skins/original/details.txt
 ..\src\../skins/original/footer.txt
 ..\src\../skins/original/header.txt
..\src\../skins/plain_gray/css.txt
..\src\../skins/plain_gray/details.txt
..\src\../skins/plain_gray/footer.txt  ..\src\
../skins/plain_gray/header.txt  ..\src\../skins/rounded1/css.txt
..\src\../skins/rounded1/details.txt
..\src\../skins/rounded1/footer.txt  ..\src\../skins/rou
nded1/header.txt  ..\src\../skins/xekri/css.txt
..\src\../skins/xekri/details.txt  ..\src\../skins/xekri/footer.txt
..\src\../skins/xekri/header.txt  ..\src\d
iff.tcl  ..\src\markdown.md  ..\src\wiki.wiki > builtin_data.h
mkcss.exe ..\src\default_css.txt ..\src\default_css.txt default_css.h
Usage: .\mkcss.exe INPUTFILE OUTPUTFILE
NMAKE : fatal error U1077: '.\mkcss.exe' : return code '0x1'
Stop.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Windows make fail: mkcss.c

[jungle Boogie]

Hi All,

First time to compile Fossil on Windows in awhile, so this might me a
fault of my own doing.

 ..\src\../skins/original/header.txt
..\src\../skins/plain_gray/css.txt  ..\src\../skins/plain_gr
../skins/plain_gray/header.txt  ..\src\../skins/rounded1/css.txt
..\src\../skins/rounded1/details
nded1/header.txt  ..\src\../skins/xekri/css.txt
..\src\../skins/xekri/details.txt  ..\src\../skin
iff.tcl  ..\src\markdown.md  ..\src\wiki.wiki > builtin_data.h
cl /nologo /MT /O2 ..\src\mkcss.c
mkcss.c
..\src\mkcss.c(79): warning C4129: '%': unrecognized character escape sequence
mkcss.exe ..\src\default_css.txt ..\src\default_css.txt default_css.h
Usage: .\mkcss.exe INPUTFILE OUTPUTFILE
NMAKE : fatal error U1077: '.\mkcss.exe' : return code '0x1'
Stop.

Any hints on correcting this?

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] Metadata in Timeline Verbose View

[Rolf Ade]

Florian Balmer writes:
> At first I maintained my own Fossil skins. But after two or three
> updates, even with only simple changes to the default CSS, I gave up
> my own skins, as I didn't want to spend my hobby time with CSS
> diffing.

It's mixing completely different things and levels but -- having own
skins and CSS as branch of the main trunk(s) (the build-in skins) and to
be able to merge the own skins/CSS from the build-in skins, as they
development ...

It would just feel right.
___
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] Where did the skins go

[Svyatoslav Mishyn]

(Mon, 26 Mar 15:53) Scott Doctor:
> I updated my copy of fossil to the latest version. I created a new
> repository, launched the fossil ui, opened admin->skins, all I see is the
> options to create a new skin. What happened to all of the predefined skins?

they are here: /setup_skin_admin (Step 8 from admin->skins).

Note as you can read from /setup_skin page you can't edit directly
predefined skins anymore, in order to do it, first you need to
initialize some of draft[1-9] skin (Step 3 from /setup_skin), then make
edits (Step 4), check if everything look ok (Step 5), and publish that
new draft skin (Step 7, mark two checkboxes).

After that it will appear in /setup_skin_admin page under Draft skins
section.


-- 
https://www.juef.space/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Please contribute "skins"

[Richard Hipp]

It just become easier to extend and enhance the set of built-in
"skins" that Fossil supports.  Each "skin" now consists of three
files, named "css.txt", "header.txt", and "footer.txt", in a unique
folder under "skins/" in the source tree.  See

  
https://www.fossil-scm.org/fossil/tree?ci=5137cd5e881766&name=skins&expand=1

Now that these files are so much easier to see and edit, I hope that
there will be renewed interest in improving and extending them.

If you have suggestions on how to improve the existing skins, please
send in diffs, either to this list or to one of the developers (like
me).

If you have interesting skins of your own that you would like to
contribute, just save off the CSS, Header, and Footer configurations
and email them to a developer (probably me) via private email for
consideration.  Also please include a "Contributors Agreement"
(https://www.fossil-scm.org/fossil/doc/tip/www/copyright-release.pdf)
which releases your contribution under the 2-clause BSD license so
that we can include it in a standard Fossil build.

-- 
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] Can't change skins on server repo

[Steve Schow]

haven’t used that command yet at all.  i wasn’t trying to copy skins from local 
to server, I was just trying to login to the webui on the server and use it 
directly through the webui.  Go into admin section and hit the link for skins 
and then there are install buttons for each of the skins you guys have 
provided, but they don’t change anything, the skin always just stays on the 
default one.

I only mentioned the local repo because when I use the webui of the local repo 
I am able to change the skins just fine.  When I try to use the webui of the 
non local repo…I can’t change the skins.


On Apr 25, 2016, at 11:46 AM, Richard Hipp  wrote:

> On 4/25/16, Steve Schow  wrote:
>> I’m having trouble changing skins.  It works on my local repo, but not on
>> the server repo.
>> 
>> 1 - created repo on machine A.  setup user foobar with s privs.
>> 
>> 2 - created clone of that repo on machine B.  also with user foobar with s
>> privs
>> 
>> 3 - Working on the local machine B, I can run fossil ui, and i’m able to
>> change the skins all i want.
>> 
>> 4 - if I start machine A as a server with “fossil server’ and then connect
>> to that ui from machine B…I’m able to create tickets and everything else
>> I’ve tried has worked but if I try to chose a different skin, it just stays
>> on the default.
>> 
>> what am I missing?
> 
> Did you do "fossil config push skin" to move your local changes over
> to the server?
> 
> -- 
> 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] Please suggest built-in skin fixes and improvements

[jungle boogie]

Thus said Richard Kipp on Sun, 17 Dec 2017 21:11:30 -0500

You can now see the canonical Fossil self-hosting repository using any
of the built-in skins by visiting links from this page:
https://www.fossil-scm.org/skins/


Thanks for the link, this is a very handy way to see all the skins.

This is primarily to Zakero, who's very responsive with my suggestions 
on the cool skin.


https://www.fossil-scm.org/skins/xekri/info/a6c5a4620a5388fd

In the context section of the link above, there's no highlighting around 
the commit text.


This is what it looks like on the default skin:

http://www.fossil-scm.org/index.html/info/a6c5a4620a5388fd

No background color here:

https://www.fossil-scm.org/skins/xekri/timeline?c=2017-12-18+02:06:40

vs.

http://www.fossil-scm.org/index.html/timeline?c=2017-12-18+02:06:40


I'd personally say the background color of the timeline needs a little 
more contrast:


https://www.fossil-scm.org/skins/xekri/timeline

I know drh just committed the css to implement a background color, so a 
more noticeable color is only needed, IMO.


Thanks!

___
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] Please suggest built-in skin fixes and improvements

[Zakero]

On Mon, Dec 18, 2017 at 9:30 PM, jungle boogie 
wrote:

> Thus said Richard Kipp on Sun, 17 Dec 2017 21:11:30 -0500
>
>> You can now see the canonical Fossil self-hosting repository using any
>> of the built-in skins by visiting links from this page:
>> https://www.fossil-scm.org/skins/
>>
>
> Thanks for the link, this is a very handy way to see all the skins.
>
> This is primarily to Zakero, who's very responsive with my suggestions on
> the cool skin.
>

Hey Jungle!

Sorry I have been slow to update the skin.  Whenever I look for free time I
end up with a divide-by-zero error. :-/
Hopefully the skin updates will begin soon...


> https://www.fossil-scm.org/skins/xekri/info/a6c5a4620a5388fd
>
> In the context section of the link above, there's no highlighting around
> the commit text.
>
> This is what it looks like on the default skin:
>
> http://www.fossil-scm.org/index.html/info/a6c5a4620a5388fd
>
> No background color here:
>
> https://www.fossil-scm.org/skins/xekri/timeline?c=2017-12-18+02:06:40
>
> vs.
>
> http://www.fossil-scm.org/index.html/timeline?c=2017-12-18+02:06:40
>
>
> I'd personally say the background color of the timeline needs a little
> more contrast:
>
> https://www.fossil-scm.org/skins/xekri/timeline
>
> I know drh just committed the css to implement a background color, so a
> more noticeable color is only needed, IMO.
>
> Thanks!
>

Thanks for the notes!  I am bookmarking the emails about the skins (and CSS
in general) so I won't lose track of them.  Lots of good comments and
feedback on this list.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Fossil Skins with help menu for 'nobody'

[jungle Boogie]

Hello All,

Kind of a continuation of this thread:
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg19442.html

Specifically regarding user permissions later on in the thread.

The following skins have the help menu exposed even if user 'nobody'
has no permissions:
-Enhanced Default
-Eagle
-Xekri

Is this expected for only these skins or should it match the other six skins?

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
___
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] Skins

[Richard Hipp]

On Sun, Jul 25, 2010 at 7:39 AM, Michael Richter wrote:

> Looking more into the skinning issue, it looks to me like the file skins.c
> contains a bunch of stuff that could be generated trivially from a script of
> some sort.  Is there any interest in me making the skinning system more
> flexible so it's easier to add a new skin by basically just checking in
> three files under a new directory?  The idea would be something like this:
>
> 
> | ...
> +- skins
> | |
> | +- skinname1
> | | |
> | | +- skininfo.txt
> | | |
> | | +- style.css
> | | |
> | | +- header.html
> | | |
> | | +- footer.html
> | |
> | +- skinname2
> | ...
>
> Then inside src would be a utility like translate that walks over all the
> subdirectories of ./skins, grabs the explanatory information from
> skininfo.txt, grabs the style, header and footer code and builds skins.c
> exactly as it is now (but with more skins, naturally) before translate is
> run on it and fossil as a whole is built.
>

Please do so.

If the translator is written in C (ex: translate.c, makeheaders.c,
mkindex.c) then that would be best.  Simply integrate the translator into
the makefile.  If the translator requires a script language, which might not
be installed on the target machine, than arrange for the translator to be
run separately and the output file (skinsdata.c?) checked in to the Fossil
repository, just as the "makemake.tcl" script generates the "main.mk"
makefile.

Fossil already links against zlib.  So you might as well compress the
content and store it as
an array of unsigned chars.  That will help keep the standalone executable
smaller as we accumulate more skins.

For development purposes, it would be nice to have a command-line option to
force the use of one of your skin folders:

 fossil server -skin skins/test-skin-one

That way, designers could edit the CSS, header, and footer files in the
specified directory and immediately see the result simply by clicking the
"Reload" button on their browser, without having to go through a recompile
process.

Another idea would be to write a read-only virtual table for SQLite that
allowed us to read the skins using SQL statements.  That way, the
user-defined skins stored in the repository database and the built-in skins
compiled into the code could be managed all by the same SQL statements in
the display logic.

Please check-in your changes into a branch for the time being.  We'll move
them over to the trunk once we settle on a final solution - we'll probably
need to iterate a few times first.



>
> The advantage to this system is that people can add new skins easily,
> without any C hacking, by simply providing four files under a subdirectory
> of ./skins:
>
>- skininfo.txt provides the name of the skin, a brief description and
>(optionally) the name of the author.
>- style.css, header.html and footer.html just do what their respective
>sections in skins.c do.
>
> A further advantage is that people unfamiliar with C won't accidentally
> insert subtle, hard-to-catch bugs.
>
> --
> "Perhaps people don't believe this, but throughout all of the discussions
> of entering China our focus has really been what's best for the Chinese
> people. It's not been about our revenue or profit or whatnot."
> --Sergey Brin, demonstrating the emptiness of the "don't be evil" mantra.
>
> ___
> 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] Please contribute "skins"

[Richard Hipp]

On 1/22/15, Samuel Debionne  wrote:
> Here is my take on skins (see attached file). You may try it with :
>
> fossil config import bootstrap.skin
>
> or see it in action here :
>
> https://flintcode.com/repo/skin

When I clone this repo and bring it up locally, or when I "fossil
config import" the attachment that you sent, I get a very different
(and incomplete) look from what I see when I visit the URL above.  I
don't know why...

>
> It uses boostrap CSS (part of it actually, it's a custom build with the
> unusable feature removed).
>
> In the footer, some javascript do restyle (e.g. add/remove classes) to
> some elements (mostly table) to take advantage of Bootstrap.
>
> The repo mentionned before can be used to develop/debug the skin if
> necessary...
>
> Le 22/01/2015 03:14, Richard Hipp a écrit :
>> It just become easier to extend and enhance the set of built-in
>> "skins" that Fossil supports.  Each "skin" now consists of three
>> files, named "css.txt", "header.txt", and "footer.txt", in a unique
>> folder under "skins/" in the source tree.  See
>>
>>
>> https://www.fossil-scm.org/fossil/tree?ci=5137cd5e881766&name=skins&expand=1
>>
>> Now that these files are so much easier to see and edit, I hope that
>> there will be renewed interest in improving and extending them.
>>
>> If you have suggestions on how to improve the existing skins, please
>> send in diffs, either to this list or to one of the developers (like
>> me).
>>
>> If you have interesting skins of your own that you would like to
>> contribute, just save off the CSS, Header, and Footer configurations
>> and email them to a developer (probably me) via private email for
>> consideration.  Also please include a "Contributors Agreement"
>> (https://www.fossil-scm.org/fossil/doc/tip/www/copyright-release.pdf)
>> which releases your contribution under the 2-clause BSD license so
>> that we can include it in a standard Fossil build.
>>
>
>


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

[Michael Richter]

Looking more into the skinning issue, it looks to me like the file skins.c
contains a bunch of stuff that could be generated trivially from a script of
some sort.  Is there any interest in me making the skinning system more
flexible so it's easier to add a new skin by basically just checking in
three files under a new directory?  The idea would be something like this:


| ...
+- skins
| |
| +- skinname1
| | |
| | +- skininfo.txt
| | |
| | +- style.css
| | |
| | +- header.html
| | |
| | +- footer.html
| |
| +- skinname2
| ...

Then inside src would be a utility like translate that walks over all the
subdirectories of ./skins, grabs the explanatory information from
skininfo.txt, grabs the style, header and footer code and builds skins.c
exactly as it is now (but with more skins, naturally) before translate is
run on it and fossil as a whole is built.

The advantage to this system is that people can add new skins easily,
without any C hacking, by simply providing four files under a subdirectory
of ./skins:

   - skininfo.txt provides the name of the skin, a brief description and
   (optionally) the name of the author.
   - style.css, header.html and footer.html just do what their respective
   sections in skins.c do.

A further advantage is that people unfamiliar with C won't accidentally
insert subtle, hard-to-catch bugs.

-- 
"Perhaps people don't believe this, but throughout all of the discussions of
entering China our focus has really been what's best for the Chinese people.
It's not been about our revenue or profit or whatnot."
--Sergey Brin, demonstrating the emptiness of the "don't be evil" mantra.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Where did the skins go

[Scott Doctor]

I updated my copy of fossil to the latest version. I created a 
new repository, launched the fossil ui, opened admin->skins, all 
I see is the options to create a new skin. What happened to all 
of the predefined skins?



--

-
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] Metadata in Timeline Verbose View

[Rolf Ade]

Warren Young writes:
> On Dec 11, 2017, at 3:09 PM, Rolf Ade  wrote:
>> Florian Balmer writes:
>>> I didn't want to spend my hobby time with CSS
>>> diffing.
>> 
>> ...having own
>> skins and CSS as branch of the main trunk(s) (the build-in skins) and to
>> be able to merge the own skins/CSS from the build-in skins, as they
>> development …
>
> Try:
>
>$ fossil conf export skin foo
>…upgrade Fossil, switch repo to skin you wish to merge…
>$ fossil conf merge foo
>
> I haven’t tested it, but it looks like it should work. See “fossil
> help conf” for more on this.

AFAIS this "merge" fossil configurations in the sense that it replaces
just the areas found in the merge file. It doesn't merge the imported
conf skin in any way in the sense as merging branches in fossil.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Please contribute Fossil "skins" or "themes"

[D. Richard Hipp]

Earlier today, I checked in a version of Fossil that has the ability  
to host multiple "themes" or "skins" for the web interface and that  
allows users (with Admin privilege) to switch between skins with a  
simple mouse click.

However, the current implementation contains only two built-in skins:   
The old default and a new "black" theme which is very similar to the  
default.  It would be good, I think to have 6 to 10 different themes  
that show a wide variety of possible looks.  Therefore, I am calling  
on the user community to submit themes for consideration.

To create a new theme or skin, edit the CSS, header, and footer to  
obtain the look you want.  Then run the following command:

 fossil configuration export skin outputfile.txt

And post the outputfile.txt here.  Thanks for contributing.

D. Richard Hipp
d...@hwaci.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] Bad wrapping on chrome with skins

[jungle Boogie]

On 10 February 2015 at 08:19, Jungle Boogie  wrote:
> What I have observed is all skins display perfectly on Firefox 35.0.1 but
> skins marked with * have bad word wrapping for the checkin column and it may
> be because of the files column.


I realize I omitted the actual page in question.

You may see it here:
http://freebsd2600.embergrace.com:8080/fileage

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
___
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] Metadata in Timeline Verbose View

[Warren Young]

On Dec 11, 2017, at 3:09 PM, Rolf Ade  wrote:
> 
> Florian Balmer writes:
>> I didn't want to spend my hobby time with CSS
>> diffing.
> 
> ...having own
> skins and CSS as branch of the main trunk(s) (the build-in skins) and to
> be able to merge the own skins/CSS from the build-in skins, as they
> development …


Try:

   $ fossil conf export skin foo
   …upgrade Fossil, switch repo to skin you wish to merge…
   $ fossil conf merge foo

I haven’t tested it, but it looks like it should work.  See “fossil help conf” 
for more on this.

If it works, it might be nice to have a shortcut:

   $ fossil conf merge skin

If given an AREA argument instead of a FILENAME, it should roll you back to the 
parent skin and then merge the changes using the same mechanism it currently 
allows for diffing your current skin against the parent skin.
___
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] Modifying button bar

[Warren Young]

On Aug 31, 2015, at 11:46 AM, Scott Doctor  wrote:
> 
> how can I customize the buttons on the button bar at the top of the page

Admin -> Skins -> Header.

That gets you a text editor containing the current HTML + TH1 code combination 
that generates the header portion of each page Fossil serves.  The footer and 
CSS files also play into it.

If you want to dig deeper into it, the stock skins are in the skins 
subidrectory of the Fossil code repo.

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

[fossil-users] Bad wrapping on chrome with skins

[Jungle Boogie]

Hello All,

For an experiment, I cloned the PCBSD git reop and setup fossil per these 
instructions:

https://www.fossil-scm.org/fossil/doc/a00a140bff46373e3685/www/inout.wiki

The completely unofficial unrelated repo is here: 
http://freebsd2600.embergrace.com:8080/


Right now it's using the skin called "Shadow boxes & Rounded Corners", which 
appears to be the same one used on https://www.fossil-scm.org


What I have observed is all skins display perfectly on Firefox 35.0.1 but 
skins marked with * have bad word wrapping for the checkin column and it may 
be because of the files column.



1.  Default 
2.  Plain Gray, No Logo 
3.  Khaki, No Logo  
* 4.Black & White, Menu on Left
* 5.Shadow boxes & Rounded Corners  
6.  Enhanced Default
* 7.San Francisco Modern
8.  Eagle


The non-stared ones are manageable to view the checkin column.

Has anyone else noticed this with Chrome vs. Firefox and Fossil before? Maybe 
I need to massage the css for the skins a little to fit better with Chrome.



Best,
Jungle
--
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Improving Fossil's "Look"

[Richard Hipp]

I have switched the default Fossil repo over to using the San
Francisco Modern skin.  Everybody seems to think it looks a lot
better, and I agree.

I think the next step of the ongoing Fossil makeover should be to
improve the homepage:
https://www.fossil-scm.org/fossil/doc/trunk/www/index.wiki

Suggestions and especially mockups of how this front page should look
are welcomed.

What are the most important features of Fossil that should be
front-and-center on the homepage?  I feel like the front page is
providing Too Much Information and that eyes gloss over when
first-time readers see all that text.  (Maybe I'm wrong - let me
know!)  So what information can be removed from the front-page and
what are the essential elements that need to be retained?

What else can be done to make Fossil easier?

FWIW:  I've made some improvements to the techniques available to
"skin" designers, and tried to write up a brief introduction to how to
design new "skins" at
https://www.fossil-scm.org/fossil/doc/trunk/www/customskin.md -
hopefully this will make it a little easier to design new skins for
Fossil, will lower the barrier to entry slightly, and encourage more
people to come up with innovative new designs.  Please read the
document, suggest improvements to the document, and give a try at
designing a new look if you have talents in that area.  That said: as
soon as 1.31 goes out the door, I'm going to start a branch for Fossil
2.0, which will be completely 100% compatible with Fossil 1.x in terms
of repository and check-ins, but will likely have a modified DOM for
the web interface and thus may break any new skins you come up with
today.  Nevertheless, I want designers to try to make skins using 1.31
so that they can suggest ways of improving the DOM to make skinning
and theming easier in 2.0.  I will help you convert 1.31 skins into
2.0 skins upon request.

Thank you all for your attention and your contributions.


-- 
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] Additional CSS skins [was Re: Proposed Fossil interface enhancement.]

[Andy Bradford]

Thus said Michai Ramakers on Mon, 30 Dec 2013 21:16:11 +0100:

> As for the visual appearance: what would be very useful already for me
> is a  clear visual  difference between  a dir-  and file-name  (in any
> file-manager, for that matter).

I use the following CSS for this (provided by someone on the ML):

li.dir:after {
content: '/';
}

It would be nice if some of the built-in skins had this as a default.

In fact, perhaps  a couple new skins should be  added to demonstrate how
to accomplish  this and the single  row listing so people  don't have to
search the archives for how to do it?

Andy
-- 
TAI64 timestamp: 400052c1de2d


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

[fossil-users] Load customized skin from subdirectory on Windows

[Florian Balmer]

On Windows, the Fossil `--skin LABEL' command line option can't be
used to load a custom skin from a subdirectory, probably because only
skin labels containing forward slashes but not backslashes are treated
as paths to subdirectories containing the skin files:

http://fossil-scm.org/index.html/artifact?name=0b6ae3&ln=101

I'm very happy with the built-in Fossil skins, and I avoid
customizations as far as possible, so as not having to update the
customized skins each time the original template is adapted. One
reason for me to use custom skins is to be able to change the default
query parameters of the "Timeline" link from the navigation bar. I
would highly appreciate a configuration option (similar to
`index-page') to set custom default timeline query parameters.

--Florian
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Can't change skins on server repo

[Steve Schow]

I’m having trouble changing skins.  It works on my local repo, but not on the 
server repo.

1 - created repo on machine A.  setup user foobar with s privs.

2 - created clone of that repo on machine B.  also with user foobar with s 
privs 

3 - Working on the local machine B, I can run fossil ui, and i’m able to change 
the skins all i want.

4 - if I start machine A as a server with “fossil server’ and then connect to 
that ui from machine B…I’m able to create tickets and everything else I’ve 
tried has worked but if I try to chose a different skin, it just stays on the 
default.  

what am I missing?

___
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] getting auto-sync error on server

[Steve Schow]

This is just a guess about the remote config…

First some background…

I have been unable to get the skins to change on my server repo when its 
running as 

   fossil server 

and connecting through the web to the named repo:

   http://host:port/repo/

I go to the admin-skins page, but click on the install button for all the 
different skins doesn’t change anything.

meanwhile, back on my cloned repo, I startup the gui using 

   fossil ui

and through that webpage, I can change the skins easily on the cloned repo.

At some point I think I probably tried to do a push config from the cloned repo 
back to the server repo, in hopes that I could push the skin there that way.  
Which didn’t work BTW.

Is it possible that when I did a push config, the remote config went with it, 
thus configuring the server to think it has a remote, which is itself?



On May 3, 2016, at 11:58 AM, Richard Hipp  wrote:

> On 5/3/16, Steve Schow  wrote:
>> This particular repo is not a clone of another repo.
>> And it appears to be trying to sync with itself.
> 
> Huh.  I don't know how you got it into that state.
> 
> The solution is probably "fossil remote off".
> 
> 
> -- 
> 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

[fossil-users] Problem with left aligned buttons in skins?

[Andy Bradford]

Hello,

I'm not sure if  I'm the only one bothered by the  left alignment of the
buttons in some of the skins...

For example, navigate to:

http://www.fossil-scm.org/index.html/timeline

Then, after clicking Older, the Newer  button shows up to the left, thus
causing the Older  button to shift to the right  (left aligned). Because
of this, I now have to move my mouse to find the Older button again.

This does  not happen with  skins where the  buttons are aligned  to the
right and I can continue clicking older  as many times as I like until I
decide to change directions.

Is this something that needs fixing? Or just a personal preference?

Perhaps for left  aligned displays, buttons should be placed  at the end
of the list of buttons rather than the beginning?

Thanks,

Andy
-- 
TAI64 timestamp: 4000550e0ab0


___
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] Please contribute Fossil "skins" or "themes"

[Stephan Beal]

On Sat, Dec 19, 2009 at 10:28 PM, D. Richard Hipp  wrote:

> Earlier today, I checked in a version of Fossil that has the ability
> to host multiple "themes" or "skins" for the web interface and that
> allows users (with Admin privilege) to switch between skins with a
> simple mouse click.
>

With version:

step...@jareth:~/cvs/fossil/whalloc$ f ver
This is fossil version [007d0a9b3f] 2009-12-19 21:04:29 UTC

i'm getting "Error 101 (net::ERR_CONNECTION_RESET): Unknown error" from
Google Chrome,  'reset by peer' from the "links" browser, and a timeout from
wget when trying to connect to the local server. i've tried different ports,
as well as localhost and over my dhcp address, but the same results.

Platform=Linux x86/32, gcc 4.4.1

:-?

Doesn't server mode have some sort of trace/debug option?

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] side-by-side diffs not shaded in skins

[James Bremner]

I like the side-by-side diffs feature, new in 1.20.  However, the shading 
( e.g. green for new code ) only appears in the default skin.  In other 
skins ( e.g. 'gradient, rounded  corners' )  I only see plain black on white 
text.

James



___
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] Can't change skins on server repo

[Richard Hipp]

On 4/25/16, Steve Schow  wrote:
> I’m having trouble changing skins.  It works on my local repo, but not on
> the server repo.
>
> 1 - created repo on machine A.  setup user foobar with s privs.
>
> 2 - created clone of that repo on machine B.  also with user foobar with s
> privs
>
> 3 - Working on the local machine B, I can run fossil ui, and i’m able to
> change the skins all i want.
>
> 4 - if I start machine A as a server with “fossil server’ and then connect
> to that ui from machine B…I’m able to create tickets and everything else
> I’ve tried has worked but if I try to chose a different skin, it just stays
> on the default.
>
> what am I missing?

Did you do "fossil config push skin" to move your local changes over
to the server?

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

[Michael Richter]

The skins available in the default build of fossil seem to be mislabelled.

When I select the one labelled "plain grey, no logo", I get a plain grey
theme with a big lighter-grey box that occupies 3/4 of the top
(left-aligned) with a logo in the middle.  "khaki, no logo" is what it says
on the box.  "Black & white, menu on the left" is as well, except it doesn't
mention not having a logo.  It doesn't have a logo, however.

Also, weren't there more skins than these three contributed?  Zed Shaw
referred to a "wedding white" that I've seen mentioned before but I'm not
seeing it.  I'm sure there were others.

-- 
"Perhaps people don't believe this, but throughout all of the discussions of
entering China our focus has really been what's best for the Chinese people.
It's not been about our revenue or profit or whatnot."
--Sergey Brin, demonstrating the emptiness of the "don't be evil" mantra.
___
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] Improving Fossil's "Look"

[j. van den hoff]

On Wed, 18 Feb 2015 00:43:15 +0100, Richard Hipp  wrote:


I have switched the default Fossil repo over to using the San
Francisco Modern skin.  Everybody seems to think it looks a lot
better, and I agree.


execpt, maybe the fixed-width layout ...



I think the next step of the ongoing Fossil makeover should be to
improve the homepage:
https://www.fossil-scm.org/fossil/doc/trunk/www/index.wiki

Suggestions and especially mockups of how this front page should look
are welcomed.

What are the most important features of Fossil that should be
front-and-center on the homepage?  I feel like the front page is
providing Too Much Information and that eyes gloss over when
first-time readers see all that text.  (Maybe I'm wrong - let me
know!)  So what information can be removed from the front-page and
what are the essential elements that need to be retained?


I've always felt the homepage is quite OK. at the very least, it will not  
put off prospective users,

I'd say. but to guide a cursory visitor around, yes, it might be better to
restructure it a bit. in this case I would stress these points in the `why  
use fossil` list


points 1, 2, and 4

as the most distinguishing ones. the others need to be mentioned  
elsewhere, sure, but they
are prob. not relevant for first time visitors. I think the  
"zero-config/(near)-zero-dependencies/single exec" point

might be especially relevant for first-time visitors/users.

one could also contemplate to just list them with a much shortened
explanatory text in parenthesis and convert the items to links where the  
full explanation can be found (the present list, that is).
then a statement `the full list of properties can be found here' or  
similar. and immediately thereafter a paragraph

containing pregnant links to `quick start' and `concepts'.

one might also try to restructure the `list for fossil users' by  
discriminating between "casual user" and "advanced user", especially
isolating highly technical material from "understanding concepts and how  
to use fosill" stuff.


just my 2c




What else can be done to make Fossil easier?

FWIW:  I've made some improvements to the techniques available to
"skin" designers, and tried to write up a brief introduction to how to
design new "skins" at
https://www.fossil-scm.org/fossil/doc/trunk/www/customskin.md -
hopefully this will make it a little easier to design new skins for
Fossil, will lower the barrier to entry slightly, and encourage more
people to come up with innovative new designs.  Please read the
document, suggest improvements to the document, and give a try at
designing a new look if you have talents in that area.  That said: as
soon as 1.31 goes out the door, I'm going to start a branch for Fossil
2.0, which will be completely 100% compatible with Fossil 1.x in terms
of repository and check-ins, but will likely have a modified DOM for
the web interface and thus may break any new skins you come up with
today.  Nevertheless, I want designers to try to make skins using 1.31
so that they can suggest ways of improving the DOM to make skinning
and theming easier in 2.0.  I will help you convert 1.31 skins into
2.0 skins upon request.

Thank you all for your attention and your contributions.





--
Using Opera's revolutionary email client: http://www.opera.com/mail/
___
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] web-UI's timeline should use non-proportional font for commit hashes

[Ron W]

On Tue, May 24, 2016 at 6:53 PM, Marko Käning 
wrote:

>
> ---
> a.timelineHistLink {
>   font-family: courier;
> }
> ---
>
>
Fossil has the capability for user defined "skins". Never used it myself,
but I have seen some nice custom skins for Fossil.

BTW, I assume CSS has styling modifiers, so I'd probably use "font-style"
(or whatever it is) to specify "monospaced".
___
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] New "Ardoise" skin

[Richard Hipp]

On 1/8/18, Antoine Chavasse  wrote:
> Here's an attempt at making diffs more readable.
>
> Since I don't have a place to host a public fossil repo with a recent
> enough version of fossil,

The self-hosting fossil has been updated to the branch, so you can see
these changes by following the ardoise link at
https://www.fossil-scm.org/skins - to wit:
https://fossil-scm.org/skins/ardoise/info/34ab58c26386bebc

-- 
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] side-by-side diffs not shaded in skins

[Jan Danielsson]

On 10/26/11 16:16, James Bremner wrote:
> I like the side-by-side diffs feature, new in 1.20.  However, the shading 
> ( e.g. green for new code ) only appears in the default skin.  In other 
> skins ( e.g. 'gradient, rounded  corners' )  I only see plain black on white 
> text.

   What browser are you using?

   Did you force the browser to reload the page?

-- 
Kind regards,
Jan Danielsson




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

[fossil-users] Interesting fossil configuration

[D. Richard Hipp]

http://support.fretwar.com/home

It would be good to have multiple prepackaged "skins" for fossil that  
new users could switch between easily, without having to do their own  
CSS and header/footer editing.  The fretwar.com skin, or something  
like it, seems like a good candidate for one of those choices.   
Volunteers to implement this?  Does anybody have any other interesting  
skins they would care to share?

D. Richard Hipp
d...@hwaci.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] appending the metadata in the section?

[Peter Vonča]

Admin/Skins page,

Step 4: Make Edits gives me 4 options, CSS,Header,Footer,Details.
Obviously I want to change the header but that's not referring to the
 element of the html doc. Instead, it's referring to the 
container of class "Header" which for all skins is the default first block
in the  of the document.
You can check this by initializing the draft1 with one of the presets such
as Default(built-in) and then edit the Header it will read :


  etc...


On Mon, Apr 30, 2018 at 1:13 PM, Richard Hipp  wrote:

> On 4/30/18, Peter Vonča  wrote:
> > Heya,
> >
> > Fossil Cookbook at
> > https://www.fossil-scm.org/xfer/wiki?name=Cookbook#tinymce has a nice
> guide
> > on how to implement tinymce, but I'm stuck as the docs seem outdated?
> AFAIK
> > there's no way for me to modify the  except for modifying the
> source
> > code and rebuilding fossil?
>
> Got to Admin/Skins.  Create a new "draft" skin.  Edit it (by modifying
>  or whatever else you need to do), test it, then publish it as
> the new default skin.
>
> --
> 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] looking for interesting new fossil skins

[Andreas Kupries]

There is also

http://fossil.include-once.org/fossil-skins/index

which seems to collect skins. Has not changed for a bit over a year now.



On Tue, Feb 11, 2014 at 8:13 AM, Stephan Beal  wrote:
> On Tue, Feb 11, 2014 at 5:08 PM, Joel Bruick  wrote:
>>
>> Richard Hipp wrote:
>>>
>>> The tree-view
>>> (http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/dir?ci=tip&type=tree
>>> <http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/dir?ci=tip&type=tree>)
>>> doesn't look quite right.
>>
>>
>> That skin sets top and bottom margins on all LI elements, which the
>> tree-view CSS doesn't account for. I just fixed this in trunk.
>
>
> Thanks! That trunk is now running with this shiny new theme here:
>
> http://fossil.wanderinghorse.net/repos/libfossil/
> http://fossil.wanderinghorse.net/repos/cwal/
>
> --
> - stephan beal
> http://wanderinghorse.net/home/stephan/
> http://gplus.to/sgbeal
> "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
>



-- 
Andreas Kupries
Senior Tcl Developer
Code to Cloud: Smarter, Safer, Faster(tm)
F: 778.786.1133
andre...@activestate.com
http://www.activestate.com
Learn about Stackato for Private PaaS: http://www.activestate.com/stackato

EuroTcl'2014, July 12-13, Munich, GER
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] [UI] Increase font size in side-by-side page?

[Gilles]

Hello,

The UI seems the easiest way to diff versions and see what changes were 
made to a file between two revisions.


Problem is, the font size is a bit small:

https://postimg.cc/image/wm6lpynzx/

I searched the archives* with "ui font size", but didn't find much.

Is there a way to increase font size, or should I install "Fossil Skins 
Extra" (http://fossil.include-once.org/fossil-skins/index) add-on?


Thank you.

* https://www.mail-archive.com/fossil-users@lists.fossil-scm.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] Please contribute "skins"

[Svyatoslav Mishyn]

(Wed, 21 Jan 21:14) Richard Hipp:
> If you have suggestions on how to improve the existing skins, please
> send in diffs, either to this list or to one of the developers (like
> me).
> 

https://cloud.openmailbox.org/public.php?service=files&t=66be8aedb2c79d8814615dc8219efec4
is it only for me?

if not,
how about to add something like (not perfect) to footer:



  if (document.querySelector('.sbsdiffcols') !== null 
   || document.querySelector('.report') !== null) {

document.write('<style type="text/css">div.header, div.mainmenu, 
div.submenu, div.content, div.footer {max-width: 100em}</style>');

  }



or just use sl theme:)


-- 
http://www.juef.tk/
___
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] Modifying button bar

[Scott Doctor]

  
  

Hmm. I guess that will work. but would be
  nice to have a simple GUI-ish type editor where I just have a list
  in order of appearance that is the name of the button and its
  link, instead of basically hacking code, thereby isolating
  language syntax from the user. 
  
  I see it working as such. User wants to add (or delete) a button.
  Clicks ADD BUTTON button. Prompt for name of button, prompt for
  link or select from tree (I think tree is better). the appropriate
  code is then inserted into the HTML where the user never sees the
  underlying code.
  


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

On 8/31/2015 10:51 AM, Warren Young
  wrote:


  On Aug 31, 2015, at 11:46 AM, Scott Doctor  wrote:

  

how can I customize the buttons on the button bar at the top of the page

  
  
Admin -> Skins -> Header.

That gets you a text editor containing the current HTML + TH1 code combination that generates the header portion of each page Fossil serves.  The footer and CSS files also play into it.

If you want to dig deeper into it, the stock skins are in the skins subidrectory of the Fossil code repo.

___
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] Using fossil with Golang (go get)

[Mark Janssen (fossil)]

On 2018-06-17 14:57, Zack Scholl wrote:


All you need to do is update your "Header" skin (Admin -> Skins) to
include a special meta tag that `go get` will fetch to interpret your
fossil as a Go library/program. For example, if you have a fossil
hosted at https://yourdomain.com/hello-world then you need to add the
meta tag in between the  tags:

https://yourdomain.com/hello-world";>



Works very well, thank you.
To add, easier and repo independent is: content="$baseurl fossil $baseurl">

IMO this would be a nice candidate for inclusion in the standard skins.

---
Mark
___
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] web-UI's timeline should use non-proportional font for commit hashes

[Marko Käning]

Hi Ron,

On 25 May 2016, at 18:07 , Ron W  wrote:

> Fossil has the capability for user defined "skins". Never used it myself, but 
> I have seen some nice custom skins for Fossil.

I know. I was using them to defined the font in its CSS section.


> BTW, I assume CSS has styling modifiers, so I'd probably use "font-style" (or 
> whatever it is) to specify "monospaced”.

Yeah, it would be “monospace” without a trailing ‘d’, but “courier” actually 
looks better, as its font size is matching.

Greets,
Marko
___
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] Please contribute Fossil "skins" or "themes"

[altufaltu]

Well, credit goes to Dmitry Chestnykh. I'm just a user of this theme :)





-Original Message-
From: Jeremy Cowgar 
To: fossil-users@lists.fossil-scm.org
Sent: Fri, Jan 15, 2010 7:38 pm
Subject: Re: [fossil-users] Please contribute Fossil "skins" or "themes"


Altu,That's a nice skin!jeremyaltufa...@mail.com wrote:> Request to add Shiny 
Fossil theme (http://dev.codingrobots.org/p/shiny-theme) to default set of 
themes.> > > Attached is a derived version with some recent changes for menu 
order / permission.> 
___fossil-users mailing 
listfossil-us...@lists.fossil-scm.orghttp://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

[fossil-users] Fossil skins: how to create your own?

[David Bovill]

I'm up and playing with Fossil - looking great so far. I'm going to
experiment with how far I can hack the look and feel of the wiki / server
output.

   - it looks like you can set up your won skins - but are fixed to the 3
   defaults. Can you add your own via the db?
   - with the header and css files you should be able to add JavaScript and
   completely customise. I'll be looking at adding DOJO - has anyone tried
   anything like this?
   - what is the effect of allowing HTML in the config settings - does that
   allow full JavaScript in the wiki pages?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Please suggest built-in skin fixes and improvements

[Richard Hipp]

You can now see the canonical Fossil self-hosting repository using any
of the built-in skins by visiting links from this page:
https://www.fossil-scm.org/skins/

I have fixed a few of the more egregious problems in these built-ins
that have resulted from the recent Modern View timeline and other
enhancements.  But more refinement is necessary.  Please suggest
additional fixes.  I mean by this, please suggest the actually CSS
changes needed to fix the problem - don't just point out that it
doesn't look right and expect me to figure out the problem and a fix.

Thanks for your help!

-- 
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] [minor] src/style.c:427 → "%

[mario]

This misses anything but plain  tags in the header
 ↓
  if( sqlite3_strlike("%%", zHeader, 0)!=0 ){
Th_Render(zDfltHeader);
  }

It might rather be %%, so any style attributes
like  get recognized still.

Perhaps zDfltHeader[] could even contain a short HTML comment as to
why it was injected. Took me an hour two figure out how the CSP came
to be^^

##

[skin-setup-refactor]. I see the value in the draft feature, but it's
also a bit confusing still (while working on broken skins at least.)

Can we have an option to hide draft admin, or the setup_skin+_admin
pages merged with e.g.:
 - draftN… just treated as saved skins?
 - edit header/footer/css buttons for each draft/skin
 - and [test] urls for each available backup/save/draft
Or something like that.


G!
___
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] Load customized skin from subdirectory on Windows

[Richard Hipp]

On 5/26/17, Florian Balmer  wrote:
> On Windows, the Fossil `--skin LABEL' command line option can't be
> used to load a custom skin from a subdirectory, probably because only
> skin labels containing forward slashes but not backslashes are treated
> as paths to subdirectories containing the skin files:
>
> http://fossil-scm.org/index.html/artifact?name=0b6ae3&ln=101
>

The reason --skin was not working on windows was different from the
above.  It should be fixed now.  I tested by running (on Windows):

fossil ui --skin skins/blitz

From the root directory of the Fossil source tree.  Note that you
still need to use forward-slash characters (not backslash) in the skin
name so that Fossil knows that you mean a directory and not one of the
built-in skins.

-- 
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] Sort skins alphabetically patch

[Jungle Boogie]

Hi All,

For your consideration...


Index: src/skins.c
==
--- src/skins.c
+++ src/skins.c
@@ -39,23 +39,23 @@
 static struct BuiltinSkin {
   const char *zDesc;/* Description of this skin */
   const char *zLabel;   /* The directory under skins/ holding this skin */
   char *zSQL;   /* Filled in at run-time with SQL to insert this skin 
*/
 } aBuiltinSkin[] = {
-  { "Default",   "default",   0 },
+  { "Ardoise",   "ardoise",   0 },
+  { "Black & White, Menu on Left",   "black_and_white",   0 },
   { "Blitz", "blitz", 0 },
   { "Blitz, No Logo","blitz_no_logo", 0 },
   { "Bootstrap", "bootstrap", 0 },
-  { "Xekri", "xekri", 0 },
-  { "Original",  "original",  0 },
+  { "Default",   "default",   0 },
+  { "Eagle", "eagle", 0 },
   { "Enhanced Original", "enhanced1", 0 },
-  { "Shadow boxes & Rounded Corners","rounded1",  0 },
-  { "Eagle", "eagle", 0 },
-  { "Black & White, Menu on Left",   "black_and_white",   0 },
+  { "Khaki, No Logo","khaki", 0 },
+  { "Original",  "original",  0 },
   { "Plain Gray, No Logo",   "plain_gray",0 },
-  { "Khaki, No Logo","khaki", 0 },
-  { "Ardoise",   "ardoise",   0 },
+  { "Shadow boxes & Rounded Corners","rounded1",  0 },
+  { "Xekri", "xekri", 0 },
 };
 
 /*
 ** A skin consists of four "files" named here:
 */

Thanks,
j.b.
___
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] Metadata in Timeline Verbose View

[Warren Young]

On Dec 11, 2017, at 9:19 PM, Warren Young  wrote:
> 
> I’d go as far as #F8F8F8 myself.

One of my Fossil projects’ skins is based on Khaki, which hasn’t yet been 
restyled to override the base styles for the timeline boxes, so I get light 
gray on yellow, not terribly attractive.  The following CSS snippet not only 
fixes that, it’s generic:

td.timelineColumnarCell[id], td.timelineModernCell[id], 
td.timelineDetailCell[id] {
background-color: rgba(0, 0, 0, 0.03);
}

That is, we do an alpha blend to construct the slightly darker color for the 
boxes based on the background color.  I like 3% black, but it can be up to 
about 5% before I start finding it objectionable.

This should work for any skin with a light background color.  Light-on-dark 
skins can use this related formation:

td.timelineColumnarCell[id], td.timelineModernCell[id], 
td.timelineDetailCell[id] {
background-color: rgba(255, 255, 255, 0.03);
}

That is, blend with 3% white instead of black.
___
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] Some more default settings for a UI user

[Marko Käning]

Hi John,

On 24 Apr 2016, at 01:45 , John P. Rouillard  wrote:
> You're missing what he is saying. He is saying change the Timeline
> (/timeline) link in the menu.

indeed, not hard to miss it. :)

I couldn’t figure out where I could change exactly those links.

Now I see that you’re pointing me to skins:

> When logged in as an admin, go to:
> 
>   Admin/Skins
> 
> You will see text that says:
> 
> A "skin" is a combination of CSS, Header, Footer, and Details 
> 
> Choose Header.

Well, that’s not really intuitive, is it! ;-)

I would have expected something like “Edit menu” or something along that line.


> The html/th1 mix that shows up in the textbox is the top section of
> the pages.
> 
> Search for Timeline and you should see:
> 
>  menulink /timeline Timeline
> 
> Change
>   /timeline
> to
>  '/timeline?n=100'
> 
> and click Apply changes. Now the default value when clicking Timeline
> menu link is to show 100 changes.

Yep, got that now.


> I don't think there is an option to allow logged in users to set those
> sorts of things on a per user basis. AFAIK there is no user data
> stored other than a password. So you would need to figure out how to
> create a user table to store user preferences. There are no custom
> forms for users (i.e. a user equivalent of the admin/tickets
> mechanism), you wouldn't be able to allow the user to edit things
> without some changes to the fossil core code.

OK.


> However once you had that info in the database, IIRC you can use th1 to
> find out who the current user is. Then you can make sql calls into the
> database. So I think in theory you could change/create a user schema
> that holds personalized settings and use th1 to customize the menu
> item.

I see.

Well, I’ve reconfigured the repo’s header now to my linking.

Thanks for the clarification wrt the "Menu Settings" aka Admin/Skins. :)

Greets,
Marko

___
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] Webpage for multiple fossil repositories - configuration options?

[Warren Young]

On Jun 5, 2017, at 3:08 PM, John Pateman  wrote:
> 
> Is it possible to customise the appearance of this  webpage without having to 
> set it up a full web server?

Say

$ fossil ui

Then in the browser that pops up, go to Admin > Skins, and edit the files 
presented, or select one of the built-in skins.

Once you save the changes, “fossil server” will show those changes to the world 
via HTTP.

That is, by using the local Fossil UI, you can modify the skin before exposing 
it to anyone who can connect to your machine over the network.

Beware that skin changes don’t normally sync between existing repositories.  
The current skin configuration is copied once only during the initial clone, so 
if you have other clones of this repo already, they’ll continue to show the 
prior skin until you say something like

$ fossil conf pull skin

from a checkout of the affected remote repository.  (Or, give -R if you don’t 
want to do this from a checkout directory.)
___
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] Metadata in Timeline Verbose View

[Florian Balmer]

Thanks for the instructions and demonstration.

Simple to do, I agree. A minor issue for me is that I have some tasks
where I copy-paste parts of the timeline view to another program, and
some web browsers do not copy the CSS parenthesis, making things
harder to read, again. Picking individual entries from the command
line timeline interface is not so straight forward.

But you got me on the wrong leg:

I'm a computer hobbyist, and I "refused" to use version control
systems for a long time, due to its complexity, and the amount of
hobby time I would have to invest. This has changed only when I
learned about Fossil, and I'm always fascinated by its simplicity.

At first I maintained my own Fossil skins. But after two or three
updates, even with only simple changes to the default CSS, I gave up
my own skins, as I didn't want to spend my hobby time with CSS
diffing.

So my strategy here was to argue for a generally accepted default that
would be built into Fossil ;-)

--Florian
___
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] Fossil is Awesome

[Alek Paunov]

On 27.10.2011 02:15, Caleb Gray wrote:

@ Stephan Beal:
I see the appeal in creating a separate HTML application. I will take
this approach, and will see how everyone feels about having "installable
skins" in Fossil: shipping it with only the "Default" skin.
+1: Absolutely - optional AJAX applications as installable (in fossil 
DB) skins with JSON datasources, I am sure that you also follow the 
progress of ace.ajax.org and the other JS projects, which are good 
candidates for employment ;-).
I think that the only missing part is feature for stored (parametrized) 
SQL queries, which can be called with lower privileges via JSON interface.



You are exactly on track with what I was envisioning for the JS
enhancements with: http://mbostock.github.com/d3/talk/20111018/#8


+1: d3 is the best for the SVG part in my eyes too, it seems even more 
powerful than his famous predecessor - protovis.org (and can be seen 
also as smart XSLT like engine - thus, can have more applications than 
just SVG drawing for fossil UX applications - i.e. "live" JSON->DOM 
templates for non-SVG enhanced pages also)


Kind Regards,
Alek
___
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] Fossil update

[Warren Young]

On Nov 7, 2018, at 6:18 AM, Zoltán Kócsi  wrote:
> 
> For some projects we used colour-coding of the Timeline entries, for
> example releases were coloured differently from developers-only commits
> and so on. That all seems to have gone.

If you upgraded your central repository server from 1.29 to 2.7 to fix the 
problem suggested by drh — someone’s been checking in SHA3-hashed artifacts — 
then you also have to update your skin.

If you were using the stock skin before, just go into Admin > Skins and select 
the Default skin again.  You might have to switch to some other skin and back 
to get it to overwrite your outdated skin files.

If you made changes to your local skin, you’ll have to merge the changes made 
to the default version of the skin you started with into your local version.

In versions 2.5 and 2.7, there were a lot of changes to the default skin, some 
of which were done to track changes made to the HTML emitted by “fossil server” 
in support of newer features.  Outdated skins won’t style the new HTML properly.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] skins not always showing properly

[Johan Samyn]

Hi,

I downloaded the Windows binary fossil-w32-20111213135356.zip, and
experienced a cosmetic issue with it.
In the 2 repos I already had created with an earlier version, choosing
either the "Black & White, Menu on left" or the "Gradient, Rounded
Corners" skin both times produced the "Black & White, Menu on left" look.
I then cloned the fossil repo itself, and there I saw that choosing
either one of the two skins mentioned above now rendered as the
"Gradient, Rounded Corners" both times.
Bit strange, no ? Anybody any clue as to what is the cause - and even
better, the solution - to this ?


PS:
I mention this via the mailing list because I was unable to register a
new ticket, though I was logged in as anonymous, which should be able to
do that if I'm right. The "www.fossil-scm.org" is the right url to do
that, isn't it ? So this is rather two tickets in one email.

-- 
Johan Samyn
___
"Perfection is achieved, not when there is nothing more to add,
but when there is nothing left to take away."
- Antoine de Saint-Exupery

___
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] appending the metadata in the section?

[Richard Hipp]

On 4/30/18, Peter Vonča  wrote:
> Admin/Skins page,
>
> Step 4: Make Edits gives me 4 options, CSS,Header,Footer,Details.
> Obviously I want to change the header but that's not referring to the
>  element of the html doc. Instead, it's referring to the 
> container of class "Header" which for all skins is the default first block
> in the  of the document.
> You can check this by initializing the draft1 with one of the presets such
> as Default(built-in) and then edit the Header it will read :
>
> 
>   etc...
> 

Fossil inserts its own default , unless you include  in
your custom header.  So if you just puts:


...whatever...


At the top of your custom header, Fossil will omit its default 
and use whatever it is you provide.

I thought I had documented that, someplace.  But probably I need to
document it *better*.  Suggestions are welcomed.

Or, maybe I should change the code so that it inserts its own default
header if and only if you omit "" from your custom header, as
that seems to make a little more sense.  I suppose I was thinking that
anybody that includes  in their header will also include .
-- 
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] Fossil skins: how to create your own?

[Stephan Beal]

On Fri, Jan 14, 2011 at 6:01 PM, David Bovill  wrote:

> I'm up and playing with Fossil - looking great so far. I'm going to
> experiment with how far I can hack the look and feel of the wiki / server
> output.
>
>- it looks like you can set up your won skins - but are fixed to the 3
>defaults. Can you add your own via the db?
>
>
You can edit the look/feel as much as you like, and use 'fossil config
export' to save it.


>
>- with the header and css files you should be able to add JavaScript
>and completely customise. I'll be looking at adding DOJO - has anyone tried
>anything like this?
>
>
Yes, you can plug in external JS (i plugged in jquery once but ended up not
using it for anything).


>
>- what is the effect of allowing HTML in the config settings - does
>that allow full JavaScript in the wiki pages?
>
>
Dunno - i'll have to punt on that one. BEWARE that enabling full HTML does
not disable wiki markup. That means that wiki-like-markup in the HTML/script
content will get hosed by the wiki marker-upper. (Been there, done that.)

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
___
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] [minor] src/style.c:427 → "%

[Warren Young]

On Jul 2, 2018, at 8:11 AM, mario  wrote:
> 
> This misses anything but plain  tags in the header
> ↓
>  if( sqlite3_strlike("%%", zHeader, 0)!=0 ){
>Th_Render(zDfltHeader);
>  }
> 
> It might rather be %%, so any style attributes
> like  get recognized still.

Under what conditions would you have two different  tags in a single 
document differing only by class, and thus need a CSS selector to differentiate 
them?

I suspect this is just a bad example, but then I ask myself, if I’m going to 
apply CSS styles to a tag, wouldn’t I just put it into the CSS file, which I 
can already modify without changing Fossil?

What’s the real motivation here?

> I see the value in the draft feature, but it's
> also a bit confusing still (while working on broken skins at least.)

While I agree that the new skin editor is considerably more complicated to use 
than the pre-2.5 method, I also don’t see how to make it simpler without losing 
functionality we gained in that release.

This feature set solves a few real problems faced by drh during the 2.5 
development sequence in support of the many UI improvements he made while 
actively soliciting feedback on those changes.  In order to get that feedback, 
he had to point people to a running instance, so rather than take the expense 
and complication of setting up a public demo server, drh created this feature 
set so he could demonstrate proposed skin changes using the fossil-scm.org 
instance to get that feedback.

This feature set adds the following abilities:

1. Lets normal site visitors A/B compare proposed changes by visiting URLs 
differing only in the skin draft’s name.

2. The Fossil admin user can now invite others to edit the skin.

3. Edits can be made to drafts, so you can test on a production server without 
breaking it for uninterested users.

The prior way skin editing worked, only the admin user could switch and edit 
skins.

I don’t think you’re going to see any changes to this mechanism unless your 
proposal can achieve the same ends.

> - draftN… just treated as saved skins?

I don’t see why that couldn’t be done in principle.

The main practical problem is that skins can be named in a way that would 
require ugly URL escaping to be specified in place of the current draftN bit:

https://fossil.example.com/Blitz%2C%20No%20Logo%20(built-in)/home

A secondary problem is that it appears that Fossil’s current URL parser can’t 
quite cope with that once decoded, based on the 404 error pages it generates.

There is a side-benefit of this change: if someone has a public Fossil instance 
and one of the end users thinks the default skin is ugly, he can change it by 
selecting the name of a skin he likes better in the URL.  Currently, you can 
only change the skin this way in a local clone which you’re running “fossil ui” 
on.

> - edit header/footer/css buttons for each draft/skin

I’m not seeing the value of that change.  The current mechanism is:

1. Select the skin/draft to edit.

2. Click the CSS/Header/Footer/Details edit links.

Are you proposing to replace this with a grid, with skin names down the left 
edge and 4 edit buttons per row to the right of each skin name?  That does not 
sound like a simplification to me.

If you have something different in mind, a graphical mockup or wireframe 
drawing might help get your point across.

> - and [test] urls for each available backup/save/draft

We already have that: it’s Step 5 on the setup_skin page.  The test URL list 
changes whenever you change the draft name in Step 1.
___
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] Fossil Web Interface - Separation of HTML from Code

[Igor de Oliveira Couto]

Oooh, all of this sounds *really* interesting and exciting:

On 22 May 2014, at 2:25 am, Stephan Beal  wrote:

> [...] That, of course, is possible, and some people here have done up some 
> impressive skins, [...]

Where can I find some of these? - I had a quick look through the repositories 
at 'Chisel', but found only 3 skins there. 

> You might also find the JSON API useful, as it basically emulates as many of 
> the CLI/HTML pages as it can, using a JSON interface.

Wow! That would be fantastic!

> You need to build Fossil with the --json option for that to be enabled, [...]

I'm afraid that recompiling is a bit beyond me... 

This would be such a MAJOR feature! Please tell me that it's close to final...

Being able to access Fossil repo data via JSON could be used not only to create 
new web interfaces, but also to create platform-specific GUIs using RAD tools 
like 'LiveCode" (http://livecode.com). Wow!!!

> Once again, many thanks for the information, and for welcoming me into the 
> Fossil community.
> 
> My pleasure. This is what i do for fun when i'm not in the mood to code ;).

You're a great ambassador ;-)

Kindest regards,


--
Igor Couto
Sydney, Australia



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] New "Ardoise" skin

[Richard Hipp]

The Ardoise skin by Antoine Chavasse is now available on trunk.  You
can take a test-drive at
https://www.fossil-scm.org/skins/ardoise/timeline

-- 
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] sqlite.org skin

[Wilson, Ronald]

What skin is the sqlite.org fossil repository using?  It is not in the default 
skins that come with fossil.  Is it published somewhere?

RW

Ron Wilson, Engineering Project Lead
(o) 434.455.6453, (m) 434.851.1612, www.harris.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] New "Ardoise" skin

[Richard Hipp]

The search results don't seem quite right.  The matching text is shown
in a black font.  Example:

 https://www.fossil-scm.org/skins/ardoise/search?s=utime&y=c

-- 
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] Search edit field placement

[Marko Käning]

OK, thanks to John I learnt in my other thread [1] that this can be achieved 
via Admin/Skins/Headers.


[1] http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg22970.html
___
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] Skins

[Richard Hipp]

On Sun, Jul 25, 2010 at 1:25 PM, Zed A. Shaw  wrote:

> On Sun, Jul 25, 2010 at 07:39:28PM +0800, Michael Richter wrote:
> > Looking more into the skinning issue, it looks to me like the file
> skins.c
> > contains a bunch of stuff that could be generated trivially from a script
> of
> > some sort.  Is there any interest in me making the skinning system more
> > flexible so it's easier to add a new skin by basically just checking in
> > three files under a new directory?  The idea would be something like
> this:
>
> I think that'd work at first, but just to be clear, this means that you
> can only change the look of a fossil site by recompiling the binary
> right?  A more useful solution would one that doesn't require a
> recompile.
>

You can always customize a skin, just as you do now.  I think the idea is
that there are more built-in prepackaged skins that you can use as starting
points or templates.  Only the built-ins are compiled in.

Use the "fossil configuration export skin" command to export a file
containing a skin for export to others.  Or "fossil configuration import" to
start using a skin previously exported by somebody else.


>
>
> --
> Zed A. Shaw
> http://zedshaw.com/
> ___
> 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] [minor] src/style.c:427 → "%

[mario]

Mon, 2 Jul 2018 17:20:17 -0600 Warren Young :

> Under what conditions would you have two different  tags in a
> single document differing only by class, and thus need a CSS selector
> to differentiate them?

Of course you wouldn't want two  tags.
But that's exactly the bug I ran into:





http://localhost:8080/timeline"; />
 Plugin Meta Data: Timeline
  


  
  
  http://localhost:8080/timeline"; />
  Plugin Meta Data: Timeline
  
  https://media.readthedocs.org/css/sphinx_rtd_theme.css";
type="text/css" /> https://media.readthedocs.org/css/readthedocs-doc-embed.css";
type="text/css" />
  
  



If you use a skin header with ``, current trunk
will prepend a default  section and second  tag:

> /*
> ** Default HTML page header text through .  If the
> repository-specific ** header template lacks a  tag, then all
> of the following is ** prepended.
> */

It should check for , not just a fixed byte sequence.

##

> > I see the value in the draft feature, but it's
> > also a bit confusing still (while working on broken skins at
> > least.)  
> 
> While I agree that the new skin editor is considerably more
> complicated to use than the pre-2.5 method, I also don’t see how to
> make it simpler without losing functionality we gained in that
> release.

TBH, I haven't really given it much more thought.

It's clearly more practical to have secondary skins to work on,
without harming the active/default template. And being able to
grant additional edit permissions there is a nifty feature. As
is the built-in help and step-by-step guide.

It just got in the way for the aforementioned issue.


> > - draftN… just treated as saved skins?  
> 
> I don’t see why that couldn’t be done in principle.
> 
> The main practical problem is that skins can be named in a way that
> would require ugly URL escaping to be specified in place of the
> current draftN bit:
> 
> https://fossil.example.com/Blitz%2C%20No%20Logo%20(built-in)/home

If the PATH_URI detection can only only recognize `draftN` prefixes,
than having all of them available wouldn't make sense. With the ugly
percent escaping anyway.

> There is a side-benefit of this change: if someone has a public
> Fossil instance and one of the end users thinks the default skin is
> ugly, he can change it by selecting the name of a skin he likes
> better in the URL.  Currently, you can only change the skin this way
> in a local clone which you’re running “fossil ui” on.

Rather than extending the internal path dispatcher, supporting a
plain/per-user cookie migth make sense. -- OTOH, this might already
be feature creep..


> I’m not seeing the value of that change.  The current mechanism is:
> 
> 1. Select the skin/draft to edit.
> 
> 2. Click the CSS/Header/Footer/Details edit links.
> 
> Are you proposing to replace this with a grid, with skin names down
> the left edge and 4 edit buttons per row to the right of each skin
> name?  That does not sound like a simplification to me.

It's sort of what came to mind. But indeed, that would probably just
make it more convoluted.

One simplification in the whole skin conundrum could be merging
css+header+footer+settings editing into one page (4x textarea)
however.
Then it might be presentable in a table/grid scheme:

 check   test
 boxes   links
   ↓   ↓
  [ ]  Skin name[Edit]
  [x]  Backup2  [Edit]
  [ ]  Draft1   [Edit]
   ↓
  [Activate]  [Use as Draft]  [Publish]  [Delete]

With the buttons just acting on the current selection.

 * Could be fewer action buttons though.
 * [Rename] or [Publish] better part of the css+head+foot editing
   page.
 * The `Authenticate` option should really be part of the `Display
   Details` settings blob, btw.
 * It would likely suffice if the template name doubles as test link
   (don't see the need for five test links).

> If you have something different in mind, a graphical mockup or
> wireframe drawing might help get your point across.

I'm gonna give this a bit more thought. There's quite a lot of
backend code for the template management already. Not really sure
if any of this would simplify code or editing workflows.

___
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] Fossil is Awesome

[Caleb Gray]

@ Stephan Beal:
I see the appeal in creating a separate HTML application. I will take
this approach, and will see how everyone feels about having "installable
skins" in Fossil: shipping it with only the "Default" skin.

Awesome, I didn't find either the JSON demo or "The Doc" while reading
through everything. Thanks for the links!

I've already mailed my copyright release last week sometime, so it
should be arriving any day now. :D

You are exactly on track with what I was envisioning for the JS
enhancements with: http://mbostock.github.com/d3/talk/20111018/#8


@Konstantin Khomoutov, @Ron Aaron, @Lluís Batlle i Rossell:
You're absolutely right, the web interface is fine. What I'm saying that
it could be enhanced with complimentary JavaScript, leaving all of the
previous CSS/HTML alone. Disabled JS wouldn't be a problem at all; you
just wouldn't see the enhancements.


@Ron Aaron:
I definitely agree that features like syntax highlighting can be very
expensive. If the Fossil server is running a JS enhanced skin, the
end-user will be presented with a way to disable features they feel
aren't worth their computational time.


@Michael Barrow:
I'm hoping that we can abstract all of Fossil's hard-coded pages and
skins, and have "installable skins" to dodge bloating Fossil with any
and all unnecessary data.


@Dmitry Chestnykh:
I just wrote a script for testing the speed and size difference between
the different compressions available, find the results here:
http://uploads.calebgray.com/contributions/compression/index.html

As far as I know, memory usage depends entirely on dictionary size... so
shouldn't DEFLATE and LZMA use the same amount of memory if configured
correctly?

I'm used to 500KiB/s download speed, but my only choice at home is
Clearwire (which is true, I'm sure, for more than just myself).
Unfortunately, it's not rare for me to get 20KiB/s download speeds on
it, if the Fossil releases were UPX compressed, that would have saved me
~5 seconds over the ZIP. Obviously, this isn't doesn't seem like a big
deal, but keep in mind that the people in Australia/New Zealand have to
pay for their bandwidth. It's not just time we're saving people, it's
money too, in the long run.

UPX has zero effect on memory usage, and would probably add a
millisecond or two to each request, leaving CPU as the only truly
impacted factor... I suppose that if a Pentium 133 uncompressed at
~10MB/s as they claim on their homepage... then if you're getting 10
requests a second on a 1MB executable... your server would begin seeing
the performance impact of Fossil being compressed using UPX. Anyway, I'm
not a huge proponent to the idea, it was just a thought.

___
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] side-by-side diffs not shaded in skins

[James Bremner]

Jan,  Forcing browser to refresh did the trick.  Thanks, James

"Jan Danielsson"  
wrote in message news:4ea81774.2030...@gmail.com...
> ___
> 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] Please contribute Fossil "skins" or "themes"

[Jeremy Cowgar]

Altu,

That's a nice skin!

Jeremy

altufa...@mail.com wrote:
> Request to add Shiny Fossil theme (http://dev.codingrobots.org/p/shiny-theme) 
> to default set of themes.
> 
> 
> Attached is a derived version with some recent changes for menu order / 
> permission.
> 

___
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] looking for interesting new fossil skins

[Samuel Debionne]

> That sounds like it would "break things," but nonetheless, i'd be
> interested in seeing it, and maybe we can make it work backwards compatibly.

Yes it may break things. I say "may" because I'm not sure that it
actually does break old skins.

> The setup page has a toggle to enable plain HTML.

Yes but my mod enables plain HTML on a page basis just like you have
Fossil Wiki, Markdown and Plain Text. This option bypass the wiki format
code (and may be a security concern). A setup option could be added if
necessary or it could be available to admins only.
Basically most of my pages are fossil wiki / markdown but the home page
that uses more of the Bootstrap features.

> i'd be all for doing that, if Richard doesn't object (he implemented the
> initial scrubbing of attributes).

To be more specific on my changes in wikiformat.c :

The data-* attributes are valid.
article, aside, footer, header, nav, section elements are valid.

> That is a work of art! The collapsing of the menu in small-screen mode
> is great!

Thanks but the credits must go to Bootstrap !

> i would most certainly be interested in seeing how we can do that while
> being backwards-compatible, but non-trivial code changes can only be
> accepted from those with a copyright waiver on file with Richard:
> 
> http://www.fossil-scm.org/index.html/doc/trunk/www/copyright-release.html

I'm not sure it falls in the non-trivial category ! Anyway Richard
should have my contributor agreement already.
<>___
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] Asciidoc(tor) & Fossil

[Martin Gagnon]

On Thu, Aug 14, 2014 at 09:56:32AM +0200, Stephan Beal wrote:
>On Thu, Aug 14, 2014 at 9:27 AM, Gour <[1]g...@atmarama.net> wrote:
> 
>  Now the interesting part in regard to is is Asciidoctor.js � - "a
>  fully-functional version of Asciidoctor that works in any JavaScript
>  environment, such as a web browser or Node.js.", so I wonder whether
>  there is
>  some possibility to make it integrate it with Fossil in order to enjoy
>  combination of Asciidoc markup + Fossil?
> 
>You can in fact do that with the JSON API. i've been serving Google
>Code-format wiki pages this way for a a couple years now:
>[2]http://fossil.wanderinghorse.net/wikis/
>all of those use the JSON API to serve GoCo-format pages, which then get
>rendered on the client side.

May be it would be more simple (if possible) to just modify fossil skins
related configuration (header, footer, css, ...) to use Asciidoctor.js.

If it is possible for google-code-prettify for syntax highlighting, I
guess it could be for Asciidoctor.js. It's only my 2 cents since I don't
know much about Asciidoctor.js.

  note:
 For google-code-prettify, I use my own skin based on the google-code
 skin from here: 
http://fossil.include-once.org/fossil-skins/index 

 That I modify to don't have to link to google-code-prettify js
 script from google, I've integrated it to my repository instead
 so it can be use on a local network without internet access.. I've
 also removed dependency on jquery.


Regards,

-- 
Martin G.
___
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] feature proposal for anonymous login

[Stephan Beal]

On Mon, Dec 7, 2009 at 9:07 PM, D. Richard Hipp  wrote:

>
> On Dec 7, 2009, at 2:48 PM, Zed A. Shaw wrote:
> > I'd say no, I wouldn't want this feature is it makes bots trivial to
> ...
>
> However, if it were an optional setting then there'd be nothing wrong
> > with it being there.  Those who need simpler user input could turn it
> > on, and those who need more spam/bot blocking can turn it off.
>
>
>
I was going to suggest the same thing, but Zed beat me to it
>

Thank you Richard, Zed, and Joshua, for the input. i agree that any feature
as arguable as this needs a toggle (if it needs to be added at all). i'll
see what needs to be done on the setup page for this, and then scramble the
underlying JS code to make it unparseable to a bot (e.g. "1234567" becomes
'1'+'2'+'3'+'4'+..., which no bot in the world would know what to do with).


> Another thing that would be really cool:  Add a feature to the Setup
> menu that gives the administrator a choice of several "skins" for
> Fossil using a single button click.


That's a larger task i'll have to punt on at the moment, but this would be a
nice feature. If we had a separate skins table which contain the
css/header/footer/etc for skin sets, we could copy that over the current
config on demand. Which parts would need to be stored for each skin
definition? e.g. CSS, header, footer... what else?

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
___
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] Re-sync skins of remote repo

[Richard Hipp]

On 7/15/18, Jungle Boogie  wrote:
> Hi All,
>
> I'd like to know if there's a way to re-sync to the skin of a remote repo,

fossil config pull skin
-- 
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] Seeing SBS between any checkins

[Leo Razoumov]

On Thu, Feb 16, 2012 at 13:43, Richard Hipp  wrote:
>
> Try pressing "Reload" several times to convince Chrome to load the newest
> CSS.
>

In order to force CSS reload go to Admin->Skins, change to any skin
and then change back to the default skin.

--Leo--
___
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] Please contribute "skins"

[Samuel Debionne]

> On mobile the menu automatically pops up and doesn't get out of the way. 

I have added a minimalist implementation (without all the shiny
animations) of the collapsible functionality.
On modern browser, the toggle button of the navbar now works as expected.
Let me know if that works (or not !) for you.
___
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] Problem with left aligned buttons in skins?

[jungle Boogie]

On 21 March 2015 at 17:19, Andy Bradford  wrote:
> Is this something that needs fixing? Or just a personal preference?

Yes, I'd prefer older left of newer for exactly the reasons you've mentioned.

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
___
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] Please contribute Fossil "skins" or "themes"

[ratwhs]

Hi

Attached you'll find a skin, i made - based on the default.

It looks a little bit more like a normal windows program. I added the
timeline-search form to the footer and reorganized the links in the
header.

Best regards
Wolfgang


fossil-skin.conf
Description: Binary data
___
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] [minor] src/style.c:427 → "%

[David Mason]

It's pretty common to put classes on  tags, to use CSS to
conditionally choose different renderings by simply changing the class of
the body tag.

../Dave

On 3 July 2018 at 00:23, mario  wrote:

> Mon, 2 Jul 2018 17:20:17 -0600 Warren Young :
>
> > Under what conditions would you have two different  tags in a
> > single document differing only by class, and thus need a CSS selector
> > to differentiate them?
>
> Of course you wouldn't want two  tags.
> But that's exactly the bug I ran into:
>
>
> 
> 
> 
> http://localhost:8080/timeline"; />
>  Plugin Meta Data: Timeline
>  href="/timeline.rss" />  href="/style.css?id=6f242840" type="text/css"  media="screen" /> 
> 
> 
>   
>   
>   http://localhost:8080/timeline"; />
>   Plugin Meta Data: Timeline
>   
>href="https://media.readthedocs.org/css/sphinx_rtd_theme.css";
> type="text/css" />  href="https://media.readthedocs.org/css/readthedocs-doc-embed.css";
> type="text/css" />
>   
>   
> 
>
>
> If you use a skin header with ``, current trunk
> will prepend a default  section and second  tag:
>
> > /*
> > ** Default HTML page header text through .  If the
> > repository-specific ** header template lacks a  tag, then all
> > of the following is ** prepended.
> > */
>
> It should check for , not just a fixed byte sequence.
>
> ##
>
> > > I see the value in the draft feature, but it's
> > > also a bit confusing still (while working on broken skins at
> > > least.)
> >
> > While I agree that the new skin editor is considerably more
> > complicated to use than the pre-2.5 method, I also don’t see how to
> > make it simpler without losing functionality we gained in that
> > release.
>
> TBH, I haven't really given it much more thought.
>
> It's clearly more practical to have secondary skins to work on,
> without harming the active/default template. And being able to
> grant additional edit permissions there is a nifty feature. As
> is the built-in help and step-by-step guide.
>
> It just got in the way for the aforementioned issue.
>
>
> > > - draftN… just treated as saved skins?
> >
> > I don’t see why that couldn’t be done in principle.
> >
> > The main practical problem is that skins can be named in a way that
> > would require ugly URL escaping to be specified in place of the
> > current draftN bit:
> >
> > https://fossil.example.com/Blitz%2C%20No%20Logo%20(built-in)/home
>
> If the PATH_URI detection can only only recognize `draftN` prefixes,
> than having all of them available wouldn't make sense. With the ugly
> percent escaping anyway.
>
> > There is a side-benefit of this change: if someone has a public
> > Fossil instance and one of the end users thinks the default skin is
> > ugly, he can change it by selecting the name of a skin he likes
> > better in the URL.  Currently, you can only change the skin this way
> > in a local clone which you’re running “fossil ui” on.
>
> Rather than extending the internal path dispatcher, supporting a
> plain/per-user cookie migth make sense. -- OTOH, this might already
> be feature creep..
>
>
> > I’m not seeing the value of that change.  The current mechanism is:
> >
> > 1. Select the skin/draft to edit.
> >
> > 2. Click the CSS/Header/Footer/Details edit links.
> >
> > Are you proposing to replace this with a grid, with skin names down
> > the left edge and 4 edit buttons per row to the right of each skin
> > name?  That does not sound like a simplification to me.
>
> It's sort of what came to mind. But indeed, that would probably just
> make it more convoluted.
>
> One simplification in the whole skin conundrum could be merging
> css+header+footer+settings editing into one page (4x textarea)
> however.
> Then it might be presentable in a table/grid scheme:
>
>  check   test
>  boxes   links
>↓   ↓
>   [ ]  Skin name[Edit]
>   [x]  Backup2  [Edit]
>   [ ]  Draft1   [Edit]
>↓
>   [Activate]  [Use as Draft]  [Publish]  [Delete]
>
> With the buttons just acting on the current selection.
>
>  * Could be fewer action buttons though.
>  * [Rename] or [Publish] better part of the css+head+foot editing
>page.
>  * The `Authenticate` option should really be part of the `Display
>Details` settings blob, btw.
>  * It would likely suffice if the template name doubles as test link
>(don't see the need for five test links).
>
> > If you

Re: [fossil-users] looking for interesting new fossil skins

[Andy Bradford]

Thus said Baptiste Daroussin on Wed, 12 Feb 2014 08:40:37 +0100:

> I  have also  stolen long  ago the  "google code"  like theme  and has
> adapted it a bit:

Is it intentional for all these ``google code'' look alikes to leave out
a background color?

Andy
-- 
TAI64 timestamp: 400052fc4dbf


___
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] Question on short-lived branches in fossil

[Stephan Beal]

On Fri, Jul 22, 2011 at 11:07 PM, Ross Berteig  wrote:

> For skins that are dark text on white background, then using the
> existing MD5 hash on the tag name, picking a convenient three;
>
...

it would make an entertaining experiment, whether or not it turns out to be
useful in practice.

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Plain Gray (No Logo) and long ticket texts (missing pre.verbatim in CSS)

[org.fossil-scm.fossil-users]

'Lo.

Unless I'm mistaken, it seems that the "Plain Gray (No Logo)" skin is missing
the following CSS present in some form in all of the other skins:

pre.verbatim {
  padding: 0.5em;
  white-space: pre-wrap;
}

This means that long ticket comments without manual linebreaks tend to result
in pages that have essentially unbounded width!

M
___
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] looking for interesting new fossil skins

[Remigiusz Modrzejewski]

On 11 Feb 2014, at 15:42, Stephan Beal  wrote:

> i'm looking to clone someone's interesting fossil skin to snazz up my fossil 
> repos a bit. Can any suggest a fossil repo with a nice skin?

I once stole a skin I like, see here:

http://dev.lrem.net/p2pvsim2/timeline

Kind regards,
Remigiusz Modrzejewski

___
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] looking for interesting new fossil skins

[Joel Bruick]

Richard Hipp wrote:
The tree-view 
(http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/dir?ci=tip&type=tree 
) 
doesn't look quite right.


That skin sets top and bottom margins on all LI elements, which the 
tree-view CSS doesn't account for. I just fixed this in trunk.

___
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] New skin: Blitz

[Jan Danielsson]

On 13/03/15 19:11, James Moger wrote:
[---]
> Blitz has two variants (with logo & without logo).  It includes an
> alternative Ticket page layout and several image resources which may be of
> use to other skins.

   Would you be willing to change the upper-case 'A-F' in hex digits to
lower-case in the timeline?

-- 
Kind Regards,
Jan
___
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] Modifying button bar

[Ron W]

On Mon, Aug 31, 2015 at 1:51 PM, Warren Young  wrote:

> On Aug 31, 2015, at 11:46 AM, Scott Doctor  wrote:
> >
> > how can I customize the buttons on the button bar at the top of the page
>
> Admin -> Skins -> Header.


Or just: Admin -> Header

(At least with the out-of-the-box Fossil, the 2 are equivalent.)
___
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 can I get 'Check-ins' by default in timeline (instead of Any Type)?

[Richard Hipp]

On 10/24/15, to...@acm.org  wrote:
> How can I get 'Check-ins' by default in timeline (instead of Any Type)?
>

Edit the "header" (under the Admin/Skins menu) and add ?y=ci to the
URL for the "Timeline" button on the menu bar.

-- 
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] Add styling to my repo's fossil wiki?

[Ron W]

On Wed, Feb 3, 2016 at 2:25 PM, John Gabriele  wrote:

> Is there any way I can add custom css styling to my fossil repo's wiki?
> Specifically, I'd like to add table borders and border-collapse.
>

Go to the "Skins" item on the "Admin" page of your Fossil web UI. (example:
http://localhost:8080/setup_skin)
___
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] Please contribute Fossil "skins" or "themes"

[Eric]

> I started this one ages ago to try to get the main menu at the side and a
> bit of a
> different feel, but only realised today that what it needed was an extra
> div. Anyway
> here you are... (tested Firefox 3.5.5, IE 6.0)
>

Thanks Richard for putting that one in. But we have now learnt that an
HTML comment in a skin (in skin.c) will be chopped to just "http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Please contribute Fossil "skins" or "themes"

[Eric]

> I started this one ages ago to try to get the main menu at the side and
a bit of a
> different feel, but only realised today that what it needed was an extra
div. Anyway
> here you are... (tested Firefox 3.5.5, IE 6.0)
>

Thanks Richard for putting that one in. But we have now learnt that an
HTML comment in a skin (in skin.c) will be chopped to just "http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil 2.1 menu scrunch.

[sky5walk]

Yeah, I'm just pointing out a change from v2.0 and down.
I think it's the 'underlining' effect that is taking extra room as the menu
collapses with zoom. Some earlier versions don't even attempt menu wrap and
make use of horizontal scrollbar. No biggie as I may be confusing stock
skins with whatever fossil-scm.org is adding?

On Wed, Mar 8, 2017 at 6:37 AM, Warren Young  wrote:

> On Mar 7, 2017, at 9:58 AM, sky5w...@gmail.com wrote:
> >
> > But, the scrunch appears with no scrollbar.
>
> I’m not sure what behavior you’re expecting, but what I see looks like
> perfectly sane HTML rendering behavior.  There isn’t enough room for
> “Download”, its padding, or the separator that’s attached to the menu item
> in the CSS.  Therefore, the browser must break the line at that point.
>
> What do you expect instead?
>
> > My zoom is 175%.
>
> If you just want to know how to make that skin work in the window width
> you’re willing to give the browser, despite your zoom level, I see two main
> options:
>
> 1a. Edit the skin to reduce the amount of padding around menu items.
> Under Admin > Skins > CSS, find the “.mainmenu a” block and decrease the
> second “padding” value.  (In 2-value form, the first value is top and
> bottom padding, and the second is left-right padding.)
>
> 1b. Same idea, only reduce font sizes or change typefaces to achieve the
> same end.
>
> 2. Remove menu items you don’t use to make room.  Do this via the same
> path in the UI, except that the last step is Header.
> ___
> 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] [UI] Increase font size in side-by-side page?

[Joel Dueck]

You can customize pretty much anything without plugins if you can
determine an appropriately specific CSS selector for it.

Assuming you use any modern browser, right click the diff and click
"Inspect Element" to see the see the HTML and CSS used to display it.
With some clicking and scrolling around, you'll find that the diff
text is inside a table with class "sbsdiffcols" and that the default
style includes "font-size: xx-small".

So in mine, I changed the size by adding the following CSS to my current skin:

table.sbsdiffcols {
  font-size: x-small;
  line-height: 1.3em;
}

When doing changes like this, be sure and look around to see if a rule
for that selector already exists in the CSS; if it does, modify that
one rather than making a new one. It's easier to debug your changes if
you don't have multiple rules potentially conflicting with each other.

Be sure and read this closely to learn more about changing Fossil's
web UI appearance:
https://www.fossil-scm.org/index.html/doc/trunk/www/customskin.md

On 8/3/18, Gilles  wrote:
> Hello,
>
> The UI seems the easiest way to diff versions and see what changes were
> made to a file between two revisions.
>
> Problem is, the font size is a bit small:
>
> https://postimg.cc/image/wm6lpynzx/
>
> I searched the archives* with "ui font size", but didn't find much.
>
> Is there a way to increase font size, or should I install "Fossil Skins
> Extra" (http://fossil.include-once.org/fossil-skins/index) add-on?
>
> Thank you.
>
> * https://www.mail-archive.com/fossil-users@lists.fossil-scm.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] side-by-side diffs

[Jan Danielsson]

Hey,

   I've taken inspiration from Stephans comments and made some slight 
updates. I also updated all the current skins (including the default) 
for sbsdiff support. Feel free to make changes which you see fit, or 
suggest changes. When it comes to changing the font list and font size, 
please bring it up for discussion first, since what works well for you 
won't necessarily work well for others. We need to find the greatest 
common denominator with regards to the font, which works for as many as 
possible.


   Two changes I made are for potential future features (see 
http://www.fossil-scm.org/index.html/artifact/6db07e500b3367f4a5ebaf76730f57399fd73249?ln=627-628). 
Though these options currently need to be changed in the source.


   collim can be used to limit the characters in a line (the ultimate 
goal is to make sure the diff table doesn't become too wide). I'm hoping 
there's a way to do this in CSS and allow the actual data to be 
preserved, but I haven't found it (yet?).


   allowExp (as in "Allow Expand") will enable or disable full 
generation of file lines in the diff. Enabling this slows down the page 
generation and currently the extra hidden rows can not be made visible, 
so I default the option to 'disabled' for now, simply because it speeds 
up page generation/loading.


   For reference, these are some screenshots (with slight CSS 
modifications) of what you should be seeing:


http://bayimg.com/kAKMgaadh
http://bayimg.com/KaKMhAaDH
http://bayimg.com/kakMIaADh
http://bayimg.com/kaKmKaaDh

   (I will remove these screenshots in a few days, so if you're reading 
through the archives, don't expect the links to work).


   If your result looks very messy, make sure you switch skins so you 
get the new changes, and make sure your browser reloads the new style 
sheets.


--
Kind regards,
Jan Danielsson

___
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] skins not always showing properly

[Tomek Kott]

Quick check: did you make sure to do a hard refresh of the page in a
browser to ensure that the CSS was reloaded properly?

As for the ticket system, for several reasons anonymous users do not have
the right to post tickets. So although you went to the right url, you don't
actually have permissions to post a ticket. The workflow now is to email
the list first, and then if the error can be reproduced, it will be filed
by devs.

Tomek

On Mon, Jan 23, 2012 at 4:31 PM, Johan Samyn  wrote:

> Hi,
>
> I downloaded the Windows binary fossil-w32-20111213135356.zip, and
> experienced a cosmetic issue with it.
> In the 2 repos I already had created with an earlier version, choosing
> either the "Black & White, Menu on left" or the "Gradient, Rounded
> Corners" skin both times produced the "Black & White, Menu on left" look.
> I then cloned the fossil repo itself, and there I saw that choosing
> either one of the two skins mentioned above now rendered as the
> "Gradient, Rounded Corners" both times.
> Bit strange, no ? Anybody any clue as to what is the cause - and even
> better, the solution - to this ?
>
>
> PS:
> I mention this via the mailing list because I was unable to register a
> new ticket, though I was logged in as anonymous, which should be able to
> do that if I'm right. The "www.fossil-scm.org" is the right url to do
> that, isn't it ? So this is rather two tickets in one email.
>
> --
> Johan Samyn
> ___
> "Perfection is achieved, not when there is nothing more to add,
> but when there is nothing left to take away."
> - Antoine de Saint-Exupery
>
> ___
> 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

[fossil-users] looking for interesting new fossil skins

[Stephan Beal]

Hi, all,

i'm looking to clone someone's interesting fossil skin to snazz up my
fossil repos a bit. Can any suggest a fossil repo with a nice skin?

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"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] What is the process for getting changes applied

[Darren Turland]

Hi

I recently found fossil and have made a few changes to the source that ...
- remove hardcoded styling from some html tags
- add class="..." to the html tags

This allows greater flexibility for skins. The plan is to make as much as
possible skinable.

What is the best approach for getting code changes applied? Sending a patch
file to the list?

Regards
Darren
___
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] Please contribute Fossil "skins" or "themes"

[altufaltu]

Request to add Shiny Fossil theme (http://dev.codingrobots.org/p/shiny-theme) 
to default set of themes.


Attached is a derived version with some recent changes for menu order / 
permission.


- Altu




-Original Message-
From: D. Richard Hipp 
To: fossil-users 
Sent: Sun, Dec 20, 2009 2:58 am
Subject: [fossil-users] Please contribute Fossil "skins" or "themes"


Earlier today, I checked in a version of Fossil that has the ability  to host 
multiple "themes" or "skins" for the web interface and that  allows users (with 
Admin privilege) to switch between skins with a  simple mouse click.However, 
the current implementation contains only two built-in skins:   The old default 
and a new "black" theme which is very similar to the  default.  It would be 
good, I think to have 6 to 10 different themes  that show a wide variety of 
possible looks.  Therefore, I am calling  on the user community to submit 
themes for consideration.To create a new theme or skin, edit the CSS, header, 
and footer to  obtain the look you want.  Then run the following command: 
fossil configuration export skin outputfile.txtAnd post the outputfile.txt 
here.  Thanks for contributing.D. Richard 
hipp...@hwaci.com___fossil-users 
mailing 
listfossil-us...@lists.fossil-scm.orghttp://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
 
-- The "skin" configuration exported from
-- repository "o:/fossil/fossil.fsl"
-- on 2010-01-15 10:11:10
REPLACE INTO config VALUES('css','/* General settings for the entire page */
body {
  margin: 0ex 1ex;
  padding: 0;
  background-color: #333;
  font-family: Verdana, "Lucida Grande", "Lucida Sans Unicode", Arial, 
sans-serif;
  font-size: 12pt;
  color: #000;
  text-align: center; /* workaround for IE box centering */
}

/* Header includes logo and project name */
div.header {
  margin: auto;
  min-width: 850px;
  width: 80%;
  margin-top: 20px; 
}

/* The project logo at the top of each page */
div.logo {
  text-align: center;
  font-weight: bold;
  color: #fff;
  text-shadow: 0 1px #000;
}

/* The page title under main menu */
div.title {
  font-size: 1.2em;
  font-weight: bold;
  text-align: left;
  color: #333;
  margin-left: 20px;
  margin-top: 0;
  padding-top: 20px;
  text-shadow: 0 1px #fff;
}

/* The login status message in the top right-hand corner */
div.status {
  float: right;
  text-align: right;
  color: #777;
  font-size: 0.8em;
  margin-top: 20px;
  margin-right: 20px;
}

/* The main menu bar that appears at the top of the page beneath
** the header */
div.mainmenu {
  padding: 10px 0;
  font-size: 0.9em;
  font-weight: bold;
  text-align: center;
  background: #315FD5;  
  -webkit-border-top-left-radius: 10px;
  -webkit-border-top-right-radius: 10px;
  -moz-border-radius-topleft: 10px;
  -moz-border-radius-topright: 10px;
  border-top-left-radius: 10px;
  border-top-right-radius: 10px;
  border-top: 1px solid #69F;
  border-bottom: 1px solid #152952;
  text-shadow: 0 -1px #152952;
  margin-bottom: 0;
}

/* The submenu bar that *sometimes* appears below the main menu */
div.submenu {
  padding: 3px 10px 3px 0px;
  font-size: 0.75em;
  text-align: center;
  color: #333;
  margin-top: -23px; /* push it to top between page title and status  */
  margin-bottom: 2px;
}

div.mainmenu a:link, div.mainmenu a:visited {
  padding: 3px 10px 3px 10px;
  color: #fff;
  text-decoration: none;
  border: 0;
}

div.submenu a:link, div.submenu a:visited {
  padding: 1px 10px;
  color: #222;
  border: 1px solid #BDBDBD;
  background: #EEE;
  -webkit-border-radius: 10px;
  -moz-border-radius: 10px;
  border-radius: 10px;
  text-decoration: none;
  text-shadow: 0 1px #fff;
}

div.submenu a:hover {
  color: #fff;
  background: #858585;
  border-color: #5B5B5B;
  text-shadow: 0 1px #000;
}

div.mainmenu a:hover, div.mainmenu a:visited:hover {
  color: #9CF;
  text-decoration: none;
}

div.container {
  margin: auto;
  min-width: 850px;
  width: 80%;  
  background: #69F;
  margin-top: 20px;
}

div.container, div.subcontainer {
  background: #f4f4f4;
  -webkit-border-radius: 10px;
  -moz-border-radius: 10px;
  border-radius: 10px;
  margin-bottom: 0;
  text-align: left;
}

div.subcontainer {
  width: 100%;
  -webkit-border-top-left-radius: 0;
  -webkit-border-top-right-radius: 0;
  -moz-border-radius-topleft: 0;
  -moz-border-radius-topright: 0;
  border-top-left-radius: 0;
  border-top-right-radius: 0;
}

/* All page content from the bottom of the menu or submenu down to
** the footer */
div.content {
  padding: 10px 20px 20px 20px;
  font-size: 0.8em;
}

/* Some pages have section dividers */
div.section {
  margin-bottom: 0px;
  margin-top: 1em;
  padding: 1px 1px 1px 1px;
  font-size: 1.2em;
  font-weight: bold;
  color: #5B677E;
  border-bottom: 2px solid #B6BECD;
}

/* The "Date" that occurs on the left hand side

Re: [fossil-users] Restoring previous timeline look

[Richard Hipp]

On 2/9/18, Chris Rydalch  wrote:
>
> Is this behavior hard-coded in newer versions of Fossil, or can it be
> changed in a skin's css? I thought I'd followed that discussion close
> enough, but I expected the skins to control the behavior so I'm clearly
> missing something...

Did you change to "Verbose View" on the timeline menu?  Is it still
not doing what you want after that?

-- 
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] Re-sync skins of remote repo

[Jungle Boogie]

Hi All,

I'd like to know if there's a way to re-sync to the skin of a remote repo, but I
don't know of an option to do so.

If I cloned the sqlite3 repo from long ago, when I run fossil server, I'll see
the former skin. `fossil sync` doesn't seem to care about changes to the skin.

Is the skin something outside the control syncing and updating?

Thanks!


___
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] [UI] Increase font size in side-by-side page?

[Gilles]

On 03/08/2018 16:19, Warren Young wrote:

On Aug 3, 2018, at 5:38 AM, Gilles  wrote:

Problem is, the font size is a bit small:

That’s because the default view is side-by-side.  Try clicking the Unified Diff 
link at the top of the Fossil UI diff view.

Thanks to both. I'll play with skins and see how it goes.
___
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] default ui look

[Richard Hipp]

On Sat, Mar 5, 2011 at 2:50 PM, Robert  wrote:

> I like the current look to the fossil home page. Can that be made the
> default, out-of-the-box, look for fossil? Pretty please?
>

You can change to that look easily enough.  Go to Admin->Skins and select
"Gradient, Rounded Corners".


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