You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by David Crossley <cr...@apache.org> on 2005/11/18 02:25:31 UTC
do not switch themes via browser (Was: svn commit: r345206)
Thorsten Scherler wrote:
> ...
> > + <code>'forrest run'</code> and
> > + point your browser to <code>http://localhost:8888/</code> and you will see the default
> > + dispatcher-based site. Use your browser's menu option "View -> Page Style" to switch
> > + themes.
>
> Hmm, why did you add this note?
Want the developers to know immediately that themes can be applied.
The default "pelt" theme looks ghastly at the moment on Mac/Firefox
using unreadable fonts. Anyway, will follow your advice below.
> 1) this option is not in all browser
I thought that developers would figure it out.
> 2) if you use this option the theme switching is not 100% done that is
> the reason why we developed the theme switcher contract.
>
> The user should use the contract to switch themes.
Ah, i didn't know that. So should we not mention
the "theme switching via browser" at all?
Should we actively discourage its use?
-David
Re: views v2 project.theme=common error
Posted by Kevin <fo...@kegcl.demon.co.uk>.
I can answer the first myself :)
On Mon, 2005-11-21 at 22:06 +0000, Kevin wrote:
> I thought I'd start again with v2. I did
>
> forrest seed-v2
>
> forrest.properties:
> project.theme=common
>
> forrest site
> (gave error)
> ....
> X [0] samples/index.html BROKEN:
> ElemTemplateElement error: Found more than one template named: noFt-body
>
> Any ideas on this error?
index.fv uses contracts that aren't defined in common! Sorry as a user
I should know the user supplies this file.
> I just wanted to get to the most simple old leather style view. Then I
> was going to modify my own common.fv and progress from there with
> <forrest:css ... and alternate css.
>
> Any tips on generating indented html from forrest site. Comments from
> contracts are passed through but it would be nice to easily read the
> html.
>
> Kevin
>
>
>
>
>
>
>
views v2 project.theme=common error
Posted by Kevin <fo...@kegcl.demon.co.uk>.
I thought I'd start again with v2. I did
forrest seed-v2
forrest.properties:
project.theme=common
forrest site
(gave error)
....
X [0] samples/index.html BROKEN:
ElemTemplateElement error: Found more than one template named: noFt-body
Any ideas on this error?
I just wanted to get to the most simple old leather style view. Then I
was going to modify my own common.fv and progress from there with
<forrest:css ... and alternate css.
Any tips on generating indented html from forrest site. Comments from
contracts are passed through but it would be nice to easily read the
html.
Kevin
Re: do not switch themes via browser (Was: svn commit: r345206)
Posted by Kevin <fo...@kegcl.demon.co.uk>.
On Fri, 2005-11-18 at 12:31 +0100, Thorsten Scherler wrote:
> El vie, 18-11-2005 a las 12:56 +1100, David Crossley escribió:
> > David Crossley wrote:
> > > Thorsten Scherler wrote:
> > > > ...
> > > > > + <code>'forrest run'</code> and
> > > > > + point your browser to <code>http://localhost:8888/</code> and you will see the default
> > > > > + dispatcher-based site. Use your browser's menu option "View -> Page Style" to switch
> > > > > + themes.
> > > >
> > > > Hmm, why did you add this note?
> > >
> > > Want the developers to know immediately that themes can be applied.
> > > The default "pelt" theme looks ghastly at the moment on Mac/Firefox
> > > using unreadable fonts. Anyway, will follow your advice below.
> >
> > Oh, and the other reason was stupidity. :-)
> > I completely forgot to look at the Samples
> > to see the theme switching in action.
> >
>
> jeje ;-)
>
> Yeah it is in the samples, gush, sorry I should have told you in the
> first place. To point to this sample contract would be the way I guess.
> I would not mention the browser for now.
>
> Kevin came up with a way how to have both theme switching with script
> and browser. Kevin do you have a patch for it?
No progress sorry, been away a while.
My previous observations about v2 theme switching:
1) Moz switching with cssStyleSwitcher.js - OK
2) Moz switching with View->PageStyle menu - No
3) IE6 switching with cssStyleSwitcher.js - No
No, means the page loses it's css. Like doing a Moz menu View->PageStyle
= "No Style". The same happens for me in IE6.
IMO if the cssStyleSwitcher.js can emulate Moz View->PageStyle menu
then IE would work in the same way. If I have some time I'll look at
this again.
ATM my example does not use inline css (branding-theme-switcher.ft)
and the simpler leather css (no corner images). Just trying to simplify
things in my mind and use <forrest:css ... for alternate css color
themes.
Kevin
> salu2
>
> > -David
> >
> > > > 1) this option is not in all browser
> > >
> > > I thought that developers would figure it out.
> > >
> > > > 2) if you use this option the theme switching is not 100% done that is
> > > > the reason why we developed the theme switcher contract.
> > > >
> > > > The user should use the contract to switch themes.
> > >
> > > Ah, i didn't know that. So should we not mention
> > > the "theme switching via browser" at all?
> > > Should we actively discourage its use?
> > >
> > > -David
Re: do not switch themes via browser (Was: svn commit: r345206)
Posted by Thorsten Scherler <th...@apache.org>.
El vie, 18-11-2005 a las 12:56 +1100, David Crossley escribió:
> David Crossley wrote:
> > Thorsten Scherler wrote:
> > > ...
> > > > + <code>'forrest run'</code> and
> > > > + point your browser to <code>http://localhost:8888/</code> and you will see the default
> > > > + dispatcher-based site. Use your browser's menu option "View -> Page Style" to switch
> > > > + themes.
> > >
> > > Hmm, why did you add this note?
> >
> > Want the developers to know immediately that themes can be applied.
> > The default "pelt" theme looks ghastly at the moment on Mac/Firefox
> > using unreadable fonts. Anyway, will follow your advice below.
>
> Oh, and the other reason was stupidity. :-)
> I completely forgot to look at the Samples
> to see the theme switching in action.
>
jeje ;-)
Yeah it is in the samples, gush, sorry I should have told you in the
first place. To point to this sample contract would be the way I guess.
I would not mention the browser for now.
Kevin came up with a way how to have both theme switching with script
and browser. Kevin do you have a patch for it?
salu2
> -David
>
> > > 1) this option is not in all browser
> >
> > I thought that developers would figure it out.
> >
> > > 2) if you use this option the theme switching is not 100% done that is
> > > the reason why we developed the theme switcher contract.
> > >
> > > The user should use the contract to switch themes.
> >
> > Ah, i didn't know that. So should we not mention
> > the "theme switching via browser" at all?
> > Should we actively discourage its use?
> >
> > -David
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: do not switch themes via browser (Was: svn commit: r345206)
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> Thorsten Scherler wrote:
> > ...
> > > + <code>'forrest run'</code> and
> > > + point your browser to <code>http://localhost:8888/</code> and you will see the default
> > > + dispatcher-based site. Use your browser's menu option "View -> Page Style" to switch
> > > + themes.
> >
> > Hmm, why did you add this note?
>
> Want the developers to know immediately that themes can be applied.
> The default "pelt" theme looks ghastly at the moment on Mac/Firefox
> using unreadable fonts. Anyway, will follow your advice below.
Oh, and the other reason was stupidity. :-)
I completely forgot to look at the Samples
to see the theme switching in action.
-David
> > 1) this option is not in all browser
>
> I thought that developers would figure it out.
>
> > 2) if you use this option the theme switching is not 100% done that is
> > the reason why we developed the theme switcher contract.
> >
> > The user should use the contract to switch themes.
>
> Ah, i didn't know that. So should we not mention
> the "theme switching via browser" at all?
> Should we actively discourage its use?
>
> -David