Some recent discussion on this list made me think a bit more about our
concepts with regard to the use of class attributes ...
I'd appreciate your comments.
Ferdinand Soethe
Function of class-Attributes
Forrest components (and users) use "class"-attributes in 4 diff
Yes!
David Crossley wrote:
CFAS Webmaster wrote:
How about this:
This stuff does go into src/documentation/sitemap.xmap to answer Ross's
question.
...
...
mime-type="application/x-javascript" />
I took the version and
corrected the mime-type and it works. Yea!
CFAS Webmaster wrote:
> David Crossley wrote:
> >
> >You can see that default match at main/webapp/resources.xmap
> >line 153 ...
> >
> >
> > >mime-type="application/x-javascript" />
> >
> >
> >I wonder if we should change that so that it first
> >looked in sub-directories and then looked at the
>
CFAS Webmaster wrote:
Hmm...
David Crossley wrote:
...
You can see that default match at main/webapp/resources.xmap
line 153 ...
mime-type="application/x-javascript" />
I wonder if we should change that so that it first
looked in sub-directories and then looked at the
top-level of resou
[ http://issues.apache.org/jira/browse/FOR-778?page=all ]
David Crossley closed FOR-778:
--
Fix Version: 0.8-dev
Resolution: Fixed
Thanks. I applied the patch, but needed to make a change (invalid xml: bare
ampersands in link). I am also going to r
Hmm...
David Crossley wrote:
Ross Gardler wrote:
CFAS Webmaster wrote:
All,
I'm submitting this to the dev list because I *think* this is new
behaviour in 0.8. I haven't tried it again with 0.7 as this machine is
a bit low on disk space.
I have an HTML file that I'm processing t
Ross Gardler wrote:
> CFAS Webmaster wrote:
> >All,
> >
> > I'm submitting this to the dev list because I *think* this is new
> >behaviour in 0.8. I haven't tried it again with 0.7 as this machine is
> >a bit low on disk space.
> >
> > I have an HTML file that I'm processing through Forrest,
>
El mié, 04-01-2006 a las 10:09 +1300, Paul Bolger escribió:
> > 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 t
David Crossley wrote:
It told me that the file was saved, but i couldn't find
it anywhere. You need to have done 'forrest site' once
before doing 'forrest run' and save. Fair enough, but
perhaps there should have been an error.
There is an item in the status file to add error checking ;-)
Howe
It told me that the file was saved, but i couldn't find
it anywhere. You need to have done 'forrest site' once
before doing 'forrest run' and save. Fair enough, but
perhaps there should have been an error.
I have a similar application that uses Cocoon's
SourceWritingTransformer which is nice. Don'
CFAS Webmaster wrote:
All,
I'm submitting this to the dev list because I *think* this is new
behaviour in 0.8. I haven't tried it again with 0.7 as this machine is
a bit low on disk space.
I have an HTML file that I'm processing through Forrest,
http://www.cfas.org/Committees/Application
El mié, 04-01-2006 a las 12:12 -0500, CFAS Webmaster escribió:
> All,
>
> I'm submitting this to the dev list because I *think* this is new
> behaviour in 0.8. I haven't tried it again with 0.7 as this machine is
> a bit low on disk space.
>
> I have an HTML file that I'm processing throug
All,
I'm submitting this to the dev list because I *think* this is new
behaviour in 0.8. I haven't tried it again with 0.7 as this machine is
a bit low on disk space.
I have an HTML file that I'm processing through Forrest,
http://www.cfas.org/Committees/Application.html if you're interes
[ http://issues.apache.org/jira/browse/FOR-779?page=all ]
Ross Gardler closed FOR-779:
Resolution: Fixed
Assign To: Ross Gardler
Patch applied.
Thanks Sjur
> xxe tool incompatible with XXE 3.0p1
>
>
>
xxe tool incompatible with XXE 3.0p1
Key: FOR-779
URL: http://issues.apache.org/jira/browse/FOR-779
Project: Forrest
Type: Bug
Components: Tool: XXE config
Versions: 0.8-dev
Reporter: Sjur N. Moshagen
Attachments:
Thorsten Scherler wrote:
El mié, 04-01-2006 a las 10:33 +, Ross Gardler escribió:
Thorsten Scherler wrote:
...
Your suggestion of adding docs to the themer directory plugin does not
work since this means all themes have to be hosted here at Forrest.
Why?
The documentation/sample
El mié, 04-01-2006 a las 10:33 +, Ross Gardler escribió:
> Thorsten Scherler wrote:
> > El mar, 03-01-2006 a las 14:14 +, Ross Gardler escribió:
> >
> >>Thorsten Scherler wrote:
> >>
> >>>El mar, 03-01-2006 a las 13:25 +1100, David Crossley escribió:
> >>>
> >>>
> Ross Gardler wrote:
Thorsten Scherler wrote:
El mié, 04-01-2006 a las 01:55 +, Ross Gardler escribió:
...
Enjoy a faster workflow:
- Edit
- preview
- save
- commit
But be careful with it, there are currently no checks for things like
changed navigation files.
Very, nice I have not look at it yet, bu
Thorsten Scherler wrote:
El mar, 03-01-2006 a las 14:14 +, Ross Gardler escribió:
Thorsten Scherler wrote:
El mar, 03-01-2006 a las 13:25 +1100, David Crossley escribió:
Ross Gardler wrote:
I propose that themes be distributed as plugins rather than having them
all in the themer plu
CFAS Webmaster wrote:
Ross,
I do find them useful for one thing. Since I haven't yet been able to
get forrestbot working, I use a different program to upload files to the
"production" site. That utility primarily uses date/time stamps from
files to figure out which ones to upload.
The che
El mié, 04-01-2006 a las 01:55 +, Ross Gardler escribió:
> OK, so there are concerns about doing this, but I think all the concerns
> can be addressed, and besides *I* want an easier way of publishing a
> spelling correction in a single page of a 500 page site (for example).
>
> So, I've don
El mar, 03-01-2006 a las 14:14 +, Ross Gardler escribió:
> Thorsten Scherler wrote:
> > El mar, 03-01-2006 a las 13:25 +1100, David Crossley escribió:
> >
> >>Ross Gardler wrote:
> >>
> >>>I propose that themes be distributed as plugins rather than having them
> >>>all in the themer plugin.
22 matches
Mail list logo