**** BEGIN LOGGING AT Fri Dec 9 16:08:50 2005 Dec 09 16:08:50 --> You are now talking on #for-dec Dec 09 16:08:51 --- #for-dec :[freenode-info] If you're at a conference, please contact freenode staff to make sure we've made special allowance for many users coming into our network from a single internet address ( http://freenode.net/faq.shtml#gettinghelp ). Private messages from unregistered users are currently blocked, except to network staff, services and participating registered users ( http://freenode.net/faq.shtml#privmsg )... Thanks! Dec 09 16:12:26 --- xley has changed the topic to: Locationmap, prioritise and cleanup Jira, xhtml2 Dec 09 18:32:59 --> pbol (n=JTZ@dsl-210-211-103-098.sa.veridas.net) has joined #for-dec Dec 09 18:33:13 Hi David Dec 09 19:01:24 hi Paul, i will be back soon. Dec 09 19:19:26 quiet start today Dec 09 19:31:46 Are you still there paul? How did you go with the site-author stuff today? Perhaps i give you some tips. Dec 09 19:52:34 just nipped out for a bit, I'm not really going to have any time for conversation till later I don't think: dinner for toddler and then we are off to a work Xmas do. I'll pop in tomorrow though. Dec 09 20:32:29 --> rgardler (n=chatzill@82-69-78-226.dsl.in-addr.zen.co.uk) has joined #for-dec Dec 09 20:32:53 Hello, anyone who is hereI'm around on and off all day (GMT) Dec 09 20:33:07 I'm on Baby sitting duty all morning though ;-) Dec 09 20:33:31 My first task is to get plugins working in-place (personal itch) Dec 09 20:33:39 then I'm going to crack on with for-200 Dec 09 20:43:48 see you later Paul. Hi Ross. Dec 09 20:57:45 http://svn.apache.org/repos/asf/forrest/events/forrest-friday/20051209-log.txt Dec 09 20:58:03 Good morning/evening David - thanks for the log Dec 09 20:58:18 Hi. Dec 09 21:00:34 There is also an evolving summary at ... Dec 09 21:00:54 http://svn.apache.org/repos/asf/forrest/events/forrest-friday/20051209-summary.txt Dec 09 21:01:23 Re: plugins working in-place Dec 09 21:01:34 Fantastic, that will be a good community enabler. Dec 09 21:01:46 It will be so much easier to develop. Dec 09 21:02:06 ... as a developer i mean Dec 09 21:03:06 It is also needed for the forrestbot instalaltion... Dec 09 21:03:29 If the FB is using Forrest trunk it is reasonable to assume... Dec 09 21:03:35 that we also want the trunk of plugins Dec 09 21:03:41 if not we can add a version number Dec 09 21:04:33 i was going to ask why, but yeah i see what you mean. Dec 09 21:04:52 I have a site that uses the Daisy plugin Dec 09 21:04:57 locally I have enhanced the plugin Dec 09 21:05:02 yes it is reasonable, that is our testing continuous build stuff Dec 09 21:05:17 but I have not committed because of the Cocoon site using the "old" version Dec 09 21:05:27 hence my personal desire to fix it Dec 09 21:06:59 cannot the Cocoon forrest.properties declare the specific version of the plugin? Dec 09 21:07:59 In this case, yes, since I have write access to the cocoon-docs site Dec 09 21:08:06 but not all devs do have that access Dec 09 21:10:08 ? why does that matter Dec 09 21:11:21 Currently the Cocoon-docs site has no version for plugins Dec 09 21:11:24 as do most sites Dec 09 21:11:53 oh.... hang on... I've not thought this through... Dec 09 21:12:07 :-) Dec 09 21:12:18 email is better :-) Dec 09 21:12:41 Yes, I will send a proposal to the list - typing it up now Dec 09 21:13:20 i was joking, but still, good idea Dec 09 21:14:04 I want to do it anyway because I am not planning on doin gthe full "in-place" thing and your questions make it clear I need to think out the implications Dec 09 21:14:17 writing an email will make me do that, even if noone responds :-) Dec 09 21:17:01 Yes, that is an interesting OSS technique ... writing email not expecting an answer. Dec 09 21:17:48 Yeah, so many times I start asking a question and in trying to formulate it clearly, I discover the answer - maybe we should document that on our mailing list page Dec 09 21:17:50 i am going to wade through Jira and also see what is left for FOR-200 Dec 09 21:18:45 yes good idea for mailing list page hint. Dec 09 23:27:09 --> tscherler (n=thorsten@242.Red-213-97-135.staticIP.rima-tde.net) has joined #for-dec Dec 09 23:27:24 hi all Dec 09 23:27:31 a quick question Dec 09 23:27:46 I wrote a locationmap source factory Dec 09 23:28:32 it is working for already cached and resolved locations but not for not cached ones Dec 09 23:28:58 I think it is because i do pass a null objectModel to the lm Dec 09 23:29:21 I need to get the right object model in the source factory Dec 09 23:29:30 somebody knows how? Dec 09 23:32:11 somebody here? Dec 09 23:36:20 i am here but haven't got a clue what you are talking about, sorry. Dec 09 23:36:24 Hi Thorsten. Dec 09 23:36:50 perhaps Ross can help later. Dec 09 23:37:18 BTW, does trunk still work for you after my Cocoon upgrade today? Dec 09 23:45:34 not made an update so far Dec 09 23:45:56 hmm I found out how Dec 09 23:46:05 but that does not solved my problem Dec 09 23:46:32 wdyt should I check in what I have even if it is not working 100% Dec 09 23:46:43 maybe others can have a look Dec 09 23:47:11 rgardler seems not to watching right now Dec 09 23:47:41 does it only affect the Dispatcher work? Dec 09 23:50:53 the only example is found there yes Dec 09 23:50:55 but Dec 09 23:51:09 you know what I did? Dec 09 23:51:35 no, what? Dec 09 23:51:50 I wrote an sourecFactory (lm://...) that contacts the lm input modul Dec 09 23:51:59 so you can then use Dec 09 23:52:09 lm://your-location Dec 09 23:52:22 instead of {lm:your-location} Dec 09 23:52:43 that makes it easier to use in java and xsl Dec 09 23:53:12 I wanted to xsl:import a lm location but {lm:} did not worl Dec 09 23:53:17 worked I mean Dec 09 23:54:52 Yes, you should commit half-finished work and others can perhaps help. Dec 09 23:56:56 k Dec 09 23:57:06 it seems to work sometimes ;-) Dec 09 23:57:13 but not yet always Dec 10 00:08:52 I found out that all matches are working that are directly referenced via Dec 10 00:08:55 http://localhost:8888/locationmap.xml Dec 10 00:09:51 but all referenced by Dec 10 00:09:51 Dec 10 00:09:55 not Dec 10 00:13:46 we lost track of which plugins have been converted to use the locationmap (and which ones don't need it) Dec 10 00:13:59 we did some of it last FirstFriday Dec 10 00:14:16 anyway here is the list of 36 plugins to check off ... Dec 10 00:14:26 http://issues.apache.org/jira/browse/FOR-726 Dec 10 00:26:29 thorsten - your sourceFactory sounds interesting, I'll take a look if you commit to the whiteboard Dec 10 00:26:51 k Dec 10 00:26:54 moment Dec 10 00:26:56 David - thanks for the list, I'll start working on it this afternoon (GMT) Dec 10 00:26:57 hmm Dec 10 00:26:59 mom Dec 10 00:27:05 whiteboard Dec 10 00:27:14 for now I've got to sort my son out, back in 1-2 hrs Dec 10 00:27:19 I implemented it in main Dec 10 00:27:48 because you need to add the source to the forrest.core.xconf Dec 10 00:29:56 i expected that you were doing it in trunk proper. That is why i asked if it might affect other stuff. I reckon that you should go ahead. Dec 10 00:30:03 xley I did an update and yes it is working Dec 10 00:30:23 k Dec 10 00:30:30 let me commit Dec 10 00:30:52 if you would have a minute afterwards for testing that would be great Dec 10 00:31:39 Re; Cocoon upgrade ... great, what about http://issues.apache.org/jira/browse/FOR-757 ... do you get that too? Dec 10 00:34:07 yes I get this too Dec 10 00:34:08 :( Dec 10 00:34:27 any clues? Dec 10 00:34:54 anyway, checkin your other work first. Dec 10 00:35:40 siteinfo-meta-navigation Dec 10 00:35:54 if you uncomment this contract then it is working Dec 10 00:36:06 meaning that something in this contract is wrong Dec 10 00:36:08 but Dec 10 00:36:17 http://localhost:8888/resolve.contract.html.siteinfo-meta-navigation Dec 10 00:36:20 and Dec 10 00:36:27 http://localhost:8888/prepare.contract.html.siteinfo-meta-navigation Dec 10 00:36:32 are resolved fine Dec 10 00:36:38 further Dec 10 00:36:56 Caused by: org.apache.commons.lang.exception.NestableRuntimeException: javax.xml.transform.TransformerException: java.lang.ClassCastException Dec 10 00:37:27 smells like there are variables used that cannot be resolved Dec 10 00:37:39 this happends if you do Dec 10 00:37:43 xsl:param Dec 10 00:38:00 and then use this param like $param/something Dec 10 00:38:06 and the param is null Dec 10 00:38:35 looking at http://localhost:8888/prepare.contract.html.siteinfo-meta-navigation Dec 10 00:38:37 you find Dec 10 00:38:44 Dec 10 00:38:58 and in the index.fv we defined: Dec 10 00:39:09 Dec 10 00:39:21 so no param passed to the contract Dec 10 00:40:15 and looking at Dec 10 00:40:16 http://localhost:8888/resolve.contract.html.siteinfo-meta-navigation Dec 10 00:40:19 you find Dec 10 00:40:35 ]]> Dec 10 00:41:01 so the contract definition in the structurer is wrong Dec 10 00:45:16 xley fixed Dec 10 00:46:03 beauty Dec 10 00:46:56 ;-) Dec 10 00:46:58 thorsten = star man! Dec 10 00:47:13 interesting that it worked before the Cocoon upgrade. Dec 10 00:47:15 David, I'm looking for something I can do in 5 minute breaks... Dec 10 00:47:21 I'm going to go through your list of plugins Dec 10 00:47:50 lol Dec 10 00:48:05 so you will be finished before breakfast then Dec 10 00:48:39 :-) you misunderstand - I'm simply going to look if they are converted or not and make a note in the issue Dec 10 00:48:54 :-) Dec 10 00:51:30 Añadiendo java/org/apache/forrest/locationmap/sourceAñadiendo java/org/apache/forrest/locationmap/source Dec 10 00:51:30 Añadiendo java/org/apache/forrest/locationmap/source/impl Dec 10 00:51:30 Añadiendo java/org/apache/forrest/locationmap/source/impl/LocationmapSourceFactory.java Dec 10 00:51:30 Enviando webapp/WEB-INF/xconf/forrest-core.xconf Dec 10 00:51:30 Transmitiendo contenido de archivos .. Dec 10 00:51:31 Commit de la revisión 355474. Dec 10 00:53:52 I added as well an example to the themer plugin Dec 10 00:54:06 please try and report back Dec 10 00:54:17 btw you need to build.sh forrest! Dec 10 00:54:24 ;-) Dec 10 00:55:21 your IRC post was garbled (something about forrest-core.xconf) ... was i supposed to do something with it? Dec 10 00:55:41 jeje Dec 10 00:55:43 no Dec 10 00:55:54 just to let you know I committed Dec 10 00:56:02 http://svn.apache.org/viewcvs?rev=355475&view=rev Dec 10 00:56:09 i get the svn mail Dec 10 00:56:10 http://svn.apache.org/viewcvs?rev=355474&view=rev Dec 10 00:56:15 k Dec 10 00:56:25 Ok will have to do some work Dec 10 00:56:56 see you later. Dec 10 01:02:46 can you try Dec 10 01:03:02 http://localhost:8888/test-lm.project.xmap.sitemap Dec 10 01:03:10 in the v2 template Dec 10 01:03:13 please Dec 10 01:06:35 what am i looking for? Dec 10 01:06:50 whether that returns something Dec 10 01:06:57 yes it does Dec 10 01:07:04 k Dec 10 01:07:07 and Dec 10 01:07:34 http://localhost:8888/test-lm.resolve.structurer.index-foo Dec 10 01:09:00 yes i do see stuff Dec 10 01:09:06 hmmm Dec 10 01:09:29 did you requested before test.dispatcher? Dec 10 01:10:23 i only did index.html then the two that you asked for. Dec 10 01:10:31 hmm Dec 10 01:10:33 lol Dec 10 01:10:42 it seems it fixed it itself Dec 10 01:11:08 I now can request any locationmap resource via test-lm. Dec 10 01:12:03 can you test some other locations from the lm please Dec 10 01:12:17 if they are working then I can remove the fix me note Dec 10 01:12:28 ah Dec 10 01:12:37 now think why it is working Dec 10 01:12:57 no wrong thought Dec 10 01:13:02 I did build ;-) Dec 10 01:38:53 Thorsten, I am back - you want me to do some testing? Dec 10 01:41:39 yeah please Dec 10 01:41:49 see my mail @dev Dec 10 01:42:50 Say that, thanks Dec 10 01:42:55 Question re: http://issues.apache.org/jira/browse/FOR-144 Dec 10 01:43:09 Can we move this to 0.9 for review? Views removes skinconf.xml Dec 10 01:43:16 yeah Dec 10 01:43:26 +1 Dec 10 02:01:12 your source resolver works for importing XSL from one resource into another - COOL! Dec 10 02:01:25 (see commit on projectInfo plugin) Dec 10 02:02:15 :) Dec 10 02:02:17 jeje Dec 10 02:03:13 guess why I wrote it in the end Dec 10 02:03:50 I need to import a common variable xsl Dec 10 02:04:09 and I was fed up to write workarounds in th sitemap ;-) Dec 10 02:11:11 (15:01:34) rgardler: (see commit on projectInfo plugin) <- which one? Dec 10 02:14:36 355492 - commit mail should be in your inbox - but SVN seems to be having problems again Dec 10 02:25:49 Can someone who followed the JXPath stuff please review http://issues.apache.org/jira/browse/FOR-675 and related issues (i.e. still fix-for 0.8?) Dec 10 02:33:38 I am not sure Dec 10 02:33:47 it is fixed with a workaround Dec 10 02:33:57 so actually it is fixed in 0.8 Dec 10 02:34:12 but not correst like David stated in the last comment Dec 10 02:34:38 anyway it is working so we should resolve it and leave it open Dec 10 02:34:44 wdyt? Dec 10 02:36:01 ross :) Dec 10 02:36:06 saw the commits Dec 10 02:36:13 so it is working 4 u Dec 10 02:36:17 nice :) Dec 10 02:37:46 btw I am developing a variable.helper.xsl Dec 10 02:38:16 which contains all xsl variables from forrest Dec 10 02:39:20 In the end it should be transformed with the new forrest.properties.xml that this variables as well got included to the xsl Dec 10 03:28:24 variable.helper sounds useful - we can enhance that quite a bit with descrption elements etc. Dec 10 03:28:28 Self documenting :-) Dec 10 03:28:48 Re JXPath issue, I agree, I'll adjust the issue now. Dec 10 03:59:32 I am off Dec 10 03:59:44 maybe I can connect later again Dec 10 03:59:49 if not cu u all Dec 10 04:00:01 nice working with you again ;-) Dec 10 04:00:03 salu2 Dec 10 04:00:06 <-- tscherler (n=thorsten@242.Red-213-97-135.staticIP.rima-tde.net) has left #for-dec Dec 10 05:22:03 I'm lonely... Dec 10 05:26:37 --> tscherler (n=thorsten@d83-180-165-147.cust.tele2.es) has joined #for-dec Dec 10 05:26:41 :) Dec 10 05:26:47 internet @home Dec 10 05:26:51 hurray Dec 10 05:52:37 Wow Thorsten - you hit the big time :-) Dec 10 05:53:19 :) what do you mean Dec 10 05:57:10 btw ross seems the lm:// is working :) nice Dec 10 06:01:08 I mean you have Internet at home. Dec 10 06:01:13 yes, the lm:// is cool Dec 10 06:01:43 :) Dec 10 06:01:49 to both ;-) Dec 10 06:04:11 I think it was the objectModel problem that I had when I entered this chat the first time this morning. I solved it before I commited but did not a build.sh clean, so I thought it was not working. Really happy that is actually does. Dec 10 06:04:40 BTW to the variables stuff Dec 10 06:04:59 your properties cannot be used in a contract, or? Dec 10 06:05:08 if yes, how Dec 10 06:05:41 They can't be used directly in a contract, but... Dec 10 06:06:14 My background is that while adjusting the branding-theme-profiler contract I found out that the $skin-img variable could not be resolved Dec 10 06:06:20 I have used them to pass values into a transformation via the sitemap () Dec 10 06:06:26 yeah Dec 10 06:06:28 Could you do something similar? Dec 10 06:06:35 hmm Dec 10 06:06:42 do u have a minute? Dec 10 06:07:01 abou 5 minutes judging by the smell coming fom the kitchen ;-) Dec 10 06:07:11 k Dec 10 06:07:13 :) Dec 10 06:08:06 please have a look at Dec 10 06:08:12 contractBean Dec 10 06:08:18 223 Dec 10 06:08:20 /* Dec 10 06:08:20 * FIXME: Set default properties Dec 10 06:08:20 */ Dec 10 06:08:20 // transformer.setParameter() Dec 10 06:08:43 here we would have to pass all default parameters to a contract Dec 10 06:09:08 that is quite cumbersome by hand Dec 10 06:09:17 we need to have something smart here Dec 10 06:09:28 your properties format is nice Dec 10 06:09:47 and "compatible" with the one we have in the structurer Dec 10 06:10:40 now to pass everything (each property) as param is not efficient Dec 10 06:11:20 the contract author will end up with a long list of params in the prolog of its contract Dec 10 06:11:27 not nice Dec 10 06:12:41 further more one have to generate a param/variable xsl/alias stylesheet to include *all* properties from forrest.properties.xml Dec 10 06:13:11 It is possible like demenstrated in v1 ;-) but not the best way Dec 10 06:13:13 IMO Dec 10 06:13:30 First question: where is contractBean? Dec 10 06:13:54 the best would be to have 1 param (forrest-variables) and that is a xml file like we did with skinconf Dec 10 06:14:07 package org.apache.forrest.dispatcher; Dec 10 06:14:40 public class ContractBean extends Beans implements ContractBeanInterface { Dec 10 06:14:56 woops I see this part is not yet committed Dec 10 06:15:16 I mean the iinterface Dec 10 06:17:23 So let me see if I understand the problem... Dec 10 06:17:58 A contract has X properties, most of which will have a default setting Dec 10 06:18:12 The user is able to override default by using a propeties file Dec 10 06:18:35 we want a way of having the properties passed to the trasnformer Dec 10 06:18:47 *without* the contract defining the properties in advance Dec 10 06:18:55 in other words the contract just uses them Dec 10 06:19:00 is that right? Dec 10 06:19:45 No wait... let me try that again... Dec 10 06:19:51 A contract has X properties, most of which will have a default setting Dec 10 06:20:15 The user is able to override the defaults (by defining them in the structurer definition) Dec 10 06:20:27 is *that* right? Dec 10 06:24:03 yes Dec 10 06:24:09 but like diwaker said Dec 10 06:25:11 but Dec 10 06:25:37 we decide between contract properties and default xsl helper properties Dec 10 06:25:40 like Dec 10 06:26:00 Dec 10 06:26:00 Dec 10 06:26:00

