Worth reviewing
http://www.pmwiki.org/wiki/PmWiki/RoadMap-Talk
On 30 April 2012 04:35, Eric Forgeot wrote:
> On 28/04/2012 03:30, tamouse mailing lists wrote:
> > opposite way. The default skin for the installation should really be
> > the simplest set of elements of all, the minimum needed t
On 28/04/2012 03:30, tamouse mailing lists wrote:
> opposite way. The default skin for the installation should really be
> the simplest set of elements of all, the minimum needed to get a site
> functional.
I agree. It should be simple, easily expandable. And nice-looking. It's
not incompatible. B
On Fri, Apr 27, 2012 at 8:10 AM, Al Louis Ripskis wrote:
> Sep 11, 2011 3:35 PM Eric Forgeot wrote:
> why not a new default pmwiki skin?- for the default installation and for the
> http://www.pmwiki.org website? The current ... looks like it was designed in
> 1992,
I know this has gone round a
Hi Al,
Friday, April 27, 2012, 2:10:05 PM, you wrote:
> Hans, can I use this new template to update the Triad skin that I
> have been using and which you developed?
I have been using the skin on a number of sites, without getting
negative feedback. That said, I have not polished the skin for
rele
Sep 11, 2011 3:35 PM Eric Forgeot wrote:
why not a new default pmwiki skin?- for the default installation and for the
http://www.pmwiki.org website? The current ... looks like it was designed in
1992,
My question is to Hans, because as I see from his website:
"Latest project: Developing a new
On 23 September 2011 04:07, Paul Giacherio wrote:
>
>>
> 2] Utilizes simple media queries to ensure the design is functional all
> the way down to mobile sizes
>
> 4] Moves all [and i mean ALL] standard style declarations into the default
> css file - the current, occasional, header style injecti
I agree we must support a wide range of media sizes (but not label them by
device type).
I think CSS rather than a separate skin is definitely the way to go
Simon
On 20 September 2011 19:42, Ville Takanen wrote:
> Another approach would be to use CSS media width rules. These work quite
> well
>
>>About 4]+5], the (:noleft:) feature in a table-less skin may require some
>> CSS
>>injection, either inline in the html page, or via a to an
>> additional
>
> Indeed, the ability to suppress sections makes a CSS implementation
> harder. Thanks for the reminder.
Agreed. Maybe a little pragmati
Petko Yotov wrote:
>> 1] Is centered, and has a flexible width to a point - the left-aligned,
>> full width current skin is difficult on big screens
>> 2] Utilizes simple media queries to ensure the design is functional all the
>> way down to mobile sizes
>> 3] Includes a css reset and solid stand
Sorry, there is an error in my last posting:
>I have a different apporach: I change the style of the current action
>e.g. the background colour, for example with a background colour and
>not being a link:
>
> $HTMLStylesFmt[] = ' .{$Action} { background-color: lightblue; }';
this adds bacground
ABClf wrote:
>This history big button, next to edit button, is (in my opinion) a
>good way to show possible users how a page is done, to enlighten the
>fact such a page is a result of x revisions and to appeal the click. I
>like that.
>(edit button should then become view button when in edit mode,
Paul Giacherio wrote:
>A css reset is just a group of css declarations which aim to iron out
>browser rendering inconsistencies: http://meyerweb.com/eric/tools/css/reset/
What's bad with inconsistencies per se?
IMO css resets are harmful, e.g. with respect to accessibility.
It reminds me of tim
rogu...@googlemail.com (2011-09-22 21:51):
> 3. Is a CSS reset (unified CSS stylesheets across browsers) really
>required? Is this merely perfectionism, or are there some crazy
>differences between browser-default stylesheets?
Ok, I thought that CSS reset meant unifying styles across brows
Thursday, September 22, 2011, 10:21:35 PM, Petko Yotov wrote:
>> 4] Moves all [and i mean ALL] standard style declarations into the default
>> css file - the current, occasional, header style injection can be maddening
>> to a first-time customizer
> I agree, but we should go there carefully. Mov
if the skin is changed, please make the menu and the content
independently scrollable. Today, if you scroll down a long page the
navigation area on the left side disapears, if you need it you have to
scroll up again. This is especially user hostile for the
current-page-navigation links I like
On Thursday 22 September 2011 18:07:43, Paul Giacherio wrote :
> there's a lot of great feedback here that I think
> is really valuable.
I strongly agree! Thank you all!
> Form my perspective, I'd like to see a default pmwiki skin that:
>
> 1] Is centered, and has a flexible width to a point - t
> A css reset is just a group of css declarations which aim to iron out
> browser rendering inconsistencies:
> http://meyerweb.com/eric/tools/css/reset/
>
> Once you do that, it's much easier to control elements and do things like
> work with a baseline grid, etc.
Thank you. If this approach was
> Forgeot Eric (2011-09-21 22:08):
>> > http://paulgiacherio.kodingen.com/pmwiki/pmwiki-2.2.30/pmwiki.php?n=PmWiki.DocumentationIndex
>>
> The way fonts are specified is not good:
> * font-family:Georgia;
> * font-family:Arial;
> They need a serif and sans-serif fallbacks respectively.
If a desig
A css reset is just a group of css declarations which aim to iron out
browser rendering inconsistencies: http://meyerweb.com/eric/tools/css/reset/
Once you do that, it's much easier to control elements and do things like
work with a baseline grid, etc.
None of this directly addresses the 'vspace'
Paul Giacherio (2011-09-22 12:07):
> 1] Is centered, and has a flexible width to a point - the left-aligned, full
> width current skin is difficult on big screens
> 2] Utilizes simple media queries to ensure the design is functional all the
> way down to mobile sizes
> 3] Includes a css reset and s
>
> I wonder whether Paul Giacherio anticipated this dissection of his(?)
> design.
>
Ha, no I didn't. However, there's a lot of great feedback here that I think
is really valuable.
Just so there's no confusion, that design was never meant to be received as-
"this is what I think pmwiki should lo
Forgeot Eric (2011-09-21 22:08):
> > http://paulgiacherio.kodingen.com/pmwiki/pmwiki-2.2.30/pmwiki.php?n=PmWiki.DocumentationIndex
>
> it just looks simple and gorgeous at the same time. I think something like
> that (or even this one) could be a good candidate for the default skin on
> pmwiki.o
> Paul Giacherio wrote:
>
>>The .vspace function can be eliminated if we include a proper css reset.
>>This includes a simple reset with and no .vspace. It needs fine tuning
>> but it handles most elements pretty well.
What does "proper css reset" mean, please?
>>
>>http://paulgiacherio.kodingen.
This history big button, next to edit button, is (in my opinion) a
good way to show possible users how a page is done, to enlighten the
fact such a page is a result of x revisions and to appeal the click. I
like that.
(edit button should then become view button when in edit mode, if
someone knows h
--- On Wed, 9/21/11, DaveG wrote:
> I also like the modernish Edit/History buttons. Very much
> in the feel of
I have to disagree about this. I don't like buttons
that simply follow links, which is what those do.
Perhaps I could think of "Edit" as an action, but
"History"?
-Martin
___
On 9/21/2011 5:08 PM, Forgeot Eric wrote:
http://paulgiacherio.kodingen.com/pmwiki/pmwiki-2.2.30/pmwiki.php?n=PmWiki.DocumentationIndex
it just looks simple and gorgeous at the same time. I think something like that
(or even this one) could be a good candidate for the default skin on pmwiki.
> http://paulgiacherio.kodingen.com/pmwiki/pmwiki-2.2.30/pmwiki.php?n=PmWiki.DocumentationIndex
it just looks simple and gorgeous at the same time. I think something like that
(or even this one) could be a good candidate for the default skin on pmwiki.org
What I like on this one:
- the content i
It does need tweaking, but that sandbox page looks like a pretty good
starting point to me.
Regarding the 'List Heading' and the following list- I might take issue with
the desired outcome. The desire to couple a heading to a list could
(should?) be handled with a unique style when needed. If tha
Oliver Betz wrote:
[...]
>Patrick
of course, I didn't want to sign this mail with Patrick's name. It was
a reformatting error, and the posting wasn't ready to send...
Oliver
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud
Paul Giacherio wrote:
>The .vspace function can be eliminated if we include a proper css reset.
>This includes a simple reset with and no .vspace. It needs fine tuning but
>it handles most elements pretty well.
>
>http://paulgiacherio.kodingen.com/pmwiki/pmwiki-2.2.30/pmwiki.php?n=PmWiki.Documenta
The .vspace function can be eliminated if we include a proper css reset.
This includes a simple reset with and no .vspace. It needs fine tuning but
it handles most elements pretty well.
http://paulgiacherio.kodingen.com/pmwiki/pmwiki-2.2.30/pmwiki.php?n=PmWiki.DocumentationIndex
On Wed, Sep 21
Echo John on the div.vspace. I do like the .vspace, but additional divs seem
a bit overkill.
On Wed, Sep 21, 2011 at 11:03 AM, John Rankin wrote:
>
> > On 9/20/11, Petko Yotov <5...@5ko.fr> wrote:
> >> On Wednesday 21 September 2011 00:40:16, Carlos AB wrote :
> [snip]
>
> > Good points.
>
> Agre
> On 9/20/11, Petko Yotov <5...@5ko.fr> wrote:
>> On Wednesday 21 September 2011 00:40:16, Carlos AB wrote :
[snip]
> Good points.
Agreed. There appears to be a good convergence of views on the
requirements for a new default skin, although there will no doubt be
devils in the detail.
This is no
On 9/20/11, Petko Yotov <5...@5ko.fr> wrote:
> On Wednesday 21 September 2011 00:40:16, Carlos AB wrote :
>> Or perhaps just simply a link from to the sidebar page.
>
> Or to a larger page like a site map.
That too.
>> The idea of not having a sidebar displayed togheter with the current
>> pag
On Wednesday 21 September 2011 00:40:16, Carlos AB wrote :
> Or perhaps just simply a link from to the sidebar page.
Or to a larger page like a site map.
> The idea of not having a sidebar displayed togheter with the current
> page, can look simple, attractive, functional and add the possibilit
The sailing site is here:
http://zenzero.marex-commodities.fr/
On Wednesday 21 September 2011 00:40:16, Carlos AB wrote :
> There is one site, that I couldn't find right now, that Petko made and
> related to sailing that could be used as a really good example for
> that.
>
> The front page is v
>> For a mobile device I would probably prefer a different menu, that is a
>> wiki
>> page other than Site.SideBar, with less selected links, eg. a topbar in a
>> single line which needs much less screen area than a full sidebar. If more
>>
>> links are required, they could be placed at the bottom
Petko Yotov (2011-09-20 16:07):
> On Tuesday 20 September 2011 13:09:26, rogu...@googlemail.com wrote :
> > I'm not browsing with mobile devices, but I am not against supporting
> > them. Are you thinking about a special skin for very small screens, or one
> > skin that is good enough for both use
On Tuesday 20 September 2011 13:09:26, rogu...@googlemail.com wrote :
> I'm not browsing with mobile devices, but I am not against supporting
> them. Are you thinking about a special skin for very small screens, or one
> skin that is good enough for both use cases?
I'm not sure the same page could
Hans (2011-09-19 09:22):
> Monday, September 19, 2011, 12:57:26 AM, Rogutės Sparnuotos wrote:
>
> > 1. Homepage for Symfony 1: http://www.symfony-project.org/
> >(a bit like PmWiki?).
>
> > 2. Homepage for symfony 2: http://symfony.com/
> >(did I just visit wordpress.org?).
>
> > 1. is n
Another approach would be to use CSS media width rules. These work quite
well in current phones and tablets.
http://mislav.uniqpath.com/2010/04/targeted-css/
On Tue, Sep 20, 2011 at 10:37 AM, Forgeot Eric wrote:
> > Anyone here who would like the PmWiki skin to support mobile devices
> > as wel
> Anyone here who would like the PmWiki skin to support mobile devices
> as well as desktop screens?
I think the best is to fallback to another skin, with this convenient cookbook:
http://www.pmwiki.org/wiki/Cookbook/DetectMobile
even for skin using non fixed width, it's generally not usable on
Le 19/09/2011 10:22, Hans a écrit :
Anyone here who would like the PmWiki skin to support mobile devices
as well as desktop screens?
sure!
jdd
--
http://www.dodin.net
http://www.youtube.com/user/jdddodinorg
http://jdd.blip.tv/
___
pmwiki-users ma
Monday, September 19, 2011, 12:57:26 AM, Rogutės Sparnuotos wrote:
> 1. Homepage for Symfony 1: http://www.symfony-project.org/
>(a bit like PmWiki?).
> 2. Homepage for symfony 2: http://symfony.com/
>(did I just visit wordpress.org?).
> 1. is not perfect, but 2. is everywhere nowadays..
On 9/18/2011 7:57 PM, Rogutės Sparnuotos wrote:
ki...@kirpi.it (2011-09-13 00:48):
I'm not sure Pmwiki would/should/could enter the race with things like
Wordpress (I like Textpattern a lot more) or any other CMS up to
TYPO3.
<..>
Do others really like the presentation trend of textpattern.c
On 9/18/2011 7:17 PM, Rogutės Sparnuotos wrote:
Though I think that using the same skin for the home page and
installations is a good thing: less to maintain; stays familiar to
newcomers after installation. If pmwiki.org adopts a skin too complex for
distribution, I think that the two skins sho
ki...@kirpi.it (2011-09-13 00:48):
> I'm not sure Pmwiki would/should/could enter the race with things like
> Wordpress (I like Textpattern a lot more) or any other CMS up to
> TYPO3.
<..>
Do others really like the presentation trend of textpattern.com,
wordpress.org, contao.org? This trend:
1. H
Agreed.
On Monday 19 September 2011 01:17:53, Rogutės Sparnuotos wrote :
> using the same skin for the home page and
> installations is a good thing: less to maintain; stays familiar to
> newcomers after installation. If pmwiki.org adopts a skin too complex for
> distribution, I think that the two
Petko Yotov (2011-09-18 20:55):
> On Sunday 18 September 2011 13:18:58, Rogutės Sparnuotos wrote :
> > The wordpress.org and textpattern.com examples others posted are too
> > loaded for me.
>
> These are sources for ideas more for the pmwiki.org home page than for a new
> default skin in the dis
Make that a width of 35em. My error.
On 19/09/11 10:34 AM, John Rankin wrote:
On 19/09/11 8:11 AM, Carlos AB wrote:
You did put it all together nicely, but a little bit of care with the
size and proportions would make it look better.
In particular, the body text would be more readable if the wi
On 19/09/11 8:11 AM, Carlos AB wrote:
You did put it all together nicely, but a little bit of care with the
size and proportions would make it look better.
In particular, the body text would be more readable if the width were
narrower.
To achieve an average of 60-70 characters per line of text,
On 9/18/11, Carlos AB wrote:
> On 9/17/11, V.Krishn wrote:
>> There is a much less used feature that allows switching of stylesheet
>> without
>> using javascript.
>> Skin providing "alternate stylesheet" like
>> 1. High contrast
>> 2. Low contrast
>> 3. 16 color
>> 4. High color
>> ..etc.. can h
On 9/17/11, V.Krishn wrote:
> There is a much less used feature that allows switching of stylesheet
> without
> using javascript.
> Skin providing "alternate stylesheet" like
> 1. High contrast
> 2. Low contrast
> 3. 16 color
> 4. High color
> ..etc.. can help, including adaptiblity to low end dev
I left the mock-up there so people could add or modify the skin idea
more easily, before it is finally "put on paper".
Change the size and proportions, decide to use the search as an action
on the action bar or put the form somewhere on the side bar and other
changes people may find significant.
On Sunday 18 September 2011 13:18:58, Rogutės Sparnuotos wrote :
> The wordpress.org and textpattern.com examples others posted are too
> loaded for me.
These are sources for ideas more for the pmwiki.org home page than for a new
default skin in the distribution.
We want a simple, minimal skin
So easily forgotten, and all too seldom used!
On 2011-09-18 1:20 am, V.Krishn wrote:
On Sunday, September 18, 2011 03:19:43 AM Carlos AB wrote:
I agree, even though I have never worked with people with such
disabilities, It is good to know that they found no problems understanding
how PmWiki di
I think a new skin development should address the fact that more and
more users access web pages on small displays, on mobile devices, on
small phone screens, tablets and wide screen monitors.
It would be nice if a skin could accommodate all of these hugely
different screen sizes, and not burden t
Carlos AB (2011-09-13 22:04):
> Hi Forgeot, List,
>
> I have created a group Called "NewSkinIdeas" and posted an initial idea there
> in
>
> http://www.pmwiki.org/wiki/NewSkinIdeas/CarlosAB
>
> Feel free to comment and post new ideas.
I found the minimal design of your mock-ups attractive and
On Sat, Sep 17, 2011 at 5:20 PM, V.Krishn wrote:
> On Sunday, September 18, 2011 03:19:43 AM Carlos AB wrote:
>> I agree, even though I have never worked with people with such
>> disabilities, It is good to know that they found no problems understanding
>> how PmWiki differentiates one type of lin
On Saturday 17 September 2011 23:49:43, Carlos AB wrote :
> if skin writers should use
> the prefs page/mechanism for skin preferences and even to choose a skin.
>
> That could be used for a lot of things like defining a preference for
> fonts (size, family, weight), styling option for links, etc
On Sunday, September 18, 2011 03:19:43 AM Carlos AB wrote:
> I agree, even though I have never worked with people with such
> disabilities, It is good to know that they found no problems understanding
> how PmWiki differentiates one type of link from the other, and also that
> people writing skins
I agree, even though I have never worked with people with such disabilities,
It is good to know that they found no problems understanding how PmWiki
differentiates one type of link from the other, and also that people writing
skins for PmWiki have to think about a lot when trying to make a new move
> I'm sorry, it's not dotted, it's a dashed underline/border-bottom .
>
> On 9/15/11, Carlos AB wrote:
>> [...]
>>
>> Does the PmWiki community wants to follow creole rules by the dot, or
>> perhaps, by the underline? :-)
And of course PmWiki already uses a dotted (not dashed) border bottom for
Le 16/09/2011 00:27, tamouse mailing lists a écrit :
set of presentation aspects and expect one size will fit all. I'm
trying to develop a more flexible means of theming/skinning/what have
you that will allow the user to take control if they need to in a more
easily handled fashion.
fine. May
I'm sorry, it's not dotted, it's a dashed underline/border-bottom .
On 9/15/11, Carlos AB wrote:
> Wiki creole says that we should use a dotted underline to flag a link
> to a non existent page and I believe it is a dotted border-bottom.
>
> Should we respect that since PmWiki supports creole and
Wiki creole says that we should use a dotted underline to flag a link
to a non existent page and I believe it is a dotted border-bottom.
Should we respect that since PmWiki supports creole and I believe that
this particular rule of creole was done that way to also give support
for people that are
I'm currently working with someone who has two different kinds of
colourblindness as well as some other vision problems. As far as it
goes, she is able to read and interpret the current pmwiki front page
very well. She has a really hard time with a lot of sites with modern
designs. It seems as thou
"John Rankin" wrote:
[...]
>What is your view of sites where the link border-bottom is dotted? It
o.k. for me
>makes links more visible, but is less intrusive than a solid rule. The
>dotted rule can turn solid on mouseover, of course.
>>
>> BTW: What's the benefit of "border-bottom" (besides di
I'd also want to point out that pmwiki still uses fixed dimensions in
its skin. I'd recommend moving away from anything fixed (px, pt) to
relative dimensions (rem, em, %).
And yes, a max-width column, not fixed.
The three Rs of web design: relative, relative, relative.
On 2011-09-15 12:34 pm,
> I agree about Verdana because it has the "wrong" size:
> http://sbpoley.home.xs4all.nl/webmatters/verdana.html
Yes! As an older reader, I tend to assume that any web site using Verdana
doesn't want me as a visitor. I know I can make the text bigger, but why
should I?
>
>> I'd suggest to use a s
>
>>horizontally, so long lines don't cause an overflow; avoid underline for
>>links (use border-bottom on hover instead, if at all); spruce up the
>
> I want links to be underlined _and_ coloured, I don not want to guess
> what could be a link.
Yes, unless there is a strong contrast between the
Oliver Betz (2011-09-14 09:31):
> To Rogutės Sparnuotos: I _definitely_ wouldn't use web fonts for
> PmWiki!
I wrote "<..> and a comment could point to pmwiki.org/wiki/Cookbook/Fonts,
which could point to google.com/webfonts", which could be translated to
something like this in the default skin:
Forgeot Eric wrote:
[...]
> Again, I don't necessary thing everything should be redesigned, but a
> few adjustement could help to look better. The geany website (powered
> by PmWiki) is a good example of an attractive design, yet quite close
> to the original : http://geany.org/ . There are still
Forgeot Eric (2011-09-13 22:15):
<...>
> Again, I don't necessary thing everything should be redesigned, but a few
> adjustement could help to look better. The geany website (powered by PmWiki)
> is a good example of an attractive design, yet quite close to the original :
> http://geany.org/ . T
Hi Forgeot, List,
I have created a group Called "NewSkinIdeas" and posted an initial idea there in
http://www.pmwiki.org/wiki/NewSkinIdeas/CarlosAB
Feel free to comment and post new ideas.
CarlosAB
On 9/13/11, Forgeot Eric wrote:
> someone posted (off list):
>
>>Hmm, perhaps you could show wh
Not dumb at all Paul. I was in doubt too on how to name it, but I went
with the name "NewSkinIdeas" for the new group, I believe it is not so
bad and I posted an idea there and also reveled my inspiration for it.
:-)
Take look and write whatever you wanna write on that page/group I have created.
Completely agree, John!
Luigi
On 13/09/2011, John Rankin wrote:
>
>> I'm not sure Pmwiki would/should/could enter the race with things like
>> Wordpress (I like Textpattern a lot more) or any other CMS up to
>> TYPO3.
>> Pmwiki is a wiki, and a file-based one.
>> Which puts its roots into a *ver
someone posted (off list):
>Hmm, perhaps you could show what you'd do differently?
I'm working on something, but I'm not a special talented designer, and I don't
know much about CSS. (I often end up on the same designs)
I'd be happy though to participate to a "contest", a brainstorming or a ne
Chris Cox wrote:
[...]
>As an example... the logo... it should be an included page. In fact it could
>be
>a multi-fall back included page... so that it could change based on context
>even. And the same could be done for page banners and the like. All of this
>is
Can you suggest a simple
"ki...@kirpi.it" wrote:
>I'm far from a tech guy, but having the standard skin with a fixed
>width (which seems to be a great request by many) should be not much
>more than enclosing it all into a
fixed width is evil IMNSHO. Consider small devices!
Readers don't want _fixed_ width, but those bro
"John Rankin" wrote:
[...]
>Before changing the default skin, it helps to know what the skin design
>goals are. Otherwise, it's hard to choose between reasonable design
very true.
>alternatives. Drawing on this and earlier posts, as a starter for 10:
>
>- as the site is text-intensive, adopt go
On Monday 12 September 2011 22:19:04, Forgeot Eric wrote :
> The drupal website is using blue link, but with a different color than the
> blue which was common during the geocities era: the design is classy and
> elegant, yet it's simple
For me the Geocities era was more about blinking and scrolli
> I'm not sure Pmwiki would/should/could enter the race with things like
> Wordpress (I like Textpattern a lot more) or any other CMS up to
> TYPO3.
> Pmwiki is a wiki, and a file-based one.
> Which puts its roots into a *very* different ground.
> No matter how powerful or useful pmwiki may be, fi
On 9/12/2011 7:21 AM, Laatz, Erek wrote:
As PM wrote, the actual default skin is a good starting point for
personal customizations. But what about an image gallery with some
screenshots of the several skins offered in the skin section of the
pmwiki-site. The images could be linked to the skin s
I'm not sure Pmwiki would/should/could enter the race with things like
Wordpress (I like Textpattern a lot more) or any other CMS up to
TYPO3.
Pmwiki is a wiki, and a file-based one.
Which puts its roots into a *very* different ground.
No matter how powerful or useful pmwiki may be, first-time visi
I believe It is time for a change too.
Why not create a new group on PmWiki and publish there any ideas we
may have, write links, upload photos, create a example designs with
wiki markup and vote for the best ideas.
Then we can get enough references to think with and come up with the best idea.
I'm far from a tech guy, but having the standard skin with a fixed
width (which seems to be a great request by many) should be not much
more than enclosing it all into a
(sort of)
or a similar thing with tables.
(Actually, it needs a slightly better effort, but my example still holds true)
I mean:
On 13/09/11 8:19 AM, Forgeot Eric wrote:
The drupal website is using blue link, but with a different color than the blue
which was common during the geocities era: the design is classy and elegant,
yet it's simple:
http://drupal.org/documentation/customization/tutorials/beginners-cookbook
Inte
The drupal website is using blue link, but with a different color than the blue
which was common during the geocities era: the design is classy and elegant,
yet it's simple:
http://drupal.org/documentation/customization/tutorials/beginners-cookbook
The same goes for this localized version: htt
Cant speak for the pmwiki site...but tables do allow for some structure inside
of text based browsers... If that's interesting anymore.
- Reply message -
From: "Kenneth Forsbäck"
To:
Subject: [pmwiki-users] it's time to change pmwiki default skin!
Date: Mon,
Dear all,
another proposal:
As PM wrote, the actual default skin is a good starting point for
personal customizations. But what about an image gallery with some
screenshots of the several skins offered in the skin section of the
pmwiki-site. The images could be linked to the skin section, where al
One of the reasons I adopted pmwiki was its easy of use.
Its default skin is a very good starting point, which:
- allows to understand how the whole thing works (not bad as you are
starting over)
- is very useable (despite the narrow column fashion of today) and
blue/underlined links are still a go
> On Sun, Sep 11, 2011 at 08:35:59PM +0100, Forgeot Eric wrote:
>> why not proposing a new default pmwiki skin?
>>
>> - for the default installation
>> - and for the http://www.pmwiki.org website?
>>
>> The current one is not attractive at all (blue, underlined links), it
>> looks like it was desi
I like blue, underlined links, it makes all links clear and easy to
spot. That's the whole point of an effective design: simplicity,
clarity, usability.
The only gripe I have with the pmwiki appearance is the layout. Of
course, there is nothing that says you couldn't still include the old
ski
On Sun, Sep 11, 2011 at 08:35:59PM +0100, Forgeot Eric wrote:
> Hello,
>
> why not proposing a new default pmwiki skin?
>
> - for the default installation
> - and for the http://www.pmwiki.org website?
>
> The current one is not attractive at all (blue, underlined links), it
> looks like it was
On 09/11/2011 02:35 PM, Forgeot Eric wrote:
Hello,
why not proposing a new default pmwiki skin?
- for the default installation
- and for the http://www.pmwiki.org website?
The current one is not attractive at all (blue, underlined links), it looks
like it was designed in 1992, and therefore,
> why not triad?
While slightly better, it's still using the old fashionned blue links, and the
interface is quite complicated with all the options (for changing colors and
such), 3 columns etc.
Somethink like http://www.pmwiki.org/wiki/PmWiki/Skins?skin=beeblebrox-gila2 a
sober. I was more thi
Le 11/09/2011 22:14, John Rankin a écrit :
why not proposing a new default pmwiki skin?
why not triad?
jdd
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
> why not proposing a new default pmwiki skin?
I support this proposal and agree with the reasons.
>
> I think a skin like this one could be great:
> http://www.pmwiki.org/wiki/Cookbook/AlalikeSkin
This is a good starting point, but does not work very well in Safari 5.
JR
--
John Rankin
_
Hello,
why not proposing a new default pmwiki skin?
- for the default installation
- and for the http://www.pmwiki.org website?
The current one is not attractive at all (blue, underlined links), it looks
like it was designed in 1992, and therefore, it give the impression PmWiki is
backward tec
100 matches
Mail list logo
