im not privvy to the inner workings of sugar development, and im no expert on either mootools or jquery. but i was wondering if making a sugar for jquery or mootools (prototype, script.aculo.us, Y.U.I etc.) would be worthwhile? i know they all use javascript, but each have their own syntax so to speak. Are any of the sugar developers looking at developing anything for these libraries?

I’m not sure if there is anyone out there currently working on one for jQuery, but when I get done with the sugars I’m working on I wouldn’t mind giving it a crack. Seeing as it’s just JS, it would mainly be snippets and code completion I’d imagine.

Yeah, a collection of text snippets injected into the Javascript Sugar’s namespace would do the trick.

I would love to see a better general JavaScript sugar implemented (with codesense for all methods). And the HTML sugar should have support for JS inside the document. But a better JavaScript sugar would be awesome. I might do one myself if I have the time, but I’ll have to get more into Sugar developement then

I have your jQuery sugar right here!

But a better Javascript sugar would be nice. But I guess MacRabbit will take care of that since its a core sugar? I guess if someone else came out with a better on they’d most likely adopt that.

Yep, JavaScript is so great in TextMate. I don’t want to switch between MooTools and JavaScript so a general sugar would be awesome.

It should be easy to recognize the syntax of the frameworks. Just look at the start:

i hadn’t looked at this thread for awhile, wicked a jQuery sugar :D awesome set of people developing sugars for espresso ... sugars are espresso’s saving grace

Has anyone thought about doing some sort of tool or script to create sugars from various JS frameworks or perhaps even building that in to the existing JS sugar?  Just curious, as I’m starting to look at making a sugar for another framework and wondered if anyone had tried to automate the process.

ping/bump… anyone?

Although I know specific Sugars whose authors have written scripts for automating the creation of CodeSense and so forth (PHP is a good example), I don’t think anyone has tried to create a general-use script for harvesting method names from disparate projects.

You might try contacting Derek (who coded the jQuery Sugar) to see if he has any tips or tricks for extending Javascript with a given framework.  Otherwise, you’ll probably need to start from scratch.