Hi Rich, Yes i am using Spket. It is good tool for OpenLaszlo developers to write a code. It can write a code with drag & drop with using their contained library and it has a futures of code suggestion and also you can edit some code template library. But unfortunately, it is just a code editor. It has not any future like visual coding.
Regards, Keiji Ono Rich Christiansen wrote: > Since we're on the subject of IDE's, can anyone comment on their > experience with this? > > http://www.spket.com/laszlo.html > -Rich > > Benjamin Shine wrote: > >> >> Generating the DTD is a fundamentally difficult problem because the >> laszlo platform lets the developer extend the DTD. One solution, for >> now, is a file that Henry created, lfc.lzx: >> >> http://svn.openlaszlo.org/openlaszlo/trunk/WEB-INF/lps/schema/lfc.lzx >> >> Eventually, we'd like to move to generating this information from the >> code itself. The js2doc tool goes part of the way to do this. I >> imagine you have a source build going, to be doing the work you're >> doing -- try building doc >> (cd docs/src; ant users) then looking at >> docs/src/build/reference/LaszloLibrary-verbose.js2doc. It will blow >> your mind! >> >> IMHO, an IDE should get information about the API and the >> documentation from this file. The documentation tools that generate >> the reference almost exclusively via XPath queries on >> LaszloLibrary-verbose.js2doc. >> >> -ben >> >> On Nov 21, 2007, at 3:18 AM, bjdevlin wrote: >> >>> >>> Hi Wayne, >>> >>> I guess you are addressing this to me rather than Rich :-) >>> >>> Fundamentally, the IDE is being driven by the Laszlo DTD. Hence my >>> request >>> that users of this list add their votes to the bug request to get >>> the DTD >>> updated. Unfortunately, there are still only three votes for that bug >>> request :-( >>> >>> I also plan to have the component palettes/inspectors driven by the >>> DTD. I >>> haven't yet tackled this area. But I think that if each developer >>> provided >>> a DTD for their component along with their component code, then DTDs >>> could >>> be added to a list. I haven't looked into how difficult it is to >>> write a >>> DTD, so I don't know how practical this idea is. Furthermore, >>> depending on >>> what elements could be contained within a 3rd party component, it >>> may be >>> possible to generate the DTD or even the pallette based on the >>> component >>> declartion itself (i.e. if the component could NOT contain anything >>> else >>> than already existed within the declaration itself, I think the DTD >>> could be >>> generated from the component itself). Anyway, as I say, I haven't >>> tackled >>> this area of the IDE yet. Maybe someone from Laszlo with more knowledge >>> about this could chime in? >>> >>> Bernard >>> >>> >>> >>> Epiphany wrote: >>> >>>> >>>> Do you think that your IDE would support the >>>> inclusion of prebuilt components? I am thinking of a recursive sort of >>>> situation here where I could use your IDE to build some components >>>> that >>>> then could later be included in your IDE. If there were a generic >>>> facility for such a thing, the IDE could then grow quickly with >>>> very rich >>>> / >>>> precanned components being added as each group/developer uses it and >>>> contributes items to the IDE itself. >>>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/new-visual-IDE-tf4821075.html#a13875231 >>> Sent from the OpenLaszlo - User mailing list archive at Nabble.com. >>>
