You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by cr...@apache.org on 2005/11/17 09:00:07 UTC
svn commit: r345206 -
/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml
Author: crossley
Date: Wed Nov 16 23:59:59 2005
New Revision: 345206
URL: http://svn.apache.org/viewcvs?rev=345206&view=rev
Log:
Minor clarifications. Remember that this is developer documentation at this stage.
Modified:
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml
Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml?rev=345206&r1=345205&r2=345206&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml Wed Nov 16 23:59:59 2005
@@ -61,51 +61,52 @@
<section id="localBuild">
<title>Build the internal.structurer and the output.themer plugins</title>
<p>
- The first step is to build and deploy the internal.structurer and the output.themer plugins. Change to a terminal window of your choice
- and go (cd) to the trunk version of forrest {forrest-trunk}. Then do an SVN update.
+ The first step is to build and deploy the internal.structurer and the output.themer plugins.
+ </p>
+ <p>
+ Run the script <code>etc/structurer.sh</code> *after* you did an svn update.
</p>
- <source>
-cd {forrest-trunk}
-svn up
-</source>
<p>
- After this deploy both plugins locally.</p>
+ Otherwise build and deploy them manually. Do your usual 'svn update', then ...
+ </p>
+
<source>
cd whiteboard/plugins/org.apache.forrest.plugin.internal.structurer/
-ant local-deploy
+$FORREST_HOME/tools/ant/bin/ant local-deploy
cd ../org.apache.forrest.plugin.output.themer/
-ant local-deploy
+$FORREST_HOME/tools/ant/bin/ant local-deploy
</source>
- <p>
- Alternatively, run the script <code>etc/structurer.sh</code> *after* you did an svn update.
- </p>
</section>
<section id="newSeed">
<title>Seed a new project</title>
- <p> Go to the directory where you want to seed a new project and seed it
- (we recommend the following). </p>
+ <p> Go to the directory where you want to seed a new project and seed it ...
+ </p>
+ <source>cd ~/src/
+mkdir v2
+cd v2/
+forrest seed-v2 </source>
<note>
For the moment we will use a special seed template called seed-v2. We still
- need to fix issues of the dispatcher that it really can replace old
+ need to fix issues of the dispatcher, so that it really can replace old
fashion skins. Like performance, standalone contracts, other testing output/input formats - using POJO based
processing will help solving this. All this will ATM happen in the v2 seed-target till the dispatcher will
- be realesed to the stable plugins. So make regular updates of your forrest-trunk to keep track.
+ be released to the stable plugins. So make regular updates of your forrest-trunk to keep track.
</note>
<warning>
The way we develop contracts will/may change with introduction of java-based processing
(for certain parts) rather then xsl. Please keep this in mind
and help updating the documentation by sending patches. TIA. ;-)
</warning>
- <source>cd ~/src/
-mkdir v2
-cd v2/
-forrest seed-v2 </source>
</section>
<section id="forrestProperties">
- <title>Modifying forrest.properties (HEADSUP: if you are *not* using the seed-v2 target nor v2/)</title>
+ <title>Modify forrest.properties</title>
+ <p>
+ Make sure to tell forrest to use the dispatcher plugins. Of course, if you are
+ using "seed-v2" then this is already done. If you are converting an existing site to use
+ dispatcher, then do this.
+ </p>
<p>
- Tell forrest that we are using the dispatcher plugins. Edit
- forrest.properties to add the required plugins:
+ Edit forrest.properties to add the required plugins:
</p>
<source>
project.required.plugins=org.apache.forrest.plugin.output.themer,org.apache.forrest.plugin.internal.structurer
@@ -115,24 +116,24 @@
<title>Test your new "dispatcher" based project</title>
<p>
Now you have finished the preparation and the setup to finally do
+ <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.
</p>
- <source>
-forrest run</source>
- <p>Point your browser to <code>http://localhost:8888/</code> and you will see the default
- dispatcher-based site.</p>
</section>
<section id="availableContracts">
<title>Available contracts</title>
<p>
To start working with the dispatcher, you need to know which contracts you can use.
- If you used the seed-v2 then click on the samples tab. You can find links there which leads to
- the available contracts (same as forrestbar).</p>
+ If you used the seed-v2 then the Samples tab will lead to
+ the available contracts.</p>
<p>
- If you are a mozilla user and have the forrestbar installed, then klick on menu point "Devs"
+ Forrestbar is another way to see available contracts. See the menu point "Devs"
(ls.contracts and/or ls.contracts.project)
</p><p>
- Now point your browser to e.g. <code>http://localhost:8888/ls.contracts.html</code>.
- On this page you will find all contracts that you can use in your project.
+ Now point your browser to e.g. <code>http://localhost:8888/ls.contracts.html</code>
+ ... On this page you will find all contracts that you can use in your project.
</p>
</section>
</steps>
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
do not switch themes via browser (Was: svn commit: r345206)
Posted by David Crossley <cr...@apache.org>.
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: svn commit: r345206 -
/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml
Posted by Thorsten Scherler <th...@apache.org>.
El jue, 17-11-2005 a las 08:00 +0000, crossley@apache.org escribió:
...
> + <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?
1) this option is not in all browser
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.
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)