Date: 2004-05-04T01:08:34 Editor: KnutWannheden <[EMAIL PROTECTED]> Wiki: Jakarta HiveMind Wiki Page: NotXMLProposal URL: http://wiki.apache.org/jakarta-hivemind/NotXMLProposal
no comment Change Log: ------------------------------------------------------------------------------ @@ -300,3 +300,5 @@ BshBuilder receives the module descriptor sets up the BeanShell interpreter by mixing in the BshBuilderHelper object and executes the evalModule script. The evalModule script reads the module descriptor one statement at a time, sets the line number of the executing node in the helper, and executes it. The helper does the needful. And that's pretty much all for handling the descriptors. Of late, I have really subscribed into KISS and [http://martinfowler.com/bliki/EnablingAttitude.html Enabling Attitude] principles and these ideas are simply a repercussion of that. + +KnutWannheden: Harish, your example is IMO getting very close to a purely descriptive form (like the SDL or XML approach). Of course someone could (ab)use the BSH design to write an absurdly cryptic module descriptor. This is where I gather you say the Enabling Attitude principle comes in to play. IMO the only thing with the XML descriptor which doesn't conform to this principle is the XML syntax itself, and that's what SDL should solve. But then again with the plethora of XML processing / spewing tools I think XML also has some nice advantages. Also I think one of the main purposes of using a descriptive syntax is to make the descriptor itself readable. And, as previously noted, if users put arbitrary Java code into the descriptor I think it could prove difficult for HiveDoc to produce something useful. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
