Re: [jira] Updated: (FOR-506) Do not hard-code site-visible message strings in skin files
On Sat, 2005-06-04 at 06:06 +0200, Thorsten Scherler (JIRA) wrote: > [ http://issues.apache.org/jira/browse/FOR-506?page=all ] > > Thorsten Scherler updated FOR-506: > -- > > Attachment: patchI18n.diff > > the previous mentioned patch I guess I just should apply this patch to trunk to make it easier to make a patch out of trunk. WDYT? salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
Re: Problems with Forrest-SVN for user [EMAIL PROTECTED]
I can confirm that I can commit again to forrest. :) Thanks again. :) On Fri, 2005-06-03 at 23:31 -0400, Gregor J. Rothfuss wrote: > Thorsten Scherler wrote: > > Hello infrastructure, hello forrest-dev, > > > > I cannot commit anymore to forrest. :( I tried to commit to lenya which > > works like a charm, but forrest does not work. > > > > I even tried setting svnpasswd new, but that makes no different. > > > > Please advise, I cannot commit anymore to forrest. > > according to the svn authorization, you were not in the forrest > committers list. > > no idea why / how this happened, but i re-added you. > > note, thorsten is a well-known forrest committer and has been on the pmc > for a while: > > http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_11_14.txt > > -gregor -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
[jira] Updated: (FOR-506) Do not hard-code site-visible message strings in skin files
[ http://issues.apache.org/jira/browse/FOR-506?page=all ] Thorsten Scherler updated FOR-506: -- Attachment: patchI18n.diff the previous mentioned patch > Do not hard-code site-visible message strings in skin files > --- > > Key: FOR-506 > URL: http://issues.apache.org/jira/browse/FOR-506 > Project: Forrest > Type: Improvement > Components: Skins (general issues) > Versions: 0.7-dev > Environment: N/A > Reporter: Pedro I. Sanchez > Assignee: Thorsten Scherler > Priority: Minor > Attachments: patchI18n.diff > > Text strings like "Copyright", "Published", and "Search" are hardcoded into > skin files like site2xhtml.xsl. When creating web sites in languages other > than English the web developer is forced to create local versions of these > skin files with the appropriated translations. > Instead, the DTD for the skinconf.xml should be improved to allow these > translations to be specified in this file. This would make Forrest much > easier to use. -- 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/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-506) Do not hard-code site-visible message strings in skin files
[ http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12312612 ] Thorsten Scherler commented on FOR-506: --- The patch enables i18n support for forrest. Mainly it is focus right now on the i18n support for skins (in particular pelt). The changes I do not mention here are related to setup i18n support for the backend. The following code changes are as well the only example I implemented right now. ;-) Index: webapp/skins/pelt/xslt/html/site2xhtml.xsl === --- webapp/skins/pelt/xslt/html/site2xhtml.xsl (revision 179925) +++ webapp/skins/pelt/xslt/html/site2xhtml.xsl (working copy) @@ -34,7 +34,8 @@ --> -http://www.w3.org/1999/XSL/Transform";> +http://www.w3.org/1999/XSL/Transform"; + xmlns:i18n="http://apache.org/cocoon/i18n/2.1";> > Key: FOR-506 > URL: http://issues.apache.org/jira/browse/FOR-506 > Project: Forrest > Type: Improvement > Components: Skins (general issues) > Versions: 0.7-dev > Environment: N/A > Reporter: Pedro I. Sanchez > Assignee: Thorsten Scherler > Priority: Minor > Attachments: patchI18n.diff > > Text strings like "Copyright", "Published", and "Search" are hardcoded into > skin files like site2xhtml.xsl. When creating web sites in languages other > than English the web developer is forced to create local versions of these > skin files with the appropriated translations. > Instead, the DTD for the skinconf.xml should be improved to allow these > translations to be specified in this file. This would make Forrest much > easier to use. -- 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/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (FOR-506) Do not hard-code site-visible message strings in skin files
[ http://issues.apache.org/jira/browse/FOR-506?page=all ] Thorsten Scherler reassigned FOR-506: - Assign To: Thorsten Scherler > Do not hard-code site-visible message strings in skin files > --- > > Key: FOR-506 > URL: http://issues.apache.org/jira/browse/FOR-506 > Project: Forrest > Type: Improvement > Components: Skins (general issues) > Versions: 0.7-dev > Environment: N/A > Reporter: Pedro I. Sanchez > Assignee: Thorsten Scherler > Priority: Minor > > Text strings like "Copyright", "Published", and "Search" are hardcoded into > skin files like site2xhtml.xsl. When creating web sites in languages other > than English the web developer is forced to create local versions of these > skin files with the appropriated translations. > Instead, the DTD for the skinconf.xml should be improved to allow these > translations to be specified in this file. This would make Forrest much > easier to use. -- 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/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Problems with Forrest-SVN for user [EMAIL PROTECTED]
Thorsten Scherler wrote: Hello infrastructure, hello forrest-dev, I cannot commit anymore to forrest. :( I tried to commit to lenya which works like a charm, but forrest does not work. I even tried setting svnpasswd new, but that makes no different. Please advise, I cannot commit anymore to forrest. according to the svn authorization, you were not in the forrest committers list. no idea why / how this happened, but i re-added you. note, thorsten is a well-known forrest committer and has been on the pmc for a while: http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_11_14.txt -gregor
Problems with Forrest-SVN for user [EMAIL PROTECTED]
Hello infrastructure, hello forrest-dev, I cannot commit anymore to forrest. :( I tried to commit to lenya which works like a charm, but forrest does not work. I even tried setting svnpasswd new, but that makes no different. Please advise, I cannot commit anymore to forrest. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
[jira] Created: (FOR-518) Change toolbox font in skinconf.xml for pelt
Change toolbox font in skinconf.xml for pelt Key: FOR-518 URL: http://issues.apache.org/jira/browse/FOR-518 Project: Forrest Type: Improvement Components: Skins (general issues) Versions: 0.7-dev Reporter: Addison Berry Priority: Minor Users can set the background color for toolbox in skincof.xml but they there is no option to set the font color. Users must go in and manually edit site/skin/profile.css. -- 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/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-518) Change toolbox font in skinconf.xml for pelt
[ http://issues.apache.org/jira/browse/FOR-518?page=all ]
Addison Berry updated FOR-518:
--
Attachment: toolbox-font.txt
Last night I fixed this by editing the pelt/css/profile.css.xslt file by moving
#menu .menupagetitle {color: ;} up to toolbox,
rather than where it was in dialog (since dialog doesn't seem to be used in
pelt?) and also adding the font attribute to the toolbox color element in
fresh-site/skinconf.xml. Worked just the way I wanted. See the attached diffs.
When I did a build clean, build on a new svn today, I am now getting an error
when I try to forrest site:
X [0] linkmap.html BROKEN: The content of
elements must consist of well-formed character data or markup.
I'm not sure what the problem is now...
> Change toolbox font in skinconf.xml for pelt
>
>
> Key: FOR-518
> URL: http://issues.apache.org/jira/browse/FOR-518
> Project: Forrest
> Type: Improvement
> Components: Skins (general issues)
> Versions: 0.7-dev
> Reporter: Addison Berry
> Priority: Minor
> Attachments: toolbox-font.txt
>
> Users can set the background color for toolbox in skincof.xml but they there
> is no option to set the font color. Users must go in and manually edit
> site/skin/profile.css.
--
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/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: Moving over to [EMAIL PROTECTED]
On Sat, Jun 04, 2005 at 12:17:23AM +0100, Ross Gardler wrote: > I've updated SVN with the new issues URL. However, I have *not* > published the site to make these changes public. > > I wasn't sure if the i.a.o site was considered stable or if it was still > in test. From the messages on infra it looks like Jeff is happy with > things. SO if we are then we should publish the site ASAP because we > don't really want too many issues to sneak into the cocoondev.org JIRA. I think we can declare it stable. I've tweaked issues.cocoondev.org permissions to prevent new issues being created in the old FOR project. --Jeff > I'd like to extend my personal thanks to cocoondev.org for hosting us > for so long and to Jeff for putting in all the work to move us across, I > can imagine that it has been a tough job. > > Ross
[jira] Resolved: (FOR-192) migrate Forrest Jira to issues.apache.org
[ http://issues.apache.org/jira/browse/FOR-192?page=all ] Jeff Turner resolved FOR-192: - Resolution: Duplicate > migrate Forrest Jira to issues.apache.org > - > > Key: FOR-192 > URL: http://issues.apache.org/jira/browse/FOR-192 > Project: Forrest > Type: Task > Components: Core operations > Reporter: David Crossley > > The Forrest issue tracker will need to move to issues.apache.org in due > course. We need to plan the task, and ease the job for infrastructure. -- 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/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (FOR-517) create test issue
[ http://issues.apache.org/jira/browse/FOR-517?page=all ] David Crossley resolved FOR-517: Resolution: Fixed it works > create test issue > - > > Key: FOR-517 > URL: http://issues.apache.org/jira/browse/FOR-517 > Project: Forrest > Type: Bug > Components: Documentation and website > Versions: 0.7-dev > Reporter: David Crossley > > foo -- 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/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Moving over to [EMAIL PROTECTED]
Ross Gardler wrote: > I've updated SVN with the new issues URL. However, I have *not* > published the site to make these changes public. I did now. But i am away for the rest of the weekend so cannot help further. The bugtracking_url in forrest.properties still needs to be amended - cannot find the new one. Could some please contact cocoondev.org and arrange for their webserver to do .htaccess redirect to issues.apache.org > I wasn't sure if the i.a.o site was considered stable or if it was still > in test. From the messages on infra it looks like Jeff is happy with > things. SO if we are then we should publish the site ASAP because we > don't really want too many issues to sneak into the cocoondev.org JIRA. I did a few tests and it seems okay, so published our website. We already have one duplicate at FOR-516 > I'd like to extend my personal thanks to cocoondev.org for hosting us > for so long and to Jeff for putting in all the work to move us across, I > can imagine that it has been a tough job. Yes, many more thanks. --David
[jira] Commented: (FOR-517) create test issue
[ http://issues.apache.org/jira/browse/FOR-517?page=comments#action_12312605 ] David Crossley commented on FOR-517: ensure that messages now come to forrest-dev without moderation > create test issue > - > > Key: FOR-517 > URL: http://issues.apache.org/jira/browse/FOR-517 > Project: Forrest > Type: Bug > Components: Documentation and website > Versions: 0.7-dev > Reporter: David Crossley > > foo -- 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/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-517) create test issue
create test issue - Key: FOR-517 URL: http://issues.apache.org/jira/browse/FOR-517 Project: Forrest Type: Bug Components: Documentation and website Versions: 0.7-dev Reporter: David Crossley foo -- 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/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-517) create test issue
[ http://issues.apache.org/jira/browse/FOR-517?page=comments#action_12312600 ] David Crossley commented on FOR-517: test comment > create test issue > - > > Key: FOR-517 > URL: http://issues.apache.org/jira/browse/FOR-517 > Project: Forrest > Type: Bug > Components: Documentation and website > Versions: 0.7-dev > Reporter: David Crossley > > foo -- 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/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Locationmap branch
Tim Williams wrote: There's obviously a good chance I'm doing something wrong but when I build a seeded site based on the branch, i get: There's an equally good chance that in my experiments I have overlooked important things, as is the (partly) the case here. For the part that is not my oversight see my original mail, in particular the section marked WARNING === which contains the line: Currently it will only work if you do "forrest run" within the FORREST_HOME/main/fresh-site directory (along with an explanation why). What I mean to say is that: a) you cannot seed a fresh site, you *have* to run, you must run from within FORREST_HOME/main/fresh-site - this is *bad* and is certainly not permanent, but as I explain in the original mail I think it requires a little work on the java code, which I have not had the time to look at yet. b) "forrest site" does *not* work. This one should be much easier to fix. It is because I have been endlessly interrupted today and so I never actually put meaningful links into the demo page (i.e. they don't point anywhere). In the branched code i don't see the "locationmap" directory either. Can you point me in the right direction as I'd like to try to this stuff out. Doh! This is the part that is my oversight. I forgot to add the files before committing, I've done that twice recently. I'm working too hard perhaps. Anyway I added them now, do an 'svn up' (beware of those links that go nowhere, perhaps you can fix them as you work out how the locationmap works, the place to dix them is in locationmap.xml). Thanks for all you help No, thank you for taking enough interest to look at such early stage work, it will be a rough ride for us all, but made smoother by more eyes on the problem and ideas in the solution. Ross
Re: Locationmap branch
There's obviously a good chance I'm doing something wrong but when I build a seeded site based on the branch, i get: "* [129/4] [1/28]0.27s 7.8Kb /samples/usemap.html * [130/3] [0/0] 0.151s 4.1Kb /samples/usemap.pdf X [0] samples/locationmap/index.html BROKEN: No pipeline matched request: samples/locationmap/index.xml * [133/0] [0/0] 0.34s 243b /skin/images/rc-t-r-5-1header-2searchbox-3searchbox.png Logging Error: Writing event to closed stream. Total time: 1 minutes 22 seconds, Site size: 874,398 Site pages: 98" In the branched code i don't see the "locationmap" directory either. Can you point me in the right direction as I'd like to try to this stuff out. Thanks for all you help, hopefully as I learn more I'll be a little more self-sufficient... --tim
Moving over to issues@apache.org
I've updated SVN with the new issues URL. However, I have *not* published the site to make these changes public. I wasn't sure if the i.a.o site was considered stable or if it was still in test. From the messages on infra it looks like Jeff is happy with things. SO if we are then we should publish the site ASAP because we don't really want too many issues to sneak into the cocoondev.org JIRA. I'd like to extend my personal thanks to cocoondev.org for hosting us for so long and to Jeff for putting in all the work to move us across, I can imagine that it has been a tough job. Ross
[jira] Commented: (FOR-200) Locationmap for Forrest and Users
[ http://issues.apache.org/jira/browse/FOR-200?page=comments#action_12312551 ] Ross Gardler commented on FOR-200: -- Created a branch for work on the locationmap http://svn.apache.org/viewcvs.cgi/forrest/branches/locationmap_branch/?rev=179856 > Locationmap for Forrest and Users > - > > Key: FOR-200 > URL: http://issues.apache.org/jira/browse/FOR-200 > Project: Forrest > Type: New Feature > Reporter: Nicola Ken Barozzi > Fix For: 0.9 > > The locationmap gives us the ability to specify where sources are, both for > Forrest and for the users. > Beware that it will not work for raw files that are not linked, as this > "feature" currently uses a fixed dir being being copied by Ant. -- 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/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Locationmap branch
As requested I have set up a branch with my experiments with the locationmap. This branch is *not* to be used for any real work as I have done little testing. It is merely for experimentation right now. However, I do need the locationmap working in order to properly develop the Daisy plugin. So things will progress over there. At present there is a new demo page in fresh-site on that branch (see last menu item in samples). This is intended to document the working features. Which currently is only the link rewriting. There is no documentation for the locationmap at present except that page and http://issues.apache.org/jira/browse/FOR-200 WARNING === If you take a look at the changes to forrest.xconf you will see a FIXME regarding the location of the locationmap file. I don't know how to define it within xconf from a property set in forrest.properties. I suspect you can't and we will have to change the implementation of the org.apache.forrest.locationmap.LocationMapModule to accept it as a parameter from the sitemap. Currently it will only work if you do "forrest run" within the FORREST_HOME/main/fresh-site directory If anyone wants to have a play around with this branch I'll do my best to answer questions, but I'm not exactly familiar with it right now. Ross
[JIRA] Created: (FOR-516) motd in image area looks incorrect
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-516 Here is an overview of the issue: - Key: FOR-516 Summary: motd in image area looks incorrect Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Plugin: photoGallery Versions: 0.7-dev Assignee: Reporter: kevin Created: Fri, 3 Jun 2005 1:21 PM Updated: Fri, 3 Jun 2005 1:21 PM Environment: Any Description: Generates a working site but motd in image area looks incorrect. Suggest in plugin skinconf.xml Kevin. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-516) motd in image area looks incorrect
The following issue has been updated: Updater: kevin (mailto:[EMAIL PROTECTED]) Date: Fri, 3 Jun 2005 1:23 PM Comment: Patch if my fix ok. Changes: Attachment changed to skinconf.xml.diff - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-516?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-516 Here is an overview of the issue: - Key: FOR-516 Summary: motd in image area looks incorrect Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Plugin: photoGallery Versions: 0.7-dev Assignee: Reporter: kevin Created: Fri, 3 Jun 2005 1:21 PM Updated: Fri, 3 Jun 2005 1:23 PM Environment: Any Description: Generates a working site but motd in image area looks incorrect. Suggest in plugin skinconf.xml Kevin. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-516) Migrate Forrest's JIRA URLs from cocoondev to issues.apache.org
Migrate Forrest's JIRA URLs from cocoondev to issues.apache.org --- Key: FOR-516 URL: http://issues.apache.org/jira/browse/FOR-516 Project: Forrest Type: Test Components: Documentation and website Reporter: Jeff Turner Hi, I've migrated the Forrest JIRA project from cocoondev.org to http://issues.apache.org/jira: http://issues.apache.org/jira/browse/FOR This involved a gloriously hacky XSLT, so there may be problems. Please report anything you notice to me. If there are no problems the Forrest JIRA project on cocoondev.org can be shut down, and URLs changed to http://issues.apache.org/jira -- 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/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Jira migration in progress
Thanks for the headsup, Steven. :) Thanks for doing the migration Jeff. :) salu2 On Fri, 2005-06-03 at 17:32 +0200, Steven Noels wrote: > Hi all, > > could you please refrain from filing new Jira issues on > issues.cocoondev.org as Jeff Turner is currently testing the results of > the migration to issues.apache.org. > > Thanks, > > -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
Jira migration in progress
Hi all, could you please refrain from filing new Jira issues on issues.cocoondev.org as Jeff Turner is currently testing the results of the migration to issues.apache.org. Thanks, -- Steven Noelshttp://outerthought.org/ Outerthought - Open Source Java & XMLAn Orixo Member Read my weblog athttp://blogs.cocoondev.org/stevenn/ stevenn at outerthought.orgstevenn at apache.org
Re: How to avoid hard-coding site-visible message strings in skin files
On Thu, 2005-02-06 at 19:30 +0200, Thorsten Scherler wrote: > Hola Pedro, > > I can understand that i18n scares you a bit but I reckon it is the > simplest solution. If you are willing to finish my job I will start it > for the "old fashion" skins with the setup of sitemap, *one/two* props > and you would finish the work. We are talking about 3 -6 stylesheets (3 > common/3 pelt) where you need to add Published and > then add this key in the message catalog. I do not have enough time to > finish that but if you want I add a patch to the issue and you can > finish it. > > salu2 I will set aside some time this weekend to read about the i18n stuff and to try to understand what exactly has to be done. Anything you can add is certainly welcome. I'll be glad to help, but as I guess everyone else, I can only do it in my spare time. So don't expect things to be done over night :| Cheers, -- Pedro
Re: Meetup at ApacheCon? --> Room nearby!
On Fri, 2005-06-03 at 13:48 +0200, Reinhard Poetz wrote: > Reinhard Poetz wrote: > > Thorsten Scherler wrote: > > > >> On Fri, 2005-06-03 at 10:55 +0200, Nicola Ken Barozzi wrote: > >> > >>> Reinhard Poetz wrote: > >>> ... > >>> > If there is no Forrest event on Sunday, we would be more than happy > to see you at the Blockathon > (http://wiki.apache.org/cocoon/Blockathon) which will start on Sunday. > >>> > >>> > >>> Ah, ok, will see if I can make it :-) > >>> > >> > >> > >> I want to go there as well (if possible with you Reinhard). > > > > > > > > I gonna write this mail in German - if I'm wrong and you're not a German > > speaker please let me know!. > > > > Hi Thorsten, > > > > Meintest du, dass du versuchen wirst, im selben Hotel zu nächtigen, oder > > reist du über Wien an. Falls du letzteres gemeint hast, lass es mich > > ASAP wissen, weil ich Anfang nächster Woche den Zug buchen werde. > > sorry, I wanted to send this mail directly to Thorsten ;-) :) Yes I am a native German. ;-) No I mean whether I can attend the http://wiki.apache.org/cocoon/Blockathon as well. ;-) Then I will add myself there. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
[JIRA] Updated: (FOR-514) Do not limit status.xml contexts in project info plugin
The following issue has been updated: Updater: Cyriaque Dupoirieux (mailto:[EMAIL PROTECTED]) Date: Fri, 3 Jun 2005 7:41 AM Comment: - Udpate of the Status DTD 1.3 in order to be able to add the following information : - Update of changes2document.xsl in order to take into account the context title or by default the context ID. - Update of status.xml files (with documentation associated in comments) Regards, Cyriaque, Changes: Attachment changed to patch.txt - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-514?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-514 Here is an overview of the issue: - Key: FOR-514 Summary: Do not limit status.xml contexts in project info plugin Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Plugin: projectInfo Assignee: Reporter: Ross Gardler Created: Wed, 1 Jun 2005 6:02 AM Updated: Fri, 3 Jun 2005 7:41 AM Description: (This comment brought over from FOR-487) This improvement of changes page is nice. I have my own version based on xsl:key definition in order to be able to simply manage as many contexts as you can define (My Dtd is not limited to "build|docs|code|admin|design". The advantage - on my opinion - is that my own contexts are very various and not developpement oriented nor language dependant. here a short example - using releaseNote... : http://cyriaque.dupoirieux.free.fr/changes_6.2.1.html The following code replace the 5 blocks : Version () + + + + + + + + + + + Hope you'll like the idea... Regards, Cyriaque, - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Re: Meetup at ApacheCon? --> Room nearby!
Reinhard Poetz wrote:
Thorsten Scherler wrote:
On Fri, 2005-06-03 at 10:55 +0200, Nicola Ken Barozzi wrote:
Reinhard Poetz wrote:
...
If there is no Forrest event on Sunday, we would be more than happy
to see you at the Blockathon
(http://wiki.apache.org/cocoon/Blockathon) which will start on Sunday.
Ah, ok, will see if I can make it :-)
I want to go there as well (if possible with you Reinhard).
I gonna write this mail in German - if I'm wrong and you're not a German
speaker please let me know!.
Hi Thorsten,
Meintest du, dass du versuchen wirst, im selben Hotel zu nächtigen, oder
reist du über Wien an. Falls du letzteres gemeint hast, lass es mich
ASAP wissen, weil ich Anfang nächster Woche den Zug buchen werde.
sorry, I wanted to send this mail directly to Thorsten ;-)
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
Re: Meetup at ApacheCon? --> Room nearby!
Thorsten Scherler wrote:
On Fri, 2005-06-03 at 10:55 +0200, Nicola Ken Barozzi wrote:
Reinhard Poetz wrote:
...
If there is no Forrest event on Sunday, we would be more than happy to
see you at the Blockathon (http://wiki.apache.org/cocoon/Blockathon)
which will start on Sunday.
Ah, ok, will see if I can make it :-)
I want to go there as well (if possible with you Reinhard).
I gonna write this mail in German - if I'm wrong and you're not a German speaker
please let me know!.
Hi Thorsten,
Meintest du, dass du versuchen wirst, im selben Hotel zu nächtigen, oder reist
du über Wien an. Falls du letzteres gemeint hast, lass es mich ASAP wissen, weil
ich Anfang nächster Woche den Zug buchen werde.
Liebe Grüße
Reinhard
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
Handling raw HTML
I've been putting some thought into how to handle raw HTML. There are quite a few solutions to this, but somehow they all seem wrong for various reasons. The suggested attribute in skinconf feels like a hack The include/exclude patterns in site.xml is very powerful but is quite complex to implement and I think there may be a better solution when we switch to views because that will provide per directory configs. The locationmap provides a good place to mark raw content, but that is not ready yet and won't be until 0.8. I would like to suggest yet another alternative for 0.7 for the issue of raw HTML. This would be one in the form of a FAQ, a link to the FAQ from the upgrade doc and a demo in fresh-site - in other words there is no complex implementation to hold 0.7 up further. The FAQ would give the following sitemap match which should be placed in the project sitemap in order to duplicate the 0.6 behaviour. An advantage of doing it this way is that we can have the same kind of functionality that is proposed with the include/exclude behaviour but without any additional implementation. For example: I'm going to implement this unless someone spots a fatal flaw in my plan (lazy consensus is in operation) Ross
Re: Meetup at ApacheCon? --> Room nearby!
Thorsten Scherler wrote: On Fri, 2005-06-03 at 10:55 +0200, Nicola Ken Barozzi wrote: Reinhard Poetz wrote: ... If there is no Forrest event on Sunday, we would be more than happy to see you at the Blockathon (http://wiki.apache.org/cocoon/Blockathon) which will start on Sunday. Ah, ok, will see if I can make it :-) I want to go there as well (if possible with you Reinhard). I have not bought the plane tickets yet, but I think that I will stay a whole week... Cheers, cheche
Re: Problems when accessing directories...
Harald Krottmaier wrote:
Hi!
I've noticed a problem when accessing the samples/-resource in a freshly
seeded project: index.xml is not automatically appended, so
forrest/cocoon (current svn-snapshot forrest_20050530043903.tar.gz)
reports a "Resource Not Found" error.
Putting the redirects (currently the last entries in sitemap.xmap) to an
earlier position, solves this problem.
OK I've diagnosed the problem. A request such as
http://localhost:/samples/
will be matched by:
raw.xmap contains:
So Forrest tries to read "{project:content.xdocs}/samples/", this is a
directory so Resource Not Found
There are a number of ways to fix this, but I'm, not sure which is best:
1) remove the "**" match in raw.xmap
This will result in some raw files not being served, we would have to
add specific matches for each content type. However, this will make the
redirect to index.html work for URLs ending with or without a '/'
2) change the match "**" to a regexp that says anything not ending with '/'
This will only prevent raw.xmap from matching URLs ending with a '/', in
other words http://lcoalhost:888/samples/ would work but
http://lcoalhost:888/samples would not work
(how would this regexp look? I'm not good with regular expression, even
simple ones like this)
3) change the first match (in sitemap.xmap) to only match filenames with
an extension
This assumes that there will be no raw content without an extension.
4) ???
Which should I implement?
Ross
Re: Forrest as an XML repository
Juan Jose Pablos wrote: FYI: Ricardo Beltran wrote: I've CC'd Ricardo on this reply - please reply all. ... My questions are: Do you think that Forrest is an appropriate framework for this purpose? and Do you think that Lucene or Google will do the job of indexing about (5 GB) of XML files? I can't comment with authority on the suitability of Google or Lucene for this as I have no experience. My gut is telling me that this is not the optimal solution. I do have a project that has around 8Gb of dynamic data being published via the Forrest webapp. The solution I employed, and one that appears to be working well, was to have the data in an XML enabled database, in this case we used Oracle, but we have successfully used XIndice and eXist in similar, smaller, projects in the past. I wrote a custom generator to retrieve the data from the DBMS. It should be noted that Cocoon has some database components that can be utilised (there is the results of some early experiments of I did with these components in the whiteboard plugin org.apache.forrest.plugin.Database). The reason I never completed work on this plugin was not a problem with it, but additional requirements that made it easier to build a custom generator (our requests were also dependant on live data from sensor readings over an RS232 port). The system has now been running for about 3 months and we are very happy with it. Because we are using a Database server as the repository we have all the indexing and optimisation provided by that server. We also have the benefit of a very expressive and mature search language. Of course, this solution requires that you run the system dynamically. Using Google to index your site would allow you to run statically. Trying to build a static site from 5GB of data would be a wonderful stress test, if you do this please report your findings to us. Ross
Re: Meetup at ApacheCon? --> Room nearby!
On Fri, 2005-06-03 at 10:55 +0200, Nicola Ken Barozzi wrote: > Reinhard Poetz wrote: > ... > > If there is no Forrest event on Sunday, we would be more than happy to > > see you at the Blockathon (http://wiki.apache.org/cocoon/Blockathon) > > which will start on Sunday. > > Ah, ok, will see if I can make it :-) > I want to go there as well (if possible with you Reinhard). > Ferdinand Soethe wrote: > . > > Does this mean you are not attending the conference (Wed-Fri)? > > Nope, I'm using the Apachecon simply as an opportunity of meeting people. > I guess I will do it like Nicola. > > Do we need to rethink the scheduled date for our Views-seminar on > > Thursday? > > It would be nice for me if we could -also?- do something on Monday evening. > Yeah I would like to do something on Monday as well. I thought on monday there is the ASF hackathon as well, or? When are the 2 days hackathon? salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
[JIRA] Updated: (FOR-510) Setting Environment Variables Information
The following issue has been updated: Updater: Ross Gardler (mailto:[EMAIL PROTECTED]) Date: Fri, 3 Jun 2005 5:09 AM Changes: Fix Version changed to 0.7-dev - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-510?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-510 Here is an overview of the issue: - Key: FOR-510 Summary: Setting Environment Variables Information Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Documentation and website Fix Fors: 0.7-dev Versions: 0.6 Assignee: Reporter: Addison Berry Created: Sat, 28 May 2005 8:53 AM Updated: Fri, 3 Jun 2005 5:09 AM Description: Since we describe how to set the Forrest env variables in our docs we should make sure we have instructions for varying OS and versions. If you know of an OS that sets variables differently than that listed in our current docs, please add it in the comments. Make sure you state the OS and version as well as the full process to set the Forrest variables. Current instructions (0.7) In Unix/Linux: change directory to the top-level of the forrest distribution and do ~/apache-forrest-0.7$ export FORREST_HOME=`pwd` ~/apache-forrest-0.7$ export PATH=$PATH:$FORREST_HOME/bin In Windows: Go to "My Computer", "Properties", "Advanced", "Environment Variables" and add: FORREST_HOME as C:\full\path\to\apache-forrest-0.7 PATH as %PATH%;%FORREST_HOME%\bin - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Re: Forrest as an XML repository
FYI: Ricardo Beltran wrote: Hello Forrest developers team: First of all I would like to thank your efforts to bring to reality this great project! I'm planning to use Forrest in a project in Mexico, for a Social Sciences University in Mexico. We have about 10,000 polls about public opinion from the last 18 years of the Mexican history. Those polls were written (and executed) in Clipper (prg). I have a DTD that describes the content and structure of these polls, my plan is to transform those Clipper files to XML and use Forrest to make publicly available this information. As you can imagine there's a lot of information (about 5 GB) and it is very important to have a mechanism to search all this info using keywords. As you can see I'm planning to use Forrest as an XML repository and use Lucene or Google as my search engine. My questions are: Do you think that Forrest is an appropriate framework for this purpose? and Do you think that Lucene or Google will do the job of indexing about (5 GB) of XML files? If not, do you know some other project that could be suitable for this purpose. For your attention to this e-mail thanks a lot. Best Regards Ricardo Beltran [EMAIL PROTECTED] __ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail
Re: Meetup at ApacheCon? --> Room nearby!
Ferdinand Soethe wrote: Nicola Ken Barozzi wrote: >> Do we need to rethink the scheduled date for our Views-seminar on >> Thursday? It would be nice for me if we could -also?- do something on Monday evening. Well, Monday evening has never been suggested as far as I remember. I'd be happy to move the View-Workshop there if we can find a room and there are no crossovers with other events? Although Ross was planning on coming Tuesday I think (is this fixed?) No it is not fixed, my wife, son and I will be visiting friends in Germany for a few days either side of the conference, I will make myself available whenever others are available. Although, to be honest I was planning on only being at the conference itself so that I would be with my family and friends for at least some of the time. So I'm -0 on moving the date, I will be there if the majority wish to move the date. Ross
Re: Meetup at ApacheCon? --> Room nearby!
Nicola Ken Barozzi wrote: >> Do we need to rethink the scheduled date for our Views-seminar on >> Thursday? > It would be nice for me if we could -also?- do something on Monday evening. Well, Monday evening has never been suggested as far as I remember. I'd be happy to move the View-Workshop there if we can find a room and there are no crossovers with other events? Although Ross was planning on coming Tuesday I think (is this fixed?) Might make more sense than having a little discussion during the Hackathon and some more on Tuesday. What do other people think? -- Ferdinand Soethe
Re: Meetup at ApacheCon? --> Room nearby!
Reinhard Poetz wrote: ... If there is no Forrest event on Sunday, we would be more than happy to see you at the Blockathon (http://wiki.apache.org/cocoon/Blockathon) which will start on Sunday. Ah, ok, will see if I can make it :-) Ferdinand Soethe wrote: . > Does this mean you are not attending the conference (Wed-Fri)? Nope, I'm using the Apachecon simply as an opportunity of meeting people. > Do we need to rethink the scheduled date for our Views-seminar on > Thursday? It would be nice for me if we could -also?- do something on Monday evening. -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
Re: Meetup at ApacheCon? --> Room nearby!
Ferdinand Soethe wrote: > Nicola Ken Barozzi wrote: > > > Probably I will be staying only Monday and Tuesday during the week, as I > > cannot stay away for more than two days from work. Probably I will come > > earlier, like Saturday or Sunday, but it depends on who is going to be > > there on those days. > > Does this mean you are not attending the conference (Wed-Fri)? > Do we need to rethink the scheduled date for our Views-seminar on > Thursday? During the Hackathon, probably Tuesday, we should have a gathering of our committers. We can do some Views workshop there, then do the main workshop as already planned. --David
Re: does checksums-uri in cli.conf work?
Ferdinand Soethe wrote: David Crossley wrote: Cocoon-related questions would get better answers on cocoon-users. Is there an easy way to do this w/o subscribing to their list? My mailbox is already getting a bit crowded :-) A good place to start would be their archives. There may be some discussion about how to use it and its effects in the user list. There will almost certainly be some discussion about how and why it was implemented in the dev list. See http://cocoon.apache.org/community/mail-archives.html The Cocoon docs are also a good place to look. They are not well organised but they are reasonably complete. Judicious use of the search facility may help (note docs are split between the website and their wiki so two searches will be required). I'll try that and compare the results (Though diff is a Unix-only command, but I know what you mean). I'd recommend installing Cygwin if you are on Windows. You get a much more powerful shell and you can use proper *nix commands as given on the list. See http://www.cygwin.com/ Ross
Re: Meetup at ApacheCon? --> Room nearby!
Reinhard Poetz wrote: > If there is no Forrest event on Sunday, we would be more than happy to see > you at the Blockathon (http://wiki.apache.org/cocoon/Blockathon) which will > start on Sunday. I will attend for some of the time. Probably way over my head. --David
Re: Slide Integration
Thorsten Scherler wrote: On Fri, 2005-06-03 at 08:43 +0200, Nicola Ken Barozzi wrote: Ross Gardler wrote: ... I'm currently experimenting with the locationmap code, I have it working "to an extent". But have not yet managed to get it to work at the generation stage (through lack of time rather than a problem with the code, I think). I will attach a patch against the current SVN tree to the above issue that will enable the location map if you would like to experiment with it. It would be great to have someone working with me on this, you with Slide, me with Daisy (and Thorsten is looking at Lenya integration). Why don't you make a branch to work on it? +1 OK, will do it today. Ross
Re: Meetup at ApacheCon? --> Room nearby!
Nicola Ken Barozzi wrote: > > Probably I will be staying only Monday and Tuesday during the week, as I > cannot stay away for more than two days from work. Probably I will come > earlier, like Saturday or Sunday, but it depends on who is going to be > there on those days. I plan to arrive on the Friday and be there all week. --David
Re: Meetup at ApacheCon? --> Room nearby!
Ferdinand Soethe wrote:
Reinhard Poetz wrote:
If there is no Forrest event on Sunday, we would be more than happy to see you
at the Blockathon (http://wiki.apache.org/cocoon/Blockathon) which will start on
Sunday.
What exactly is a blockathon? Under the weblink above I found not much
further info about content.
thanks for the reminder - it was on my (mental) todo list to add some
information to the wiki page about what we will do at the Blockathon. In short:
we (the Cocoon developers) want to dedicate the upcoming ApacheCon Hackathon to
the devlopment of 'real blocks'.
See http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=111659636932761&w=2 and
http://wiki.apache.org/cocoon/Blocks for more detailed information about what
Cocoon blocks are.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
Re: Meetup at ApacheCon? --> Room nearby!
Reinhard Poetz wrote: > If there is no Forrest event on Sunday, we would be more than happy to see you > at the Blockathon (http://wiki.apache.org/cocoon/Blockathon) which will start > on > Sunday. What exactly is a blockathon? Under the weblink above I found not much further info about content. -- Ferdinand Soethe
Re: Meetup at ApacheCon? --> Room nearby!
Nicola Ken Barozzi wrote: > Probably I will be staying only Monday and Tuesday during the week, as I > cannot stay away for more than two days from work. Probably I will come > earlier, like Saturday or Sunday, but it depends on who is going to be > there on those days. Does this mean you are not attending the conference (Wed-Fri)? Do we need to rethink the scheduled date for our Views-seminar on Thursday? -- Ferdinand Soethe
Re: Meetup at ApacheCon? --> Room nearby!
Nicola Ken Barozzi wrote:
David Crossley wrote:
...
Here is the current schedule:
Tuesday 19 July
Event: Apache Committers Hackathon
Time: all day
Location: ApacheCon
Probably I will be staying only Monday and Tuesday during the week, as I
cannot stay away for more than two days from work. Probably I will come
earlier, like Saturday or Sunday, but it depends on who is going to be
there on those days.
If there is no Forrest event on Sunday, we would be more than happy to see you
at the Blockathon (http://wiki.apache.org/cocoon/Blockathon) which will start on
Sunday.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
Re: does checksums-uri in cli.conf work?
David Crossley wrote: > Cocoon-related questions would get better answers on cocoon-users. Is there an easy way to do this w/o subscribing to their list? My mailbox is already getting a bit crowded :-) > One way to see if there are any side-effects, would be to create > two separate sites with 'forrest seed' and do 'forrest' in each. > then compare the differences: > cd forrest-test > diff -rq seed-1/build/site seed-2/build/site > ... will report any files with differences. > It would be great if you can get this facility working. Thanks David, I'll try that and compare the results (Though diff is a Unix-only command, but I know what you mean). -- Ferdinand Soethe
