forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r355561 - /forrest/events/forrest-friday/20051209-log.txt
Date Fri, 09 Dec 2005 18:20:17 GMT
Author: crossley
Date: Fri Dec  9 10:20:12 2005
New Revision: 355561

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

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

Modified: forrest/events/forrest-friday/20051209-log.txt
URL: http://svn.apache.org/viewcvs/forrest/events/forrest-friday/20051209-log.txt?rev=355561&r1=355560&r2=355561&view=diff
==============================================================================
--- forrest/events/forrest-friday/20051209-log.txt (original)
+++ forrest/events/forrest-friday/20051209-log.txt Fri Dec  9 10:20:12 2005
@@ -246,3 +246,54 @@
 Dec 10 05:52:37 <rgardler>	Wow Thorsten - you hit the big time :-)
 Dec 10 05:53:19 <tscherler>	:) what do you mean
 Dec 10 05:57:10 <tscherler>	btw ross seems the lm:// is working :) nice
+Dec 10 06:01:08 <rgardler>	I mean you have Internet at home.
+Dec 10 06:01:13 <rgardler>	yes, the lm:// is cool
+Dec 10 06:01:43 <tscherler>	:)
+Dec 10 06:01:49 <tscherler>	to both ;-)
+Dec 10 06:04:11 <tscherler>	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 <tscherler>	BTW to the variables stuff
+Dec 10 06:04:59 <tscherler>	your properties cannot be used in a contract, or?
+Dec 10 06:05:08 <tscherler>	if yes, how
+Dec 10 06:05:41 <rgardler>	They can't be used directly in a contract, but...
+Dec 10 06:06:14 <tscherler>	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 <rgardler>	I have used them to pass values into a transformation via
the sitemap (<map:param ...>)
+Dec 10 06:06:26 <tscherler>	yeah
+Dec 10 06:06:28 <rgardler>	Could you do something similar?
+Dec 10 06:06:35 <tscherler>	hmm
+Dec 10 06:06:42 <tscherler>	do u have a minute?
+Dec 10 06:07:01 <rgardler>	abou 5 minutes judging by the smell coming fom the kitchen
;-)
+Dec 10 06:07:11 <tscherler>	k
+Dec 10 06:07:13 <tscherler>	:)
+Dec 10 06:08:06 <tscherler>	please have a look at
+Dec 10 06:08:12 <tscherler>	contractBean 
+Dec 10 06:08:18 <tscherler>	223
+Dec 10 06:08:20 <tscherler>	  /*
+Dec 10 06:08:20 <tscherler>	                     * FIXME: Set default properties
+Dec 10 06:08:20 <tscherler>	                     */
+Dec 10 06:08:20 <tscherler>	                    // transformer.setParameter()
+Dec 10 06:08:43 <tscherler>	here we would have to pass all default parameters to a
contract
+Dec 10 06:09:08 <tscherler>	that is quite cumbersome by hand
+Dec 10 06:09:17 <tscherler>	we need to have something smart here
+Dec 10 06:09:28 <tscherler>	your properties format is nice
+Dec 10 06:09:47 <tscherler>	and "compatible" with the one we have in the structurer
+Dec 10 06:10:40 <tscherler>	now to pass everything (each property) as param is not
efficient 
+Dec 10 06:11:20 <tscherler>	the contract author will end up with a long list of params
in the prolog of its contract
+Dec 10 06:11:27 <tscherler>	not nice
+Dec 10 06:12:41 <tscherler>	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 <tscherler>	It is possible like demenstrated in v1 ;-) but not the
best way
+Dec 10 06:13:13 <tscherler>	IMO
+Dec 10 06:13:30 <rgardler>	First question: where is contractBean?
+Dec 10 06:13:54 <tscherler>	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 <tscherler>	package org.apache.forrest.dispatcher;
+Dec 10 06:14:40 <tscherler>	public class ContractBean extends Beans implements ContractBeanInterface
{
+Dec 10 06:14:56 <tscherler>	woops I see this part is not yet committed 
+Dec 10 06:15:16 <tscherler>	I mean the iinterface
+Dec 10 06:17:23 <rgardler>	So let me see if I understand the problem...
+Dec 10 06:17:58 <rgardler>	A contract has X properties, most of which will have a default
setting
+Dec 10 06:18:12 <rgardler>	The user is able to override default by using a propeties
file
+Dec 10 06:18:35 <rgardler>	we want a way of having the properties passed to the trasnformer
+Dec 10 06:18:47 <rgardler>	*without* the contract defining the properties in advance
+Dec 10 06:18:55 <rgardler>	in other words the contract just uses them
+Dec 10 06:19:00 <rgardler>	is that right?
+Dec 10 06:19:45 <rgardler>	No wait... let me try that again...
+Dec 10 06:19:51 <rgardler>	A contract has X properties, most of which will have a default
setting



Mime
View raw message