My apologies, I thought I was looking at the current docs. It does
explain why I couldn't find the reference to setting your own theme
though.
In my mind the dispatcher is so central to Forrest I would expect it
to be in the core docs. I wouldn' t consider running Forrest without
it. I notice a l
On 22/11/06, Cyriaque Dupoirieux <[EMAIL PROTECTED]> wrote:
Paul Bolger a écrit :
> The ODT plugin seems to be working with images now, which is a great
> step forward. Does anyone know what the status is with getting the
> images to then get sent through to a rendered PDF?
>
The ODT plugin seems to be working with images now, which is a great
step forward. Does anyone know what the status is with getting the
images to then get sent through to a rendered PDF?
Just been referring back to the Dispatcher install docs, and it seems
they've gone missing from the menus. Easy enough to find using Google,
but I can't see any way of getting from
http://forrest.apache.org/docs_0_80/index.html
to
http://forrest.apache.org/docs_0_80/howto/howto-dispatcher-insta
Hi all
I'm another lurker, although I read, and occasionally understand, the
dev list. Addi and Gav sum have already said some of this.
Forrest is great for simple website construction - I've used it quite
a bit to knock up 'mocks' - test sites to see how a navigation scheme
works - but doing an
of you on your kids, although I'm not sure about life
being 'about to start' - I can't really remember the first three
months of my daughter's life, a blur of being woken up, vomited on,
etc. I think nature blanks it out to some extent, so you don't avoid
doing it agai
Has anyone had any luck getting the odt plugin to translate graphics
from a source document yet?
> I've no time to look at this right now - rushing out. However, I can
> provide a hint, if you still need help after the weekend I'll look in
> more detail.
It'll probably take me longer than that to try it out...
> > Any clues how I'd fix this?
>
> You need to add the OOo dtd's to the Forrest c
That's ok. The question really for Ross, who put the plugin together.
Better to discuss on list though, as it might help someone else later.
On 14/04/06, Thorsten Scherler <[EMAIL PROTECTED]> wrote:
> El vie, 14-04-2006 a las 13:56 +0930, Paul Bolger escribió:
> > I've
dException:...\{yourFile}.sxw\office.dtd
* (The system cannot find the path specified)
* @throws com.sun.star.io.IOException
*/
Any clues how I'd fix this?
One thing I notice is that OpenOffice needs to be running for the
plugin to work - does it work with OpenOffice 2.0?
Paul Bolger
Yes it's working again now thanks. Forgot about 'build/clean...so not
sure if it was my fault all along. Back to the MS plugin.
On 03/04/06, Thorsten Scherler <[EMAIL PROTECTED]> wrote:
> El dom, 02-04-2006 a las 17:29 +0200, Thorsten Scherler escribió:
> ...
> > I need to commit another new feat
3879328795&w=2
>
> Gav...
>
> > -Original Message-
> > From: Paul Bolger [mailto:[EMAIL PROTECTED]
> > Sent: Sunday, 2 April 2006 11:16 AM
> > To: dev@forrest.apache.org
> > Subject: dispatcher problem
> >
> > I've just done a svn up, and t
I've just done a svn up, and the dispatcher is returning 'Could not
resolve locationmap location'
errors.
I've:
* rebuilt forrest
* redeployed the two plugins
* seeded a new instance
* added
project.required.plugins=org.apache.forrest.plugin.output.pdf,org.apache.forrest.themes.core,org.apache.for
That'd be extremely useful to me Ross. I'm running a small (sub) site
which uses MS Word docs as source. At present - having not worked out
the command line Office conversions, and with Ooo's diminishing
support for the old swx format, I'm stuck with manually converting the
docs into swx. Would a w
take advantage of that.
0\
rler <[EMAIL PROTECTED]> wrote:
> El vie, 17-03-2006 a las 15:26 +1100, David Crossley escribió:
> > At the recent ForrestFriday Paul Bolger wrote:
> > > (09:24:17) pbol: Thorsten - have you given any thought to
> > > native SVG fr
El dom, 12-03-2006 a las 10:54 +0930, Paul Bolger escribió:
> > I'm building a site with Forrest which will be a subsite of a larger,
> > static, site. The main site uses SSI's extensively and I'm trying to
> > emulate the look and feel of the main site
GenericMarkup strips comments
-
Key: FOR-834
URL: http://issues.apache.org/jira/browse/FOR-834
Project: Forrest
Type: Bug
Components: Dispatcher (aka views)
Versions: 0.8-dev
Reporter: paul bolger
Priority: Minor
Yeah, I mean I'm not sure yet. Have to backtrack a bit to check fully
as I used a workaround (did an @import within the stylesheet, thnks
diwaker)
On 14/03/06, Thorsten Scherler <[EMAIL PROTECTED]> wrote:
> El mar, 14-03-2006 a las 22:29 +0930, Paul Bolger escribió:
> >
The reverted version seems to be ok.
I'll speak up if that turns out not to be the case.
On 14/03/06, Thorsten Scherler <[EMAIL PROTECTED]> wrote:
> El mar, 14-03-2006 a las 19:05 +0800, Gav escribió:
> > In pattern2link it says:-
> >
> >
>
> jeje, nice investigation gav. ;)
>
> svn blame p
content-xml-link.ft outputs pdf
---
Key: FOR-830
URL: http://issues.apache.org/jira/browse/FOR-830
Project: Forrest
Type: Bug
Components: Dispatcher (aka views)
Versions: 0.8-dev
Reporter: paul bolger
Priority: Minor
[
http://issues.apache.org/jira/browse/FOR-827?page=comments#action_12370277 ]
paul bolger commented on FOR-827:
-
Code sample
this line in the stylesheet:
background: url(/images/tednoffsfoundation.jpg) top left no-repeat;
is rendered as
background
Thanks Johannes.
By 'header' I meant a graphic such as a company logo or trademark. In
the case of the site I'm working on the organisation uses a particular
graphic at the top of all printed correspondence which doesn't appear
on their website.
Thanks for the pointers.
Pau
I'm building a site with Forrest which will be a subsite of a larger,
static, site. The main site uses SSI's extensively and I'm trying to
emulate the look and feel of the main site in the Forrest site.
My problem is that genericMarkup.ft doesn't seem to like comments,
which means SSI's don't get
Is there a Forrest specific way of adding a custom graphic as the
header for Forrest generated PDFs, or do you have to modify
document2fo.xsl?
: Improvement
Components: Dispatcher (aka views)
Versions: 0.8-dev
Reporter: paul bolger
Priority: Minor
This seems pretty trivial, but it has the potential to confuse users about the
distinction between skins and Dispatcher.
--
This message is automatically generated by JIRA.
-
If
/browse/FOR-828
Project: Forrest
Type: Bug
Components: Dispatcher (aka views)
Versions: 0.8-dev
Reporter: paul bolger
First four lines of Dispatcher rendered page:
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
http://apache.org/forrest/templates/1.0&quo
Ok, found it.
On 10/03/06, Paul Bolger <[EMAIL PROTECTED]> wrote:
> What's the channel name this month?
>
>
> On 10/03/06, Tim Williams <[EMAIL PROTECTED]> wrote:
> > We're about 13 hours out now...
> > --tim
> >
> > On 3/2/06, Tim W
What's the channel name this month?
On 10/03/06, Tim Williams <[EMAIL PROTECTED]> wrote:
> We're about 13 hours out now...
> --tim
>
> On 3/2/06, Tim Williams <[EMAIL PROTECTED]> wrote:
> > Forrest Friday is rapidly approaching, little more than a week away now.
> >
> > http://forrest.apache.org/
Weirdness in CSS after url
--
Key: FOR-827
URL: http://issues.apache.org/jira/browse/FOR-827
Project: Forrest
Type: Bug
Components: Dispatcher (aka views)
Versions: 0.8-dev
Reporter: paul bolger
Priority: Minor
Don&#
> In my view this is a feature and not a 'lack'. Or - to put it
> differently - one of two ways of handling menus. Keeping everything
> open that the user opens is an alternative way of handling menus that
> will soon become a pain because the menu will become quite cluttered.
- But - If you are d
> It would be great if you could provide a patch or this. The advantage is
> that you will not have to keep your OOo plugin in synch with the one we
> release and, of course, we all get the benefit of your work.
I've made a patch, but can't see the option appearing in
forrest.properties in a new
Fix typos in common.fv and pelt.fv
--
Key: FOR-826
URL: http://issues.apache.org/jira/browse/FOR-826
Project: Forrest
Type: Improvement
Components: Dispatcher (aka views)
Versions: 0.8-dev
Reporter: paul bolger
could tell me where the this
part of the output document is being generated.
paul
On 08/03/06, Thorsten Scherler <[EMAIL PROTECTED]> wrote:
> El mié, 08-03-2006 a las 13:09 +0930, Paul Bolger escribió:
> > As mentioned I'm developing a site with Dispatcher.
> >
> Now, back to parameterisation.
>
> In 0.7 it is not easy to parameterise plugins. It is possible, but
> complex and requires modifications to core, which is obviously not a
> good thing for a plugin to do. In 0.8-dev though it is much easier.
>
> Basically, you create a default.plugin.properties.
As mentioned I'm developing a site with Dispatcher.
I don't use Internet Explorer, but unfortunately most of my clients
do. Checking my site in IE revealed a problem: Although Firefox
correctly sets the character encoding to UTF8, as set in the XML
declaration at the head of the doc, IE doesn't see
> > Do you know were I can see site.xml for the Forrest site?
>
> I suggested that earlier in this thread
> $FORREST_HOME/site-author/content/xdocs/site.xml
Thought you were referring to the sample site sorry. Had a slight
detour through 'server error' land, but it seems to be doing what I
need no
> "Information loss" is not very accurate, I should have said something
> like "unpredictable behaviour". Here's just one example of such
> unpredictable behaviour:
>
> Consider a TOC built within OOo. It includes all headings of level 1 or
> 2. If you go from level 1 heading to level 3 heading thi
> Paul i notice that you do not have a @tab attribute
> on the outer "site" element of site.xml
That's getting there - its now displaying the 'old papers' label with
the contents listed, but what I'd like to do is tell it to open the
list of files in that fold, and to be able to add more folds an
> true
Already switched on I'm afraid. I suspect Cyriaque's got the answer to
this one, seems to be the nav guru ;)
Did notice a couple of typos in pelt.fv though. Patch attached (I hope...)
pelt.fv
Description: Binary data
> You have two options right now, create a new plugin as you have done or
> parameterise the existing plugin behaviour. The best way to do it would
> be to parameterise the things you think need to change and commit the
> changes back to Forrest. My reasoning is that since you need it to work
> one
> You said you are using dispatcher, right? Which version?
Good question! I think it's RC1.
I'm using the plugins
org.apache.forrest.plugin.internal.dispatcher
org.apache.forrest.themes.core
and set the dispatcher up using the 'Dispatcher Quickstart' doc about
five days ago.
> Can we see the
> Have you seen the tips?
> http://forrest.apache.org/docs/dev/linking.html#tab-site
Yes.
> Also look at our forrest site for an example
> $FORREST_HOME/site-author/content/xdocs/site.xml
> See the @tab attributes for each section,
> which refer to the @id attributes in tabs.xml
>
> -David
I've
How does one control which of the menus in nav-section will be open
when the tab is first selected? Been through the docs and recent list
discussion on this and can't see it, my apologies if it's been there
all along.
I've been building a site with the Dispatcher, using the Open Office
plugin to translate documents to Forrest internal document format. I
found that I had to make a couple of minor modifications to the plugin
- turned off the warning that the heading hierarchy is wrong (the
documents are supplied b
> developing my site from scratch again I have to admit I am pretty tired
> of editing the site.xml. Further the current site.xml is very limiting
> regarding different "views" of the site and reusability for e.g. the
> lenya CMS.
Alternate nav schemes would be fantastic.
> Today I stumbled ove
Ross
This relates to an issue I've been thinking about for a while. If one
had a pile of html and wanted to convert the docs to Forrest internal
format, and then convert them back into html as a Forrest generated
site presumably leaving the source documents in their original
location would result
Hi Helena
> no original rss is used for rss output.
> only original, local xml content.
Good, That sounds interesting. I don't suppose you could add a sample
xdoc with the relevant metadata included to the Jira issue. BTW, that
site of yours looks pretty good.
> helena
>
>
(ross)
> This would
ternal indexing format, and just filtering
the RSS to suit the use case.
On 18/01/06, Paul Bolger <[EMAIL PROTECTED]> wrote:
> > The rss is from existing content as well as newly-published content.
>
>
> Can I just clarify, does the existing content have to be rss?
>
> regards
> Paul Bolger
>
Hi Ferdinand
Thanks for offering. As you may be aware the 'news' contract has
developed somewhat since this conversation began, see Helena's RSS
contribution: FOR-784. What I was originally thinking of was a more
generic indexer, a contract which could parse a directory, or
directory tree, (or cont
> The rss is from existing content as well as newly-published content.
Can I just clarify, does the existing content have to be rss?
regards
Paul Bolger
Hi Thorsten, I've been trying to digest your replies before answering.
Not easy when I understand about 20% of it...
>
> The only difference is that you are linking to more/other css files in
> the {customTheme}.fv. ...and like always in the dispatcher we have
> fallbacks implemented.
Yeah, I'm be
I've done a bit more experimentation and it seems that pult.fv works
as expected in the xdocs directory - affects all documents below it -
if a pult.fv file exists in the project local themes directory. It
doesn't matter if that file has any content. It also seems this also
sets the project css def
> >
>
> Actually that is only interesting for the theme switcher and optional.
The dispatcher docs (howto-structurer-dsl) says
(attribute:theme) 3. the theme, "pelt" is the default theme (another
is the "common" theme). Change this if you are using your own theme.
Which to me means 'if you wan
> If you do and want a fallback for pult you can
> a) add it to {yourProject}/.../themes/pult.fv
> b) add it to {yourProject}/.../xdocs/pult.fv
>
> This are absolute fallbacks.
>
> > Now I have common.fv working,
> > but Forrest isn't finding the modified theme.
>
> Hmm, weird. ...but if you do no
Actually, come to think of it: the css links in the common.fv file
have theme attributes:
but Forrest ignoring them and just looking in the common/css directory.
# views is using a fallback mechanism for theming.
> > # You can configure the theme name and its extension here
> > project.theme-extension=.fv
> > project.theme=*common*
> >
> > Then your common fv file should be common.fv...
> >
> > Salutations,
&
I've just done a SVN update, built Forrest, built the two dispatcher
plugins, Forrest seed-v2 a new instance. I then added an instance of
common.fv but Forrest ignores it. I'd think that there was a setting
in forrest.properties which I've missed (it's changed quite a bit
since I last did this) but
> RSS is a standard format fur such things. It lists content of a
> particular type in a format that can be read by a large number of
> clients, not just Forrest.
> The idea would be create an RSS feed of all items, then use the feeder
> plugin (with modifications) to return the top four items.
> Sounds to me like Forrest should be generating an RSS feed of these news
> items. You could then leverage the feeder plugin for your home page
> headlines, whilst you would also be able to provide feeds for external
> sites.
>
> Since RSS is a more widely adopted standard for this kind of thing I
> Have you got the news sources in RSS? If so use the Feeder
> plugin/contract. (note that contract should now be moved to the feeder
> plugin since we now have that capability)
No, the stories are just (hypothetically) Forrest internal document
format. In most sites I work on the most frequent co
> Hmm, yes because the dispatcher is grown from skins and have to slimed
> down. The best way is to return a simple txt string. That would enhance
> the usability of the contract in different formats.
"...best way is to return a simple txt string" - could you explain
this a bit more?
> it is
On 04/01/06, Ross Gardler <[EMAIL PROTECTED]> wrote:
> Paul Bolger wrote:
> > Having had a chance to experiment a bit with the dispatcher I keep
> > finding that the existing contracts are too Forrest, or Apache,
> > specific - it's no coincidence that most &#
> Actually the thing that most worries me that all the conversations and
> complaints not have been directed to this list but to others. We never
> had a chance to help or response.
>
> > The way forward, in the short term, has to be to support users willing
> > to be *power* users. We need to prov
ml\default.body.html (The
system cannot find the file specified)
This happened when I used the code above.
As a matter of interest, how would one extend the match to include
files with .htm and .asp extensions?
paul b
On 18/12/05, David Crossley <[EMAIL PROTECTED]> wrote:
> David Cro
[ http://issues.apache.org/jira/browse/FOR-768?page=all ]
paul bolger updated FOR-768:
Attachment: csslinking.txt
Sorry, not sure how patching works, and no time to work it out this morning -
flying to NZ. Here's a text file of the additional par.
is How-To is
very detailed and I've learnt a lot from it, but it'd be good to have
a. and example file of sitemap.xmap with the extra element included (I
can't find the place that it's supposed to go...)
and
b. an example xsl file.
Thanks
Paul Bolger
Components: Dispatcher (aka views), Documentation and website
Versions: 0.8-dev
Reporter: paul bolger
Priority: Minor
I've added a section on simple linking to external css files to this How-To. At
present I'm not sure it's worth getting into too much detail as views a
> > ---
> >
> > Key: FOR-766
> > URL: http://issues.apache.org/jira/browse/FOR-766
> > Project: Forrest
> > Type: Improvement
> > Components: Dispatcher (aka views)
>
arddrive and then check them in?
>
> Like said as soon I check them in the only links that are working for
> the v2 seed are the once prefixed with "test"!!! Which is breaking trunk
> for the v2 seed.
>
> wdyt?
> --
> thorsten
>
> "Together we stand, divi
Can anyone explain how to link to an external CSS file from an .fv file?
Thanks
Paul Bolger
[ http://issues.apache.org/jira/browse/FOR-766?page=all ]
paul bolger updated FOR-766:
Attachment: howto-structurer-dsl-edit.xml
> A new note in howto-structurer-dsl explaining common
-dev
Reporter: paul bolger
Priority: Minor
lines 144 and 145. I've left spaces above and below to make it stand out.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/s
I'm not seeing a Close Issue link, which must mean I don't have
permission to resolve the issue. I've written a comment saying that.
paul
On 15/12/05, David Crossley <[EMAIL PROTECTED]> wrote:
> Paul Bolger wrote:
> > How do I resolve that BUILD FAILED issue
[
http://issues.apache.org/jira/browse/FOR-761?page=comments#action_12360464 ]
paul bolger commented on FOR-761:
-
Yes you're right Ross. I didn't realise that you had to rebuild each time you
do an SVN update.
I don't have permission to se
How do I resolve that BUILD FAILED issue in JIRA?
paul b
Winxp SP2, Java build 1.5.0_06-b05
Reporter: paul bolger
Forrest build fails, but only on a seed-v2 instance.
Output below.
C:\java\forrest\test>forrest
Apache Forrest. Run 'forrest -projecthelp' to list options
Buildfile: C:\java\forrest\main\forrest.build.xml
chec
I've got a copy of the whole log. Should I put lodge it as an issue on
JIRA and include the log?
paul
On 12/12/05, David Crossley <[EMAIL PROTECTED]> wrote:
> Paul Bolger wrote:
> > I did a SVN update yesterday and got the following error:
> >
> > BUILD FAILED
I did a SVN update yesterday and got the following error:
BUILD FAILED
C:\java\forrest\main\targets\site.xml:171: Warning: Could not find file C:\java\
forrest\test\build\tmp\brokenlinks.xml to copy.
This happened again with a new v-2 seed, but not with a 'vanilla'
seed. Reverted to a build from
> Edit the doc (retain existing whitespace
> or your patch will be unreadable).
Just to clarify, do you mean I need to keep the odd, mid-sentence, linebreaks?
> (NOTE: default.fv is now common.fv!!!)
> > [views:modify html classes] I'm trying to work out where css classes
> > are being inserted, specifically in content-main.ft, because I'd like
> > to modify local versions to skip a lot of the superfluous ones.
> >
>
> http://forrest.apache.org/docs_0
t; > Ross Gardler wrote:
> >
> >>Diwaker Gupta wrote:
> >>
> >>>Paul Bolger wrote:
> >>>
> >>>
> >>>>[views: .fv files] Is there a way to specify one .fv file for multiple
> >>>>input files, or does every page need an in
Thanks for the quick response Diwaker.
On 12/5/05, Diwaker Gupta <[EMAIL PROTECTED]> wrote:
> On Sunday 04 December 2005 9:08 pm, Paul Bolger wrote:
> > [views: .fv files] Is there a way to specify one .fv file for multiple
> > input files, or does every page need an individ
Hi all
Finally had a chance to mess around with V2, which brings up a few
questions. Rather than sending a heap of emails it might be easier to
suggest thread titles with each question.
[views: .fv files] Is there a way to specify one .fv file for multiple
input files, or does every page need an i
> Further I want to propose to get rid of the forrest:css element. This
> element is too html specific and can be easily replaced by a standard
> contract. No extra element needed.
I agree. Better to concentrate on stylesheet linking (which allows you
to arrange stylesheets by media type). Barring
So, what is the function of site.xml, if it's not to do the above? I'm
a bit confused over the definition of CMS being used here - I'm used
to it being used to refer to a system which does the lot - user input,
site and database management, output formats, conversions, archiving,
etc.
If Daisy did
> Actually, I should say, I do think that partnering wth a CMS that does
> this stuff is the way to go. Forrest should not attempt to become a CMS.
My apologies for forking this discussion somewhat.
I was more referring to using an Xforms or Cocoon forms interface to
control linking, input docume
not sure what happened there - Gmail hiccup! My apologies.
On 11/3/05, Paul Bolger <[EMAIL PROTECTED]> wrote:
> > As for mangling the names to get the right order - it makes me shudder!!
>
> Although I've found for big sites it's not a bad idea to use the ISO
> date
> As for mangling the names to get the right order - it makes me shudder!!
Although I've found for big sites it's not a bad idea to use the ISO
date-of-creation/page-subject-event as the first part of your file
name anyway, particularly for content such as news stories, press
releases, articles.
I
> As for mangling the names to get the right order - it makes me shudder!!
Although I've found for big sites it's not a bad idea to use the ISO
date-of-creation/page-subject-event as the first part of your file
name anyway, particularly for content such as news stories, press
releases, articles.
I
> Because this is no longer Vague - you have made a very concrete
> suggestion. The change of subject makes it much easier to read the
> archives where subject is all that is initially seen when searching.
>
> > if this has already
> > been implemented isn't there a case for making the
> > '#projec
> I agree, to an extent, with your observations. However, are you aware
> that Eclipse can be deployed with a specific set of plugins (and minus
> all the IDE stuff). This makes it reasonably lightweight and highly
> focussed on a specific task.
I think if there were some way to avoid the online s
a forrest.properties from a seed site:
> #project.menu-scheme=tab_attributes
> #project.menu-scheme=directories
>
> The former is the default.
> http://forrest.apache.org/docs_0_80/linking.html#other-menu-selection
> Directory-based selection
>
> However site.xml has two functions:
> >> - A simple, intuitive way for non-XMLers to add things to site.xml
> >
> >
> > Have you any suggestions about what this may look like?
Not sure how technically possible this is, but how about a directory
parser which builds the site nav? In other words the user would create
a directory struct
Thorsten
You may remember that I had some problems with views a week or so
back. Since then I haven't had much luck getting them to work, and I
gather that lots has happened with views/themer/structurer whatever in
that time anyway. Is there a document in the howtos which reflects the
current stat
that once we
> > settle on a name for views v2.
>
> I already copied them and used structurer as codename. I have not linked
> them yet, so we should agree on the codename and I will update them
> meanwhile.
>
> > This is head of trunk. Be careful about how many
> > backflips we perform to keep people up-to-date
> > with rapidly changing development.
> >
>
> Agreed.
>
> Thanks David.
>
> salu2
> --
> thorsten
>
> "Together we stand, divided we fall!"
> Hey you (Pink Floyd)
>
>
--
Paul Bolger
19 Raggatt St
Alice Springs
NT 0870
08 8953 6780
ince my last Subversion update the previously mentioned forrest
instance has packed up completely. When I get a bit of time I'll do a
new one and see what happens.
pb
On 10/11/05, Thorsten Scherler <[EMAIL PROTECTED]> wrote:
> El lun, 10-10-2005 a las 23:25 +0930, Paul Bolger escri
dev because this thread is about the next generation views
> (themer & structurer) and not the stable once (view & viewHelper).
>
> El dom, 09-10-2005 a las 17:16 +0100, Ross Gardler escribió:
> > Paul Bolger wrote:
> > > I'm trying to get Forrest Views to work. Got the pl
97 matches
Mail list logo
