| Age | Commit message (Collapse) | Author |
|---|
|
* debian/control: Add suggests for libhighlight-perl, although
that package is not yet created by Debian's highlight source package.
(See #529869)
|
|
|
|
If an inlined page contains a floating element, this ensures
that the footer appears beneath it, and prevents the floating element from
possibly leaking down to the next inlined page.
|
|
The horizontal line was only meant to be displayed under
the actions at the top of a page.
|
|
|
|
I saw a layout similar to this on blogger, and I sorta like it
The dash avoids parens sitting next to each other in some cases.
|
|
Makes it look more like a blog, but not enough to be confusing, and with
nothing as large as in a blog. Removal of the vertical line under the
subject imho makes it easier to scan through comments as each box is a new
one. Bolding the subject seems to make it stand out enough, especially as
its a link now. (Also considered increasing its font size to 110%.)
|
|
|
|
The PageSpec is still called "postcomment" since that's what it means.
|
|
|
|
Also put "posting comments disabled" in [], and change "Page preview"
to "Comment preview".
|
|
|
|
.inlineheader
In the initial template for blog-style comments, I don't want the author
name to be quite as large and prominent as the author of a blog post - I
expect that comments will be rather short, so the author name stands out
better for a given font size.
|
|
Some aggregated contents do not include a span element, so there was zero
padding without this.
|
|
|
|
|
|
|
|
This helps make sure the sidebar displays above it on some browsers
|
|
|
|
|
|
If a floating div is next to (and in front of) a div that takes up the
whole screen width, and has a background color set, that color can bleed
through into the floating div. One exampe of this is inline's blogpost
form. Avoid it by setting the background color of the floating element.
|
|
This removes clear:both from the trailing metadata of inlined entries as
requested by tschwinge, but if you want that feature back, you can set
.inlinefooter { clear: both; } in local.css.
|
|
|
|
|
|
* rcs_diff is a new function that rcs modules should implement.
* Implemented rcs_diff for git, svn, and tla (tla version untested).
Mercurial and monotone still todo.
|
|
|
|
are not included in the map. Include special styling for such pages.
* map: Remove common prefixes and don't over-indent.
* Add class option to htmllink().
|
|
|
|
|
|
and style sheet updates, and unless you're using customised versions,
you'll want to rebuild wikis on upgrade to this version to avoid
inconsistencies.
* Allow WIKINAME to to used in footers, as an example of something to put
there.
|
|
|
|
styled using the stylesheet, rather than by creating signin and prefs
templates.
* Make the openid login form nicely styled.
|
|
|
|
|
|
|
|
|
|
* More style sheet updates, remove the hack that used the tags div to create
the footer border.
|
|
|
|
in some cases it's not possible to move the mouse over the more backlinks
using the old method
|
|
the numbacklinks setting.
|
|
available templates. Rename the old templates page to wikitemplates.
* Include the note template in the basewiki.
* Add a popup template in the basewiki. CSS based on some by Martin Krafft.
* Make the note, popup, and plugin templates detect missing variables and be
self-documenting, listing the available variables.
|
|
that shouldn't appear in a printout: Search box, actions bar,
blog post form, tags, backlinks, and feed buttons.
|
|
OpenID login form rather than linking to a remote logo, to avoid various
issues. Since there is not yet a license for the actual OpenID logo, this
file is currently a blank image. Users who want to can copy
http://openid.net/login-bg.gif into their wiki.
|
|
in the doc wiki. This will allow direct edits to alter the base wiki
without manual munging.
|
|
|
|
|
|
fonts in the feed button style.
|
|
so I don't need to maintain two copies anymore.
You might also want to remove the files provided in the basewiki underlay
from your wiki, if you have not created custom local versions of them, so
that these pages will be automatically updated in future ikiwiki upgrades.
|
|
|
|
|
