hing text is shown
> in a black font. Example:
>
> https://www.fossil-scm.org/skins/ardoise/search?s=utime=c
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm
nt. Example:
>
> https://www.fossil-scm.org/skins/ardoise/search?s=utime=c
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:
in 2.3 is just fine.
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...
Thanks
On 2/9/18, Chris Rydalch <cryda...@gmail.com> 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
&
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
On Fri, Jan 14, 2011 at 6:01 PM, David Bovill da...@architex.tv 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
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
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
Oooh, all of this sounds *really* interesting and exciting:
On 22 May 2014, at 2:25 am, Stephan Beal sgb...@googlemail.com 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
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
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
On 4/30/18, Peter Vonča <pvo...@gmail.com> 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
> 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 &q
er 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 othe
@ 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
On Dec 20, 2009, at 2:30 PM, Eric wrote:
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
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
On Mon, Apr 4, 2011 at 2:52 PM, Wilson, Ronald rwils...@harris.com wrote:
What skin is the sqlite.org fossil repository using? It is not in the
default skins that come with fossil. Is it published somewhere?
Published? If you clone the fossil repository and then do fossil config
export
Hi folks,
Being new to Fossil, I decided to write up a blog post on how to change the
style of Fossil to something approximating Google code - with most of the
hard styling work done by Dmitry @ CodingRobots. You can find the post here:
On Fri, Jul 22, 2011 at 7:25 PM, Richard Hipp d...@sqlite.org wrote:
On Fri, Jul 22, 2011 at 5:32 PM, Stephan Beal sgb...@googlemail.comwrote:
On Fri, Jul 22, 2011 at 11:07 PM, Ross Berteig r...@cheshireeng.comwrote:
For skins that are dark text on white background, then using
include Alex’s syntax
highlighter in your repository, or refer to the online version (which
means you don’t get syntax highlighting when offline).
Another is that you have to re-incorporate it every time you change skins.
(Lastly as a side note, my apologies if this reply comes in crazy
another issue is that the configuration is local to the respective
repo. so if I fix the configuration on some server-side repo, the local
clone of somebody else will not profit from it.
anyway, thanks again. I at least know now how to fix it for my own repos.
Fossil supports skins, so it would
On Tue, Feb 11, 2014 at 4:06 PM, Stephan Beal sgb...@googlemail.com wrote:
On Tue, Feb 11, 2014 at 3:54 PM, Remigiusz Modrzejewski
l...@maxnet.org.pl wrote:
I once stole a skin I like, see here:
http://dev.lrem.net/p2pvsim2/timeline
Very googlecode-ish! How's it look on me?
On Tue, Feb 11, 2014 at 4:28 PM, Richard Hipp d...@sqlite.org wrote:
The tree-view (
http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/dir?ci=tiptype=tree)
doesn't look quite right.
i don't notice anything wrong with that particular link (but i'm new to the
new tree view), but i did
On 11 February 2014 16:35, Stephan Beal sgb...@googlemail.com wrote:
On Tue, Feb 11, 2014 at 4:28 PM, Richard Hipp d...@sqlite.org wrote:
(http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/dir?ci=tiptype=tree)
i don't notice anything wrong with that particular link (but i'm new to
On Tue, Feb 11, 2014 at 5:08 PM, Joel Bruick j...@joelface.com wrote:
Richard Hipp wrote:
The tree-view (http://fossil.wanderinghorse.
net/repos/libfossil/index.cgi/dir?ci=tiptype=tree
http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/
dir?ci=tiptype=tree) doesn't look quite
Remigiusz Modrzejewski schreef op 11-2-2014 15:54:
On 11 Feb 2014, at 15:42, Stephan Beal sgb...@googlemail.com 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
On Wed, Feb 12, 2014 at 8:40 AM, Baptiste Daroussin
baptiste.darous...@gmail.com wrote:
I have also stolen long ago the google code like theme and has adapted
it a bit:
- timeline is showing raw logs (because we do multiline commit logs -
btw I can't get the cli timeline respecting multiline
On Thu, Feb 13, 2014 at 6:07 PM, Matt Welland estifo...@gmail.com 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?
conf pull skin pulls not only the CSS but also the index page name, so
On Thu, Feb 13, 2014 at 12:09 PM, Stephan Beal sgb...@googlemail.comwrote:
On Thu, Feb 13, 2014 at 6:07 PM, Matt Welland estifo...@gmail.com 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
On Thu, Feb 13, 2014 at 2:18 PM, Stephan Beal sgb...@googlemail.com wrote:
On Thu, Feb 13, 2014 at 7:52 PM, Richard Hipp d...@sqlite.org wrote:
Do we need to change config pull skin so that it omits the index page
name?
i'd vote for that, or a flag for it.
Huh. Apparently you can
On 11 Feb 2014, at 19:42, Martijn Coppoolse li...@martijn.coppoolse.com wrote:
Remigiusz Modrzejewski schreef op 11-2-2014 15:54:
On 11 Feb 2014, at 15:42, Stephan Beal sgb...@googlemail.com wrote:
i'm looking to clone someone's interesting fossil skin to snazz up my
fossil repos a bit.
The Skin looks really great. But ...
That is the problem with Twitter Bootstrap, you have to change the
markup to fit to the CSS. And that is plain wrong. There are solutions
that help with responsive and grid layouts like Neat
(http://neat.bourbon.io/) where the CSS is generated for the
On Fri, Feb 14, 2014 at 2:52 PM, Stephan Beal sgb...@googlemail.com wrote:
article, aside, footer, header, nav, section elements are valid.
That sounds good to me. i'll clear this with Richard before changing it.
Here you go:
http://www.fossil-scm.org/index.html/info/93dffb9147
i
That was fast !
i couldn't add data-* attributes (despite Richard's OK) because the internal
structure of the parser needs to know all full attribute names and their
integer IDs at compile-time (this makes it very fast, but useless for dynamic
data-* name lookups). But the requested
On Fri, Feb 14, 2014 at 4:43 PM, Samuel Debionne
samuel.debio...@ujf-grenoble.fr wrote:
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.
Something I noticed while
.
Requires fossil-search-table.php run beforehand for fx_search/_stats.
I plan on using this to not be nagged about switching to actual git+github.
Can be downloaded here as usual:
http://fossil.include-once.org/fossil-skins/
Some editing is required though.
Btw, maybe someone can lend some
versions).
In any case, in the process I was looking at schema and saw there is a
photo column in the users table. I imagine it is for a photo of the user,
but cannot find anywhere that it is used. Is this something that was added
for specific skins/themes to use or is it something
On 1/23/15, Samuel Debionne samuel.debio...@ujf-grenoble.fr wrote:
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
:
.submenu a {
border: 1px solid transparent;
}
Uploaded a patched version here:
wget https://fossil.include-once.org/fossil-skins/cat/sanfrancisco.txt
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080
Hello All,
Does anyone else have issues with alignment with /reports?view=byfile
on any of the skins?
For the Fossil repo itself, it's perfectly fine but from a git import
of Freeswitch, its bad on Firefox and worse on Chromium.
...
After scrolling all the way through the files, I see there's
apply to other MIT licensed
dependencies.
@Richard: Is there an online version of your CLA? Or do you require a
mailed copy?
On-line CLA at
https://www.fossil-scm.org/fossil/doc/trunk/www/copyright-release.html
For algorithmic code, I ask for hard-copy. But for themes and skins
Please continue to offer suggestions for improvement.
What about adding javascripts as part of the skin (as it is done for
css) ? Motivation: skins could be made responsive and/or include more
dynamic components and there is no way to do that without a bit of
javascript. Large javascript
Hi,
At a quick glance there does not seem any way to determine the Fossil Release
Version from the web interface.
It seems some skins show the Release Version in the footer, and some do not. I
would like to request the default skin to do so as per this trivial patch...
@@ -1,6 +1,6
em.
It should still be possible to customize under Admin->Skins (or
/setup_skin via UI)
Andy
--
TAI64 timestamp: 4000567b047d
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
fically, 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-user
New enhancements to the "skin" mechanism of Fossil allow up to 9
separate "draft" skins that can be independently edited and viewed,
for easier A/B comparisons.
For the moment, I have assigned "draft1" to Steve Landers and "draft2"
to Warren Young, sin
s.
>
> So, if anybody sees any last minute tidying up that we need to do to
> the website in anticipation of a huge influx of first-time visitors,
> please speak up. Quickly.
>
Perhaps expand point #2 to talk about themes/skins built into fossil, and a link
to the URL where the use
ldn’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
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 m
urrent 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 , no
; 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:
>
>> The Ardoise skin by Antoine Chavasse is now available on trunk. You
>> can take a test-drive at
>> https://www.fossil-scm.org/skins/ardo
>
>
> If it's not already obvious, the fields on the ticket page are also too
> bright:
> https://www.fossil-scm.org/skins/ardoise/tktview?name=c541b6e734
>
> Thanks for the new skin, Antoine! I appreciate the work.
>
> > --
>
text is shown
>> in a black font. Example:
>>
>> https://www.fossil-scm.org/skins/ardoise/search?s=utime=c
>>
>> --
>> D. Richard Hipp
>> d...@sqlite.org
>> ___
>> fossil-users mailing list
&
t;d...@sqlite.org> wrote:
> On 2/9/18, Chris Rydalch <cryda...@gmail.com> 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 t
llowed 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
On Sat, Mar 17, 2018 at 4:42 AM, J Ronald <follow...@yahoo.com> wrote:
>
> steps now:
> 1. click tab "Tickets"
> 2. click "All Tickets"
>
> steps I want:
> 1. click tab "Tickets"
>
Go to Admin > Skins and edit the Header part, c
ns
as makes sense for your your purposes.
Then do the same for Admin > Skins. At minimum here, you’ll want my Bugs and
Wish List button changes.
You need to copy from a local clone because you won’t be able to get into my
repository’s Admin section via my public Fossil instance, lacking ad
Tickets.
> Copy as much or as little of what you see there into your Admin > Tickets
> sections as makes sense for your your purposes.
>
> Then do the same for Admin > Skins. At minimum here, you’ll want my Bugs
> and Wish List button changes.
>
> You need to copy from a loc
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
Here is a simple algorithm that choses light shades for background - useful for
skins having white/light background with black text - may be tweaked for skins
for black/dark backgrounds as well (by not adding constant - but I haven't
tested it). This one uses 30%/59%/11% ratio for R/G/B dynamic
.
see what looks good and what doesn't. If you select the built-in skin #4
(the one with rounded corners and gradients) and then go to the built-in
CSS editor, you'll find some border-bottom-properties which are
commented out.
i don't see those properties, and AFAIK skins are not synched via
trunk
comment: initial empty check-in (user: matt)
check-ins:1
But it seems it is not enough: when `fossil ui` is started, the ticket
tables, skins etc. where not copied.
I tried to copy the configuration from the original repository without
more success:
matt@xps:~/pro
ssil, "Header" represents all the
html content or structure prior to the generated content.
Fossil Theme docs explain this but somehow it flew right over my head.
On Mon, Apr 30, 2018 at 7:08 PM, Richard Hipp <d...@sqlite.org> wrote:
> On 4/30/18, Peter Vonča <pvo...@gmail.
The background of the table in the "tickets" page is too light.https://www.fossil-scm.org/skins/ardoise/rptview?rn=12018年1月8日 07:08，Antoine Chavasse <a.chava...@gmail.com>寫道：Hi,Thanks for the feedback!I agree that the diff view could use some improvement. I'll experiment tomorrow
347ca3e7eb2e8c64b1c60b7a9
> checkout: 1fb3f04b1892b10c1fda206cab4b08a75056e388 2013-07-25 12:17:21
> UTC
> tags: trunk
> comment: initial empty check-in (user: matt)
> check-ins:1
>
>
> But it seems it is not enough: when `fossil ui` is started, the ti
8, 2018, 03:23 gumblex <gumb...@aosc.io> wrote:
> The background of the table in the "tickets" page is too light.
>
> https://www.fossil-scm.org/skins/ardoise/rptview?rn=1
>
> 2018年1月8日 07:08，Antoine Chavasse <a.chava...@gmail.com>寫道：
>
> Hi,
>
> T
somewhat to have more room for the diff
view, but it seems to look alright. I know some people even prefer skins
with a full width anyway - as a side note you can tweak the width or unlock
it by editing or removing the line "max-width: 1200px;" from the css.
I have submitted this tweak on t
feel it's slightly betraying the documentation-nature
> of the Fossil homepage.
> · And if implemented, people would want to have it with their
> own Fossil setup (= must to be slim enough to be embedded
> with one of the skins).
>
> On the other hand it's a cheap feature:
&g
y too abstract for a concrete pictogram.
· I feel it's slightly betraying the documentation-nature
of the Fossil homepage.
· And if implemented, people would want to have it with their
own Fossil setup (= must to be slim enough to be embedded
with one of the skins).
On the other hand it's a
the same thing, but Zed beat me to it
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. Leave the current look as the
default, but make the wonderinghorse.net skin one
On Mar 7, 2010, at 11:42 PM, Rodney Malone wrote:
I was just trying out the latest snapshot of Fossil and ran into a
small quirk that might cause a headache for someone.
Thanks for pointing this out. The problem is now fixed. The previous
release cancelled and a new release is now
access and alter these directly?
All the templates fossil is using are under Admin (header, footer,
[skins, css])
and you can change them as much as you want.
But the template language is basic, no include other templates. TH1
is available so
you have if then else. But you have to code
Thanks for the writeup Tomek.
I personally would be interested in any advancements you make with
javascript, or any other improvements from the basic fossil ui.
Thanks,
Ambrose
On Mon, May 23, 2011 at 12:06 AM, Tomek Kott tkott.s...@gmail.com wrote:
Hi folks,
Being new to Fossil, I decided
On Sun, May 22, 2011 at 6:17 PM, Ambrose Bonnaire-Sergeant
abonnaireserge...@gmail.com wrote:
I personally would be interested in any advancements you make with
javascript, or any other improvements from the basic fossil ui.
Me as well. If you extend the GoCo theme to include diff
On Fri, Jul 22, 2011 at 5:32 PM, Stephan Beal sgb...@googlemail.com wrote:
On Fri, Jul 22, 2011 at 11:07 PM, Ross Berteig r...@cheshireeng.comwrote:
For skins that are dark text on white background, then using the
existing MD5 hash on the tag name, picking a convenient three
, 2011 at 5:32 PM, Stephan Beal sgb...@googlemail.com wrote:
On Fri, Jul 22, 2011 at 11:07 PM, Ross Berteig r...@cheshireeng.com 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
Beal sgb...@googlemail.com
wrote:
On Fri, Jul 22, 2011 at 11:07 PM, Ross Berteig r...@cheshireeng.com
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
).
see what looks good and what doesn't. If you select the built-in skin #4
(the one with rounded corners and gradients) and then go to the built-in
CSS editor, you'll find some border-bottom-properties which are
commented out.
i don't see those properties, and AFAIK skins are not synched via
of
local fossil repositories being served, then we could have a central
navigation page which would be updated when new repositories were installed
/ deleted. This would also enable fossil skins to offer navigation to other
fossil sites on the same server
programming sessions.
Of course keep you in the zone does not make a lot of sense for a website. I
simply like the colorset.
If we had the skins/themes in a public repository, anyone could fork and
contribute a high contrast version.
Thanks for sharing.
Thank you all for providing Fossil
that (a feature we've
talked about a couple times but have no compelling need for).
Of course keep you in the zone does not make a lot of sense for a website.
I simply like the colorset.
If we had the skins/themes in a public repository, anyone could fork and
contribute a high contrast version.
If you
Maybe make them a config area that must be explicitly pushed, pulled or
synced along with skins, users, etc.? (Assuming that isn't how they're
already implemented.)
On 02/13/2012 05:37 PM, Steve Bennett wrote:
On 14/02/2012, at 9:30 AM, Gé Weijers wrote:
On Mon, Feb 13, 2012 at 1:49 PM
I've noticed that myself, so I never to 'fossil config 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
On Tue, Feb 11, 2014 at 7:42 PM, Martijn Coppoolse
li...@martijn.coppoolse.com wrote:
Another one I liked is this one:
http://projects.depar.is/divers/
It's based on GitHub's style, as the one above is based on Google Code's
style. :-)
Oooo, i like that one, too, but Google Code sits
I have also stolen long ago the google code like theme and has adapted it
a bit:
- timeline is showing raw logs (because we do multiline commit logs - btw
I can't get the cli timeline respecting multiline commits log :()
- the tree view is default and has icons (stolen from openclipart as well)
The timeline does not support multi-line commit message, I sent the patch
for the web version of the time line as well as the info page that you
integrated, but I was never able to figure out how to do the same with the
the timeline cli.
For the command line I always messed up in the way I count
On Thu, Feb 13, 2014 at 8:24 PM, Richard Hipp d...@sqlite.org wrote:
Huh. Apparently you can already do config pull css. What else other
than the CSS file needs to be brought over to move a look from one repo
to another?
Didn't know that. In my case i pulled (css,header,footer), but i
Am 14.02.2014 11:02, schrieb Samuel Debionne:
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,
On Fri, Feb 14, 2014 at 2:27 PM, Samuel Debionne
samuel.debio...@ujf-grenoble.fr wrote:
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
. Is this something that was added
for specific skins/themes to use or is it something that is generally
usable/accessible?
Originally designed for a photo of the user, but not currently used.
This is mostly a curiosity based question. At the moment all the photo for
all rows is NULL so it's not something
for specific skins/themes to use or is it something that is generally
usable/accessible?
Originally designed for a photo of the user, but not currently used.
Thanks. BTW, for those who might be curious, it is a pain to get php
fossil to cooperate to create a new repo (HOME env var needs to be set
be a potential buglet in how it publishes the base URL. All of the skins
for the header include the following:
base href=$baseurl/$current_page /
Which results in the following output:
$ printf 'GET /doc/tip/file%%2b%%2b.wiki HTTP/1.1\r\nHost:
localhost:8080\r\n\r\n' | nc localhost 8080 | grep base
is doing the right thing in converting + characters in the
URL into spaces.
It certainly handles them correctly when given them, however, there may
be a potential buglet in how it publishes the base URL. All of the skins
for the header include the following:
base href=$baseurl/$current_page
it publishes the base URL. All of the skins
for the header include the following:
base href=$baseurl/$current_page /
Which results in the following output:
$ printf 'GET /doc/tip/file%%2b%%2b.wiki HTTP/1.1\r\nHost:
localhost:8080\r\n\r\n' | nc localhost 8080 | grep base
base href=http://localhost:8080
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
101 - 200 of 252 matches
Mail list logo
