Skip to main content
fabianmoronzirfas
Known Participant
April 28, 2011
Question

Why using .JSX?

  • April 28, 2011
  • 3 replies
  • 3519 views

Hi,

i have a basic question. Is it of any importance to use the .jsx extension instead of the .js?

Best

:F

This topic has been closed for replies.

3 replies

fabianmoronzirfas
Known Participant
April 28, 2011

So it is only the file association with the ESTK?

The advantage for me in .js is

- OSX Quicklook works with .js

- Git seems to have (sometimes) problems with .jsx

I thought maybee there is some tiny hidden but super important feature when using. jsx

Thanx a lot

:F

Harbs.
Legend
April 28, 2011

JSX files created by BBEdit or TextWrangler also work with Quicklook...

Harbs

fabianmoronzirfas
Known Participant
April 28, 2011

Really?

The JSX files I produce with TextMate and with the ESTK don't work with Quicklook (OSX 10.6.7).

Could for some reason the encoding be a problem?

I tried to change the encoding, but the terminal says always: charset=us-ascii

Or is there some other way to make the system treat the .jsx files like .js files?

I already know how to associate the extension with a program (e.g. TextMate) that works.

But the QuickLook problem is anoying me.

:F

Harbs.
Legend
April 28, 2011

js will work.

The main advantage to using jsx is in regard to file associations. jsx is associated with the ESTK, so if you open a jsx file it will open in ESTK. js files very often have other associations (such as Dreamweaver)...

Harbs

emerasoft_srl
Participating Frequently
April 28, 2011

Hello,

I think you could use ".js" extension instead of ".jsx" but I cannot find any advantage on this (BTW, I tried importing some scripts on the InDesign scripts panel with the ".js" extension and they work without any problem).

".jsx" stays for ExtendScript which is - as you know - a "special" version of Javascript, the same way as ActionScript (.as) is again a "special" version of Javascript too.

Best,

Luca