svn commit: r368694 - /forrest/events/forrest-friday/20060113-log.txt

[cr...@apache.org]

Author: crossley
Date: Fri Jan 13 04:00:12 2006
New Revision: 368694

URL: http://svn.apache.org/viewcvs?rev=368694&view=rev
Log:
Update

Modified:
    forrest/events/forrest-friday/20060113-log.txt

Modified: forrest/events/forrest-friday/20060113-log.txt
URL: http://svn.apache.org/viewcvs/forrest/events/forrest-friday/20060113-log.txt?rev=368694&r1=368693&r2=368694&view=diff
==============================================================================
--- forrest/events/forrest-friday/20060113-log.txt (original)
+++ forrest/events/forrest-friday/20060113-log.txt Fri Jan 13 04:00:12 2006
@@ -82,3 +82,75 @@
 Jan 13 23:35:52 <_Gav_>	Congrats to Ross on ASF Membership, good stuff.
 Jan 13 23:35:55 <_Gav_>	:)
 Jan 13 23:38:25 -->	rgardler (n=chatzill@82-69-78-226.dsl.in-addr.zen.co.uk) has joined #for-j
+Jan 13 23:40:52 <_Gav_>	ok, caught up on logs :|
+Jan 13 23:41:12 <_Gav_>	Morning Ross
+Jan 13 23:43:58 <Cyriaque>	Thorsten, can you tell me why cannot use the $root variables in contracts and why I cannot access to the render-logo template which is defined in the structurer
+Jan 13 23:44:01 <tscherler>	Paul is not around today, or?
+Jan 13 23:44:08 <Cyriaque>	in the render-logo.xsl
+Jan 13 23:44:21 <tscherler>	path?
+Jan 13 23:44:26 <tscherler>	v3?
+Jan 13 23:44:41 <xley>	tscherler: not heard from Paul yet on IRC
+Jan 13 23:44:55 <Cyriaque>	actually, I don't know ;)
+Jan 13 23:44:55 <tscherler>	render-logo.xsl ?
+Jan 13 23:45:05 <tscherler>	xley thx
+Jan 13 23:45:10 <tscherler>	k
+Jan 13 23:45:21 <tscherler>	but it is for v3
+Jan 13 23:45:23 <tscherler>	right?
+Jan 13 23:45:25 <Cyriaque>	yes
+Jan 13 23:45:51 <rgardler>	XLey - I'm looking at the locationmap in plugins stuff
+Jan 13 23:46:03 <xley>	me too
+Jan 13 23:46:08 <rgardler>	is the error you referred to earlier reported as a {project:skinconf} problem
+Jan 13 23:46:15 <Cyriaque>	First, in v2 we didn't have to define a root variable in contracts, now I wander how to define it ?
+Jan 13 23:46:27 <tscherler>	k Cyriaque have a look at
+Jan 13 23:46:29 <tscherler>	master.ft
+Jan 13 23:46:34 <Cyriaque>	Ok
+Jan 13 23:46:52 <xley>	rgardler: not sure what you mean ...
+Jan 13 23:47:12 <xley>	no, i was getting actual xml validation errors
+Jan 13 23:47:18 <xley>	gone now
+Jan 13 23:47:27 <rgardler>	OK, I'll svn up and check again - thanks
+Jan 13 23:47:42 <Cyriaque>	Thorsten: Ok for the root defaultVariables, thanks,
+Jan 13 23:47:54 <tscherler>	<xsl:variable name="skin-img-dir" select="$defaultVariables/*/*[@name='skin-img-dir']/@value"/>
+Jan 13 23:48:16 <tscherler>	actualy it works for all variables
+Jan 13 23:48:39 <tscherler>	I documented that somewhere but cannot find it where  :(
+Jan 13 23:49:22 <tscherler>	jeje in master.fv
+Jan 13 23:49:22 <Cyriaque>	in master.ft...
+Jan 13 23:49:27 <tscherler>	:)
+Jan 13 23:49:28 <tscherler>	 <!-- If you need default variables: -->
+Jan 13 23:49:28 <tscherler>	      <!--<xsl:param name="defaultVariables" select="'test.html'"/>-->
+Jan 13 23:49:28 <tscherler>	      <!-- then extract the variable like: -->
+Jan 13 23:49:28 <tscherler>	      <!--<xsl:variable name="skin-img-dir" select="$defaultVariables/*/*[@name='skin-img-dir']/@value"/>-->
+Jan 13 23:49:28 <tscherler>	      <!-- more information which variables are aviable can be found at lm://transform.xml.variable.helper 
+Jan 13 23:49:29 <tscherler>	        
+Jan 13 23:49:31 <tscherler>	          FIXME: This property xsl is in early stage and aims to be connected to the new established input module based one.
+Jan 13 23:49:34 <tscherler>	          We need to write a custom generator for this. The generator will contact the prop-input module to get all aviable key/values and
+Jan 13 23:49:37 <tscherler>	          outputs them to xml (dtd like forrest.properties.xml). -->
+Jan 13 23:49:39 <tscherler>	          
+Jan 13 23:50:08 <tscherler>	rgardler
+Jan 13 23:50:17 <tscherler>	is there a way to use
+Jan 13 23:50:22 <tscherler>	forrest.properties.xml
+Jan 13 23:50:27 <tscherler>	instead of 
+Jan 13 23:50:30 <tscherler>	forrest.properties
+Jan 13 23:50:36 <tscherler>	for the ant build?
+Jan 13 23:51:01 <rgardler>	I've not looked into it yet, but... 
+Jan 13 23:51:13 <rgardler>	I am pretty sure that there is an ANT task to load...
+Jan 13 23:51:20 <rgardler>	properties from an XML file...
+Jan 13 23:51:26 <rgardler>	Not sure of the format though...
+Jan 13 23:51:28 <tscherler>	yeah nothing default I am afraid
+Jan 13 23:51:30 <rgardler>	we should check that ASAP
+Jan 13 23:51:35 <tscherler>	yes
+Jan 13 23:51:47 <tscherler>	I want to delete forrest.properties
+Jan 13 23:51:54 <tscherler>	from the dispatcher
+Jan 13 23:52:16 <rgardler>	That would need a vote as the xml properties are only in testing now
+Jan 13 23:52:16 <tscherler>	all dispatcher projects *have* to work without this probs
+Jan 13 23:52:29 <tscherler>	that brings us closer to multiple projects
+Jan 13 23:52:32 <rgardler>	(can't see a problem, but its a major issue)
+Jan 13 23:52:43 <tscherler>	yeah
+Jan 13 23:52:51 <rgardler>	DO you want to call it then?
+Jan 13 23:53:17 <tscherler>	atm need to finish some work 
+Jan 13 23:53:36 <tscherler>	I can do later if no on beats me to it
+Jan 13 23:54:10 <rgardler>	Actually, thinking about it we should decide on the branch or not issue for dispatcher (see my last mail in that thread)
+Jan 13 23:54:51 <tscherler>	Yeah maybe a branch would be better
+Jan 13 23:55:34 <tscherler>	I am only afraid that if I branch i need to sync that with trunk and being alone ;-)
+Jan 13 23:57:00 <xley>	if each branch is quick and purpose-specific, then easy to merge. Why would you be "alone"?
+Jan 13 23:57:56 <tscherler>	I am not sure if more people want to take the extra step of work related to using a branch
+Jan 13 23:59:33 <xley>	i for one have no trouble - either a separate checkout or 'svn switch' (usually do the former)