koalaxml-developers Mailing List for koalaXML
Status: Inactive
Brought to you by:
rzuasti
Menu
▾
▴
koalaxml-developers — developers list
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(7) |
Sep
(25) |
Oct
|
Nov
|
Dec
|
|---|
|
From: Ricardo Z. <rz...@ko...> - 2002-09-26 12:10:53
|
people, we just released version 0.4.6! the main thing about it is comments support... so, go get the jar :P later :: ricardo zuasti :: rz...@ko... :: http://rzuasti.koaladev.com |
|
From: Ricardo Z. <rz...@ko...> - 2002-09-25 01:15:39
|
people, fabian will add support for comments in XMLs, ie <!-- this is a comment --> this will be really nice for GML as people will be able to document their gml files... we're also planning a 0.4.6 release for thursday (if fabian agrees) so if you come up with some other feature you think we should add speak up and lets do it bye :: ricardo zuasti :: rz...@ko... :: http://rzuasti.koaladev.com |
|
From: Ricardo Z. <rz...@ko...> - 2002-09-19 18:43:31
|
checkout my brand new personal homepage http://rzuasti.koaladev.com ... what u think? you have homepages? perhaps we can link them from the people page in the projects, u agree? later :: ricardo zuasti :: rz...@ko... |
|
From: Ricardo Z. <rz...@ko...> - 2002-09-14 19:30:33
|
people, a bug went thru in last xml version (0.4.4) so i had to make a new release! please get it because you *need* it to get koalaGML working... bye :: ricardo zuasti :: rz...@ko... |
|
From: Ricardo Z. <rz...@ko...> - 2002-09-14 18:11:54
|
to tell you that we changed the packaging scheme a little to comply with
chris suggestion... so the new sources and docs packages are something
like:
koaLaXML-source-0.4.4.tgz
|---koaLaXML-0.4.4
|
|README
|CHANGELOG
|---org
|---koala
...
hope u agree... it's nicer because u can have multiple versions in the
same dir by just unpacking them there...
later
:: ricardo zuasti
:: rz...@ko...
|
|
From: Ricardo Z. <rz...@ko...> - 2002-09-14 18:07:56
|
hi every1, we just released koaLaXML 0.4.4, the most important thing about it is that we added empty tags support (<tag/>) and fixed a *serious* bug that didn't allowed nested tags with the same name to be processed by the parser... anyway, go get it :P where from here? please suggest something ;) later ricardo :: ricardo zuasti :: rz...@ko... |
|
From: Ricardo Z. <rz...@ko...> - 2002-09-13 10:48:58
|
people, for some unknown reason we got like 750 hits yesterday!! congrats later :: ricardo zuasti :: rz...@ko... |
|
From: F. I. <fi...@ko...> - 2002-09-12 01:09:26
|
On Wed, 2002-09-11 at 21:58, Ricardo Zuasti wrote: > the second one is already assigned to nando (you asked for it ;), nando, > if you want the bug fix too let us know... gimme gimme shock treatment!! all tasks due staturday night, right? greetings,=20 --=20 this message was delivered from epsilon by Evolution at 2002-09-11 22:09:00 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Fernando Ipar - fi...@ko... koaLa Developers (http://www.koaladev.com) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D this machine is powered by Free Software (http://www.gnu.org) |
|
From: Ricardo Z. <rz...@ko...> - 2002-09-12 00:58:58
|
hi people! we just updated project tasks... so, for koaLaXML we created just two tasks, one is a bug fix, and the other is about adding empty tasks support... the second one is already assigned to nando (you asked for it ;), nando, if you want the bug fix too let us know... we plan to make a 0.4.4 release on saturday because we need the fix and the new features for GML. we created a new tasks subproject called release-0.4.4 for this tasks (the idea is to create one subproject for each release) later ricardo |
|
From: Ricardo Z. <rz...@ko...> - 2002-09-11 18:13:22
|
the point is perhaps that the <% and %> are pre-processed before you
parse the XML in such things as JSP or ASP or PHP.... but everyone of
them uses it, its like a de facto standard to embed code in a XML doc
also, if someday we want to allow the developer to put code "in the
middle" of a value something like
<%while (true){%>
hi koala :P
<%}%>
we need a separator....
just thinking out loud ;)
this is like kernighan vs. wall, just without the wisdom and genius :))
ltr
ricardo
On Wed, 2002-09-11 at 14:38, Christopher Lennert wrote:
--- Ricardo Zuasti <rz...@ko...> wrote:
> chris, i agree with you in some parts, i think we must improve our XML
> "quality"... but i'm not sure that scriptlets (<%...%>) should be inside
> a CDATA, the intuitive idea we had was to create a tool very similar to
> JSP, so web developers (or anyone) could easily develop a GUI
> application... and JSP doesn't use CDATA tags. I think this is because
> the scriptlets are kind of "pre-XML-processing" instructions, so if we
> look at it the same way, and we strip the scriptlets our XML is almost
> well formed... we need the <?xml.../> and empty tags support...
One question: is it necessary for the "<%" and the "%>" to be present? I
understand the desire to give developers some familiarity to JSP, but no
XML parser in the world, except koalaXML, is going to accept an unescaped
"<" in an attribute (this is an XML well-formedness constraint as defined
by the W3C, see http://www.w3.org/TR/2000/REC-xml-20001006#ValueType). If
the code in an onclick-type attribute is code of some sort, the "<%" and
"%>" shouldn't be needed.
OR: Perhaps we could use something else intuitive that won't require much
code rewrite, but is equally intuitive, like "{%" and "%}".
Sorry for being a hardass on this, :). It's just important that koalaXML
markup have the same common foundation as every other XML language.
> on the other hand, we created koalaXML to make XML processing easier and
> more simple than what SAX or DOM provide, while supporting a valid (but
> not complete) piece of the XML features (so our documents were valid)
> and our parser *really* easy and intuitive to use in the most common
> situations....
I can go along with that :).
Later,
chris
__________________________________________________
Yahoo! - We Remember
9-11: A tribute to the more than 3,000 lives lost
http://dir.remember.yahoo.com/tribute
-------------------------------------------------------
In remembrance
www.osdn.com/911/
_______________________________________________
Koalaxml-developers mailing list
Koa...@li...
https://lists.sourceforge.net/lists/listinfo/koalaxml-developers
|
|
From: Christopher L. <cal...@ya...> - 2002-09-11 17:38:03
|
--- Ricardo Zuasti <rz...@ko...> wrote: > chris, i agree with you in some parts, i think we must improve our XML > "quality"... but i'm not sure that scriptlets (<%...%>) should be inside > a CDATA, the intuitive idea we had was to create a tool very similar to > JSP, so web developers (or anyone) could easily develop a GUI > application... and JSP doesn't use CDATA tags. I think this is because > the scriptlets are kind of "pre-XML-processing" instructions, so if we > look at it the same way, and we strip the scriptlets our XML is almost > well formed... we need the <?xml.../> and empty tags support... One question: is it necessary for the "<%" and the "%>" to be present? I understand the desire to give developers some familiarity to JSP, but no XML parser in the world, except koalaXML, is going to accept an unescaped "<" in an attribute (this is an XML well-formedness constraint as defined by the W3C, see http://www.w3.org/TR/2000/REC-xml-20001006#ValueType). If the code in an onclick-type attribute is code of some sort, the "<%" and "%>" shouldn't be needed. OR: Perhaps we could use something else intuitive that won't require much code rewrite, but is equally intuitive, like "{%" and "%}". Sorry for being a hardass on this, :). It's just important that koalaXML markup have the same common foundation as every other XML language. > on the other hand, we created koalaXML to make XML processing easier and > more simple than what SAX or DOM provide, while supporting a valid (but > not complete) piece of the XML features (so our documents were valid) > and our parser *really* easy and intuitive to use in the most common > situations.... I can go along with that :). Later, chris __________________________________________________ Yahoo! - We Remember 9-11: A tribute to the more than 3,000 lives lost http://dir.remember.yahoo.com/tribute |
|
From: Ricardo Z. <rz...@ko...> - 2002-09-11 15:26:54
|
chris, i agree with you in some parts, i think we must improve our XML
"quality"... but i'm not sure that scriptlets (<%...%>) should be inside
a CDATA, the intuitive idea we had was to create a tool very similar to
JSP, so web developers (or anyone) could easily develop a GUI
application... and JSP doesn't use CDATA tags. I think this is because
the scriptlets are kind of "pre-XML-processing" instructions, so if we
look at it the same way, and we strip the scriptlets our XML is almost
well formed... we need the <?xml.../> and empty tags support...
on the other hand, we created koalaXML to make XML processing easier and
more simple than what SAX or DOM provide, while supporting a valid (but
not complete) piece of the XML features (so our documents were valid)
and our parser *really* easy and intuitive to use in the most common
situations....
what do the rest of you think? in my opinion we need a middle point
where we continue to use koalaXML but we evolve to a more standards
compliant document (+ scriptlets ;)
later
ricardo
On Wed, 2002-09-11 at 08:36, Christopher Lennert wrote:
Ric,
1. Since the caption for buttons, labels, etc. is generally a short
string of text and not a long-running block of text, it should be included
as a attribute of the tag, rather than enclosed by the tag, as follows:
<label name="label1" width="60" height="20" caption="before"/>
2. One the flip side, since onload, onclick, etc. bits of code have the
*potential* to be long-running they should be separate tags nested within
their parent , NOT attributes.
3. OK, here's my biggie: One *major* (in my opinion) thing that needs to
be addressed is:
GML files must be well-formed XML at all times: we will be criticized if
our product depends upon mark-up that *looks* like XML but isn't
really...If we don't address this, we will be discouraging folks from ever
seriously considering koalaGML.
What this means is that koalaXML must support CDATA sections. CDATA
sections are used in XML documents to denote text that is not to be parsed
by the parser. (There's a CDATA section in build.xml that encloses the
HTML License statement that's inserted into the Javadocs.) koalaXML must
do this so that the JSP bits <%...%> can be nested within CDATA sections,
thus allowing well-formed XML.
(Personally, I favor the use of a third-party XML parser/validator since
the good folks at Sun and Apache have been working on XML
parser/validators *much* longer than we have. We could a SAX processing
model where, as we parse the GML file, SAX events are fired: "Parser
says: 'hey! i just encountered a button tag! What do you want to do with
it?' koalaGML says: 'Oh good! I'll generate code for a button.'"
However, I won't push that just yet ;)
OK, this email is becoming a dissertation :D so I'll finish with an
example of how koalaGML mark-up should look like, to be well-formed,
respectable XML. Rewriting buttonLabelExample.gml with these changes will
produce a document that looks like:
<?xml version="1.0" encoding="UTF-8" ?>
<form language="Java" width="205" height="105">
<head>
<title>
koaLaGML button/label example
</title>
</head>
<body>
<space height="10"/>
<label name="label1" width="60" height="20" caption="before"/>
<space height="10"/>
<button name="button1" caption="click me!">
<onclick>
<![CDATA[
<%
form.getLabel("label1").setValue("after");
form.getButton("button1").setValue("ouch!");
%>
]]>
</onclick>
</button>
<space height="10"/>
</body>
</form>
;) ok, so i threw that "<?xml version="1.0" encoding="UTF-8" ?>" bit in
there also.
adios, guys.
chris
__________________________________________________
Yahoo! - We Remember
9-11: A tribute to the more than 3,000 lives lost
http://dir.remember.yahoo.com/tribute
-------------------------------------------------------
In remembrance
www.osdn.com/911/
_______________________________________________
Koalaxml-developers mailing list
Koa...@li...
https://lists.sourceforge.net/lists/listinfo/koalaxml-developers
|
|
From: Christopher L. <cal...@ya...> - 2002-09-11 11:36:34
|
Ric,
1. Since the caption for buttons, labels, etc. is generally a short
string of text and not a long-running block of text, it should be included
as a attribute of the tag, rather than enclosed by the tag, as follows:
<label name="label1" width="60" height="20" caption="before"/>
2. One the flip side, since onload, onclick, etc. bits of code have the
*potential* to be long-running they should be separate tags nested within
their parent , NOT attributes.
3. OK, here's my biggie: One *major* (in my opinion) thing that needs to
be addressed is:
GML files must be well-formed XML at all times: we will be criticized if
our product depends upon mark-up that *looks* like XML but isn't
really...If we don't address this, we will be discouraging folks from ever
seriously considering koalaGML.
What this means is that koalaXML must support CDATA sections. CDATA
sections are used in XML documents to denote text that is not to be parsed
by the parser. (There's a CDATA section in build.xml that encloses the
HTML License statement that's inserted into the Javadocs.) koalaXML must
do this so that the JSP bits <%...%> can be nested within CDATA sections,
thus allowing well-formed XML.
(Personally, I favor the use of a third-party XML parser/validator since
the good folks at Sun and Apache have been working on XML
parser/validators *much* longer than we have. We could a SAX processing
model where, as we parse the GML file, SAX events are fired: "Parser
says: 'hey! i just encountered a button tag! What do you want to do with
it?' koalaGML says: 'Oh good! I'll generate code for a button.'"
However, I won't push that just yet ;)
OK, this email is becoming a dissertation :D so I'll finish with an
example of how koalaGML mark-up should look like, to be well-formed,
respectable XML. Rewriting buttonLabelExample.gml with these changes will
produce a document that looks like:
<?xml version="1.0" encoding="UTF-8" ?>
<form language="Java" width="205" height="105">
<head>
<title>
koaLaGML button/label example
</title>
</head>
<body>
<space height="10"/>
<label name="label1" width="60" height="20" caption="before"/>
<space height="10"/>
<button name="button1" caption="click me!">
<onclick>
<![CDATA[
<%
form.getLabel("label1").setValue("after");
form.getButton("button1").setValue("ouch!");
%>
]]>
</onclick>
</button>
<space height="10"/>
</body>
</form>
;) ok, so i threw that "<?xml version="1.0" encoding="UTF-8" ?>" bit in
there also.
adios, guys.
chris
__________________________________________________
Yahoo! - We Remember
9-11: A tribute to the more than 3,000 lives lost
http://dir.remember.yahoo.com/tribute
|
|
From: F. I. <fi...@ko...> - 2002-09-11 03:03:56
|
On Tue, 2002-09-10 at 23:40, Ricardo Zuasti wrote: > - add empty tag support i'd like to give it a shot, i'm still unfamiliar with xml internals so if there isn't much of a hurry for this, assign it to me.=20 later,=20 --=20 this message was delivered from epsilon by Evolution at 2002-09-11 00:03:00 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Fernando Ipar - fi...@ko... koaLa Developers (http://www.koaladev.com) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D this machine is powered by Free Software (http://www.gnu.org) |
|
From: Fabian P. <fp...@ko...> - 2002-09-11 02:54:05
|
i agree with you! let's do it greetings Fabian -----Original Message----- From: koa...@li... [mailto:koa...@li...] On Behalf Of Ricardo Zuasti Sent: Tuesday, September 10, 2002 11:40 PM To: koalaxml-developers Subject: [Koalaxml-developers] design & future people, i think in the XML project while it's pretty much stable we need to add some functionality... in particular i think we must add support for empty tags (without value) ie: <bean name="beanName" attribute1="value1" ... /> (without the </bean>) we could *really* use this in the GML project to simplify some tags that dont need a value... other thing that's pending is the development of a simple user guide, perhaps with some examples and common methods documentation on the testing side we need to review the junit classes and standarize (is that right spelled? ;) their structure... so, the tasks would be: - add empty tag support - write user guide - review and complete junit classes tell me what you think and if you agree i'll create and assign them to any mercifull soul that wants to do them later ricardo |
|
From: Ricardo Z. <rz...@ko...> - 2002-09-11 02:41:03
|
people, i think in the XML project while it's pretty much stable we need to add some functionality... in particular i think we must add support for empty tags (without value) ie: <bean name="beanName" attribute1="value1" ... /> (without the </bean>) we could *really* use this in the GML project to simplify some tags that dont need a value... other thing that's pending is the development of a simple user guide, perhaps with some examples and common methods documentation on the testing side we need to review the junit classes and standarize (is that right spelled? ;) their structure... so, the tasks would be: - add empty tag support - write user guide - review and complete junit classes tell me what you think and if you agree i'll create and assign them to any mercifull soul that wants to do them later ricardo |
|
From: Ricardo Z. <rz...@ko...> - 2002-09-10 11:53:54
|
hi every1, we have a new member! Lin will be doing some junit testing with lauren... perhaps you can take one package each, say one does the org.koala.koalagml and the other the org.koala.koalagml.runtime... or separate one project each, i don't know, do it how you feel better, this is for fun! (well, some glory would be nice though ;) if any of you need help please use the list, we'll try to answer as soon as possible bye ricardo ps: i'll be taking the job position for tester out of sourceforge, i think for now two enthusiastic (hope that's spelled right) memebers are more than enough... if you think we need more help in this or any other area let me or fabian know and we'll post an ad |
|
From: Ricardo Z. <rz...@ko...> - 2002-09-09 19:36:08
|
people, i released v0.4.3 of koalaXML, all minor bug fixes, but they were stacking ;) later ricardo |
|
From: Ricardo Z. <rz...@ko...> - 2002-09-09 01:53:02
|
ready! chris, you're an xml dude now too ;)
i agree with you on focusing in GML, it's the one that will make us all
famous :P
hasta la vista people,
me
On Sun, 2002-09-08 at 22:22, Christopher Lennert wrote:
Ricardo,
no biggie...i could simply be mistaken! :)
membership in koalaxml: aw, heck, why not? sign me up. I could probably
do doc. writing for that as well, although if it's alright with you, i may
focus my attention on koalagml initially.
adios,
Chris
--- Ricardo Zuasti <rz...@ko...> wrote:
> chris, i couldn't find the diference between the XML-developers list and
> the GML one, perhaps you cant see the archives because i created the xml
> list as private and then made it public, while the GML was created
> public from the beginning....
>
> if you like i can make u a memeber of the xml project so you can...
>
> bye
> ricardo
>
>
>
__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Koalaxml-developers mailing list
Koa...@li...
https://lists.sourceforge.net/lists/listinfo/koalaxml-developers
|
|
From: Christopher L. <cal...@ya...> - 2002-09-09 01:22:16
|
Ricardo, no biggie...i could simply be mistaken! :) membership in koalaxml: aw, heck, why not? sign me up. I could probably do doc. writing for that as well, although if it's alright with you, i may focus my attention on koalagml initially. adios, Chris --- Ricardo Zuasti <rz...@ko...> wrote: > chris, i couldn't find the diference between the XML-developers list and > the GML one, perhaps you cant see the archives because i created the xml > list as private and then made it public, while the GML was created > public from the beginning.... > > if you like i can make u a memeber of the xml project so you can... > > bye > ricardo > > > __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com |
|
From: Ricardo Z. <rz...@ko...> - 2002-09-08 20:21:51
|
chris, i couldn't find the diference between the XML-developers list and the GML one, perhaps you cant see the archives because i created the xml list as private and then made it public, while the GML was created public from the beginning.... if you like i can make u a memeber of the xml project so you can... bye ricardo |
|
From: Ricardo Z. <rz...@ko...> - 2002-09-08 00:18:55
|
i fixed a bug in XML.getAttributeScriptlet and in the XML parser that raised an exception when a scriptlet had spaces or tabs around (ie: att=' <%...%> '), it just needed a couple of trims... a check was missing in the StringUtil.fillLeft and fillRight methods, now they raise an exception if the filler has more than 1 char... (it returned crap before) bye me |
|
From: Ricardo Z. <rz...@ko...> - 2002-09-05 11:47:38
|
ok, just lo let everyone know, our brand new developer/tester, lauren, is part of XML and GML mailing lists... bye |
|
From: Ricardo Z. <rz...@ko...> - 2002-09-03 03:54:49
|
gente, hicimos hoy el release de la nueva version... acuerdense de bajarla y usar el nuevo jar para el GML... lo nuevo que tiene son getAttributeXXX que reciben ademas del nombre del atributo un valor por defecto, que es devuelto en caso de que el atributo no exista... muy util para cosas opcionales del gml ;) bye |
|
From: Nicolas O. <no...@ad...> - 2002-09-01 04:22:13
|
Para titi, voy a tener que comprar adsl para tanto update y download. On Sat, 2002-08-31 at 20:02, Ricardo Zuasti wrote: > che, ya agregue los getAttributeXXX con valor por defecto, si les parece > ma=F1ana saco una version (0.4.2) con esto asi lo empezamos a usar en el > GML... >=20 > bye >=20 >=20 |