hivemind-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hivemind-...@jakarta.apache.org
Subject [Jakarta HiveMind Wiki] Updated: NotXMLProposal
Date Wed, 28 Apr 2004 22:50:55 GMT
   Date: 2004-04-28T15:50:55
   Editor: HowardLewisShip <hlship@apache.org>
   Wiki: Jakarta HiveMind Wiki
   Page: NotXMLProposal
   URL: http://wiki.apache.org/jakarta-hivemind/NotXMLProposal

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -186,3 +186,5 @@
 [http://wiki.apache.org/jakarta-tapestry/GeoffLongman GeoffLongman]: Speaking as a Hivemind
user, XML and SDL look fine. I have not warmed up to [http://www.yaml.org YAML] at all. Using
a true scripting language like Groovy turns me off completely. Leave the descriptors as ''descriptors''
that describe or declare something and are not executable. Speaking as somebody who ''might
someday'' commit to building an Eclipse plugin for Hivemind, XML is the path of least resistance
for me. A declarative markup like SDL or [http://www.yaml.org YAML] would be ok too if the
parser support were at a level conducive to developers tools. An DOM equivalent (AST tree)
with line ''and'' character offset ''and'' range precise information is needed. FYI, no open
source XML parsers were this precise out of the box for [http://spindle.sourceforge.net Spindle].

 
 ChristianEssl: XML is for me. If I look at the tremendous work Howard has put into the XMLParser
I'd say a JavaCC grammar would be even easier for !HiveMind - less validation. XML is for
me because I somehow got to know what an element and an attribute is, how to start and end
the document, how to escape things, how to add comments, the meaning of whitespace, what are
valid names, knowing which block-close belongs to which start without a lot of counting and
finally knowing that others know that (and certainly much more) too. Apart of this looking
at the example Harish gave I think he actually meant an language whith only expression-instructions.
Well that's not everyones taste, but I'd call it declarative and line pricese reporting can
be maintained this way. It has the advantage that it's relatively easy to use combined with
!JavaDoc. Further it would be very easy to implement convinience methods.   
+
+HowardLewisShip: ["JavaCC"] generates a token stream and each token knows it start and end
line number and column. I think it will be much easier to support this than with XML. I suspect
we'll be able to easily get that information out of the parser and into the plugin. Like Tapestry,
a plugin shouldn't be all that necessary ... the SDL stuff takes the teeth out of XML, making
it look quite pleasant.

---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-cvs-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-cvs-help@jakarta.apache.org


Mime
View raw message