Stylesheet: MyStylesheet.css

with MyStylesheet.css in the FlexWiki root folder (where all other such as
wiki.css reside) doesn't work. Do I have to specify a path? Which path?
/FlexWiki/MyStylesheet.css doesn't work either. By the way, I'm using
FlexWiki 2.0.0.179...

Benno.

> If you want the content from the left on the right and vice versa, can't
> you
> just switch the definitions in _NormalBorders, rather than doing the
> switch
> in CSS?
>
> The Stylesheet page property defines an additional CSS file for that
> topic.
> E.g.
>
> Stylsheet: myNewStyleSheet.css
>
> Derek.
>
> --------------------------------------------------
> From: <[EMAIL PROTECTED]>
> Sent: Wednesday, January 23, 2008 4:34 PM
> To: <flexwiki-users@lists.sourceforge.net>
> Subject: Re: [Flexwiki-users] Separate stylesheets for admin and content?
>
>> Hi Derek,
>>
>> thanks a lot for your answer.
>>
>>> Admin.css is a hangover from before we updated the stylesheet. As you
>>> point
>>> out, I don't think it actually gets used by anything. At this stage, I
>>> don't
>>> think it's possible to explicitly specify a different stylesheet for
>>> the
>>> admin pages without making some code changes. That said, the admin
>>> pages
>>> are
>>> quite simple from a CSS point of view, so it shouldn't be too difficult
>>> to
>>> handle them in your override CSS file.
>>
>> Unfortunately, it is... For example, I exchange LeftBorder and
>> RightBorder
>> so that LeftBorder is on the right side and RightBorder on the left.
>> Sounds weird, but I do lots of javascript manipulations to nested lists
>> in
>> the left
>> sidebar (building up a tree control). This takes some time during which
>> IE
>> stops rendering the rest of the page (regardless wether I start this
>> window.onload or earlier). To enable the user to look at the topic
>> content
>> while the tree is generated, I placed the lists in the RightBorder which
>> comes after TopicBody in the pages' html. Long story, but in short it
>> messes up my admin pages.
>>
>>> You can apply a specific stylesheet (in addition to any overrides or
>>> alternates) to a topic by using the Stylesheet page property. However,
>>> there
>>> doesn't seem to be a way to apply a stylesheet across a namespace,
>>> although
>>> it shouldn't be too onerous to use the Stylesheet page property from
>>> the
>>> _ContentBaseDefinition topic for the namespace if you want to raise a
>>> feature request on the bug tracker [1]
>>
>> How do I use this Stylesheet page property? I wrote
>>
>> Stylesheet: MyStylesheet
>>
>> to a page, but it doesn't have any effect.
>>
>>> --------------------------------------------------
>>> From: <[EMAIL PROTECTED]>
>>> Sent: Wednesday, January 23, 2008 2:16 PM
>>> To: <flexwiki-users@lists.sourceforge.net>
>>> Subject: [Flexwiki-users] Separate stylesheets for admin and content?
>>>
>>>> Hi all,
>>>>
>>>> for my project, I've highly customised stylesheets for a namespace. If
>>>> I
>>>> include it using OverrideStylesheet in flexwiki.config, it gets
>>>> applied
>>>> to
>>>> all pages, including the admin section. Unfortunately, my
>>>> customisations
>>>> mess up the latter considerably so I'm looking for a possibility to
>>>> specify separate stylesheets for single namespaces and for the admin
>>>> pages.
>>>>
>>>> I can define my stylesheet as an alternate stylesheet in
>>>> flexwiki.config,
>>>> but this way the user would have to select my stylesheet in the drop
>>>> down
>>>> box, which is not an option for me.
>>>>
>>>> How can I specify a default stylesheet for a namespace and a separate
>>>> on
>>>> for the admin section?
>>>>
>>>> There is a admin.css in the admin directory, but it doesn't seem to be
>>>> used anywhere... The admin pages just include wiki.css... What's the
>>>> purpose of this  admin.css?
>>>>
>>>> Additional question: Is it possible to specify stylesheets per
>>>> namespace?
>>>> Different namespace, different stylesheet?
>>>>
>>>> Cheers,
>>>>
>>>> Benno.
>>>>
>>>>
>>>> -------------------------------------------------------------------------
>>>> This SF.net email is sponsored by: Microsoft
>>>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>>> _______________________________________________
>>>> Flexwiki-users mailing list
>>>> Flexwiki-users@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/flexwiki-users
>>>
>>>
>>> -------------------------------------------------------------------------
>>> This SF.net email is sponsored by: Microsoft
>>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>> _______________________________________________
>>> Flexwiki-users mailing list
>>> Flexwiki-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/flexwiki-users
>>>
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Flexwiki-users mailing list
>> Flexwiki-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/flexwiki-users
>>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Flexwiki-users mailing list
> Flexwiki-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flexwiki-users
>



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users

Reply via email to