Thanks David. Yes, actually the esp script produces generic JSON. When I get that in my Ajax call, I then build a Dojo tree-specific object which attaches the JSOn structure as a property, so it should be usable for anything that wants general JSON, I hope.
I think I'll let you guys decide where to put Bunkai, if you want it in somewhere. I don't know to much about specifics of Sling yet. However, the resource type is fairly important, and I think that I will choose to read and 'standard' files with Sling, geared towards a web / JavaScript editing setting. I'll check the Apache license, which sounds nice. One issue is of course the EditArea source code editor, which is released under LGPL, and I don't really know if that has any impact if any on the license I choose to release Bunkai under. Cheers, PS On Feb 12, 2008 4:44 PM, David Nuescheler <[EMAIL PROTECTED]> wrote: > Hi Peter, > > Thanks a lot for the update, that sounds great. Congratulations. > > > heres a snippet which I used in conjunction with the 15 minutes Sling > > example; > > <... source code ... /> > that looks about what i expected for a dojo-tree specific integration > effort, > that you were referring to very early on... is that about right? > > > > Also, I'm not sure where this script should reside, and where bunkai > itself > > should be put.. > Generally we (at Day) tend to put applications into the /apps folder. > So you would find your script somewhere in the /apps/bunkai folder. > > I think there are a still couple of open questions around where to put > what > when it comes to something very general, like the mentioned alternative > .json rendition. > > > I also need to find a good license to put bunkai under. > > The source code editor is not mine, for instance. > I think from an Apache standpoint we certainly would have a recommendation > about the preferred licensing terms in the part of the galaxy ;) > [ hint: http://www.apache.org/licenses/LICENSE-2.0.html ] > > regards, > david >