Dec 10 06:26:00

Dec 10 06:26:00 Dec 10 06:26:18 the problem is that this props are only aviable in xsl Dec 10 06:26:26 which makes them less usable Dec 10 06:27:15 so we should generate a forrest.properties.xml out of all this variables from xsl Dec 10 06:27:29 then we can use the * FIXME: Set default properties Dec 10 06:27:29 (19:08:30) tscherler: */ Dec 10 06:27:29 (19:08:30) tscherler: // transformer.setParameter() Dec 10 06:28:35 to pass the forrest.properties.xml into the transformation via *one* param for the default variables Dec 10 06:29:01 those would have been now accessed differently but that is a small change Dec 10 06:29:29 do you understand what I mean? Dec 10 06:31:37 I think I understand the concept, but I'm not really seeing the problem... Dec 10 06:31:59 I am going to have my dinner now, perhaps you could formulate a mail on this... Dec 10 06:32:06 I'll ahve a look when I return Dec 10 06:32:36 (since don't see the problem, I obviously don't understand you fully ;-) Dec 10 06:34:53 jeje Dec 10 06:34:57 no worries Dec 10 06:35:06 there is no big problem Dec 10 06:35:35 I will go now to bball practise cu later Dec 10 06:35:44 --- tscherler is now known as bball Dec 10 09:23:49 hello, is anyone still there Dec 10 09:25:41 --- #for-dec :[freenode-info] If you're at a conference, please contact freenode staff to make sure we've made special allowance for many users coming into our network from a single internet address ( http://freenode.net/faq.shtml#gettinghelp ). Private messages from unregistered users are currently blocked, except to network staff, services and participating registered users ( http://freenode.net/faq.shtml#privmsg )... Thanks! Dec 10 09:28:30 --> rgardler_ (n=chatzill@82-69-78-226.dsl.in-addr.zen.co.uk) has joined #for-dec Dec 10 09:28:56 hello Dec 10 09:30:07 good morning to yu / evening to me Dec 10 09:30:36 Hi Ross, you got a lot done with tidying up Jira. Thanks. Dec 10 09:30:43 Why am I here twice? Must be because my laptio went to sleep or something Dec 10 09:30:51 Someone has to do it ;-) Dec 10 09:31:07 I was about to do some more as I have had enough of coding for a while Dec 10 09:31:48 sorry - I should have said someone has to help you do it ;-) Dec 10 09:32:51 :-) we need to be doing more as we go, rather than leave it to mount up. Dec 10 09:33:20 Yes, I agree, it is clear that we are all just dumpring into the next version Dec 10 09:33:34 I think our discussion on list neds to be docuemnted and "enforced" Dec 10 09:35:52 I was hoping that Cocoon would join forces with us and we could solve that Severity/Priority/Fix-Priority thing. Dec 10 09:36:31 I will reply to my own cocoon-dev email ... perhaps it got lost in the noise of the last few days. Dec 10 09:37:01 Too much "shiny new thing" stuff over there right now - maybe when ... (you typed "noise level" so no need for me to go on) Dec 10 09:38:23 good noise, but other things got swamped. Dec 10 09:39:39 definetely good :-)) Dec 10 09:40:06 Another issue with Jira is fix releases for plugin issues - e.g. http://issues.apache.org/jira/browse/FOR-259 Dec 10 09:40:38 plugins don't have version numbers in Jira so no way to schedule them independantly of Core Dec 10 09:43:21 <-- bball has quit (Read error: 110 (Connection timed out)) Dec 10 09:43:59 <-- rgardler has quit (Read error: 110 (Connection timed out)) Dec 10 09:45:12 i don't see how we can fix that. I see from infra@ messages that Maven project is creating Jira sub-project for each plugin. Dec 10 09:45:42 We should investigate their Jira and see if we should do the same. Dec 10 09:46:27 I'm not sure about that, 36 plugins if we count whiteboard... Dec 10 09:48:30 yes, a problem. Dec 10 09:49:07 Perhaps the suggestion about a new "fix-priority" field will suffice. Dec 10 09:49:24 it will certainly help Dec 10 09:50:48 do you know where is Maven's issue tracker? Cannot see it from their website. Dec 10 09:51:42 woops, one of those collapsed left-hand menus Dec 10 09:52:03 :-) Dec 10 09:52:04 it goes to http://jira.codehaus.org/browse/MNG Dec 10 09:55:33 So they are managing their own instance of Jira - that makes the subprojects idea more manageable Dec 10 09:57:18 been separate since the beginning, like forrest was Dec 10 09:57:49 there is talk of bringing it to ASF on infra@ Dec 10 09:58:38 not "own instance" Dec 10 09:58:39 My concern is that there are already too many projects to make wide searches meaningful Dec 10 09:58:59 more at codehaus Dec 10 09:59:46 Yes, I see now... Dec 10 09:59:53 They have a large list of components Dec 10 10:00:08 i don't use default search Dec 10 10:00:12 but isn't that the same as us? Dec 10 10:00:44 yes, i think they want to do it differently Dec 10 10:00:53 like us Dec 10 10:01:00 Ahhh... ok Dec 10 10:01:14 and Cocoon, when we realise Dec 10 10:01:35 When I asked on Infra@ Jeff Turner said they (Atlassin) were aware of the issue Dec 10 10:01:49 The more projects make noise in their test site (Apache) the more likely they are to fix it Dec 10 10:02:22 Perhaps the best thing to do is to object to Maven on the grounds of everyone will want to do it - explosion of projects Dec 10 10:04:43 in the meantime we need to explore the custom field "fix-priority" etc. and per-project screens. Dec 10 10:04:57 +1 Dec 10 10:05:19 (although Jeff said per project screens were not possible) Dec 10 10:05:39 sorry, i meant Dec 10 10:06:09 ... Dec 10 10:06:54 the "issue screens" ... can be per-project, so we could add the "fix-priority" to ours Dec 10 10:06:57 ... Dec 10 10:07:26 and then get reports based on that field, also helps with search. Dec 10 10:08:18 +1 Dec 10 10:14:05 i have only got a bit more time, then travelling for couple hours. will check back in (but modem-based) so won't be doing much Dec 10 10:14:26 as you saw, i automated the log Dec 10 10:16:14 i see a couple of issues that i can close (nice clear roadmap :-) Dec 10 10:16:22 I'm off to bed early(ish) tonight, so I'll probably miss you when you check back in Dec 10 10:16:48 I hope you have a nice day Dec 10 10:16:49 it has been great Dec 10 10:17:30 yes, we will ... a bit of outdoors. Dec 10 10:17:55 No outdoors for me, too damn cold... Dec 10 10:18:09 we just built a new fireplace in the living room though... Dec 10 10:18:11 still here for a little longer. Anything you need to co-operate on? Dec 10 10:18:22 never owned an open fire before - superb! Dec 10 10:18:36 Co-operation.... let me think Dec 10 10:19:24 nice AtmosphereGenerator Dec 10 10:20:21 Yeah, I've always loved them, and have fires in the garden in the summer, but now I have one in the winter too :-)) Dec 10 10:21:21 You now, on the cooperation front... Dec 10 10:21:28 are you in a valley? Becoming a SmogGenerator here Dec 10 10:21:38 okay Dec 10 10:22:11 it's a real shame Gobby isn't running on mac, we really could do with working on a doc to guide the use of Jira and Gobby is the way to do it Dec 10 10:22:25 There was a new release a while back, I'm going to see if they improved the mac version Dec 10 10:22:44 (in a valley? no- I live in a place called Longridge - the name gives it away ;-) Dec 10 10:22:56 I'm in a village on the top of a hill Dec 10 10:24:23 :-( Gobby no good for mac yet Dec 10 10:25:33 Oh.. hang on, another page says DarwinPorts is ready Dec 10 10:25:35 http://darcs.0x539.de/trac/obby/cgi-bin/trac.cgi/wiki/HowToGobbyFromSourceMacOSX Dec 10 10:25:42 does that make it installable? Dec 10 10:28:05 i will do some research. I have steered clear of X11 based apps because the first one needs to install so much other stuff. Dec 10 10:28:34 wanted to wait until that infrastructure had improved. Probably now. Dec 10 10:28:41 Yeah, I read the "run the install it overnight" comment Dec 10 10:29:25 Well it really would be useful for writing projet guidelines/docs etc. collaboratively Dec 10 10:29:32 i need other X11 apps, so will install them first, then Gobby. Dec 10 10:29:34 assuming that FF continues Dec 10 10:29:52 (I'll continue doing it I find it useful to block the time out for Forrest) Dec 10 10:31:15 by "co-operate" i meant is there something forrest-related we need to discuss in this near real-time? Dec 10 10:32:29 yeah, I appreciate that, but not really, other than something like how touse Jira Dec 10 10:32:33 but we did that onlist... Dec 10 10:32:45 Having said that, have you looked at the new forrest.properties.xml stuff? Dec 10 10:33:41