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?
I have worked on the ODT
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
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
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?
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
, 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 again...
Paul Bolger
On 12/07/06, Web Maestro Clay
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 catalog
:...\{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
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 been trying to get the MS Word
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 feature
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
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
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 from Forrest?
Forrest already does it. See main/webapp
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:-
!--HEADSUP: thorsten changed this because we get working
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.
Paul Bolger
That's
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
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 Williams [EMAIL PROTECTED] wrote:
Forrest Friday is rapidly approaching
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
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't
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.
I don't use Internet Explorer, but unfortunately most
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
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 this will be
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 now.
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.xml
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 been
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
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 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 be a
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 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
*
Then your common fv file should be common.fv...
Salutations,
Cyriaque,
Paul Bolger a écrit :
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
Actually, come to think of it: the css links in the common.fv file
have theme attributes:
forrest:css url=styles.css media=screen theme=pult/
but Forrest ignoring them and just looking in the common/css directory.
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 not specify
forrest:css url=styles.css media=screen theme=pult/
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
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
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'd
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.
Ok,
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)
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
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 'Forrest Powered' sites look
a little bit like
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 Crossley wrote:
Paul Bolger wrote:
I've been trying to get this to work, and I'm not sure what's going
wrong. I'll explain what I'd
: 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 are
changing very rapidly
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
[ 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. Note
-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/secure
[ 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.fv
---
Key
Can anyone explain how to link to an external CSS file from an .fv file?
Thanks
Paul Bolger
How do I resolve that BUILD FAILED issue in JIRA?
paul b
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 in JIRA?
There should be a Close issue
, 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\testforrest
Apache Forrest. Run 'forrest -projecthelp' to list options
Buildfile: C:\java\forrest\main\forrest.build.xml
check-java-version
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
C:\java\forrest\main\targets\site.xml:171
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?
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 individual file?
Yes. If you
about protocols, if I edit one of the
Howtos how do I submit it? If I'm unsure about whether something is
correct how do I pass it on for a second opinion?
On 12/6/05, Ross Gardler [EMAIL PROTECTED] wrote:
David Crossley wrote:
Ross Gardler wrote:
Diwaker Gupta wrote:
Paul Bolger wrote
(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.
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
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 a
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.
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-of-creation/page-subject-event
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.
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
) 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 plugin and Contracts
list view working but now I'm a bit confused. If I apply a contract
such as the one in the Howto
64 matches
Mail list logo
