Re: New Plugin: Filtering output
Ferdinand Soethe wrote: Working on our presentation for ApacheCon, Ross and I have the problem that the presentation contains a lot of internal info and also some that should only be part of someversions (speaker version, slide version, printed notes). They are marked up with class attributes, so filtering is possible, the question is where. And since filtering might vary on a per document basis, I was wondering whether we could have a filtering plugin that can be applied before any other output plugin and apply the filtering needed. Ideally the criteria would be defined in the site element. So instead of my current version (that opens the presentation as a normal Forrest document as well as an s5-slideshow) apachecon label=ApacheCon slides label=slides href=s5slides/ssp_with_forrest.html/ slides label=document href=ssp_with_forrest.html/ /apachecon I could then have apachecon label=ApacheCon slides label=Slides href=s5slides/ssp_with_forrest.html filter=cleanSlides.xsl/ slides label=Slides href=s5slides/ssp_with_forrest.html filter=speakerSlides.xsl/ slides label=document href=ssp_with_forrest.html filter=printedVersion.xsl/ /apachecon I asked this question before, but there was a flurry of activity at the time and i don't think that there was a reply. I don't understand how those site entries would get used for linking. They are all the same. a href=site:apachecon/slidesclean/a a href=site:apachecon/slidesspeaker/a a href=site:apachecon/slidesprint/a --David where the xsl-files contain the desired filter. Am I thinking along the right track here or are there better ways to do this. I first wanted to create this as output plugin, but since all there is is custom xsl which can be different for each file, I didn't think this would made a lot of sense. -- Ferdinand Soethe
Re: New Plugin: Filtering output
Just another use case and some more RTs. We are writing styleguides with forrest. Application developers need less information than component developers, so we are offering different versions for both. Now we do this with two separate project sitemaps to create the (static) output. We would happily adopt some live filtering. In our case it's more like we do know what info is not needed for a specific user group and so we drop it in a first transformation step (i.e. from a specialized DTD to DocBook). Thus the filtering applies only to specialized parts of the document (e.g. matches **-ABC.html) and the rest is handled normally. There is no special markup (like class=dirCut/actorCut). Ideally the reader can adjust the filtering, like: give me all information about version A; give me my information about versions A, B, D. The information about this is in the specialized markup, so, theoretically it can be done. Our writers don't care about filtering, they provide the full information anyway (each one his/her bit). It's the admin or publisher who creates the published version(s). We would like to do 'forrest run' and access the versions using the same instance, e.g. like http://localhost:/app-dev/ and http://localhost:/core-dev/ (see also: http://issues.cocoondev.org/browse/FOR-490) I'd agree with Ross, that this is not a output/skinning step, but an internal one. For us it would be sooner than xdoc-skin because it'll be hard to preserve all the semantics up to the xdoc-format. Cheers Johannes Ferdinand Soethe schrieb: Two quick responses since I'm still working on the apachecon presentation: - I'm happy for this to be a part of views and I hope after apachecon I'll know how to use them for this purpose. - I agree that the filter could and perhaps should be configured as part of the configuration. ...and content writer != admin (site.xml) - I do not agree that editing site.xml is admin work as Thorsten seems to suggest since it is the only way a user can make Forrest show his page. - And since I (with the content writer hat) usually make the decisions about which file to show in which menu and what filter should be applied to it (e.g. show the directors version of Shakespeare in my 'Directors resources' menu while the full version is in the 'Popular Dramas') I (user) need a way simply apply a filter to a given resource. To determine which filters to apply to which resources (by the list of patterns in the plugin config that Ross suggested) does not seem an ideal solution to me as it requires an understanding of patterns that users don't usually have and also makes it much harder to see what will actually the outcome of a certain site.xml (because you have to also look at the filter patterns in the plugin (and apply that knowledge to site) to know what will actually show. Very difficult and not easy to maintain. I understand the objective not to extend site-grammar for every new plugin (and share it), but I'd raise the question if it wouldn't be a good idea to consider it at least for some basic operations like filtering, pdf-aggregation and ... And if that is not agreeable, to find some other way of keeping the selection of a given filter closely with the site-element. -- Ferdinand Soethe -- 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: New Plugin: Filtering output
David Crossley wrote: apachecon label=ApacheCon slides label=Slides href=s5slides/ssp_with_forrest.html filter=cleanSlides.xsl/ slides label=Slides href=s5slides/ssp_with_forrest.html filter=speakerSlides.xsl/ slides label=document href=ssp_with_forrest.html filter=printedVersion.xsl/ /apachecon I asked this question before, but there was a flurry of activity at the time and i don't think that there was a reply. I don't understand how those site entries would get used for linking. They are all the same. a href=site:apachecon/slidesclean/a a href=site:apachecon/slidesspeaker/a a href=site:apachecon/slidesprint/a Sorry, must have missed that. Of course you are right. The site excerpt should have been to enable linking. apachecon label=ApacheCon slidesClean label=Slides href=s5slides/ssp_with_forrest.html filter=cleanSlides.xsl/ slidesSpeaker label=Slides href=s5slides/ssp_with_forrest.html filter=speakerSlides.xsl/ slidesPrint label=document href=ssp_with_forrest.html filter=printedVersion.xsl/ /apachecon -- Ferdinand Soethe
Re: New Plugin: Filtering output
Johannes Schaefer wrote: Ideally the reader can adjust the filtering, like: give me all information about version A; give me my information about versions A, B, D. The information about this is in the specialized markup, so, theoretically it can be done. Yes, I'd like that as an option. Though sometimes you want that, other times you don't. Our writers don't care about filtering, they provide the full information anyway (each one his/her bit). It's the admin or publisher who creates the published version(s). If you call it publisher or editor I agree. But these are also content workers and not techies in most businesses I know. -- Ferdinand Soethe
Addi Berry is out of the office.
I will be out of the office starting 05/23/2005 and will not return until 05/31/2005. I will respond to your message when I return on Tuesday, May 31.
Re: New Plugin: Filtering output
Ferdinand Soethe wrote: David Crossley wrote: apachecon label=ApacheCon slides label=Slides href=s5slides/ssp_with_forrest.html filter=cleanSlides.xsl/ slides label=Slides href=s5slides/ssp_with_forrest.html filter=speakerSlides.xsl/ slides label=document href=ssp_with_forrest.html filter=printedVersion.xsl/ /apachecon I asked this question before, but there was a flurry of activity at the time and i don't think that there was a reply. I don't understand how those site entries would get used for linking. They are all the same. a href=site:apachecon/slidesclean/a a href=site:apachecon/slidesspeaker/a a href=site:apachecon/slidesprint/a Sorry, must have missed that. Of course you are right. The site excerpt should have been to enable linking. Doh! I missed that in my alternative approach too, thank goodness for many eyes when such a simple issue can get overlooked. However, Thorstens,method seems to address that issue. I'm going to come back to this after we have submitted the Apachecon presentation. I'd like to see how Thorstens work integrates with locationmap as that is the next thing I need in Forrest. It makes using things like Daisy or Lenya far easier and may be the ideal place for view configurations like this one. I'll catch up with Thorstens recent RT's and try and bring the locationmap idea into them. Ross
Re: Plugin error - no internet available
[moved to dev list, CC'd to users so readers there know the discussion has moved, replies will go to the dev list] David Crossley wrote: , Mark Eggers wrote: Addi wrote: ...be able to download plugins. Is there any way for me to download the plugin files and transfer them to the laptop? Any other workarounds? I don't know about the snapshot. If you use subversion to check out the current Forrest environment, you'll get a directory $FORREST_HOME/plugins In there, you should find the source to all of the plugins. ... I typically do an svn update, build clean, build, cd to the plugins and then ant local-deploy each plugin. I wish there was an easier way of building and deploying all of the plugins. Maybe that's a good candidate for an enhancement suggestion. Since the plugins exist in the subversion checkout, maybe the main build script could check for the plugins and build them locally (or as a separate ant task). This would not work for released versions as they do not have the source available and the whole idea of plugins is to only provide the functionality needed. There isn't really anything we can do about that, it is possible for the user to manually download the plugins and they will never have to repeat this process again since the plugins are cached locally. For devs using SVN head or the snapshots we do need something better than the current approach. It is proposed that the system will look for the plugin source locally and not require them to be brought into the build directory of Forrest if they are available. In other words, if you have the source version of Forrest you would not need the do anything special, the plugins would be used in place. However, a quick hack would be as Mark suggests, have the Forrest build scripts build all the available plugins in the distribution (FORREST_HOME/plugins and FORREST_HOME/whiteboard/plugins) So who knows how to make ANT iterate over a set of subdirectories and call a target on a build.xml file within. A new local-deploy-all target should be added to the plugins build.xml and this should be called by the Forrest build target. Thanks to all those people that are using 0.7-dev and providing feedback. Let me echo that. It is great to see users helping out in this way, it is a very valuable contribution to Forrest. Ross
Re: Meetup at ApacheCon?
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. --David
Re: Meetup at ApacheCon?
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. :) salu2 -- thorsten Together we stand, divided we fall! Hey you (Pink Floyd)
AW: Meetup at ApacheCon?
Title: AW: Meetup at ApacheCon? I hope I can update my Forrest knowledge from 0.4 to 0.7 at the Con :-) See you there Jan -Ursprüngliche Nachricht- Von: Thorsten Scherler [mailto:[EMAIL PROTECTED]] Gesendet am: Montag, 23. Mai 2005 14:43 An: dev@forrest.apache.org Betreff: Re: Meetup at ApacheCon? 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. :) salu2 -- thorsten Together we stand, divided we fall! Hey you (Pink Floyd)
cocoon 2.2 infos
Hi! Where can I find information about Cocoon 2.2? Wasn't sucessful at cocoon.a.o Thanks! Johannes -- 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: cocoon 2.2 infos
Johannes Schaefer wrote: Where can I find information about Cocoon 2.2? Wasn't sucessful at cocoon.a.o There aren't any published docs because it is not yet released. They are actually re-organising the docs in the trunk. You would be best to stick with the 2.1 docs. That should cover most of what you need to know. Gee i hope we don't lose you, the cocoon docs is huge. Are you looking for anything in particular? Perhaps we can guide you. Don't forget the Forrest sitemap-ref.html which explains some things and links to relevant Cocoon docs. --David
Re: cocoon 2.2 infos
You won't loose me, we'll meet in Stuttgart! I'm looking into Cocoon to use for another project (not forrest-related). Maybe I'll deepen my knowledge in Forrest this way until I come back to use Forrest again extensively. Is there a minimalistic example I can use to see how to build a simple web-app with Cocoon? Thanks again! Johannes David Crossley schrieb: Johannes Schaefer wrote: Where can I find information about Cocoon 2.2? Wasn't sucessful at cocoon.a.o There aren't any published docs because it is not yet released. They are actually re-organising the docs in the trunk. You would be best to stick with the 2.1 docs. That should cover most of what you need to know. Gee i hope we don't lose you, the cocoon docs is huge. Are you looking for anything in particular? Perhaps we can guide you. Don't forget the Forrest sitemap-ref.html which explains some things and links to relevant Cocoon docs. --David -- 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
committer trouble deploying plugins
Can any other committer deploy any plugins to the server? I am having trouble. The dtdx plugin changed the other day when its jars were moved from the core, but it wasn't deployed. The first time that i run 'tools/ant/bin/ant deploy' there are a heap of already under version control messages. The second time it is run, i get 'svn add' errors. --David
Re: committer trouble deploying plugins
David Crossley wrote: Can any other committer deploy any plugins to the server? I am having trouble. The dtdx plugin changed the other day when its jars were moved from the core, but it wasn't deployed. The first time that i run 'tools/ant/bin/ant deploy' there are a heap of already under version control messages. The second time it is run, i get 'svn add' errors. The plugins have been deployed by you (see SVN commit mails). The output you are seeing appears to be a result of the way that the SVN ANT tasks work. I've never tried to debug it as I have got used to it. However, it is clearly misleading. Perhaps we need to raise an issue. Ross
Re: Meetup at ApacheCon?
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
Re: committer trouble deploying plugins
Ross Gardler wrote: David Crossley wrote: Can any other committer deploy any plugins to the server? I am having trouble. The dtdx plugin changed the other day when its jars were moved from the core, but it wasn't deployed. The first time that i run 'tools/ant/bin/ant deploy' there are a heap of already under version control messages. The second time it is run, i get 'svn add' errors. The plugins have been deployed by you (see SVN commit mails). Yeah, i saw that and became even more confused. The output you are seeing appears to be a result of the way that the SVN ANT tasks work. I've never tried to debug it as I have got used to it. However, it is clearly misleading. Perhaps we need to raise an issue. This is strange, because it didn't happen to me a couple of weeks ago when i was developing the dtdx and listLocations plugins. --David
Re: cocoon 2.2 infos
Guess I'm up and running Cocoon now ... thanks again! Johannes David Crossley schrieb: Johannes Schaefer wrote: You won't loose me, we'll meet in Stuttgart! :-) Looking forward to that. I'm looking into Cocoon to use for another project (not forrest-related). Maybe I'll deepen my knowledge in Forrest this way until I come back to use Forrest again extensively. Is there a minimalistic example I can use to see how to build a simple web-app with Cocoon? Thanks again! Ah, then download Cocoon, either trunk of SVN (2.2) or 2.1 branch and look at some Samples, e.g. Supersonic Tour block. Also there is wiki.apache.org/cocoon which has some minimal examples. --David -- 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: committer trouble deploying plugins
David Crossley wrote: Ross Gardler wrote: David Crossley wrote: Can any other committer deploy any plugins to the server? I am having trouble. The dtdx plugin changed the other day when its jars were moved from the core, but it wasn't deployed. The first time that i run 'tools/ant/bin/ant deploy' there are a heap of already under version control messages. The second time it is run, i get 'svn add' errors. The plugins have been deployed by you (see SVN commit mails). Yeah, i saw that and became even more confused. The output you are seeing appears to be a result of the way that the SVN ANT tasks work. I've never tried to debug it as I have got used to it. However, it is clearly misleading. Perhaps we need to raise an issue. This is strange, because it didn't happen to me a couple of weeks ago when i was developing the dtdx and listLocations plugins. I think it is all to do with there being subsequent deployments, or it could be to do with the newly added docs uploading. I'll do some investigation when I get the time. Ross
Self documenting sitemaps
This snippet from a mail on Cocoon Dev will be interesting to those wishing to improve our sitemap documentation. Original Message From: Bertrand Delacretaz [EMAIL PROTECTED] Subject: Re: [PlanetCocoon] 4 new ideas to discuss on Planet Cocoon Date: Mon, 23 May 2005 20:44:06 +0200 To: dev@cocoon.apache.org Le 23 mai 05, à 20:33, Sebastien Arbogast a écrit : ...finally it appears it's not as interesting as I thought at the beginning because current samples are code only whereas we think code-illustrated documentation is what we need most... Sure. Note that I just applied a patch to both the 2.1 branch and the trunk, which allows you to add annotation to sitemaps, like: map:match pattern=news.pdf n:explainGet news in XML from server/n:explain map:generate src=http://newsserver/somestuff.xml/ n:explainConvert to xsl-fo/n:explain map:transform src=news-to-fo.xsl/ n:explain And let a href=http://xml.apache.org/fop;FOP/a generate PDF /n:explain map:serialize type=fo2pdf/ /map:match This could be very useful to create self-describing samples. There's also stuff in the tour block that could be reused to extract code excerpts from sitemaps, xml and text files. -Bertrand
Re: committer trouble deploying plugins
Ross Gardler wrote: I think it is all to do with there being subsequent deployments, or it could be to do with the newly added docs uploading. I'll do some investigation when I get the time. :-) I reckon that it is the latter, because i was doing subsequent deployments okay before the addition of the docs deployment. --David
[JIRA] Created: (FOR-502) Forrest Plugin in eclipse 3.0.2 requires FORREST_HOME path set but it is not handled properly
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-502
Here is an overview of the issue:
-
Key: FOR-502
Summary: Forrest Plugin in eclipse 3.0.2 requires FORREST_HOME path set but
it is not handled properly
Type: Bug
Status: Unassigned
Priority: Critical
Project: Forrest
Components:
Tool: Eclipse config
Versions:
0.6
0.7-dev
Assignee:
Reporter: Praveen Bhatia
Created: Mon, 23 May 2005 8:08 PM
Updated: Mon, 23 May 2005 8:08 PM
Environment: eclipse 3.0.2, Forrest 0.7
Description:
I could export the plugin to eclipse. The 'seed' and 'new xdoc' option for the
site menuitem worked. However, Trying, to run the forrest xdoc files in server,
gives error..
First, eclipse forrest plugin asks the preferences for forrest home to be set
for the plugin.
Now if we set c:\forrest as the Forrest Home, it can locate the
forrest.build.xml, but then gives the following error from the server:
CASE 1: If we set FORREST_HOME=C:\forrest in preferences and the FORREST_HOME
variable in cmd shell:
==
C:\forrest\main\forrest.build.xml:63: C:\forrest\main\C:\forrest\lib\core
not found.
at
org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileS
et.java:342)
at org.apache.tools.ant.types.Path.list(Path.java:331)
CASE 2: To avoid the above problem, left the cmd line setting blank.
However, this also gives error. Error when FORREST_HOME is left blank in cmd
shell, but set as c:\forrest in the preferences ==
C:\forrest\main\forrest.build.xml:63:
C:\forrest\main\{$env.FORREST_HOME}\lib\core not found.
at
org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileS
et.java:342)
at org.apache.tools.ant.types.Path.list(Path.java:331)
-
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-503) org.burrokeet.serveletEngine required for eclipse plugin to forrest
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-503 Here is an overview of the issue: - Key: FOR-503 Summary: org.burrokeet.serveletEngine required for eclipse plugin to forrest Type: Improvement Status: Unassigned Priority: Blocker Project: Forrest Components: Compile Versions: 0.6 0.7-dev Assignee: Reporter: Praveen Bhatia Created: Mon, 23 May 2005 8:12 PM Updated: Mon, 23 May 2005 8:12 PM Environment: eclipse 3.* forrest 0.6, 0.7 Description: org.burrokeet.serveletEngine is required for the plugin for eclipse. However, there are no instructions mentioned that needs to be downloaded seperately. Best if it could be bundled with the plugin itself. - 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
