[16:06] » You changed the topic to "finish locationmap, clean up Jira, prioritise issues for next release, more xhtml2 dev, Dispatcher + docs.". [18:42] » JennyCurran joined the chat room. [18:43] » tscherler joined the chat room. [18:43] » cheche joined the chat room. [18:43] cheche: good morning... [18:43] tscherler: hi [18:44] tscherler: cheche at what time you will come to my home? [18:44] xley: g'day [18:44] tscherler: hi david [18:45] tscherler: BTW [18:45] tscherler: > Thanks David, you are now the official dispatcher "profiler" for me (no [18:45] tscherler: > strings attached). ;-) [18:45] tscherler: I see the smiley, but please, no. We all need to try [18:45] tscherler: to interpet it. [18:45] cheche: tscherler: I do not know ... but have you realied that it is going to be the 14th february [18:45] tscherler: It was a job [18:45] cheche: I do not want to ruin your dinner [18:45] tscherler: if you keep on comment this like you did I will not do them anymore [18:45] tscherler: what is a petty [18:45] tscherler: smilling is good [18:46] tscherler: ;-) [18:46] tscherler: cheche [18:46] tscherler: no worries [18:46] tscherler: I am married now 6 years ;-) [18:47] tscherler: (08:45:27) tscherler: It was a job-> should read it was a joke [18:47] cheche: ok, so possibly around 9 pm [18:48] cheche: http://casa.che-che.com/~bot/forrest/forrest.log.10Feb2006 [18:48] cheche: that is the live log [18:48] tscherler: k [18:48] tscherler: looking forward dude [18:50] cheche: I am a bit sad about forrest... [18:50] cheche: I was doing a web site for a customer [18:50] tscherler: why? [18:50] cheche: http://www.cesarnieto.com/ [18:51] cheche: I did it using forrest v.07 [18:51] cheche: and I ask a css programer to help me with the site [18:51] cheche: I have got an email yesterday from him [18:52] tscherler: and? [18:52] cheche: he said that it was the most complex css code that he ever saw [18:52] cheche: and he quit for the job :-) [18:53] tscherler: lol [18:53] tscherler: but it was not jose, or? [18:53] cheche: no, it was not jose [18:53] tscherler: k [18:53] cheche: it was other person that I contact before jose [18:53] cheche: jose does not seem an expert on css code [18:53] tscherler: the css was growing [18:54] tscherler: yeah can be [18:54] tscherler: I had feeling once ;-) [18:55] cheche: well, that was with the old version [18:55] cheche: is the dispatcher going to help in this way? [19:00] cheche: xley: about the user moderation policy [19:00] cheche: I am ok with the new changes. [19:01] xley: okay, as you can see i don't know much about moderation, so just stumble along [19:01] cheche: but I think that when a new email comes to the moderation state,, should sent an email to the person asking to sned an email to user-subcribe@forrest.apache.org [19:02] cheche: xley: can I add www.cesarnieto.com as en example site? [19:02] xley: better if they do. [19:02] xley: sure please do [19:03] cheche: but It has his own skin and a lot of modifications [19:03] xley: no problem, it is still an example of what can be done. [19:03] cheche: ok then [19:04] tscherler: cheche yes and no [19:04] tscherler: the css codes is not rewritten for the dispatcher [19:04] tscherler: but it would make sense [19:05] tscherler: it makes it way easier for a designer to change everything but still you need to do it ;-) [19:05] tscherler: k [19:05] tscherler: I will have to run [19:05] tscherler: will be back in 1 hour cu [19:05] cheche: cu [19:06] cheche: for the next project, I am going to try the dispacher and use this person to modify the css. [19:06] cheche: It is an experiment [19:06] tscherler: :) [19:15] cheche: added cesarnieto.com [19:16] cheche: I have to go, I will try to find a bit of time latter on... is everything ok xley? [19:17] xley: yes thanks cheche, see you later. [19:32] » tscherler left the chat room. (Read error: 110 (Connection timed out)) [19:42] » _Gav_ joined the chat room. [19:45] _Gav_: Afternoon [19:48] xley: Hi Gavin, i am just heading off for dinner, back later. [19:49] xley: http://casa.che-che.com/~bot/forrest/forrest.log.10Feb2006 [19:50] _Gav_: thanks [19:50] _Gav_: I'll work on pelt.fv if no-one else is [19:57] » Cyriaque joined the chat room. [20:03] _Gav_: Hi Cyriaque [20:04] Cyriaque: Hi [20:04] _Gav_: Hows things [20:04] _Gav_: log : http://casa.che-che.com/~bot/forrest/forrest.log.10Feb2006 [20:12] xley: Gav, you will make Cheche very pleased to tidy up the structure and the CSS of pelt.fv [20:12] xley: Hi Cyriaque [20:12] xley: dinner is cooking, back soon. [20:12] Cyriaque: Hi David [20:29] _Gav_: no problem, will do [21:01] » rgardler joined the chat room. [21:02] rgardler: Good morning/evening for anyone around. [21:02] rgardler: I'm going to be hear on and off today [21:02] rgardler: moving office and there has been a problem with the movers [21:02] rgardler: Whilst around I will be working on FOR-200 [21:04] xley: get those movers moving. [21:04] rgardler: they're moving now :-) [21:07] xley: Re: FOR-200 locationmap, our never-ending issue ... [21:08] xley: http://issues.apache.org/jira/browse/FOR-726 (lm in plugins) ... what is the story with the second-last comment [21:09] xley: "verify the version numbers in each plugin's build.xml (some use a -dev and some do not) and in plugins.xml" [21:09] rgardler: OK, I've been meaning to address that for a while, [21:09] rgardler: I need to check some of the install code [21:09] rgardler: I know I *planne* something, not sure if I implemented it [21:09] rgardler: looking now - back soon [21:10] rgardler: (planne = planned) [21:10] xley: i will look too. [21:11] rgardler: I have a feeling the -dev means nothing - I think I went for no versionnumber meaning latest version in the end [21:11] xley: i wondered that too. [21:13] rgardler: I see no occurance of "dev" in plugins.xml (the build file) [21:13] rgardler: therefore my conclusion is that I did go for no version number in the end [21:13] rgardler: therefore we should *not* have "-dev" extensions [21:13] xley: i did find and grep "\-dev" in main ... nothing that seems relevant. [21:14] rgardler: (OT my son just ate his first breakfast without assistane - applause for my son - who now need to be cleaned up) [21:14] rgardler: looking at main... [21:14] xley: okay i will go any fix that aspect [21:15] rgardler: I only see "dev" in the context of Forrest core version numbers so we seem to agree [21:16] rgardler: Going to clean zeph, back in 10 mnutes, then on with FOR-711 (LM caching) [22:01] xley: Ross, when you are back, i would like to have a talk about plugin deployment. [22:01] rgardler: I'm back - give me a few minutes to write some notes on what I have discovered re FOR-711 - 2 minutes [22:02] xley: k [22:05] _Gav_: Ive been out, back to work on Pelt theme, should I work directly in plugin directory on this, or deploy it to a test site [22:05] _Gav_: What concerns has cheche with this [22:05] xley: do both [22:06] _Gav_: ok cheers [22:06] xley: cheche might be back later today. [22:06] _Gav_: ok [22:10] rgardler: OK, David, fire away [22:11] xley: about plugin deployment ... [22:11] xley: we have talked about this once before (cannot yet find it) [22:12] xley: anyway ... [22:12] xley: http://svn.apache.org/repos/asf/forrest/site/plugins/ [22:12] xley: I presume that the 0.8-dev directory is a mistake caused by [22:12] xley: the badly named version numbers in the plugins/*/build.xml files. [22:12] xley: Fixed now so i suppose that can be removed. [22:12] xley: ... [22:13] rgardler: No... [22:13] xley: tell me [22:13] rgardler: I think we may have been at cross-purposes earlier [22:13] rgardler: I was talking about -dev extension to plugin names [22:13] rgardler: were you talking about -dev on the forrest version? [22:14] xley: i also about -dev extension to plugin names ... [22:14] rgardler: OK [22:14] xley: the -dev on the forrest version is related ... [22:14] rgardler: So the 0.8-dev directory is the Forrest core version [22:14] rgardler: when we release 0.8 that becomes 0.8 (loses the -dev) [22:14] xley: because that is where the end up being deployed, gotta get both right. [22:15] rgardler: Can we remove the confusion? Just drop -dev in both cases? [22:15] » twilliams_ joined the chat room. [22:15] xley: that is what i wondered too [22:15] rgardler: I think we can... some background... [22:16] rgardler: I used the -dev extension (for core) so it matched what is in the docs [22:16] rgardler: So, dropping it will make it the *only* place we don't use -dev [22:16] rgardler: But will simplify the release process [22:17] xley: so what are the zips at the top-level then? [22:17] rgardler: The top level zips are the current dev version [22:18] rgardler: I think it is a throw back to pre-versioned plugins [22:18] rgardler: would have to verify the download process [22:18] rgardler: we should be able to lose them now [22:18] rgardler: No.. just remembered [22:19] xley: :-) glad that we are talking about it [22:19] rgardler: if you specificy a dev version (-dev) [22:19] rgardler: it will (used to?) always use the unversioned top level pugin [22:19] xley: http://casa.che-che.com/~bot/forrest/forrest.log.10Feb2006 [22:19] rgardler: thus it made no difference what forrest core version you used [22:20] rgardler: However, our eralier conversation seems to imply this is no longer the case [22:20] rgardler: (I wish I could remember everything I've done - reviewing commit logs now) [22:21] rgardler: (By the way Hi Tim. When you get chance can you review my comments on FOR-711) [22:22] xley: Hi Tim (had to keep that conversation with Ross going). [22:23] rgardler: Original deployment code at: [22:23] rgardler: http://svn.apache.org/viewcvs.cgi/forrest/trunk/plugins/build.xml?rev=105856&r1=76254&r2=105856&diff_format=h [22:24] rgardler: Versioned deployment code at [22:24] rgardler: http://svn.apache.org/viewcvs.cgi/forrest/trunk/plugins/build.xml?rev=189638&r1=189630&r2=189638&diff_format=h [22:24] twilliams_: hey everyone, just trying to catch up. i'll be mostly lurking -- have paid work to do today:( [22:25] rgardler: Another deplyment related commit [22:25] rgardler: http://svn.apache.org/viewcvs.cgi/forrest/trunk/plugins/build.xml?rev=189945&r1=189872&r2=189945&diff_format=h [22:25] rgardler: OK, now I'm going to try and decipher those commits ;-) [22:29] xley: about the forrest.version number in plugins/*/build.xml ... some had "0.8" and some had "0.8-dev". Now no "-dev". [22:29] rgardler: No "-dev" is good and agreed [22:29] rgardler: Regarding the top-level zips [22:30] rgardler: SVN is a wonderful tool: [22:30] rgardler: I found this: [22:30] rgardler: [22:30] rgardler: So I was remembering correctly... [22:30] rgardler: In summary... [22:30] xley: phew [22:30] rgardler: when an unversioned plugin is specified it *always* loads from [22:31] rgardler: the top level [22:31] rgardler: what should happen (above fixme) [22:31] rgardler: is that it looks in the highest forrest core version as that will be the highest dev version [22:31] rgardler: Does this make sense? [22:32] rgardler: i.e. pluginname-0.2 will look for 0.2 in the correct forrest core directory, but pluginname will look in the *latest* forrest core regardless of what the user is running [22:32] rgardler: (sounds wrong now I write it) [22:33] xley: why don't we have just directories. /0.7/ and /0.8/ and /0.9/ [22:34] rgardler: I'm leaning that way now, I'll explain my original thinking [22:34] rgardler: But I'll do it in a mail, needs a little thought to get the message across, [22:34] xley: okay. [22:36] rgardler: Wait no need for a mail, it's simpler than I thought... [22:36] rgardler: the above fixme is confusing me (I wrote it!) [22:36] xley: even better [22:37] rgardler: Use case: a user wants to have the cutting edge Foo plugin [22:37] rgardler: they specifcy o.a.f.p.i.foo in their forest properties (no version number) [22:37] rgardler: Since they want to be on the cutting edge they want to know when new features require an upgrade [22:37] rgardler: (of forrest core) [22:38] rgardler: so the plugi is downloaded from the top-level (no core version number) [22:38] rgardler: If local Forrest install can't run pugin it throws an error asking user to upgrade core or downgrade plugin version [22:38] rgardler: No user can specify a version number (say 0.2) [22:39] rgardler: this is deployed in the relevant forrest core folder (say 0.7) [22:39] rgardler: OR [22:39] rgardler: They continue to specify no number but upgrade to forrest 0.8-dev [22:39] rgardler: In other words, the versioned directories contain releases, the top level contains dev [22:40] rgardler: Make sense now? [22:43] xley: yes, i think that this is where were arrived at before. [22:43] xley: So at 0.8 release, we will do 'svn copy' those top-level zips into a new 0.8 directory. [22:44] rgardler: No, need... [22:44] rgardler: unversioned plugins always come from top level [22:45] rgardler: released (versioned) plugins will be deployed automatically into correct forrest core directory [22:45] xley: Ah, of course. [22:46] rgardler: So, it seems all we need to do is change the deploy code to remove the unversioned plugins from the versioned core directories [22:46] rgardler: and change the unversioned download to only use the top-level directory [22:46] rgardler: Both easy to do [22:47] » tscherler joined the chat room. [22:47] rgardler: "remove the unversioned plugins" = "do not deploy to versioned core" [22:47] _Gav_: hmm, after an 'svn up' it seems I have to re-apply dispatcher enabler patch [22:47] _Gav_: mr T, Just in time, hows things :) [22:47] rgardler: Morning Thorsten, tish on time for Gavs Dispatcher work ;-) [22:47] xley: rgardler: but hold on ... [22:49] tscherler: jeje [22:49] xley: Will we need to deploy an unversioned plugin to the top-level AND a copy with the relevant version number too into the /0.8/ directory? [22:49] tscherler: I just figured out that my connection time ot ;-) [22:49] tscherler: hi all [22:50] xley: hello [22:50] tscherler: [22:05] _Gav_: What concerns has cheche with this [22:50] tscherler: he said is way to verbose and I share this concern [22:50] rgardler: xley: my fixme regarding 2remove duplication" implies that at present we do need to duplicate, but we shouldn't, I agree [22:50] xley: gavin that should not happen on 'svn up' [22:50] rgardler: It's just a case of modifying the download code [22:50] tscherler: pelt has too much css files [22:51] xley: rgardler: no i think that we do need to. [22:51] _Gav_: ok, so simplify it to one css file maybe [22:51] rgardler: Oh, OK, why? [22:51] tscherler: we should try to have one/two static css and one dynamic css contract [22:52] _Gav_: xley: my thoughts too, but Im getting that error : Could not resolve locationmap location. [22:52] tscherler: further the naming is sometimes really spacy [22:52] tscherler: we should follow [22:52] xley: rgardler: after we release 0.8, there will need to be a versioned plugin there for future users. [22:53] tscherler: http://svn.apache.org/viewcvs.cgi/*checkout*/forrest/trunk/main/webapp/skins/leather-dev/contracts.initial.txt [22:53] tscherler: when ever possible [22:53] tscherler: The task involved are: [22:54] tscherler: 1) reduce css files (merge the files) [22:54] rgardler: xley: I misread your original question... [22:54] xley: gavin: do 'svn diff main/webapp/WEB-INF/xconf/forrest-core.xconf' [22:54] tscherler: 2) rename css elements and the corresponding structurer hooks/contracts [22:54] rgardler: You asked about unversioned in top-level and versioned in core version dirs [22:54] rgardler: I read unversioned in both [22:54] rgardler: SO... [22:55] rgardler: Yes, we will need an unversioned in top-level and versioned plugin in versioned core dir [22:55] tscherler: BTW rgardler I have heaps of problems to deploy the dispatcher plugins [22:55] rgardler: the top level unversioned plugin will be replaced, possibly with a version only compatible with 0.9-dev (for example) [22:55] tscherler: I spended some time on it now and I am close to give up [22:56] tscherler: there too much stuff going on where cannot find any logical explanation [22:56] rgardler: tcherler, I'm giving my son his dinner in a few minutes, drop some notes in an email, I'll look when I return [22:56] rgardler: xley: are we reaching a conclusion? [22:56] tscherler: it is actually still the same prob then before (already reported to ml) [22:56] xley: yes, done. [22:57] tscherler: the projectPlugin src stuff [22:57] _Gav_: xley: diff shows patch is still there, must have another problem theen [22:57] rgardler: tscherler - OK, will look when I return [22:57] tscherler: further it is a chicken and egg problem [22:57] tscherler: k thanks [22:57] rgardler: xley: thanks - I hope we are finally making this clear [22:58] xley: thanks too. [22:58] tscherler: I cannot deploy the dispatcher plugin without the themes one [22:58] rgardler: I recall writing a JIRA issue on rewriting this stuff to a Java ANT task, it is just too complicated in an ant build file [22:58] rgardler: (would probably help with Thorstens problem too) [22:58] tscherler: yeah [22:59] tscherler: I had a look and it scared me away ;-) [22:59] tscherler: but [22:59] tscherler: ANT has the *big* downside that you normally has to invoke it on the cli and restart [22:59] tscherler: do not like this [23:00] tscherler: should be done with an action that is triggered via an URI [23:00] tscherler: lenya has this awesome usecase framework where it is a pice of cake ;-) [23:06] xley: rgardler: regarding your comments at http://issues.apache.org/jira/browse/FOR-711 Cache results from the Locationmap [23:06] xley: the XMLFileModule seems to have its own cache and not using Cocoon's cache. [23:07] twilliams_: xley: I just added my thoughts on that;) [23:07] xley: which causes our issue ... finding number ... [23:08] twilliams_: for-591 i think [23:09] xley: yes [23:12] _Gav_: my problem sorted, used themes from whiteboard themer plugin, which seem to be the old versions now [23:13] _Gav_: copied updated themes from my site, cant remember where updated ones are [23:15] _Gav_: now next job then is to get pelt theme looking like pelt skin, then optimise [23:21] tscherler: _Gav_http://issues.apache.org/jira/browse/FOR-797 [23:21] tscherler: and http://issues.apache.org/jira/browse/FOR-787 [23:22] tscherler: have a look at http://issues.apache.org/jira/browse/FOR-787?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel [23:23] _Gav_: ok [23:23] tscherler: k [23:25] _Gav_: ah, ../themes.core there it is! [23:25] tscherler: ;-) [23:28] twilliams_: thorsten, when you say configure lm on a sitemap level, you mean locationmap level? [23:29] twilliams_: and not actual extensions to the sitemap grammar, right? [23:32] tscherler: no+ [23:33] tscherler: mom [23:33] tscherler: see our main sitemap [23:33] tscherler: you will find [23:33] tscherler: [23:33] tscherler: [23:33] tscherler: [23:33] tscherler: [23:33] tscherler: [23:33] tscherler: [23:33] tscherler: [23:33] tscherler: [23:33] tscherler: [23:34] tscherler: [23:34] tscherler: (13:33:34) tscherler: [23:34] tscherler: this both should be extended by forrest [23:34] tscherler: meaning [23:34] tscherler: using caching pipes will force lm to cache [23:35] tscherler: using non-caching will force lookup *not* in the cache [23:35] tscherler: if we do not want to extend the above classes we should create new implemetations [23:36] tscherler: that let us reuse it everywhere and implement a "update" pipe [23:36] tscherler: like [23:36] tscherler: requesting [23:36] xley: but what does that have to do with the ... ProfilingCachingProcessingPipeline stuff that you pasted above. [23:36] tscherler: ...?forceupdate=true [23:37] tscherler: laziness of c'p [23:37] tscherler: and [23:37] tscherler: actually to profile this work [23:37] tscherler: we need to extend those as well [23:37] tscherler: ...but that is not prio [23:38] rgardler: tscherler: I have a few minutes before my next task, which plugin am I trying to deploy for you? [23:38] tscherler: both dispatcher [23:39] tscherler: thanks very much [23:39] rgardler: yeah, but what are their names, I'm so confused about which plugin is which [23:39] tscherler: org.apache.forrest.themes.core [23:39] tscherler: org.apache.forrest.plugin.internal.dispatcher [23:39] rgardler: thanks [23:39] rgardler: report back soon [23:39] tscherler: de nada [23:39] tscherler: :) [23:39] tscherler: gracias [23:39] _Gav_: themes.core does not create themes directory in target site, will this change [23:40] tscherler: ø? incompatible encoding [23:40] tscherler: _Gav_ can you explain what u mean? [23:40] _Gav_: \forrest\whiteboard\plugins\org.apache.forrest.themes.core\themes\ [23:41] _Gav_: has all the pelt.fv etc and common.fv and all contracts [23:41] _Gav_: these are not recreated in a seed-sample [23:41] _Gav_: hmm, maybe thats why [23:42] tscherler: no [23:42] _Gav_: need a new target, seed-rc1 [23:42] tscherler: hmm [23:42] tscherler: or we need to update all seeds and add [23:42] _Gav_: otherwise manual copying of themes from ../themes.core is neccessary [23:42] tscherler: resource/themes [23:42] tscherler: no [23:43] tscherler: in a project you only override the original [23:43] twilliams_: sorry thorsten you've lost me. how/why would an input module extend a pipeline component? [23:43] tscherler: you do not need contract in your project [23:43] tscherler: twilliams_ [23:44] _Gav_: ok, so where does project.theme=pelt get contracts from? [23:44] tscherler: do not understand the question [23:44] tscherler: ah [23:44] tscherler: now I gues [23:44] tscherler: ok the pipe concepts sets some params [23:44] tscherler: that forces cocoon to ommit the cache [23:45] tscherler: now since it is a java class you can set the caching in the lm class via such a class, right? [23:45] tscherler: makes sense? [23:45] tscherler: (13:44:01) _Gav_: ok, so where does project.theme=pelt get contracts from? [23:45] tscherler: see the fallback mechanism [23:46] tscherler: moment [23:46] twilliams_: your just suggesting that the lm caching respect the context of the pipe that it's in (e.g. caching/non-caching)? [23:47] tscherler: yes [23:47] twilliams_: i thought you were suggesting actually change the LM Module to extend from Pipeline component and I wasn't getting why/how [23:47] twilliams_: Now that i understand what you're suggesting... [23:47] tscherler: no would be too much trouble ;-) [23:48] twilliams_: lm's can be referenced in different pipes indepedently, so i'm still not sure how that would work in reality [23:48] tscherler: _Gav_http://svn.apache.org/viewcvs.cgi/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/java/org/apache/forrest/dispatcher/acting/RecursiveDirectoryTraversalAction.java?view=markup [23:48] _Gav_: I understand the fallback of themes, and over-riding them in new themes, but if no themes directory exists in site structure.. [23:48] tscherler: http://svn.apache.org/viewcvs.cgi/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/locationmap.xml?view=markup [23:49] _Gav_: does it then fallback to pelt skin? [23:49] tscherler: skin [23:49] tscherler: no skins are dead in rc1 [23:50] tscherler: _Gav_ we are talking about contracts right? [23:50] _Gav_: yep [23:50] _Gav_: say I have a new seed-sample, it is created without a /resources/themes/* folder [23:50] twilliams_: in other words would lead to some indeterminate caching because of multiple references to the same hints [23:51] _Gav_: Tim, were keeping Thorsten busy [23:51] _Gav_: :) [23:51] tscherler: [23:51] tscherler: see below this _Gav_ it is in the dispatcher lm [23:51] tscherler: jeje [23:52] tscherler: (13:50:39) twilliams_: in other words would lead to some indeterminate caching because of multiple references to the same hints -> hmm I am not sure because I have to admit that I have not looked close enough into the classes [23:52] tscherler: but [23:52] _Gav_: so what would a noFT site look like - looks like a pelt site to me [23:52] tscherler: I think it will set a cocoon enviroment variable in the objectmodel [23:52] tscherler: or another place [23:52] twilliams_: _Gav_: Tim, were keeping Thorsten busy [23:53] twilliams_: and he thought he was going to have another peaceful FF [23:53] tscherler: that you can get in your class (somthing like: super.getCachingStatus) [23:53] tscherler: jeje [23:53] twilliams_: yeah i don't doubt i can get the name of the pipe [23:53] _Gav_: maybe I'll just get on with converting the theme and understand this bit later [23:54] twilliams_: pipeA is caching / pipeB is non-caching [23:54] tscherler: (13:52:34) _Gav_: so what would a noFT site look like - looks like a pelt site to me -> site? You mean contract. [23:54] twilliams_: pipeA refers to lm:my.resource and also pipeB refers to lm:my.resource [23:54] tscherler: the " If no implementation can be found we use the noFt (~ - no forrest:template) implementation" [23:55] tscherler: is used as fallback that the whole process is not failing if the requested contract is not found [23:55] tscherler: it is resulting in nothing [23:55] _Gav_: I did a forrest run on a seed-sample site that had no themes directory, and looked like pelt [23:56] tscherler: twilliams_ put can't you get the type of the pipe? [23:56] tscherler: better name [23:56] tscherler: no type was right: [23:56] tscherler: [23:57] tscherler: yeah [23:57] tscherler: _Gav_ because you activated pelt theme [23:57] tscherler: since it is not in your project we are using the plugin core contracts for pelt [23:57] twilliams_: type= is a friendly (e.g. user-determined name) right? [23:58] tscherler: ø? incompatible encoding [23:58] tscherler: no [23:58] _Gav_: hmm, how do you copy a quote in IRC [23:58] tscherler: You define it in the component configuration [23:58] tscherler: [23:59] tscherler: but yeah it is user defined [23:59] twilliams_: so i'd hate to depend on that in an input module [23:59] tscherler: on the naming you mean [23:59] twilliams_: and i don't see as where the pipes implement some caching interface either [23:59] twilliams_: right [00:00] tscherler: lemme have a look at the class [00:00] _Gav_: can I get rid of all those in pelt.fv [00:00] twilliams_: i think this all would be cleaner if we just let lm caching be independent of pipe caching [00:01] twilliams_: something like: [00:01] twilliams_: [00:01] twilliams_: *in* the lm [00:01] twilliams_: whereas right now the whole input module is either cached or not [00:02] twilliams_: of course by doing it that way we are, i think, limiting our ability to use the cocoon store too [00:03] twilliams_: .. which is where we ultimately want to move the caching to instead of our own implementation [00:03] tscherler: (14:00:31) _Gav_: can I get rid of all those in pelt.fv -> If they are in the contract explanation yes [00:03] tscherler: it needs to be somewhere [00:03] tscherler: but better in the description of the contract [00:04] tscherler: twilliams_ yeah [00:04] tscherler: but [00:04] tscherler: which is where we ultimately want to move the caching to instead of our own implementation [00:04] tscherler: yes [00:04] tscherler: I think it is better [00:04] _Gav_: Yes, there are quite a few 'live' uncommented ones there also, as part of a cleanup, do you want to keep them in there all commented out, or just remove them altogether in favour of using them only in css [00:05] tscherler: otherwise we will add too much different locators and reserving to much url spaces, or? [00:05] tscherler: (14:04:56) _Gav_: Yes, there are quite a few 'live' uncommented ones there also, as part of a cleanup, do you want to keep them in there all commented out, or just remove them altogether in favour of using them only in css ->ø? incompatible encoding [00:06] tscherler: sorry where and what? ;-) [00:06] _Gav_: in pelt.fv , in the section. [00:06] _Gav_: [00:06] _Gav_: [00:07] tscherler: yeah [00:07] _Gav_: and about 20 more, but they don't do anything. [00:07] tscherler: no they are coming as example [00:07] tscherler: if you see the names that are color schemes from other project [00:08] tscherler: we should keep them but move them to the branding-theme-profiler.ft [00:08] tscherler: in the description [00:08] tscherler: like [00:09] tscherler: --bla... Here are some color schemes that projects are using [00:09] tscherler: ... [00:09] tscherler: makes sense? [00:09] _Gav_: yes, so remove that property altogether from the contract implementation of pelt.fv? [00:10] _Gav_: (Beacuse it will then be empty) [00:10] tscherler: hmm [00:10] tscherler: should not [00:10] tscherler: ah [00:10] tscherler: right [00:10] tscherler: that depends [00:11] tscherler: if forrest want to deliver with the lenya style or with the forrest one [00:11] tscherler: if with forrest style we need the contract [00:11] tscherler: and the color section of forrest [00:12] _Gav_: contract can stay, remove that [00:12] _Gav_: [00:12] _Gav_: oops [00:12] _Gav_: wrong paste [00:12] xley: the forrest scheme was the one that i documented fully in the old skinconf.xml [00:12] _Gav_: leave contract in there, just remove [00:13] _Gav_: maybe leave one sample in there [00:13] _Gav_: [00:14] tscherler: hmm [00:14] tscherler: xley wdyt? [00:14] _Gav_: and leave a comment to point to the .ft contract where the rest will be moved to? [00:14] xley: Gav: why is there a space problem with too many examples? [00:15] _Gav_: Just an idea for cleanup of files, there got to be at least 150 lines in there commented out as examples [00:15] _Gav_: too many I think [00:15] xley: users lose examples [00:15] xley: lose = love [00:15] xley: haha funny typo [00:16] _Gav_: but so many examples saying the same thing [00:17] xley: It is hard job working out a color scheme, so some examples are good. [00:17] _Gav_: ok, lines 33 to 181 are examples, I'll leave them there then and carry on. [00:18] xley: how many, i don't know, at least two sets. [00:19] tscherler: (14:08:20) tscherler: we should keep them but move them to the branding-theme-profiler.ft [00:19] tscherler: I reckon one is enough [00:19] tscherler: if the rest is in the contract desc. [00:19] _Gav_: I just thought leaving CSS examples in pelt.fv would detract from using them elsewhere, like .ft or .css files [00:21] _Gav_: ok, I'll leave a few and move the rest [00:23] » kronenpj joined the chat room. [00:30] rgardler: tscherler: Sorry got distracted by other things [00:30] rgardler: Howver, I just deployed the dispatcher plugin [00:30] rgardler: Are you ready to kick yourself? [00:31] tscherler: lol [00:31] tscherler: yeah always [00:31] rgardler: You forgot to include the pdf plugin therefore the site couldn't build [00:31] tscherler: hi paul [00:31] tscherler: grr [00:31] rgardler: Hi paul [00:31] tscherler: and the project plugin [00:31] tscherler: did it not request src/java? [00:31] tscherler: if not [00:32] tscherler: did you tried on a fresh checkout of trunk [00:32] tscherler: or do you have locally modified files in the trunk? [00:33] rgardler: It should never request src/java there is a check for this (see mail thread) [00:33] rgardler: I have no local modifications that would affect things I am aware of... [00:33] rgardler: checking now [00:34] tscherler: hmm [00:34] tscherler: that is weird [00:34] tscherler: why do I alwasy get this message [00:37] rgardler: Just checked - I have no local mods [00:37] tscherler: hmm [00:37] rgardler: I've not tried deploying the them.core yey [00:37] rgardler: doing that now [00:37] tscherler: is the project plugin activated? [00:37] rgardler: what is "the project plugin"? [00:37] tscherler: thanks a million rgardler [00:38] tscherler: project info [00:38] tscherler: mom [00:38] rgardler: Yes, why? [00:38] tscherler: org.apache.forrest.plugin.input.projectInfo [00:38] tscherler: hmm [00:38] tscherler: very weird [00:38] twilliams_: mom? [00:38] tscherler: do you use ant from forrest [00:38] tscherler: mom=moment [00:38] tscherler: ;-) [00:39] rgardler: just checked which ant is default and it is *not* forrests (never knew this) [00:39] rgardler: testig using forrests ant [00:41] rgardler: you also had the wrong forrest version in build.xml (this is not a cause of your issues though) [00:43] rgardler: worked OK with Forrests ant too [00:43] tscherler: thanks for helping out will have a close look of all your changes to the plugins [00:43] tscherler: hmm [00:43] tscherler: then I have something fishy [00:44] tscherler: thanks for testing it again [00:44] rgardler: No problem, I'll deploy the themer plugin as well [00:44] tscherler: themes ;-) [00:44] tscherler: themes.core [00:44] rgardler: yes [00:44] tscherler: themer is *old* [00:44] tscherler: btw can I remove coat [00:45] tscherler: it is obsolete now, because it is in the themes.core [00:45] rgardler: as long as it is in core that is fine by me [00:45] kronenpj: Hi guys, got distracted too... [00:46] rgardler: tscherler: I have a break on changes.rss and changes.pdf in themes.core - investigating [00:46] xley: hi Paul [00:46] tscherler: k [00:46] tscherler: thx [00:47] * tscherler is happy that ross now seems to see his problem [00:51] rgardler: *my* problem ;-) [00:53] * kronenpj shrugs [00:54] tscherler: jeje [00:54] _Gav_: is forrest.apache using pelt skin, I have pelt theme to alter to match and cant see what it looks like now [00:55] rgardler: Gav: pelt skin [00:55] rgardler: Thorsten: *my* problem (translation - *your* problem) is... [00:55] rgardler: changes.rss uses [00:56] rgardler: theme.core has no status.xml [00:56] rgardler: (sorry skinconf.xml) [00:56] _Gav_: FOR:811 need a theme that closely resembles the pelt skin [00:56] rgardler: (forgot smiley on your problem/my problem comment) [00:57] tscherler: lol rgardler [00:57] tscherler: yeah [00:57] rgardler: thscerler, we can replace the depndency on skinconf.xml with a plugin supplied property for the projectInfo plugin [00:57] tscherler: why (14:55:58) rgardler: changes.rss uses [00:57] tscherler: k [00:58] tscherler: skinconf should be gone with dispatcher/themes [00:58] rgardler: Ceating an issue for it against your control issue [00:58] tscherler: k [00:58] tscherler: thx [00:59] xley: tscherler: i notice from the Cocoon Profiler that dispatcher still requests skinconf.xml [00:59] rgardler: could be for requests for changes.rss? [00:59] tscherler: the whole problem is that the dispacther is still builded on top of cocoon [01:00] tscherler: there a *many* pipes in core that request skinconf [01:00] tscherler: I can either rewrite the forrest core with the dispatcher or wait till we depreceate skins [01:01] tscherler: I have rewritten big parts of the core but some still needs fixes [01:01] tscherler: that is as well the reason that I think the build time is nearly the double [01:01] tscherler: (14:59:56) tscherler: the whole problem is that the dispacther is still builded on top of cocoon -> forrest I mena [01:02] rgardler: I think we need to take that to the mailing list [01:03] tscherler: +1 [01:03] xley: _Gav_: what is the problem (i don't understand your comment "_Gav_: is forrest.apache using pelt skin, I have pelt theme to alter to match and cant see what it looks like now" [01:12] _Gav_: Just that I wanted a rendered pelt skin site to look at whilst I change the pelt theme to match [01:12] _Gav_: Also, MOTD options dont seem to work any more [01:13] _Gav_: e.g. - If MOTD option is 'page' is will still appear in navigation if thats where the contract is. [01:13] _Gav_: So , maybe no need for the options any more ? [01:13] tscherler: where in skins or themes? [01:13] _Gav_: themes [01:13] tscherler: yeah [01:13] xley: use either our site-author or a seed-sample site (different sets of colours) [01:13] tscherler: because the page option is frankly speaking bullshit [01:14] tscherler: because the structurer works like [01:14] _Gav_: so 'page' or 'both' or 'alt' dont work any more [01:14] tscherler: you place in position x and it get rendered in x [01:14] tscherler: so [01:14] tscherler: have to be removed [01:14] _Gav_: yep, these options need removing then [01:14] tscherler: does not make sense anymore [01:14] _Gav_: :) [01:15] tscherler: in general alternative positions [01:15] tscherler: that is skins a wee bit advanced [01:15] _Gav_: Where do you remove these options, or can they just be omitted [01:15] tscherler: ...but now we have the dispatcher ;-) [01:15] tscherler: need to be removed in [01:16] tscherler: contracts usage/description [01:16] tscherler: and structurer [01:16] » kronenpj left the chat room. (Read error: 110 (Connection timed out)) [01:16] tscherler: I removed some of them while refactoring but not all [01:16] _Gav_: xley: I already have a seed-sample running with forrest run, can I forrest run another seed-sample or site-author at the same time [01:16] xley: yes ... finding FAQ ... [01:17] tscherler: you need to change the port [01:18] xley: http://forrest.apache.org/docs/dev/faq.html#run_port [01:19] » kronenpj joined the chat room. [01:22] _Gav_: cool! [01:22] _Gav_: thanks [01:23] tscherler: _Gav_ you know the acrynom RTFM ;-) [01:27] _Gav_: yep, but short-cutting to try and be 'doing' rather than 'reading' [01:27] tscherler: jeje [01:28] _Gav_: The Manual is getting to be as big as the mySQL one [01:28] tscherler: sometimes it saves you a lot of time (I can tell from my own experience) ;-) [02:07] tscherler: ok cu you guys later [02:07] tscherler: need to fix my car [02:07] tscherler: back in about 2-3 hours [02:08] tscherler: then from homw [02:08] tscherler: and doing work ;-) [02:08] tscherler: ...on? [02:08] xley: great, i will get some sleep and catch up with you later. [02:09] tscherler: k [02:09] tscherler: cu [02:16] _Gav_: cya [02:17] _Gav_: must be gone 2am over east [02:17] tscherler: jeje [02:17] tscherler: later dude [02:17] tscherler: ...when it will be 2 am for me ;-) [02:17] _Gav_: no idea [02:17] xley: yep Zzzz ... just gotta finish this one thing or i will lose track. You know how it is. [02:18] tscherler: :) [02:18] _Gav_: yep, I'll carry on for an hour or so then continue in the morning [02:18] tscherler: _Gav_ I mean if it is 2am for me I reckon I will catch up again with you guys from downunder ;-) [02:19] _Gav_: tis true [02:19] tscherler: spot [02:19] » tscherler left the chat room. ("Download Gaim: http://gaim.sourceforge.net/") [02:22] xley: _Gav_: are you able to add a patch of your work so far? perhaps someone can commit what you have done. Smaller chunks. [02:29] _Gav_: I will before I go yes [02:30] _Gav_: cant see these themes/images/roundcorner-t-r-5-bgffffff-strokeE5E4D9-fgE5E4D9.png files for looking [02:30] » Cyriaque left the chat room. ("Chatzilla 0.9.70 [Firefox 1.5.0.1/2006011112]") [02:30] xley: generated from svg [02:31] _Gav_: ok, need to change the colors to match #4c6c8f ( i think thats the pelt nav colours) [02:34] xley: try following the sitemaps in the dispatcher plugin, or is it themes.Core [02:35] xley: i presume that it picks up the colour from those branding-theme.ft colours that you were dealing with. [02:38] _Gav_: in dispatcher and branding yes, thanks [02:49] » You have set yourself away with "Zzzzz". [03:08] _Gav_: will carry on later, I can not seem to get the colors to change yet. [03:20] _Gav_: Ah, how clever (not me , the implementation). [03:20] _Gav_: background-image: url(../themes/images/roundcorner-t-l-5-bgffffff-stroke4C6C8F-fg4C6C8F.png); [03:21] _Gav_: Just change the colors in the url itself! [03:23] _Gav_: back later [03:30] rgardler: twilliams: are you about? I would like to ask your opinion on a possible LM caching solution [03:34] twilliams_: i'm here for a couple minutes. [03:37] rgardler: OK, I think I've found a solution - using the MultSourceValidity class, but... [03:38] rgardler: My concern is why doesn't the only inputmoudle that uses caching (the XMLFileInputModule) use "normal" cocoon pipeline cache components [03:38] rgardler: DO you have any insights into this qeustion? [03:39] twilliams_: it depends on the day i'm asked... sometimes I think i understand it; others, not so much:( [03:40] rgardler: :-)) [03:40] rgardler: I suspect that means I should experiment then compare notes with you cia the mail list? [03:41] twilliams_: when i first looked into this, i assumed it didn't use "normal caching" because of it's inability at the module level to do implement CacheableProcessingComponent since it deals with multiple inputs [03:42] twilliams_: now I'm not so sure and need to better understand the lifecycle of these input components [03:43] rgardler: Yes, that is my problem too... what if I said I may have an interim solution that does not implement CacheableProcessingComponent, but does use cocoons validity classes [03:43] rgardler: i.e. we could later move to implement the interface when we understand how [03:44] twilliams_: we're already using SourceValidity, i do like the idea of swapping our m_src out for the MultiSourceValidity though [03:44] twilliams_: then add a new source with every mount [03:45] rgardler: Oh. I didn't realise we already used SourceValidity - seems an ovcious move to multisourcevalidity then [03:45] rgardler: I'll do that we can do the rest on the mail list [03:45] twilliams_: ok [03:45] rgardler: Cool, thanks for your input [03:46] twilliams_: later... [03:46] rgardler: bye for now [05:22] » tscherler joined the chat room. [05:22] tscherler: ji again [05:46] rgardler: welcome back throsten - fixed the car? [05:48] » rgardler left the chat room. (Read error: 104 (Connection reset by peer)) [05:52] tscherler: yeah [06:14] tscherler: http://forrest.apache.org/forrest-issues.html [06:43] tscherler: anybody still here [06:44] tscherler: I need someone looking at [06:44] tscherler: http://forrest.apache.org/forrest-issues.html#%5BFOR-546%5D+Sitemap+reference+doc+should+be+updated+to+reflect+plugin+architecture [06:49] tscherler: I see [06:49] tscherler: completeness.

  <map:components>
    <map:serializers>
