Author: crossley
Date: Fri Feb 10 05:20:05 2006
New Revision: 376656
URL: http://svn.apache.org/viewcvs?rev=376656&view=rev
Log:
Update
Modified:
forrest/events/forrest-friday/20060210-log.txt
Modified: forrest/events/forrest-friday/20060210-log.txt
URL:
http://svn.apache.org/viewcvs/forrest/events/forrest-friday/20060210-log.txt?rev=376656&r1=376655&r2=376656&view=diff
==============================================================================
--- forrest/events/forrest-friday/20060210-log.txt (original)
+++ forrest/events/forrest-friday/20060210-log.txt Fri Feb 10 05:20:05 2006
@@ -435,3 +435,72 @@
[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 <color name=...> 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_: <locator caching="true">
+[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 <color
name=...> 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_ <locator caching="true"> 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 <forrest:property
name="branding-theme-profiler"> section.
+[00:06] _Gav_: <color name="breadtrail" value="#cedfef" font="#0F3660"
link="#0F3660" vlink="#0F3660" hlink="#000066"/>
+[00:06] _Gav_: <color name="header" value="#294563"/>
+[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 <color name="breadtrail"
value="#cedfef" font="#0F3660" link="#0F3660" vlink="#0F3660" hlink="#000066"/>
+[00:12] _Gav_: <color name="header" value="#294563"/>
+[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 <forrest:property
name="branding-theme-profiler">
+[00:13] _Gav_: maybe leave one sample in there
+[00:13] _Gav_: <color name="breadtrail" value="#cedfef" font="#0F3660"
link="#0F3660" vlink="#0F3660" hlink="#000066"/>
+[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
