|
|||||
|
|||||
Home
You've reached the documentation site for the Marmalade Project. CaveatMarmalade is extremely experimental as of now. We believe the core functionality to be reasonably stable, with decent unit test coverage. However, since this is still alpha software, the core api could and probably will change with successive releases, so exercise reasonable caution before including Marmalade in your production software plans. You might want to join the -user mailing list, too. QuickLinks
News2005-Mar-08I've been working hard on marmalade lately, getting it ready to replace jelly in maven2...in fact, I've been working too hard to update this content. Sorry.
2004-09-09
IntroductionMarmalade is a second-generation, extensible XML scripting tool. In function, it is similar to Jelly, but is much smaller and more flexible. It is also similar to JSP in some (admittedly superficial) ways. The basic idea behind Marmalade is a realization that scripting, and especially XML-based scripting, is really a combination of two simple languages. The first language is made up entirely of struture delimiters, and essentially determines how the language constructs are related to one another. The second language is really just a data access mechanism, used to retrieve data. Separating these concepts allows Marmalade to mix-and-match many different mechanisms for each, using a parser to translate native format to the Marmalade object model, and an evaluator to translate object-graph expressions into data access calls into the context of the script. In fact, given the right parser, Marmalade doesn't even have to be an XML-only scripting language... Also, keeping the data access language flexible and context defintion reasonably simple allows for easy creation of X-to-Marmalade bridges. For example, Marmalade currently contains a Jelly compatibility layer which can be used to run any Jelly taglib from within a Marmalade script. You can even mix-and-match Jelly tags with Marmalade native tags in many cases. Most importantly, Marmalade strives to minimize the trail of dependencies you as the developer are forced to include in your project. To that end, the Marmalade Project is best described as an umbrella project consisting of many sub-component suites, all centered on the marmalade-core library. This allows developers to take a buffet approach to Marmalade's functionality: you can use Jelly-compat, but that means including all of the libraries needed by Jelly. Marmalade's core requires only a single library other than itself in order to function (compared to 13 dependencies for Jelly). What you add from there is entirely up to you. Mailing ListsSee Mailing lists for more information. Bugs, Features, What-NotsMarmalade has an issue tracking project on the Codehaus JIRA instance, so please log any feature requests, improvements, bug reports, etc. there. The address is: Status2005-Mar-08The core functionality, marmalade-core, is basically stable now. I'm only adding the random tiny new feature now and again, without changing old APIs, in order to solidify the feature set and move toward a 1.0-alpha2 release. At this point, we're basically just waiting on documentation before the release! If you'd like to test drive marmalade, please checkout from CVS or contact the marmalade-dev list, and I'll put a distro up. 2004-07-27Forgot to document one of the nicer features of Marmalade:
2004-07-20Marmalade currently contains the following features:
Up-and-coming features:
Currently idle (for lack of demand):
|
|||||
|
Copyright 2003-2006 - The Codehaus. All rights reserved unless otherwise noted.
Powered by Atlassian Confluence
|
|||||