Re: Meetup at ApacheCon? -- Room nearby!
Good news: we can have a room at the FHT for the evenings, thanks to Prof. Hauber. The faculty is close by the conference center, see http://www.hft-stuttgart.de/Hochschule/wirueberuns/Lageplan/ It's right below the ApacheCon sign in the map http://apachecon.com/2005/EU/images/Stuttgart-Plan_gross.gif We'll need to decide when we'll meet. Prof. Hauber works in the area oif Internet Technologies, Web Programming, Web Content Management Systems, and Open Source Software. One special interest is in Apache (he'll try to join the conference). Looking forward to see you all there! Johannes Ross Gardler schrieb: Thorsten Scherler wrote: On Mon, 2005-05-23 at 21:46 +1000, David Crossley wrote: Nicola Ken Barozzi wrote: Ross Gardler wrote: Ferdinand Soethe wrote: Thorsten Scherler wrote: Well perhaps we can organize something on our own. I'd certainly be interested ... Why else is planning on coming and when? Well there will be at least three of us there. That makes it worth meeting up for some high bandwidth work. Anyone else going to ApacheCon Europe? Count me in. And me, yes all the way from the antipodes just to meet up with you people. I haven't decided how long yet, but certainly some extra days. WOW! That is awesome. Nearly all Forrest PMC will be there. That is just great. Thanks David for coming from downunder. :) I can see I will have to extend my stay. I was planning on just a couple of nights since my wife and child will be visiting friends elsewhere in Germany. However, if we are all to be there... Ross -- User Interface Design GmbH * Teinacher Str. 38 * D-71634 Ludwigsburg Fon +49 (0)7141 377 000 * Fax +49 (0)7141 377 00-99 Geschäftsstelle: User Interface Design GmbH * Lehrer-Götz-Weg 11 * D-81825 München www.uidesign.de Buch User Interface Tuning von Joachim Machate Michael Burmester www.user-interface-tuning.de
Re: Meetup at ApacheCon? -- Room nearby!
Dear Apaches, there was a misunderstanding: I am _interested_ in the areas mentioned above, I _don't_ really work in those areas (I just teach them to undergraduates). I work mainly in IT Security and Cryptography. Looking forward to meeting you all, Peter (Hauber) Johannes Schaefer wrote: Good news: we can have a room at the FHT for the evenings, thanks to Prof. Hauber. The faculty is close by the conference center, see http://www.hft-stuttgart.de/Hochschule/wirueberuns/Lageplan/ It's right below the ApacheCon sign in the map http://apachecon.com/2005/EU/images/Stuttgart-Plan_gross.gif We'll need to decide when we'll meet. Prof. Hauber works in the area oif Internet Technologies, Web Programming, Web Content Management Systems, and Open Source Software. One special interest is in Apache (he'll try to join the conference). Looking forward to see you all there! Johannes -- -- Prof. Dr. Peter Hauber FH Stuttgart - University of Applied Sciences Department of Geomatics, Computer Science, and Mathematics Stuttgart, Germany -- http://www.hft-stuttgart.de http://www.hft-stuttgart.de/Mathematik/personal/Professoren/Professor?n=16 Phone: +49-711-121-2715 --
Re: [JIRA] Closed: (FOR-508) available-skins command returns incorrect information
On Mon, 2005-05-30 at 01:45 -0500, [EMAIL PROTECTED] wrote: Message: The following issue has been closed. Resolver: David Crossley Date: Mon, 30 May 2005 1:44 AM ... * removed leather-dev because it has evolved to form the basis of the views plugin. Yeah, that is right, still we cannot remove the source files. salu2 - View the issue: http://issues.cocoondev.org//browse/FOR-508 Here is an overview of the issue: - Key: FOR-508 Summary: available-skins command returns incorrect information Type: Bug Status: Closed Priority: Major Resolution: FIXED Project: Forrest Components: Skins (general issues) Fix Fors: 0.7-dev Versions: 0.6 Assignee: Reporter: Maurice Lanselle Created: Fri, 27 May 2005 5:27 AM Updated: Mon, 30 May 2005 1:44 AM Environment: Win XP (but I don't think that matters in this case). Description: Forrest available-skins command returns incorrect information, including a skin (crust) which no longer exists, and omitting some (plain-dev, leather-dev) which are available (but not fully supported). - 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 -- thorsten Together we stand, divided we fall! Hey you (Pink Floyd)
Re: [OT] Come on Preston!!! (Re: [Proposal] remove views from forrest (Re: Views as a Domain Specific Language))
On Mon, 2005-05-30 at 10:04 +0100, Ross Gardler wrote: Thorsten Scherler wrote: On Sun, 2005-05-29 at 21:33 -0500, Antonio Gallardo wrote: On Dom, 29 de Mayo de 2005, 21:15, David Crossley dijo: Well said Ross, you express yourself well even when drunk. +1 Perhaps we need to send him more beers? ;-) Seriously, it was a very nice answer! I liked it much. +1 Sorry for being such a pain in the a*++. I will answer the thread after work by taking your observations to another topic. Well you guys just took away my hangover, now I can go watch my local Football team in the Play-Off finals for a place in the Premiership. Come on Preston!!! ( http://news.bbc.co.uk/sport1/hi/football/eng_div_1/4591287.stm ) Ross +1 Go preston. ;-) ...best against hangover is another beer. ;-) It is on me. ;-) salu2 -- thorsten Together we stand, divided we fall! Hey you (Pink Floyd)
Re: Skins
Tim Williams wrote: it got me thinking that maybe there should be a little skininfo.xml in each skin directory where the current status of the skin could be pulled Would it make sense to also pull a short description of the skin so that users can get a list of available skins including a short description (with the available-skins command). That way we could perhaps stop maintaining the descriptions of skins on the web site and simply have each skin explain itself. Might be useful to include the development status of the skin in the listing as well. -- Ferdinand Soethe
Re: Fussy feelings about 0.7
David Crossley wrote: Thorsten, you started this thread, and Cheche you said me too. However neither of you followed up to tell us what your concerns are. Please say something. Even if your comments are not specific, we need to know why you are making these disruptive statements. sure, I think that FOR-465: Logging Error: Writing event to closed stream. and the output Lazy mode: true and a log4j:WARN Please initialize the log4j system properly. look bad. I think as well that they do not affect to the output site, but in order to fix the first two issues, we would need to upgrade our version of cocoon. At the moment we are not able to do so, Carsten is aware that the command line enviroment is not working, so we need to wait for him to fix it and them test those changes. But I am happy if those changes go to the next release (0.71)
Re: Fussy feelings about 0.7
Let's not be fussy, let's act! I can see good reasons for delaying the release and fix a few things and I see _just as many reasons_ to roll out the improvements we have made until now. The only real mistake we can make is to talk about this forever. However: If we decide to postpone, I'd suggest to address a number of extra issues (like dir structure) that was scheduled for 0.8. And that will mean a considerable delay. So in short: let's do 0.7 now. I'll help by fixing the linking samples this Wednesday. -- Ferdinand Soethe
Problems when accessing directories...
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. HTH, Harald.
Re: Meetup at ApacheCon? -- Room nearby!
Ferdinand Soethe wrote: Johannes Schaefer wrote: Good news: we can have a room at the FHT for the evenings, thanks to Prof. Hauber. Hey this is great news. Thanks to Johannes and Peter for solving this problem for us. We'll need to decide when we'll meet. OK, I suggest to have - the general Forrest Meetup on Wednesday evening (the day of our Forrest presentation) so that people can come and ask more questions ... - the views-workshop on Thursday so that people won't have to hang around for all three days of the conference. With Johannes' mail saying evenings (plural) I'd gratefully take the offered room for both evenings to not exclude people. If that is not stretching Peter's hospitality too far? Would 19:00 hrs be good time to start? I'm off-line till Wednesday. Since some people need to arrange for their travel we should decide soon. So how about taking the time to comment until Wednesday so we can finalize the arrangements this week? I like your proposal, if it needs to change to accommodate other people that is fine by me. I will be in Germany for about a week in total. Most of it I will not be in Stuttgart however, I will ensure I am present when there is anything Forrest going on. (Below I'll include the agenda for both meetings from previous mail.) -- Ferdinand Soethe We General Exchange on Forrest an opportunity for Forrest users and developers to meet and have an open exchange about Forrest. If we have enough people committed to participating, we could/should we announce this meeting in our Forrest session for interested people to join us. It is possible that we will not have many non-Forrest people taking this up. If this is the case I would like to use this time to do some forward planning and bug fixing. Will there be net access in this room? I see this as being compatible with an open exchange with potential users and devs as we can ask what peoples use cases are and discuss whether Forrest should/would be considered for that use case. In cases where Forrest seems appropriate we can look at what changes need to be made. Th Workshop Forrest Views with Thorsten explaining the concept and practical details of his Forrest-Views and plenty of opportunity to ask questions. My hope is that I will have a chance to understand Views after that which means that we will address people with a limited understanding of Forrest and Plug-ins. Duration: ~ 2 hrs? I propose no changes at all to this part of the agenda. Views is key to the next release of Forrest and will, I think, finally see us moving to a subset of XHTML2 as the internal. This should be a purely design focused meeting. Ross
Re: Fussy feelings about 0.7
Ferdinand Soethe wrote: Let's not be fussy, let's act! I can see good reasons for delaying the release and fix a few things and I see _just as many reasons_ to roll out the improvements we have made until now. The only real mistake we can make is to talk about this forever. +1 So in short: let's do 0.7 now. I'll help by fixing the linking samples this Wednesday. +1 Ross
[JIRA] Created: (FOR-513) Messages from Cocoon about Lazy mode
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-513 Here is an overview of the issue: - Key: FOR-513 Summary: Messages from Cocoon about Lazy mode Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Core operations Versions: 0.7-dev Assignee: Reporter: David Crossley Created: Mon, 30 May 2005 7:38 PM Updated: Mon, 30 May 2005 7:38 PM Description: Cocoon issues messages Lazy mode: true etc. These are issued when Cocoon loads a sitemap component. - 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] Commented: (FOR-513) Messages from Cocoon about Lazy mode
The following comment has been added to this issue: Author: David Crossley Created: Mon, 30 May 2005 7:44 PM Body: The reason that we are seeing these messages is probably because we are using a version of Cocoon that still contains debug statements about this facility. The messages can be ignored. Lazy mode: true means that Cocoon will only load each sitemap component when it is actually required. This helps to speed Cocoon startup. Forrest has configured Lazy mode: true for the 'forrest site' and Lazy mode: false for the 'forrest run'. - View this comment: http://issues.cocoondev.org//browse/FOR-513?page=comments#action_12452 - View the issue: http://issues.cocoondev.org//browse/FOR-513 Here is an overview of the issue: - Key: FOR-513 Summary: Messages from Cocoon about Lazy mode Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Core operations Versions: 0.7-dev Assignee: Reporter: David Crossley Created: Mon, 30 May 2005 7:38 PM Updated: Mon, 30 May 2005 7:44 PM Description: Cocoon issues messages Lazy mode: true etc. These are issued when Cocoon loads a sitemap component. - 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] Commented: (FOR-505) Allow the retrieval of raw html files
The following comment has been added to this issue: Author: David Crossley Created: Mon, 30 May 2005 8:41 PM Body: Discussion about a solution is at: http://marc.theaimsgroup.com/?t=11169681410 - View this comment: http://issues.cocoondev.org//browse/FOR-505?page=comments#action_12453 - View the issue: http://issues.cocoondev.org//browse/FOR-505 Here is an overview of the issue: - Key: FOR-505 Summary: Allow the retrieval of raw html files Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Versions: 0.7-dev Assignee: Reporter: Ross Gardler Created: Tue, 24 May 2005 3:53 PM Updated: Mon, 30 May 2005 8:41 PM Description: With the merging of the raw content directory and the xdocs directory it is no longer possible to retrieve the raw, unprocessed version of an HTML file. The raw HTML files were removed from the fresh-site in revision 178279. When we have added support for raw HTML files back into the system we should revive these files as a demo. - 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: [JIRA] Created: (FOR-505) Allow the retrieval of raw html files
Ross Gardler wrote: [ snip ] We could add a new skinconf property to define the behaviour for *.html files in xdocs we can tell people affected by this issue to make their embedded content ihtml and their raw content html. i.e. !-- HTML files in the XDoc directory can wither be passed unprocessed to the client, or they can be skinned like any other content. If you set this setting to false, you can include skinned files by giving them the ihtml extension. -- skinHTMLSourcestrue/skinHTMLSources The result is, setting skinHTML to false will give the same behaviour as 0.6 We could make this the default in order to minimise the upgrade behaviour. If we implement this workaround, then i reckon that the default should be true. It would be easier to explain the false case and it would be a smaller number of people affected. However, it forces them to change their filename extensions. That would be difficult for the main use-case, which is to include a set of existing *.html docs as part of the site. The thread RT: RAW content that is linked from issue FOR-505 ended with an interesting idea about using site.xml to specify exclude/include patterns. http://marc.theaimsgroup.com/?l=forrest-devm=110172196321097 It seems to be independent from the locationmap ideas discussed earlier in that thread. Would that be better to implement now, rather than the skinHTMLSources=true workaround? --David
Re: Meetup at ApacheCon? -- Room nearby!
Ross Gardler wrote: Ferdinand Soethe wrote: Johannes Schaefer wrote: Good news: we can have a room at the FHT for the evenings, thanks to Prof. Hauber. Hey this is great news. Thanks to Johannes and Peter for solving this problem for us. We'll need to decide when we'll meet. OK, I suggest to have - the general Forrest Meetup on Wednesday evening (the day of our Forrest presentation) so that people can come and ask more questions ... - the views-workshop on Thursday so that people won't have to hang around for all three days of the conference. With Johannes' mail saying evenings (plural) I'd gratefully take the offered room for both evenings to not exclude people. If that is not stretching Peter's hospitality too far? Would 19:00 hrs be good time to start? I'm off-line till Wednesday. Since some people need to arrange for their travel we should decide soon. So how about taking the time to comment until Wednesday so we can finalize the arrangements this week? I like your proposal, if it needs to change to accommodate other people that is fine by me. I will be in Germany for about a week in total. Most of it I will not be in Stuttgart however, I will ensure I am present when there is anything Forrest going on. (Below I'll include the agenda for both meetings from previous mail.) -- Ferdinand Soethe We General Exchange on Forrest an opportunity for Forrest users and developers to meet and have an open exchange about Forrest. If we have enough people committed to participating, we could/should we announce this meeting in our Forrest session for interested people to join us. It is possible that we will not have many non-Forrest people taking this up. If this is the case I would like to use this time to do some forward planning and bug fixing. Will there be net access in this room? I see this as being compatible with an open exchange with potential users and devs as we can ask what peoples use cases are and discuss whether Forrest should/would be considered for that use case. In cases where Forrest seems appropriate we can look at what changes need to be made. Th Workshop Forrest Views with Thorsten explaining the concept and practical details of his Forrest-Views and plenty of opportunity to ask questions. My hope is that I will have a chance to understand Views after that which means that we will address people with a limited understanding of Forrest and Plug-ins. Duration: ~ 2 hrs? I propose no changes at all to this part of the agenda. Views is key to the next release of Forrest and will, I think, finally see us moving to a subset of XHTML2 as the internal. This should be a purely design focused meeting. I agree with all of those aims. However i propose a different schedule so that we fit in better with the ApacheCon events, especially the Welcoming Reception and the official Birds of a Feather (BoF) sessions. http://apachecon.com/2005/EU/html/sessions.html Event: Apache Committers Hackathon Date: Tuesday Location: ApacheCon Topics: Meet other committers. Open discussion. Bug fixing. Audience: Committers only. Event: Apache Forrest project workshop Date: Tuesday 19:00 until whenever. Location: The HfT room. Topics: Views, XHTML internal format, project planning. Audience: Anyone is welcome, but discussions will be technical and will assume knowledge of Forrest. We will certainly answer questions to ensure that people understand background. However the main aim is an intensive project design session. Event: Apache Forrest get together Date: Wednesday 20:00 until whenever Location: The HfT room. Topics: Open discussions. Audience: Anyone. Event: Apache Forrest Birds of a Feather (BoF) session Date: Thursday 20:00 until 21:00 Location: ApacheCon Topics: Open discussions. Audience: Conference attendees.
