Unfortunatelly as far as I know in Opera there is only implementation in en. In
general, there is significant lag between visual and audio in web
technologies... Maybe other frequently used languages are implemented in other
borwsers, but I doubt. And IMHO I think that X-V by iteself should
Something like the following should do it:
xsl:apply-tempaltes select=@*[name(.) !- 'id']/
Thanks. A bit of finetuning and some corrections and it seems to work
ok. Will be offline next week so feel free to roll-back if I missed
something.
--
Ferdinand Soethe
Looking closely at document2html (in common) I have my doubts about
the usefulness of translating every id-attribute into an html-anchor
(a name=.../) element. Especially when I start using ids for CSS,
it means that this drastically increases the volume of the final page
by creating lots of
Ferdinand Soethe wrote:
Looking closely at document2html (in common) I have my doubts about
the usefulness of translating every id-attribute into an html-anchor
(a name=.../) element. Especially when I start using ids for CSS,
it means that this drastically increases the volume of the final page
I've taken a quick glimpse at Forrest's memory usage, using the
lovely Yourkit Java Profiler (http://www.yourkit.com/).
I did the following: I ran forrest site in site-author/, and made a
snapshot, quite at the end of the run. Note that I have only limited
understanding of Forrest's and Cocoon's
G'day devs,
for now we limited views to templates in our discussion *but* what I
recommend is more then this templating part of forrest:views.
forrest:views will change the way we are processing a request. I
designed it after the Dispatcher View J2EE design pattern [1].
Dispatcher View
Context
On Sat, 2005-07-16 at 00:54 -0700, Diwaker Gupta wrote:
(some of the comments here might not be specific to views and encroach into
other areas of Forrest)
Experiences as a user
=
Let me first talk a little about my user experience of views so far:
o Its *really*
Nicola Ken Barozzi wrote:
Over time, some seem to recurringly ask that Forrest creates a simple
committer role used as a step between being a developer and a PMC member.
Here is an explanation of what I think I have learned in this respect.
Other people might have different views and
Ross Gardler wrote:
However, if anyone wants to go to ApacheCon the way to reduce your costs
considerably is to participate in the conference organisation or
presentations. There is a list for the organisation (David, what is the
address?).
Don't know, but start at apachecon-discuss
[EMAIL PROTECTED] wrote:
+ warningOpera with Voice is currently not available for Linux./warning
There is not any alternative for linux users?
Cheers,
cheche
Forgive me for being obtuse, but I completely missed the change in procesing
paradigm part :-) I mean, were you talking about a conceptual paradigm
shift, or an implementation detail? Conceptually, IIUC, we still follow a
dispatcher-view patter, no? I mean Forrest has been about separating
On Saturday 30 July 2005 3:49 am, Ferdinand Soethe wrote:
Looking closely at document2html (in common) I have my doubts about
the usefulness of translating every id-attribute into an html-anchor
(a name=.../) element. Especially when I start using ids for CSS,
it means that this drastically
Thorsten Scherler wrote:
forrest:views will change the way we are processing a request.
Please explain why your example below changes the *way* we process a
request:
forrest:contract name=content-feeder
forrest:properties contract=content-feeder
forrest:property
Thorsten Scherler wrote:
I replied in a another response with respect to the processing paradigm.
This response is about a different issue, hence the change in subject.
The business helper that we have are best described by our most famous
contract.
forrest:contract name=content-feeder
Thorsten Scherler wrote:
On Sat, 2005-07-16 at 00:54 -0700, Diwaker Gupta wrote:
...
Then, I think we should build up a publicly available repository of the
following:
o contracts
o views
o skins
contracts: As a very crude analogy, think of these as components in a portal
or thinggies
[NOTE: this is my summary of my interpretation of *part* of the
discussion at the views workshop at Apachecon. In other words I have
tried to represent the views of those present, but may have got some
bits wrong - this is a document for discussion not a final document.
You can get the audio
Diwaker Gupta wrote:
Forgive me for being obtuse, but I completely missed the change in procesing
paradigm part :-) I mean, were you talking about a conceptual paradigm
shift, or an implementation detail? Conceptually, IIUC, we still follow a
dispatcher-view patter, no?
See my overlapping
HANAX wrote:
Unfortunatelly as far as I know in Opera there is only implementation in en. In
general, there is significant lag between visual and audio in web
technologies... Maybe other frequently used languages are implemented in other
borwsers, but I doubt. And IMHO I think that X-V by
This is *my* interpretation of the talks we have had (or at least the
ones I was a part of), it does not necessarily represent the views of
other devs, nor is it necessarily complete.
We tried to include the views of devs not present (where they had been
outlined on the list prior to ApacheCon),
A lot of Apache projects have their Wiki hosted at
http://wiki.apache.org/general/. I think we *really* need a Wiki right now
for Forrest, for the following reasons:
o turn around time for making small documentation changes on the Forrest
website is high
o a Wiki will give chance to Forrest
Just a minor correction:
On Saturday 30 July 2005 4:53 pm, Ross Gardler wrote:
We had a design discussion about this and you can find Nicola's notes in
SVN (see the hackathon directory in the etc directory of trunk).
Together with the audio of our dicsussions (thanks David)
These now live in
On Saturday 30 July 2005 4:38 pm, Ross Gardler wrote:
o naming and terminology: what is a view? what is a template? given the
same content (generated by some template), are there different views
for each output type?
This was discussed at the hackathon, and I just sent a mail to help us
On Saturday 30 July 2005 3:22 pm, Ross Gardler wrote:
forrest:contract name=content-feeder
forrest:properties contract=content-feeder
forrest:property name=content-feeder
nugget=get.nugget.feeder
url/feeds/somefeed.xml/url
/forrest:property
Ross Gardler wrote:
We discussed a roadmap, Nicola (or was it David) took some notes on it.
Hopefullly he has read this far and still has the scraps of paper.
Otherwise we need to recreate it here.
Actually we were deliberately not calling it a roadmap.
Rather topics for discussion. These and
Ron Blaschke wrote:
I've taken a quick glimpse at Forrest's memory usage, using the
lovely Yourkit Java Profiler (http://www.yourkit.com/).
Thanks a million. That is one of our important tasks.
I did the following: I ran forrest site in site-author/, and made a
snapshot, quite at the end of
Ross Gardler wrote:
Ferdinand Soethe wrote:
Ross Gardler wrote:
Hmmm... we had better create an issue for this, it smells of a memory
leak.
Done a while ago: FOR-572.
Don't get me wrong I just took the first size that worked. Doesn't
mean it has to be this much.
Yeah, I understand
Diwaker Gupta wrote:
A lot of Apache projects have their Wiki hosted at
http://wiki.apache.org/general/. I think we *really* need a Wiki right now
for Forrest, for the following reasons:
Not so fast. We have discussed this recently in the
mail archives. The decision was not to do it because
27 matches
Mail list logo