[06:50] tscherler: can somebody confirm this? [07:08] » tscherle1 joined the chat room. [07:14] » tscherler left the chat room. (Read error: 110 (Connection timed out)) [07:23] » tscherle1 is now known as tscherler. [10:08] » raoul joined the chat room. [10:35] » tscherler left the chat room. (Read error: 110 (Connection timed out)) [10:37] xley: hi, is anyone still here. [10:43] xley: rgradler: Earlier today we talked about plugins deployment. [10:43] xley: Found the old discussion that we referred to: [10:43] xley: http://issues.apache.org/jira/browse/FOR-742 [10:43] xley: "trouble accessing unversioned plugin for a released version ..." [10:43] xley: There is mail discussion linked from FOR-742 [11:20] » raoul left the chat room. ("Leaving") [11:29] twilliams_: anyone still there [11:29] twilliams_: ? [11:39] _Gav_: yep, hi tim [11:39] _Gav_: unfortunatly for you, just me atm :) [11:40] twilliams_: yeah, i'm just checking in quickly back from dinner [11:41] twilliams_: i had a thought about this lm caching issue and i think i'm on to something but i'm wondering about some of our xconf configuration [11:46] _Gav_: jeez, double dutch to me tim [11:46] _Gav_: sorry for delay, other 1/2 demanding cuppa [11:46] twilliams_: alright, i'll write up some thoughts to the mail list, thanks [11:47] _Gav_: I have pelt.fv and css changes, I made them on test site, how do I transfer those changes so they can be diffed [11:49] _Gav_: if i overwrite those files in .themes.core then the whole file will be diffed wont it? [11:50] twilliams_: is that not what you want [11:50] twilliams_: ? [11:50] twilliams_: paste over them and svn diff > my.patch? [11:51] _Gav_: I just thought pasting all the contents of the files would show as all the contents changed, is this not right [11:51] _Gav_: Ive made changes in lots of little different places [11:52] _Gav_: didnt want a massive diff [11:52] twilliams_: unless you have line-ending issues, it should be a true diff of the current > original [11:53] twilliams_: the good news is that you can't hurt much by trying;) [11:53] twilliams_: svn revert [11:53] _Gav_: ok, I'll try it. I used modified vim , so line-endings shouldnt be a problem. [11:54] _Gav_: just a bit more to do then I'll patch it [11:56] _Gav_: the current pelt theme shows both pdf export link and xml export link [11:56] _Gav_: I need to remove the xml link [11:56] _Gav_: this is implemented i think by this line... [11:56] _Gav_: [11:56] _Gav_: any ideas where I disable the xml link then? [12:03] twilliams_: sorry, i haven't been following this lately [12:03] twilliams_: i'll look quickly but no guarantees [12:04] _Gav_: cheers [12:04] » tscherler joined the chat room. [12:07] _Gav_: mr T, hows things [12:08] tscherler: fine [12:08] tscherler: was cut of for a while [12:08] _Gav_: bummer, thought you had a permanant connection now? [12:08] tscherler: my internet was down [12:08] tscherler: yeah dunno what the .... is going on [12:09] _Gav_: are you in city or country area [12:09] tscherler: near city [12:09] _Gav_: ok, thats not good then, inet should be reliable by now [12:10] _Gav_: I have a couple of questions, tim is looking at one but you may know straight away [12:10] tscherler: k [12:11] _Gav_: I need to disable the xml link in the pelt theme to immitate the pelt skin [12:11] _Gav_: [12:11] _Gav_: implements both, I cant see where to split them [12:12] tscherler: just comment the [12:12] tscherler: and have a look at [12:12] twilliams_: maybe it falls back to common? [12:12] twilliams_: export-link.vt.xml? [12:12] _Gav_: ok, so will that remove the required pdf link [12:12] tscherler: export-link.vt.xml [12:13] tscherler: yeah [12:13] _Gav_: hehe, I guess I'll look there then :) [12:13] twilliams_: yeah, that includes both links [12:13] tscherler: [12:13] tscherler: yeah [12:13] tscherler: [12:16] _Gav_: thanks, that done , question 2 ... [12:16] _Gav_: built with forrest and built with cocoon appear underneath each other [12:17] _Gav_: cant get them side by side [12:18] _Gav_: [12:18] _Gav_: [12:18] _Gav_: Built with Apache Forrest [12:18] _Gav_: http://forrest.apache.org/ [12:18] _Gav_: images/built-with-forrest-button.png [12:18] _Gav_: 88 [12:18] _Gav_: 31 [12:18] _Gav_: [12:18] _Gav_: [12:18] _Gav_: Built with Cocoon [12:18] _Gav_: http://cocoon.apache.org/ [12:18] _Gav_: http://forrest.apache.org/images/built-with-cocoon.gif [12:18] _Gav_: [12:18] _Gav_: [12:18] _Gav_: is the section causing this [12:19] _Gav_: brb [12:21] tscherler: ø? incompatible encoding [12:23] _Gav_: ok back, any ideas [12:24] tscherler: (02:18:40) _Gav_: is the section causing this [12:24] tscherler: (02:19:22) _Gav_: brb [12:24] tscherler: (02:21:38) tscherler: ø? incompatible encoding [12:25] tscherler: dunno what u mean [12:26] _Gav_: on the forrest site, the built with forrest logo and cocoon logo appear next to each other on the same line [12:26] _Gav_: in the pelt theme, the cocoon logo is underneath the forrest logo [12:27] _Gav_: this makes the footer wider also [12:28] _Gav_: they are implemented with the code above, inside tags, so I wondered if the tags were causing this effect [12:28] _Gav_: what does role="accueil" mean [12:29] tscherler: did you looked in the pelt contract? [12:29] tscherler: I mean [12:30] tscherler: pelt/siteinfo-credits.ft [12:30] tscherler: (02:28:44) _Gav_: what does role="accueil" mean -> dunno this seems to come from chiraque [12:31] tscherler: [12:31] tscherler:
[12:31] tscherler: [12:32] _Gav_: just saw that, how to disable that [12:32] tscherler: k [12:32] tscherler: we need to document that [12:33] _Gav_: just remove it do you think for the time being? [12:33] _Gav_: comment it out [12:33] tscherler: I looked at the contract and it has nearly no description :( [12:33] tscherler: well [12:33] tscherler: make it configurable ;-) [12:33] _Gav_: love to, but xsl is my downfall at the moment [12:34] _Gav_: so I don't know how [12:34] tscherler: add a forrest:property [12:34] tscherler: ok [12:34] tscherler: easy [12:34] tscherler: in the pelt.fv declaration of the contract [12:35] _Gav_: I have 'Sams Teach Yourself....' book :) [12:35] tscherler: false [12:36] tscherler: [12:37] tscherler: false [12:37] tscherler: thats it [12:37] tscherler: ;-) [12:37] _Gav_: cool, clÌche, 'easy when you know how' incompatible encoding [12:38] _Gav_: I'll try it now [12:38] tscherler: jeje [12:38] tscherler: yeah I should know ;-) [12:46] tscherler: grr [12:46] tscherler: I am trying to fix [12:47] _Gav_: fix what [12:48] tscherler: http://issues.apache.org/jira/browse/FOR-807 [12:48] tscherler: but jira is buggy [12:48] tscherler: and returns for [12:49] tscherler: http://issues.apache.org/jira/secure/IssueNavigator.jspa?view=rss&pid=12310000&fixfor=12310040&resolutionIds=-1&sorter/field=priority&sorter/order=DESC&tempMax=25&reset=true&decorator=none:367:1 [12:49] tscherler: an invalid xml docu [12:49] tscherler: grrr [12:49] tscherler: so can be i fixed it and tested this buggy return :( [12:50] tscherler: does jira looks weird 4u2? [12:51] _Gav_: i see it, yes, huge footer repeating comments [12:51] tscherler: hmm [12:51] tscherler: bummer [12:51] _Gav_: wonder if all those
comments broke it [12:52] _Gav_: either way, shouldnt we be using
in code [12:52] tscherler: yeah [12:52] _Gav_: br is a self-closing tag and shouldnt be closed with
[12:52] tscherler: but that is coming from jira [12:53] _Gav_: Oh, yeah I realise, but the issue itself is about
[12:53] tscherler: ah [12:53] _Gav_: no idea how to fix jira [12:53] tscherler: me neither [12:54] _Gav_: I'm subscribed to Jira Issues, should I log an issue [12:55] tscherler: dunno can be something temp [13:00] » cheche left the chat room. ("Download Gaim: http://gaim.sourceforge.net/") [13:02] _Gav_: i've broken siteinfo-credits.ft, where does that param line go? [13:03] tscherler: (02:35:54) tscherler: false -> pelt.fv [13:04] tscherler: (02:37:24) tscherler: false -> where the other xsl param are in siteinfo-credits.ft [13:04] tscherler: (02:36:47) tscherler: -> before
[13:05] _Gav_: ok got it, needs more tinkering , now the images do not appear at all [13:06] tscherler: hmm [13:07] _Gav_: [13:07] _Gav_: [13:07] _Gav_: credit [13:07] _Gav_: false [13:07] _Gav_: [13:07] _Gav_: false [13:07] _Gav_: [13:07] _Gav_: [13:07] _Gav_: Built with Apache Forrest [13:07] _Gav_: http://forrest.apache.org/ [13:07] _Gav_: images/built-with-forrest-button.png [13:07] _Gav_: 88 [13:07] _Gav_: 31 [13:07] _Gav_: [13:07] _Gav_: [13:07] _Gav_: Built with Cocoon [13:07] _Gav_: http://cocoon.apache.org/ [13:07] _Gav_: http://forrest.apache.org/images/built-with-cocoon.gif [13:07] _Gav_: [13:07] _Gav_: [13:07] _Gav_: [13:07] _Gav_: [13:08] tscherler: (03:07:10) _Gav_: [13:08] tscherler: (03:07:10) _Gav_: false [13:08] tscherler: na [13:08] tscherler: you cannot nest properties [13:08] tscherler: move false one line above [13:09] tscherler: before! [13:09] _Gav_: doh [13:09] tscherler: ;-) [13:10] _Gav_: ok good, they are now next to each other. They are however one line below the compliance links. [13:11] tscherler: switch the position in the structurer [13:13] _Gav_: same thing only other way round [13:13] _Gav_: compliance links are in their own div though [13:13] xley: _Gav_: ... Michael Kay "XSLT 2nd Edition - Programmer's Reference" Wrox Press [13:14] xley: and Forrest has many example stylesheets to learn from. [13:15] tscherler: xley I wrote to [13:15] tscherler: xsl-list@lists.mulberrytech.com [13:15] _Gav_: Thanks David, will take a look [13:15] tscherler: and he gave me this answer to the forrest-issue.html problem [13:15] » diwaker joined the chat room. [13:15] tscherler: I'm afraid none of the tools handle this well. The sole purpose of CDATA is [13:15] tscherler: to tell the system that the angle brackets around
aren't to be treated [13:15] tscherler: as markup, which means that when you want to treat them as markup, you've [13:15] tscherler: got a problem. disable-output-escaping is one way around that problem, but [13:15] tscherler: it's messy. [13:15] tscherler: It's not clear what you actually want to produce as your output or exactly [13:16] tscherler: where your difficulty lies. [13:16] tscherler: Michael Kay [13:16] tscherler: http://www.saxonica.com/ [13:16] diwaker: hey guys [13:16] diwaker: whats going on [13:16] tscherler: hey [13:16] xley: Hi DIwaker [13:16] _Gav_: gday diwaker [13:16] diwaker: hey david, thorsten [13:16] diwaker: hey gav [13:17] diwaker: sorry i missed more than half already [13:17] diwaker: is the URL to the log on the mailing list? [13:17] tscherler: yaaaazzz [13:17] tscherler: its in svn [13:17] _Gav_: is it still yesterdays date on it, or has it changed [13:18] tscherler: http://svn.apache.org/viewcvs/forrest/events/forrest-friday/20060210-log.txt?rev=376905&r1=376904&r2=376905&view=diff [13:18] xley: http://svn.apache.org/repos/asf/forrest/events/forrest-friday [13:18] diwaker: ah, thanks [13:18] xley: i am automatic commit another log ... it seems that JennyCurran fell asleep again at midnight. [13:18] _Gav_: ok, so cheche log changed at 0:00 [13:19] tscherler: yeah [13:19] _Gav_: fell asleep is better [13:19] tscherler: or change the url ;-) [13:20] tscherler: http://issues.apache.org/jira/browse/FOR-807 [13:20] tscherler: is fixed besides the problem I cannot test the last bit [13:21] tscherler: http://issues.apache.org/jira/secure/IssueNavigator.jspa?view=rss&pid=12310000&fixfor=12310040&resolutionIds=-1&sorter/field=priority&sorter/order=DESC&tempMax=25&reset=true&decorator=none:367:1 [13:21] tscherler: returns invalid xml [13:21] tscherler: that is the reason why [13:22] tscherler: forrest site on site-author fails ATM for skins and dispatcher [13:22] tscherler: somebody mind testing site-author [13:24] xley: it looks to me like Jira is broken today. Just browsing is returning gobbledegook. [13:24] tscherler: jupp [13:24] tscherler: 4 me 2 [13:28] tscherler: grr cannot even login anymore to jira [13:33] diwaker: i'm testing site-author [13:33] diwaker: do i need to do anything special with forrest.properties or anything else? [13:33] diwaker: i just did cd site-author; forrest; now waiting for it to finish [13:33] tscherler: k [13:33] tscherler: perfect [13:34] tscherler: that means you testing with skins [13:34] diwaker: got this right after: X [0] forrest-issues.html BROKEN: An invalid XML character (Unicode: 0x0) was found in the element content of the document. [13:34] diwaker: but the build is still going strong [13:34] tscherler: yeah [13:34] tscherler: k [13:35] tscherler: that means I need to wait till jira is working again for closing FOR-807 ;-) [13:35] tscherler: let a side that I cannot login ATM ;-) [13:35] diwaker: 3min 9 seconds [13:36] tscherler: Total time: 3 minutes 14 seconds [13:36] tscherler: with dispatcher :) [13:36] xley: diwaker: that sounds like using skins. [13:37] tscherler: so my notbook is not to bad after all [13:37] tscherler: ah wait [13:37] tscherler: yes it was skins for me as well [13:37] xley: http://forrest.apache.org/docs/dev/howto/howto-dispatcher-quickstart.html [13:38] diwaker: i guess. i didn't touch any configuration. [13:38] diwaker: now testing with dispatcher [13:38] tscherler: no [13:38] tscherler: not without an update ;-) [13:38] tscherler: and rebuild of the plugin, ... etc ;-) you know ;-) [13:39] xley: and the patch noted in the Quickstart. [13:39] diwaker: yep, i already have the patch in place i think [13:40] xley: Then all you need is the forrest.properties tweaks. [13:41] xley: and local-deploy the plugins. [13:42] diwaker: i did a 'forrest run' to make sure i had it right [13:42] diwaker: the header says 'new seed powered by dispatcher' [13:42] diwaker: so i think its working [13:42] diwaker: let me do the full build now [13:43] tscherler: Total time: 4 minutes 47 seconds [13:44] tscherler: with common theme [13:44] tscherler: [13:44] tscherler: − [13:44] tscherler: [13:44] tscherler: [13:44] tscherler: [13:44] tscherler: k [13:49] diwaker: 5min 9 seconds for me [13:49] diwaker: and lots of broken links [13:50] diwaker: [13:50] diwaker: [13:50] diwaker: mostly of that form [13:51] xley: I am doing it too, so i can compare with http://issues.apache.org/jira/browse/FOR-803 [13:52] tscherler: diwaker [13:53] tscherler: have you done svn up on site? [13:53] tscherler: site-author i mean [13:53] diwaker: yes [13:53] diwaker: svn info says r376907 [13:53] diwaker: ah just pulled in some more changes [13:53] diwaker: will try again [13:54] diwaker: do i need to change the theme to something else? pelt/coat? [13:54] tscherler: common is fastes ;-) [13:54] xley: I get only the known broken stuff: the expected forrest-issues.html and menu-index.html etc. [13:55] tscherler: xley [13:55] tscherler: did you do an svn up [13:55] xley: See FOR-803 ... i did both default and pelt. [13:55] tscherler: the expected forrest-issues.html and menu-index.html should be gone since my last commit [13:55] diwaker: i'm still getting forrest-issues [13:55] tscherler: (03:53:02) tscherler: have you done svn up on site? [13:55] tscherler: (03:53:11) tscherler: site-author i mean [13:55] xley: tscherler: Ah, not recently. Du'oh will start again. [13:56] tscherler: yeah that is because jira is down [13:56] diwaker: i changed theme to pelt [13:56] diwaker: and now i'm getting this too: [13:56] diwaker: X [0] images/project.png BROKEN: /home/diwaker/software/forrest/build/plugins/org.apache.forrest.plugin.internal.dispatcher/.../images/project.png (No such file or directory) [13:56] tscherler: k will try [13:57] xley: Yep that is the svg to png stuff. In the skins, it read skinconf.xml to get the project name and group name. [13:58] tscherler: :( [13:59] tscherler: but should not [14:00] diwaker: 5min 37s [14:00] diwaker: with pelt [14:00] xley: could perhaps get that info from forrest.properties [14:00] tscherler: IMO all the skinconf reference have to be removed [14:01] tscherler: that will force us to slim down the core [14:02] tscherler: BTW did you all know that the dispatcher support xhtml2 input? [14:02] tscherler: well not fully like I want it yet but it is possible with a couple of structurer [14:03] diwaker: nope. we should have a seed-target that creates uses dispatcher + xhtml2 by default [14:03] tscherler: yeah would be awesome to have it in the release [14:03] tscherler: after my conference I will write a RT about it [14:04] tscherler: actually v3 has an implementation [14:05] tscherler: in the xdocs dir you find e.g. abstract-to-xhtml2.fv [14:05] xley: Last time (FOR-803) it took me 6m 30s for default theme. Today 5m 15s [14:05] tscherler: we making small procresses ;-) [14:06] tscherler: progress [14:06] xley: BIG [14:06] diwaker: 5min 3s with default theme [14:06] xley: gee your pelt and default are close. [14:07] tscherler: hmm weird [14:07] tscherler: because pelt has much more contracts [14:08] tscherler: BTW diwaker can I play around with the css of common.fv [14:08] diwaker: sure, go right ahead [14:08] tscherler: k thx [14:09] tscherler: Total time: 6 minutes 29 seconds [14:09] tscherler: for me with pelt [14:11] tscherler: k [14:11] tscherler: need to refactor [14:11] tscherler: [14:11] tscherler: [14:11] tscherler: [14:11] tscherler: [14:11] tscherler: [14:11] tscherler: [14:12] tscherler: [14:12] tscherler: [14:12] tscherler: [14:12] tscherler: [14:12] tscherler: [14:12] tscherler: [14:12] tscherler: [14:12] tscherler: [14:12] tscherler: [14:12] tscherler: [14:12] tscherler: [14:12] tscherler: but right now will have to go to sleep [14:12] tscherler: ;-) [14:13] tscherler: the only bummer is that the resources.xmap is quite verbose [14:13] tscherler: when somebody want to try [14:13] tscherler: the stuff should go into the themes.xmap [14:13] tscherler: after refactoring ;-) [14:14] tscherler: but that leads to the xhtml2 RT [14:14] xley: Last time (FOR-803) it took me 8m 10s for pelt theme. Today 6m 40s [14:15] tscherler: it is now possible to generate svg with contracts which leads to new possibilities [14:15] tscherler: k [14:16] tscherler: so I reckon if we refactor resources.xmap to themes.xmap we are coming close to skin build time [14:16] tscherler: :) [14:16] tscherler: without even changing the DOM implementation [14:17] tscherler: jeje that gives hopes [14:25] tscherler: k cu you all [14:25] xley: cheers [14:25] tscherler: (04:25:30) time to sleep [14:25] tscherler: de nada [14:25] _Gav_: cya [14:25] tscherler: to you all [14:26] tscherler: _Gav_ BTW have a look at forrest/trunk/site-author/content/xdocs/docs_0_80/tab-index.fv [14:27] _Gav_: ok [14:27] tscherler: this is what you can do for your sponsor links [14:27] _Gav_: thanks [14:27] tscherler: de nada = not to mention ;-) [14:28] _Gav_: cool, I was going to look it up [14:28] tscherler: the only problem you then face is the sitemap [14:29] tscherler: you need to create a data model input [14:29] _Gav_: ok, I'll take a look, but most likely get stuck [14:29] tscherler: like you can find in forrest-trunk/site-author/sitemap.xmap [14:30] tscherler: if you get stuff you can ask @ml [14:30] _Gav_: i need to implement in themes.xmap? [14:30] tscherler: no [14:30] tscherler: in your project sitemap.xmap [14:30] tscherler: the best example is our docu ;-) [14:31] _Gav_: ok, I'll have lunch soon and get back to it. [14:31] tscherler: ya me is going to bed [14:31] tscherler: see u all @ml [14:31] tscherler: ;-) [14:31] » tscherler left the chat room. [14:37] » pbol joined the chat room. [14:37] pbol: Hi all [14:37] _Gav_: Hi Paul [14:37] pbol: Hi Gavin [14:37] » pbol left the chat room. (Client Quit) [14:39] » pbol joined the chat room. [14:39] pbol: ...oops [14:39] _Gav_: you went [14:39] _Gav_: hows things in the wet season [14:41] pbol: Yeah, closed the 'buddy' window accidently. [14:41] * _Gav_ slaps pbol around a bit with a large trout [14:42] _Gav_: ah, thats funny, never did that before :) [14:42] pbol: It's not really supposed to be wet up here, but we have had a bit of monsoonal stuff - which is disgusting. 43 and 60% humidity. [14:42] pbol: Hows your site translation going? [14:43] _Gav_: 33 here today. I am slowly converting pelt theme to look similar to pelt skin, but have some hiccups aong the way [14:44] _Gav_: just looking at suggestion from Thorsten [14:44] pbol: your in v3? [14:44] _Gav_: can not get siteinfo-credits to sit next to siteinfo-compliance links [14:45] _Gav_: ah no, for RC1 [14:45] _Gav_: my site is getting there, but on hold for a couple of days [14:46] _Gav_: next job is navigation for my site, probably just rewrite the tabs.xml for that, seems to be the easiest way [14:46] pbol: I've been doing some real (for money) work so had to keep a low profile since getting back from NZ in jan. [14:47] _Gav_: money tends to do that :) [14:47] pbol: Have you tried the 'generate nav from directory structure' option? It doesn't seem to work for me. [14:48] _Gav_: No not yet [14:48] pbol: Super hot weather isn't that conducive to sitting at a computer either... [14:48] _Gav_: no, should be in the ocean, no air-con then? [14:49] pbol: The ocean is 2000km away. Pool's ok. air-con up here are mostly [14:49] pbol: 'swampies' - evaporative. [14:50] pbol: they don't work in high humidity. [14:50] _Gav_: no, I heard that [14:51] _Gav_: 2000k away, sounds like the alice [14:51] pbol: Got it in one. [14:52] _Gav_: wow, I'm 2 minutes from the Indian, I'll go in for you then :) [14:52] xley: Paul see: http://forrest.apache.org/docs/dev/howto/howto-dispatcher-quickstart.html [14:54] pbol: The tabs/site nav is ok, but I'd really like an option for Forrest to 'watch' part of the file system and generate extra nav from that. I haven't had a chance to try the resume plugin yet. [14:54] pbol: Hi David - which bit? [14:55] pbol: Are you in Cottesloe Gavin? [14:56] _Gav_: No, 30k north, new suburb called Butler/Brighton, near Quinns Rocks [14:56] pbol: Near Joondalup? [14:56] _Gav_: Yep, thats it, about 10 mins from there [14:57] _Gav_: not even on google earth yet [14:57] pbol: I've got friends there who used to do the Joondalup festival. [14:57] _Gav_: cool [15:01] xley: You asked whether Gav was using the seed-v3 ... that doc shows how to dispatcher-enable any existing site. If you want to experiment. [15:01] xley: See you all later - going out for a while. [15:02] xley: the is a partial summary and the log at http://svn.apache.org/repos/asf/forrest/events/forrest-friday/ [15:03] » You have set yourself away with "food and a music concert". [15:04] pbol: Ok, thanks. I was asking because I seeded a v3 site and noticed something a little odd: the body and head sections of my pages were transposed. Firefox didn't seem to care. [15:04] pbol: Gavin. Did you end up trying Helen's RSS plugin? [15:16] _Gav_: hi paul, no not tried the rss plugin [15:16] _Gav_: do you have a published version of your site, or was this just local [15:17] _Gav_: I used genericMarkup.ft to put in right-hand content [15:19] pbol: So how are you generating the content? [15:19] _Gav_: http://apache.minitutorials.com/ is result of RC1 dispatcher, not v3 any more [15:20] _Gav_: I havent yet put in actual 'main' content, only rewritten index.xml for sample data [15:25] _Gav_: i used [15:25] _Gav_: [15:25] _Gav_: and then normal html markup [15:26] _Gav_: then closed the contract. [15:26] _Gav_: saved into my pili.fv file [15:26] _Gav_: appears on all pages [15:26] _Gav_: not sure if that was the question though! [15:27] _Gav_: when i get thew chance to try nav from directory structure, i'll let you know [15:43] pbol: Sorry - I'm going to have to nip out for a bit. [15:44] pbol: I was wondering if you were pulling the fp content from other places in the site. [17:05] pbol: the RSS idea is interesting because it means you could also syndicate content to other sites using the same mechanism. [17:22] _Gav_: not all having to be forrest sites though [17:25] _Gav_: \forrest\site-author\content\xdocs\docs_0_80 does not have tab-index.fv [17:37] » _Gav_ left the chat room. (Read error: 104 (Connection reset by peer)) [18:04] » diwaker left the chat room. (Remote closed the connection) [19:13] » twilliams_ left the chat room. [21:15] » pbol left the chat room. [21:18] » _Gav_ joined the chat room. [21:18] _Gav_: are we still going [21:18] _Gav_: I have changes I will patch soon [21:19] _Gav_: catch u on the list [21:20] » _Gav_ left the chat room. (Client Quit) [21:38] » kronenpj left the chat room. ("Chatzilla 0.9.70 [Firefox 1.5.0.1/2006020721]") [12:34] » JennyCurran left the chat room. (Remote closed the connection)