forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thorsten Scherler <thors...@apache.org>
Subject Re: [RT] Why using views - in comparison with "old fashion" skins - usecase i18n.
Date Sun, 05 Jun 2005 11:39:55 GMT
On Sat, 2005-06-04 at 21:03 -0700, Diwaker Gupta wrote: 
> > Yes that would be great. :) That could be the 'last-published-net'
> > contract.
> 
> Its funny, I chose the *exact* same name even before I wrote my first mail :)
> 

lol :)

Yeah, once started working with views and contracts the naming for the
contracts is pretty straight forward I guess. :) ;-)

> Anyways, I'm attaching last-published-net.ft. It uses an improved
> version of the XSL date service (no Perl script!). 

:) very nice. I just copied the contract in my local development project
(for testing) and it works like a charm. :) Thx a million. 

I will check that now in (in the viewHelper.xhtml) with a small change
in the caption instead of 
Last published on <xsl:value-of select="$dt"/>

I will checkin
<i18n:text >Last Published:</i18n:text>&#160; <xsl:value-of
select="$dt"/>

Now were we set up the i18n support we should use it. ;-)

I added as well a blank.ft which can serve as copy'n paste master in the
beginning for your offline editor and later on for the cform-based
view/contract online-editor-plugin I will add (hopefully) soon. 

BTW if you want to submit another contract that will get rid of jscript,
try sending a patch for http://issues.apache.org/jira/browse/FOR-134
Right now that do not exists as a contract, but I would like to see the
breadcrumbs.ft solving FOR-134 and not implementing the old
code. ;-) ...after wards it easy to back port that to "old fashion
skins".

> In addition, if a
> network connection is not available, one can use a similar solution on
> the localhost -- I have written a simple Python script to generate the
> required XML, so just replace the URL in the document function call
> with the path to date.py
> 

:) For now I did not check that script in but if you could write some
words how to setup everything and provide a 'last-published-local-net'
contract I will do that ASAP. 

My problem is where to add the *.py. IMO that is a businessService and I
still have to still look into the locationmap branch where I guess
businessServices should be defined. 

BTW the commits and mails relating to that topic are *very* promising.
@Ross how are the changes that we can use the locationmap stuff in a
plugin (businessHelper-plugin). ;-)

> I had a related question: it seems wasteful to generate the timestamp
> again and again for each processed file. Since the build happens
> within a few minutes at most, I'm content with recording the time at
> the start of the build and then using that throughout. This will save
> a lot of CPU cycles. I'm not an expert at XSL so I'm still looking as
> to what is the best way to define such a "global timestamp variable".
> 

Yeah +1 

Any suggestions how to implement that? Maybe with the locationmap? 

Thank you very much, Diwaker, for your constant testing effort, feedback and patches for views
that is helping me a million. Keep on! :)

salu2
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)


Mime
View raw message