[SVN] r4269 (JavaScript Prototype & Script_aculo_us)

[thomas Aylott]

On Jul 16, 2006, at 4:35 PM, Allan Odgaard wrote:
> On 16/7/2006, at 20:14, Thomas Aylott wrote:
>
>> A   trunk/Bundles/JavaScript Prototype & Script_aculo_us.tmbundle/ 
>> Preferences/JS Indent.tmPreferences
>
> I believe these should be in the JavaScript bundle. So should any  
> pure JS snippets as well.

Done.

>> A   trunk/Bundles/JavaScript Prototype & Script_aculo_us.tmbundle/ 
>> Syntaxes/JavaScript + Prototype Bracketed.tmLanguage
>
> This bracketed thing, that’s to markup brackets with meta scopes  
> for your special nested coloring? I think to keep confusion down  
> (two syntaxes for the same thing) either this or the standard  
> should be removed.

There's a lot more to it than that.
It's really meant to be for Javascript what the XHTML strict syntax  
is for xhtml.
The idea is that it should better understand the larger parts of the  
language.
I just upgraded it to scope the {…} of functions separately from  
javascript object {…}.
The first useful upshot of all that is the fancy coloring  
possibilities that it allows.
But you could use the scopes to make function block specific snippets  
or what-have-you.

The reason i don't just use it for prototype or javascript itself is  
that it drastically reduced parsing performance on large and complex  
scripts (like the prototype library).
Other than that, it doesn't hurt anything.

Maybe I should move it into Experimental?

>> A   trunk/Bundles/JavaScript Prototype & Script_aculo_us.tmbundle/ 
>> Syntaxes/JavaScript + Prototype.tmLanguage
>> A   trunk/Bundles/JavaScript Prototype & Script_aculo_us.tmbundle/ 
>> Syntaxes/Prototype & Scriptaculous.tmLanguage
>
> We probably want to be consistent and either use + or &. Probably  
> though just name them “Prototype” and “Prototype &  
> Scriptaculous” as the latter also includes JavaScript!?!

Changed to use "&". Sharing a single repo should help keep  
inconsistencies from cropping up in the future.
Thought i'd fixed that before i posted it. Guess i didn't. Sorry.

I wasn't going to use JavaScript in the name, but... I wanted to use  
the ⌘⌥⇧J keystroke for all the javascript dialects (Prototype,  
MochiKit, Script.aculo.us, Moo.FX, jWhatever, etc...). Without  
JavaScript in the name it wouldn't make as much sense to have that  
keystroke. I guess that's pretty stupid reasoning though.

> Please also never add new languages which has a file types array  
> containing extensions already taken by default languages.

Fixed.

thomas Aylott—subtleGradient




thomas Aylott
subtleGradient


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macromates.com/textmate-dev/attachments/20060717/f0718967/attachment.html>