This all sounds really good :o)
Yes, I'd prefer a group construct for the alternate stylesheet definitions
and a title would make sense, too.
Presumably this all gets loaded along with the other stylesheets in
PageUtilities.InsertStylesheetReferences?
What's the UI going to look like for this? Will it fit into one of the
existing sidebars? If so, how is the necessary code inserted to make it
happen? i.e. is it part of the _NormalBorders topic that can be edited to
remove it?
On 8/15/07, Nathan Jones <[EMAIL PROTECTED]> wrote:
>
> On 8/15/07, Derek Lakin <[EMAIL PROTECTED]> wrote:
> > Ideally, if we're going to implement this at all, then I'd like to see
> the
> > same level of style switching support in IE as is available in FF, one
> way
> > or another, but I (personally) don't have a problem with the feature
> being
> > FF-specific.
> >
>
> We would. Actually, even FF falls down due to the fact that in the
> default implementation, it makes the user re-select the alternates
> every time. Silly, IMO, but there it is. The solution that I've found
> would use javascript to do the work and not the browser, so it should
> work in both environments. The implementation that I found does use
> cookies, though... I don't know if we have a stance for/against
> cookies. Obviously, if the user has cookies disabled, then this
> feature wouldn't work.
>
>
> > Presumably the OverrideStylesheet config option still works alongside
> your
> > AlternateStylesheet option? Additionally, I'd go with
> AlternateStyleSheets
> > if you can specify more than one.
> >
>
> Yes, OverrideStylesheet works just as it does now. The use of the
> StyleSheet property in the Topic still works as well. To be very
> explicit, this is what gets spat out:
>
> <link href=".../wiki.css" rel="stylesheet" />
> <link href=".../override.css" rel="stylesheet" title="Basic" />
> <link href=".../alt1.css" rel="alternate stylesheet" title="Style 1" />
> <link href=".../another.css" rel="alternate stylesheet" title="Style 2" />
>
> what all this means to the browsers is:
> wiki.css is always used as the base style, the others cascade on top of
> it.
> override.css is the default one the browser will show (plus wiki.css of
> course)
> alt1.css and another.css will show up in FF's View->Page Style menu.
>
> We'd setup some JS somewhere on the site to manage this for all
> browsers (that support, of course.)
>
> I went with AlternateStylesheet cause the xml looks like this:
>
> <OverrideStylesheet>override.css</OverrideStylesheet>
> <AlternateStylesheet>al1.css</AlternateStylesheet>
> <AlternateStylesheet>another.css</AlternateStylesheet>
>
> I can add a grouping construct, (and being able to specify the title
> might be nice too...) These would require creating a new Config class,
> but that's pretty straightforward to do.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Flexwiki-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/flexwiki-users
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Flexwiki-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
