Re: One more Forrest example site

Diwaker Gupta wrote: > Rasik Pandey wrote: > > > DisCountDracula -- Website containing > > Bargains / Deals on various products and services > > Added. You added it to source, but don't forget that it needs to be generated and published too. See etc/publishing_o

Re: [RT] Dynamic Content in Forrest

Ross Gardler wrote: > Tim Williams wrote: > >I'm wondering how folks handle dynamic content within their Forrest > >sites. > > Forrest has a stated goal to provide static representations of sites > where possible. We have always said that Forrest is intended to be either static or dynamic. See

Re: One more Forrest example site

> Posts on the user list are fine. One of the devs will get around to it> eventually :-):)> > DisCountDracula -- Website containing > > Bargains / Deals on various products and services> > Added.Thanks.-- Regards,Ruswww.discountdracula.com"Your Bargain BloodSucka: S

Re: Wizard to create a New Site

On Wednesday 27 July 2005 5:22 pm, Anil Ramnanan wrote: > I am moving on to the Wizard to create a new Forrest Site. Currently, > the wizard does the following: I think we should expedite the discussion on the new Forrest configuration system, so that Anil can put in efforts once into the right p

Re: web conference for views workshop?

David Crossley wrote: > We will be able to create a sound recording and make > that available for later download. Let us hope > that we can all speak clearly. There is now a separate SVN repository at http://svn.apache.org/repos/asf/forrest/events to hold such stuff. The sound files are there now

Wizard to create a New Site

I am moving on to the Wizard to create a new Forrest Site. Currently, the wizard does the following: - Enter the name of the site - Choose if you want forrest:views activated - Choose the plugins that you will be using for that site What else is needed when setting up a new site ? I was thinkin

Re: [Views] use twice a contract drive two include twice the header...

On Wed, 2005-07-27 at 19:47 +0200, Thorsten Scherler wrote: > On Wed, 2005-07-27 at 18:17 +0200, Cyriaque Dupoirieux wrote: > > Just a remark, > > > > When you use twice the same contract in a page, the *.js are include > > twice in the header. > > Only the includes call or the whole head te

additional resources for plugins (was Re: problem)

HANAX wrote: The second thing: I have external grammar in .jsgf file. I need to use it in .xsl. So I ask which path I should use and how to make that the .jsgf file will be copied to buided site when plugins takes its job. Example: > So after site builging I need to have simple.jsgf in Gra

Debugging transformations in Forrest (was Re: problem)

HANAX wrote: My sitemap seems ok: http://apache.org/cocoon/sitemap/1.0";> line from forrest.properties for loading plugin seems ok too project.required.plugins=org.apache.forrest.plugin.output.pdf,org.apache.forrest.plugin.output.v

RE: Re: problem

My sitemap seems ok: http://apache.org/cocoon/sitemap/1.0";> line from forrest.properties for loading plugin seems ok too project.required.plugins=org.apache.forrest.plugin.output.pdf,org.apache.forrest.plugin.output.voice And I got

Re: problem

HANAX wrote: Yesterday I made some progress and I've got fine results with my plugin But this morning I've turn-on computer and for some reason scandisk started. Then I found that my plugin don't work. My .xsl file remains was unchanged as well as output.xmap. But instead of vociexml output I've g

problem

Hi, Yesterday I made some progress and I've got fine results with my plugin But this morning I've turn-on computer and for some reason scandisk started. Then I found that my plugin don't work. My .xsl file remains was unchanged as well as output.xmap. But instead of vociexml output I've got pla

Re: [Views] use twice a contract drive two include twice the header...

On Wed, 2005-07-27 at 18:17 +0200, Cyriaque Dupoirieux wrote: > Just a remark, > > When you use twice the same contract in a page, the *.js are include > twice in the header. Only the includes call or the whole head template? > ( It also works with *.css includes :-) ) > You mean if y

[Views] use twice a contract drive two include twice the header...

Just a remark, When you use twice the same contract in a page, the *.js are include twice in the header. ( It also works with *.css includes :-) ) -- Cordialement, Cyriaque,

Re: forrest:hooks configurations examples (was [Views] strange behaviour)

Nicola Ken Barozzi wrote: Cyriaque Dupoirieux wrote: ... I think that's because we talked about type="span" and type="div" which are well known for XHTML writer. We might have talked about type="inline" and type="block" but it would have been a little bit oriented :-) . Which actually is in

Re: forrest:hooks configurations examples (was [Views] strange behaviour)

