a
slightly better use of vertical space.
Steve
On 3 Dec 2017, 10:26 AM +0800, Richard Hipp <d...@sqlite.org>, wrote:
> New enhancements to the "skin" mechanism of Fossil allow up to 9
> separate "draft" skins that can be independently edited and view
which I'll share in case anyone else also gets stuck like me.
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://y
t running in my repos.
>>
>> On Sun, Jan 7, 2018 at 3:43 PM Richard Hipp <d...@sqlite.org> wrote:
>>
>>> The Ardoise skin by Antoine Chavasse is now available on trunk. You
>>> can take a test-drive at
>>> https:/
3:43 PM Richard Hipp <d...@sqlite.org> wrote:
>>>
>>>> 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
>>>>
>>>> --
>&g
t;> ticket reports are configured by the user in the settings.
> >>
> >
> > I might need to enhance Fossil to recognize this situation and make
> > automatic adjustments to the background color.
> >
>
> If it's not already obvious, the fields on the ticket page ar
t;> >>
>> >
>> > I might need to enhance Fossil to recognize this situation and make
>> > automatic adjustments to the background color.
>> >
>>
>> If it's not already obvious, the fields on the ticket page are also too
>> bright:
>>
of custom skins myself!
Kind regards,
--
Igor Couto
Sydney, Australia
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
.
However, not everything is prose, and there are special cases where prose
should be in a monospace font regardless.
One such place, which I hope gets fixed while all this attention is being given
to the stock skins is to make the wiki composition textbox monospace, at least
if you’ve chosen Markdown
a mention of TH1 allowed in CSS.
http://fossil.include-once.org/fossil-skins/wiki?name=TH1
It can be used in the header, footer, or CSS within th1.../th1
sections, or in the th1-setup settings textbox.
Thanks for Fossil!
On Sun, Mar 15, 2015 at 4:57 AM, mario ma...@include-once.org wrote:
Sat
of the same CSS
code.
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.
@Richard: I've emailed a signed CLA and a bundle for your review and
integration consideration.
I hope
for Fossil and shares little of the same CSS
code.
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.
@Richard: I've emailed a signed CLA and a bundle for your review and
integration
>
> echo SELECT value FROM config WHERE name = "'css';" | fossil sql -R
> /repo.fossil
>
> The header and footer are also there if you need them.
>
> It should still be possible to customize under Admin->Skins (or
> /setup_skin via UI)
>
> Andy
> --
played as white by your web browser.
Richard Hipp:
> Fixed on trunk
With the fix committed as [7ac88481a6] [0], timeline arrow colors have
been turned off completely, and all timeline arrows are now displayed
with black color, also for skins with dark background colors, see for
example "x
Anyone know the SQL command to get all the tickets data from a database.
I guess I would then need to SQL command to import those same tickets into
a newly created fossil repository.
On Mon, 08 Mar 2010 09:29:43 -0500, D. Richard Hipp d...@hwaci.com wrote:
On Mar 7, 2010, at 11:42 PM,
info page
:) It's a basic UX feature - you go from docs to source code but
can't
get back :(
All the templates fossil is using are under Admin (header,
footer,
[skins, css]) and you can change them as much as you want.
I've been trying these, and they are great. I'm not sure I can use
are under Admin (header,
footer,
[skins, css]) and you can change them as much as you want.
I've been trying these, and they are great. I'm not sure I can use
them to create conditional links from the file section to the
documentation section - it may be possible using TH1 / and / or some
resolutions on small desktops/laptops
- the logo should still be a fossil of some sort. Petrified wood and
microscopic fossils allowed
- changing the name is not an option.
Winner gets the respect and admiration of their peers, runners up get
included as selectable skins.
What do you think?
Stephen
also that the set of suitable background colors
will also depend on what foreground color you use for the font.
I guess you could assume that foreground is always black
For skins that are dark text on white background, then using the
existing MD5 hash on the tag name, picking a convenient
export all'. I
only export 'tickets' or 'skins' usually, so not a big deal. I avoid
every pulling / pushing the users table.
Tomek
On Wed, Mar 21, 2012 at 7:20 AM, ST smn...@gmail.com wrote:
On Tue, 2012-03-20 at 08:27 -0400, Richard Hipp wrote
Hmmm I thought I could just do a fossil config pull skin to get these
but that seems not to be sufficient. What are the steps to clone a skin?
On Wed, Feb 12, 2014 at 12:40 AM, Baptiste Daroussin
baptiste.darous...@gmail.com wrote:
I have also stolen long ago the google code like theme
Hi Stephen,
I have made a skin using Twitter Bootstrap CSS that looks quite good
IMHO (responsive layout and all). Actually this is a bit more involving
than just using the skin, it requires patching the markup that is
generated by fossil a bit, something that I maintain in my private
branch (but
On 8/7/2014 15:09, Warren Young wrote:
you can use a meta tag to do the same thing
Confirmed. If you go to Admin Skins Header, and add this line
somewhere in head, IE8+ will work in standards mode when you point it
at an intranet instance of Fossil:
meta http-equiv=x-ua-compatible
Following is a patch (against 9e48dad49b) to add a new option to the
/setup_timeline web page to specify the default query parameters for
the /timeline web page, that works without modifications to the web UI
skins.
To keep it simple and avoid code duplication, the QUERY_STRING
variable
On 6/5/2017 8:37 PM, Andreas Kupries wrote:
I am not sure that this would help him.
My reading of his request is that he wants to customize the page
generated by fossil itself [1].
That was my read too. The $64K question then is where such customization
would be stored. Skins are per
e, I already know I can edit the /home wiki page and the skin to
provide #1 today, though it would be nice if the stock skins contained these.
> Prior to
> that, they were doing an "apt-get install fossil" followed by a
> "fossil clone" and "fossil open" -
ons for improvement.
>
> Web developers - help me with this: For item (3) above, how can I
> make the ellipsis or icon to "show more detail" configurable using
> CSS? What's the best way to handle that so that people can customize
> the look for various skins?
>
> --
>
(3) above, how can I
make the ellipsis or icon to "show more detail" configurable using
CSS? What's the best way to handle that so that people can customize
the look for various skins?
--
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing l
>>>> On Sun, Jan 7, 2018 at 3:43 PM Richard Hipp <d...@sqlite.org> wrote:
>>>>
>>>>> The Ardoise skin by Antoine Chavasse is now available on trunk. You
>>>>> can take a test-drive at
>>>>> https://www.fossil-scm.org/skins/a
font than in a monospace font. It’s been studied to death.
However, not everything is prose, and there are special cases where prose
should be in a monospace font regardless.
One such place, which I hope gets fixed while all this attention is being
given to the stock skins is to make the wiki
Gitblit, then this theme will feel comfortable,
although it is specialized for Fossil and shares little of the same CSS
code.
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.
@Richard
l some discussion about that in the past.)
But skins are not autosync'ed. You get a copy of some skin on clone, but
without some effort by an authorized user of the main repo, no changes
made to a skin in a clone will propagate back.
So if you have personal preferences for timeline defaults, rep
Timeline
(/timeline) link in the menu.
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.
The html/th1 mix that shows up in the textbox is the top section of
the pages.
Search fo
are the capabilities of my test user : bceghjnprw
>>
>>
>> But it seems it is not enough: when `fossil ui` is started, the ticket
>> tables, skins etc. where not copied.
>>
> I cannot reproduce the problem. When I set "nobody" permissions to
> ju
Op Za, 19 december, 2009 22:28, schreef 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
Hi,
Another patch to adapt content to HTML5.
Replaces with
Alternative to patch:
find . -type f -print0 | xargs -0 perl -pi -e 's///g'
Best Regards,
Johan
Index: skins/black_and_white/header.txt
==
--- skins/black_and_white
of some sort. Petrified wood and
microscopic fossils allowed
- changing the name is not an option.
Winner gets the respect and admiration of their peers, runners up get
included as selectable skins.
What do you think?
Stephen
On Thursday, March 3, 2011, Kristoffer Lawson se...@scred.com wrote:
On 3
and admiration of their peers, runners up get
included as selectable skins.
What do you think?
Let it be so, as Stephen as suggested. Go forth and prototype.
Stephen
On Thursday, March 3, 2011, Kristoffer Lawson se...@scred.com wrote:
On 3 Mar 2011, at 13:41, Richard Hipp wrote
Hello Stephan,
Here is a short patch that removes the use of the nobr element which
has never been part of the standard. I have found that it is used solely
in stat.c to display the URL stats.
The fix is to replace nobr by span class=nobr and add span.nobr {
white-space: nowrap; } to the default
(Oops, my last reply didn't make it to the list..)
Anyway, it's now a bit more polished, and works in Firefox as well.
There are a some usage hints here now:
http://fossil.include-once.org/fossil-skins/wiki/GitHub
2014-03-17 19:27 GMT+01:00 mario xm...:
2014-03-17 17:33 GMT+01:00 Stephan
to customize the page
>> generated by fossil itself [1].
>
> That was my read too. The $64K question then is where such customization
> would be stored. Skins are per repository, and this is running outside of all
> repositories. There is the global settings location, of cour
gt;> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>
>
>
While I agree that it is important to have a default (original) skin that
works well (text must be readable, etc.) , I think the one important thing
is that all in
have on-line and send
>> me your complaints and suggestions for improvement.
>>
>> Web developers - help me with this: For item (3) above, how can I
>> make the ellipsis or icon to "show more detail" configurable using
>> CSS?
gt;>>>
>>>>> Wow that's a slick skin. Antoine, if you're on the list, top notch
>>>>> work. Can't wait to get it running in my repos.
>>>>>
>>>>> On Sun, Jan 7, 2018 at 3:43 PM Richard Hipp <d...@sqlite.org> wrote:
>>>>>
>>
On 18/02/15 00:43, Richard Hipp wrote:
[...]
will likely have a modified DOM for
the web interface and thus may break any new skins you come up with
today.
This might be a good time to mention that I've been playing with a
Material Design skin for Fossil, using the Polymer engine. There's
the respect and admiration of their peers, runners up get
included as selectable skins.
What do you think?
Stephen
On Thursday, March 3, 2011, Kristoffer Lawson se...@scred.com wrote:
On 3 Mar 2011, at 13:41, Richard Hipp wrote:
On Thu, Mar 3, 2011 at 4:26 AM, Trou Macacq mac...@gmail.com wrote
On Wed, May 21, 2014 at 6:49 PM, Igor de Oliveira Couto
i...@semperuna.comwrote:
Where can I find some of these? - I had a quick look through the
repositories at 'Chisel', but found only 3 skins there.
i think you'll either need to search the list archives or wait until
someone who's created
was weird to me at first. Also I very much used SVN's ability
to have multiple working copies checked out from a single repository. With
git I have to clone the repository to get additional working copies. And
then I have to push/pull changes between them.
== wiki syntax ==
>
> One of the wea
On 1/8/2018 6:57 PM, Richard Hipp wrote:
On 1/8/18, The Tick <the.t...@gmx.com> wrote:
Curious about the new skins, I attempted to compile Fossil-24c2b99d on
win7x64 with a current (as of today) MSYS2 using
There are changes on trunk that might fix these build problem. But,
as nobod
leaf login main manifest md5
merge merge3 name path pivot popen pqueue printf rebuild report rss schema
search setup sha1 shun skins sqlcmd stash stat style sync tag tar th_main
timeline tkt tktsetup undo update url user verify vfile wiki wikiformat
winhttp xfer zip http_ssl
)
# Additional
Hello Stephan,
Yep adding data-* is not that straightforward… If you want I can try
to create a patch with that functionality alone (a subset of the
diff I send you earlier).
Yes, please.
Here you go !
For the records, this patch enables the use of data-* attributes in the
unning gcc 5.3.0.
Curious about the new skins, I attempted to compile Fossil-24c2b99d on
win7x64 with a current (as of today) MSYS2 using
$ gcc -v
Using built-in specs.
COLLECT_GCC=D:\msys64\mingw64\bin\gcc.exe
COLLECT_LTO_WRAPPER=D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/7.2.0
\
$(OX)\sha1$O \
$(OX)\shell$O \
$(OX)\shun$O \
$(OX)\skins$O \
$(OX)\sqlcmd$O \
$(OX)\sqlite3$O \
$(OX)\stash$O \
$(OX)\stat$O \
$(OX)\style$O \
$(OX)\sync$O \
$(OX)\tag$O \
$(OX)\tar$O \
$(OX)\th$O
201 - 252 of 252 matches
Mail list logo
