Nicola Ken Barozzi wrote:
One thing I like about Forrest is that it's not only a static site
generation engine, but it's capable of serving the site live. Changes
are instantaneous, bandwith is perserved, and dynamic content can be
employed.
IMHO every Apache project that produces something
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-490
Here is an overview of the issue:
-
Ferdinand Soethe wrote:
My point:
Making use of the only purpose we came up with for the current
mechanism (being able to have menus longer than the page) will create
an extremely user-unfriedly page because opening a menu item at the
bottom of such a menu
- requires the user to
scroll the page
Ferdinand Soethe wrote:
Sorry, this needs to be long (and dirty)
in a freshly seeded site change site.xml to
site label=Demo Site xmlns=http://apache.org/forrest/linkmap/1.0; tab=
menu1 label=Menu 1
page1 label=Page 1 href=page1.html/
page2 label=Page 2 href=page2.html/
/menu1
/site
Ferdinand Soethe wrote:
in a freshly seeded site?!
* [68/1][0/0] 0.281s 22.6Kb samples/linking.pdf
* [69/0][0/0] 0.1s 3.2Kb samples/index.pdf
Logging Error: Writing event to closed stream.
Total time: 0 minutes 24 seconds, Site size: 403.728 Site pages: 59
David Crossley wrote:
Ross, would you please take this up on [EMAIL PROTECTED]
This is the first time that i have heard discussion of
this SISSL license.
Sure, I'll report back when we have an answer. In the meantime, if
anyone is interested in the (alpha) MSOffice plugin I can make it
available
Ferdinand Soethe wrote:
Ross Gardler wrote:
RG Best to change it in all occurances of the file as people could look at
RG any of the official Apache docs for guidance.
Added info to files in fresh-site and site author. I'd rather not
do this in the future but instead prefer for us to agree that we
Ferdinand Soethe wrote:
My point:
Making use of the only purpose we came up with for the current
mechanism (being able to have menus longer than the page) will create
an extremely user-unfriedly page because opening a menu item at the
bottom of such a menu
- requires the user to
scroll the page
Ferdinand Soethe wrote:
After doing some radical changes in xdocs I noticed that there was
still an old index.html in build/site that was not updated because it
was no longer part of the site. It should definitely have been
removed.
It doesn't by default for performance reasons. During development
Ross Gardler wrote:
RG I'd suggest finding the solution, adding it as a configuration option
RG and then, if you still want to, take it to a vote to make it the default.
Sounds good to me since such a change would only make sense if we
get it to work properly. Implementing it as an option
Ross Gardler wrote:
(about this comment
FS !-- Note: No matter what you configure here, Forrest will always try to
load
FSindex.html when you request http://yourHost/
FS --
)
RG I'm -1 on the current comment as it gives the impression that it *can't*
RG be changed. This is bad. If
Ross Gardler wrote:
RG http://issues.cocoondev.org/browse/FOR-465
Ooops. Sorry. Time to start reading issues again ...
--
Ferdinand Soethe
The following comment has been added to this issue:
Author: Johannes Schaefer
Created: Tue, 3 May 2005 3:28 AM
Body:
Here's the link to the Mail:
http://marc.theaimsgroup.com/?l=forrest-devm=111510406905741w=2
-
On 26 Apr 2005, at 23:29, Ross Gardler wrote:
The big advantage of Daisy over other CMS systems is that it
compeltely separates the front end from the repository. The access
control is done in the repository. However at present, for simplicity,
the plugin uses the daisy-wiki interface to
Ferdinand Soethe wrote:
Ross Gardler wrote:
(about this comment
FS !-- Note: No matter what you configure here, Forrest will always try to
load
FSindex.html when you request http://yourHost/
FS --
)
RG I'm -1 on the current comment as it gives the impression that it *can't*
RG be
Ross Gardler wrote:
RG It doesn't by default for performance reasons. During development it is
RG usually not important if the odd file is left hanging and cleaning a
RG directory with a few thousand files in it can take quite some time.
RG If you want to do a clean build then do 'forrest
Ross Gardler wrote:
RG But that simply is not correct. It *is* configurable as I have written
RG on a number of occasions now.
Sorry, I shouldn't respond to messages one by one. That way I missed
your solution in 'Re: Inkonsistency in implementation of default file
and site.xml and what to do
On Tue, 2005-05-03 at 09:49 +0100, Ross Gardler wrote:
Ferdinand Soethe wrote:
...
I disagree here. It might have been ok to just leave it before we knew
about the inconsistencies it will create if you don't use index.html.
As far as I am aware the only inconsistency is that the index
Hello devs,
I am implementing another format for the viewHelper. That forced me to
rename the current implementation to viewHelper.xhtml.
*You have to* rename the forrest.properties of your projects that are
using the view/viewHelper!!!
BTW we need to discuss the contracts that we have right
[EMAIL PROTECTED] wrote:
+faq id=defaultFileName
+ question How can I change the default file name that Forrest will look
for when I request a
+URL like codehttp://myserver/code or
codehttp://myserver/mydir//code? /question
+ answer
+pChange the setting
Ferdinand Soethe wrote:
Ross Gardler wrote:
RG But that simply is not correct. It *is* configurable as I have written
RG on a number of occasions now.
Sorry, I shouldn't respond to messages one by one. That way I missed
your solution in 'Re: Inkonsistency in implementation of default file
and
Hi Thorsten,
What are the main differences between this and the earlier implementations?
Thanks,
Diwaker
On 5/3/05, Thorsten Scherler [EMAIL PROTECTED] wrote:
Hello devs,
I am implementing another format for the viewHelper. That forced me to
rename the current implementation to
Recently I asked how I should revert a change in SVN, but no-one here
was sure how to do it smoothly. I promised to ask on a more appropriate
list, however, this recently appeared on the cocoon dev list:
Antonio Gallardo wrote:
Hi:
I want revert changes in
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project forrest-forrestbar has an issue affecting its community integration.
This issue
24 matches
Mail list logo
