forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thorsten Scherler <>
Subject Re: Pelt Theme Dispatcher Observations
Date Wed, 29 Mar 2006 10:23:16 GMT
El mar, 28-03-2006 a las 21:43 +0800, Gav.... escribió:
> Hi all,
> Thought I would revert back to pelt theme from my pili theme to check
> this is doing. I have a few observations that I wanted to clarify
> creating issues for them and sorting them, maybe they already exist as
> issues but I haven't found them as of yet.
> 1) - menus are not collapsable in IE or Firefox.

In firefox it works for me (tried on site-author and pelt theme) in run
and static. NOTE: the first time you need to click twice.

> 2) - Some images, notably spacer.gif and pdfdoc.gif are being looked
for in
> the /themes/images directory when they actually reside in /skin/images
> directory and so are not being displayed.
> e.g of output source <img alt="spacer"
src="themes/images/spacer.gif" />

No, not for me neither. 
themes/images/spacer.gif is in themes dir (and as well the pdfdoc.gif). 
The skin dir is copied even if not used since

The dispatcher *should not* use the skin dir.

> 3) - Viewing in 800x600 mode on Windows the Search the site will
overlap the
> tabs if there are five or more tabs. [1]

Yes, I can see this on linux as well, can you fill a bug?

> 4) - Not important as such but anyway... Comments in the pelt.fv are
> converted into white space it seems in the code. 

Yeah, somehow in general comments are not copied. Paul Bolger reported a
similar issue

You may want to add your following findings there. ;)

> e.g - 
> <forrest:property name="branding-css-links-input">
>         <css url="common.css" media="screen" rel="alternate
>           theme="common"/>
>         <css url="leather-dev.css" media="screen" rel="alternate
>           theme="common"/>
>         <css url="pelt.screen.css" media="screen" theme="Pelt"/>
>         <!-- You can request request specific css, but beware that you
> to use the *.dispatcher.css extension!!!-->
>         <!-- FIXME: that is not working ATM in forrest for subdir/bla
> more testing -->
>         <!--<css url="#{$getRequest}.dispatcher.css" media="screen"
> theme="Pelt"/>-->
>         <css url="pelt.print.css" media="print"/>
> Converts to :-
> <link href="themes/common.css" media="screen" rel="alternate
> title="common" type="text/css" />
>         <link href="themes/leather-dev.css" media="screen"
> stylesheet" title="common" type="text/css" />
>         <link href="themes/pelt.screen.css" media="screen"
> title="Pelt" type="text/css" />
>         <link href="themes/pelt.print.css" media="print"
> title="pelt.print.css" type="text/css" />
> 5) - Enabling use of the second instance of branding-breadcrumbs
causes an
> extra seemingly unwanted gap between the tabs section and the left
> navigation/second breadcrumbs sections. This breaks up the continuity
> between the tabs and the left navigation, is this by design or a bug?

Can I see an example? I do not understand.

> Note that points 1 and 2 above work fine in a 'Forrest Run' byt when
> statically built and deployed to a remote server is when the problems
> Seem to occur.(?)

Hmm, you mean via forrestbot?

> [1] - For a couple of days, the effects can be seen at
> Note, only a couple of pages are active at the moment.
> Gav...

Thorsten Scherler
COO Spain
Wyona Inc.  -  Open Source Content Management  -  Apache Lenya               

View raw message