On Wednesday 15 May 2002 07:45, David Crossley wrote:
. . .
So, let us develop a procedure whereby the opensource
model is still employed, yet there is initial quality control.
. . .
Following the opensource model, I think docs should be released as early as
possible, with only minimal
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9105.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9105.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On Wed, 15 May 2002, Bertrand Delacretaz wrote:
On Wednesday 15 May 2002 07:45, David Crossley wrote:
. . .
So, let us develop a procedure whereby the opensource
model is still employed, yet there is initial quality control.
. . .
Following the opensource model, I think docs should be
Dear All,
Sorry if this is noise
I just found a new (to me) editor that works very well with XML.
It is a general purpose code editor which merely has facilities
for XML.
JEdit http://www.jedit.org
What I like about it:
handles entity resolution catalogs
validates
I'm using this one for about 9 months, and that says enough, doesn't it?
You also have a lot of plugins, which beautify java code, auto-complete
of variables, etc etc.
The most important (imho) is the fact that you can do everything (at
least, everything I do: java progging, xml editing, text
Hi,
I think that we already have this. It is the duty of the
committer to undertake initial quality control when they
accept the patch from Bugzilla and prepare for their
commit. If they do not know anything about the topic, then
they should not be taking on the patch - let someone else
do it.
From: Gerhard Froehlich [mailto:[EMAIL PROTECTED]]
I think that we already have this. It is the duty of the
committer to undertake initial quality control when they
accept the patch from Bugzilla and prepare for their
commit. If they do not know anything about the topic, then
they should
Bertrand Delacretaz wrote:
On Wednesday 15 May 2002 07:45, David Crossley wrote:
. . .
So, let us develop a procedure whereby the opensource
model is still employed, yet there is initial quality control.
. . .
Following the opensource model, I think docs should be released as
early as
On Wednesday 15 May 2002 12:13, Diana Shannon wrote:
. . .
b) each doc has a unique ID
Do we really need unique ID attribute if filename is unique, or is this
short-sighted?
. .
Unique filenames would work for sure, doesn't have to be numerical, just
pratical to include in the subject
On Wednesday 15 May 2002 11:20, Stephan Michels wrote:
. . .
The best way to do this, is to implement the CVS support in cocoon.
. . .
Yes sure, but there's no such thing today AFAIK - I was trying to suggest a
concrete solution that can be implemented right away.
-Bertrand
On Wed, 15 May 2002, Jeremy Quinn wrote:
Dear All,
Sorry if this is noise
I just found a new (to me) editor that works very well with XML.
It is a general purpose code editor which merely has facilities
for XML.
JEdit http://www.jedit.org
Nice if you have a fast machine. Sadly
One of the main problem I hade when I started using web documented project
(it was CSS docs, XML/DOM, XSL, tomcat, I was young :) was to find a doc I
can understand.
Later, my problem was to find a doc without all that newbies blabla.
So I think that best topics grouping is the
http://cvs.apache.org/viewcvs.cgi/xml-cocoon2/src/documentation/xdocs/drafts/newtoc.txt?only_with_tag=MAIN
Greets
Gerhard
--
Gerhard Fröhlich
IBM Account Austria - 00/627
BIS e-business integration services
IBM Austria / Vienna
From: Morrison, John [EMAIL PROTECTED]
From: Gerhard Froehlich [mailto:[EMAIL PROTECTED]]
I think that we already have this. It is the duty of the
committer to undertake initial quality control when they
accept the patch from Bugzilla and prepare for their
commit. If they do not know
Hi,
From: Gerhard Froehlich [mailto:[EMAIL PROTECTED]]
I think that we already have this. It is the duty of the
committer to undertake initial quality control when they
accept the patch from Bugzilla and prepare for their
commit. If they do not know anything about the topic, then
they
From: David Helms [mailto:[EMAIL PROTECTED]]
Are you still seeing messages and crashes like I show below? I am a
developer at BMC Software, and we are seeing crash messages
like this while the WebHelp applet we are using is loading the
contents pane
for a sample help page. We are using
On Wednesday 15 May 2002 12:00, Gerhard Froehlich wrote:
Hi,
I think that we already have this. It is the duty of the
committer to undertake initial quality control when they
accept the patch from Bugzilla and prepare for their
commit. If they do not know anything about the topic, then
From: Torsten Curdt [mailto:[EMAIL PROTECTED]]
On Wednesday 15 May 2002 12:00, Gerhard Froehlich wrote:
Hi,
I think that we already have this. It is the duty of the
committer to undertake initial quality control when they
accept the patch from Bugzilla and prepare for their
From: Tom Klaasen [mailto:[EMAIL PROTECTED]]
I'm using this one for about 9 months, and that says enough,
doesn't it?
You also have a lot of plugins, which beautify java code,
auto-complete
of variables, etc etc.
The most important (imho) is the fact that you can do everything
I personally would like something like a component refererence (similar to
the one that exists today, extended/rewised).
This would include the Cocoon Internals that carlos suggests below. I´m a
litte fed up with looking at the code just to remember the
attributes/elements/namespaces for a given
From: Per-Olof Norén [EMAIL PROTECTED]
I personally would like something like a component refererence (similar to
the one that exists today, extended/rewised).
This would include the Cocoon Internals that carlos suggests below. I´m
a
litte fed up with looking at the code just to remember the
I second Bertrand.
Iterative documentation works for other Apache projects as well.
As long as there are inline notes asking for improvement, the doc will
eventually improve.
- Original Message -
From: Bertrand Delacretaz [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, May 15,
Perhaps a volunteer could compile the result of this thread, turn it
into a Cocoon Document Dream List, and submit it as a new planning doc
patch. We have a *great* start with Gerhard's original document. When
volunteer asks to contribute/enhance existing docs, they can consult
with this
The BEST thing about jEdit is that you can lunch VIM/GVIM
from it when you need the raw power that only VIM can provide.
Artur...
-Original Message-
From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 15, 2002 8:54 AM
To: [EMAIL PROTECTED]
Subject: RE: nice
Hi,
From: Torsten Curdt [mailto:[EMAIL PROTECTED]]
On Wednesday 15 May 2002 12:00, Gerhard Froehlich wrote:
Hi,
I think that we already have this. It is the duty of the
committer to undertake initial quality control when they
accept the patch from Bugzilla and prepare for their
Wow, thanks for letting us know about this. It's a really nice
editor. The number of plug-ins available and the ease of installing
them is excellent.
BTW, if you're using Linux it's worth getting Java 1.4 so that the
mouse wheel works and the fonts look better.
Sim
Jeremy Quinn wrote:
Dear
Use Java 1.4 on windoze as well, it doubles the speed.
One currently missing plugin is access to CVS, but
give it time.
Artur...
-Original Message-
From: Simeon Walker [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 15, 2002 10:50 AM
To: [EMAIL PROTECTED]
Subject: Re: nice editor
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7507.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi,
So what to do, what to do... ?
As I understand the problem is to understand the total
effects of a patch.
Thus you path the code, try some sample, and if
it works you say it is fixed.
The side effects of a patch, or an enhancement you may
or may not understand depending on the total
Diana Shannon wrote:
On Wednesday, May 15, 2002, at 05:20 AM, Stephan Michels wrote:
The best way to do this, is to implement the CVS support in cocoon.
But you still need some form of webapp front-end to address all CMS
concerns. CVS versioning is insufficient, IMO.
I were glad to
Thus after applying a patch, or implementing an enhancement
you run the JUnit tests, and you might see - depending
on the completness of the tests that still everything is fine,
or the patch has some unwanted side effects.
Thus building up a JUnit test base might help to keep
a
Date: Wed, 15 May 2002 18:31:46 +0100
To: [EMAIL PROTECTED]
From: Heidi Brannan [EMAIL PROTECTED]
Is this the best way to go about building and testing a cocoon webapp
(see below)?
I want to
a) write a how to on how to build and test a webapp
b) write an XMLForms How-To and
Hi :)
It looks like you've quite a lot of experience writting unit tests,
would you mind giving us a hand starting them off?
Thanks,
J.
From: Ross Gardler [mailto:[EMAIL PROTECTED]]
Subject: Getting test cases written
I promise you that the speed of our bug fixes has improved since
John Morrison wrote:
It looks like you've quite a lot of experience writting unit tests,
would you mind giving us a hand starting them off?
Our main interest is in the Portal stuff (what's the progress on
bringing that into the main branch) and the forms processing. The main
thing for me
The portal stuff has made it into HEAD. I don't know when HEAD
will next be stable and I don't see the portal stuff being moved
into the current branch at the moment. But any unit tests would
be appreciated.
J.
From: Ross Gardler [mailto:[EMAIL PROTECTED]]
John Morrison wrote:
It
I am using the portal in the development of my current project. I use it
to provide a complete administrative system for the Belgium Society of
Anesthesia and Resucitation. They will be able to manage all the data
online and also edit the content of the public and member site.
The portal is
On Wed, 15 May 2002, Sylvain Wallez wrote:
Diana Shannon wrote:
On Wednesday, May 15, 2002, at 05:20 AM, Stephan Michels wrote:
The best way to do this, is to implement the CVS support in cocoon.
But you still need some form of webapp front-end to address all CMS
concerns.
Marcelo (and anyone else listening) -
I'm a co-worker of Steve's who you responded to below. I had been looking
at your ESI submission (though from the past threads we saw it looked like
it had been put on hold for inclusion in cocoon and I don't find it in the
latest snapshot) and we're not
Bert Van Kets wrote:
I am using the portal in the development of my current project.
snip
They
have done a stress load up to 80 concurrent users with great success.
Bert
That is very encouraging, we need 50 concurrent users now, and 100 in 6
months. So it looks very promising indeed.
Hello.
We are developing a site and we're having an issue with the HTML
serializer, it seems to be adding a newline after before every br/ tag,
but not if it's preceded by an img/ tag.
Now, most of the time this is not an issue, but we have a table cell with
nobrOption 1/nobrbr/
nobrOption
On Wednesday 15 May 2002 16:27, Gerhard Froehlich wrote:
snip/
Agree ... but they must get re-viewed and applied somehow.
If not, Cocoon will stand still and the community breaks.
aggreed...
snip/
Maybe we try too hard to keep HEAD stable?
That's the point. But nobody stated this, or?
This sounds like a good idea.
I also have good overall experience with a rigorous unit testing process.
Maybe the section on Contributions should add:
Submit a unit test along with the patch to cover the error or new
functionality.
This way unit tests can be added gradually over time, as Ross
Is someone actively working on integrating XSLTC in Cocoon?
Stefano felt strongly that XSLTC should be ultimately the default stylesheet
processor in Cocoon.
Can someone comment on how far are we from this goal?
People keep discussing benchmarks for various XSLT interpreters, trying to
make
I would certainly appreciate some help with unit tests for the XMLForm
framework.
That is, if it satisfies your needs as a form handling solution.
If there is no hard oposition, it may move to the main tree with the 2.1
release.
There are a few test cases implemented, but they only scratch the
45 matches
Mail list logo