Cyriaque Dupoirieux wrote: ... > I think that's because we talked about type="span" and type="div" which > are well known for XHTML writer. > We might have talked about type="inline" and type="block" but it would > have been a little bit oriented :-) . Which actually is interesting. > Maybe we s

Re: forrest:hooks configurations examples (was [Views] strange behaviour)

On Wed, 2005-07-27 at 14:06 +0200, Cyriaque Dupoirieux wrote: > I think that's because we talked about type="span" and type="div" which > are well known for XHTML writer. > We might have talked about type="inline" and type="block" but it would > have been a little bit oriented :-) . Actually I

[jira] Commented: (FOR-585) Provide full list of plugins via "Activate Plugins" list

[ http://issues.apache.org/jira/browse/FOR-585?page=comments#action_12316919 ] Ross Gardler commented on FOR-585: -- I've applied patch ActivatePluginPatch270705.diff but I'm not closing this issue as the current solution causes a maintenance problem since a

[jira] Updated: (FOR-586) Drag and Drop in site editor should provide a meaningful node name

[ http://issues.apache.org/jira/browse/FOR-586?page=all ] Ross Gardler updated FOR-586: - Priority: Minor (was: Major) I've applied the patch as it is an improvement over previous behaviour. However, we should really extract the title of the document from t

Re: locationmap editor (was Re: Wizard for Views)

Anil Ramnanan wrote: Ross Gardler wrote: That's your call. I've not looked at Lepido in detail so can't really advise other than to say we should consider the Lepido solution (note that if we leverage the Lepido plugin we get all their other editors for free as well). There's still plenty t

Re: forrest:hooks configurations examples (was [Views] strange behaviour)

Ross Gardler a écrit : Nicola Ken Barozzi wrote: Thorsten Scherler wrote: ... Summary: A forrest:hook is an abstract layer for *any* "graphical helper container" (not only html), like an "interface". Each format can implement special matcher and transformer which decide how and whether fo

Re: forrest:hooks configurations examples (was [Views] strange behaviour)

Nicola Ken Barozzi wrote: Thorsten Scherler wrote: ... Summary: A forrest:hook is an abstract layer for *any* "graphical helper container" (not only html), like an "interface". Each format can implement special matcher and transformer which decide how and whether forrest:hooks get transformed

[jira] Updated: (FOR-586) Drag and Drop in site editor should provide a meaningful node name

[ http://issues.apache.org/jira/browse/FOR-586?page=all ] Anil Ramnanan updated FOR-586: -- Attachment: SiteXMLView.diff Instead of NewElement, the element being dreated by the drop process will have the name of the file being dropped. > Drag and Drop in si

Re: locationmap editor (was Re: Wizard for Views)

Ross Gardler wrote: That's your call. I've not looked at Lepido in detail so can't really advise other than to say we should consider the Lepido solution (note that if we leverage the Lepido plugin we get all their other editors for free as well). There's still plenty to finish off in the si

Re: forrest:hooks configurations examples (was [Views] strange behaviour)

Thorsten Scherler wrote: > On Wed, 2005-07-27 at 08:18 +0200, Nicola Ken Barozzi wrote: > >>Thorsten Scherler wrote: >>... >>>Here is a small summary example: >>> >>> >>> >>> >>> >>>will be transformed to: >>> >>> >>> >>> >>> >> >>Again, why cannot we use the second version instead of creating a

Re: forrest:hooks configurations examples (was [Views] strange behaviour)

On Wed, 2005-07-27 at 09:34 +0200, Cyriaque Dupoirieux wrote: > Nicola Ken Barozzi a écrit : ... > > > >Again, why cannot we use the second version instead of creating another > >new language? > > > > > > > I agree with Nicola, the notation becomes a little complicated just to > add a div or a s

Re: forrest:hooks configurations examples (was [Views] strange behaviour)

On Wed, 2005-07-27 at 08:18 +0200, Nicola Ken Barozzi wrote: > Thorsten Scherler wrote: > ... > > > > *or* > > > > will be transformed into > > > > Then why not simply use > > > > > The same is true for @class attribute for forrest:hooks. > > > > *or* > > > > will be transformed into >

Re: forrest:hooks configurations examples (was [Views] strange behaviour)

Nicola Ken Barozzi a écrit : Thorsten Scherler wrote: ... The same is true for @class attribute for forrest:hooks. *or* will be transformed into Then why not simply use: Another feature is that you can as well output span elements for forrest:hooks instead of div elements.