Anyway, here’s an article on the subject: Understanding Progressive Enhancement. I think it summarises things pretty well. M&Ms explain everything don’t they?

The extension currently provides TinyMCE and FCKeditor and will let you choose which one you’d like to use, as well as which admin pages you’d like it displayed on. There are a number of features that we intend on adding in in the future but, for now, this should provide you with the essentials.

I wasn’t actually involved in the creation of this extension but it’s certainly something that we’re all quite excited to have released! WYSIWYG is something that I believe Magento should already include by default, so we finally have a simple solution to the problem. Enjoy!

First of all, Ext really is just freaking massive. Although jQuery isn’t exactly minuscule it’s still a hell of a lot smaller than Ext. Loading my Ext application, even on a local connection, takes quite a while and freezes the browser while all that code is processed. Admittedly this is more to do with my browser being slow as a dog than with any inherent flaw in Ext. Still, if you want to have a lightweight site Ext is pretty much immediately out of the running.

One thing that I initially loved about Ext, that I am now starting to loath, is that it tries to be too much like Java or some other desktop programming language/library. Basically you can (and probably should) build the entire interface through JavaScript calls rather than use HTML and CSS. The problem with this is that, at the end of the day, it’s not Java and Ext just ends up doing fancy DOM manipulations anyway (for the layouts anyway) so all it’s really doing is obfuscating what’s going on and making sure you are forced to rely on the Ext interfaces rather than DOM manipulation or CSS or the like. Now, 98% of the time this won’t be an issue for you but I’ve run into a few cases where it’s tripped me up because I can’t work out how to get around all the Ext-ness.

In comparison jQuery provides almost nothing but DOM manipulation helpers, which is really useful if you already know what to do but if you want to build a layout like Ext does then you’re going to be messing around with HTML and CSS quite a bit. That said, it really isn’t that difficult to get the basics up and running but emulating something like SplitPane would be painful … unless you find an appropriate plugin. So, for what it does, jQuery is stunningly good. It makes enhancing web sites trivial and removes a lot of the sharp edges from JavaScript without attempting to fundamentally change how you use it.

As an example of how the two differ, here’s some code to run logic when a user clicks on a link and to disable the normal execution of that link.

For Ext:

Ext.select('#links a').on('click', function(event) {
    alert("You clicked: " + Ext.get(event.target).dom.innerHTML);
  },
  this,
  {stopEvent: true}
);

For jQuery:

$('#links a').click(function(event) {
  alert("You clicked: " + $(this).html());
  return false;
});

As you can see, the jQuery code is a bit shorter and easier to understand. To disable the normal browser action of following the link, Ext has a special option on the event handler whereas in jQuery you simply return false from your click function. This might seem counter-intuitive if you don’t know JavaScript so if you don’t, compare the above to how you’d do this without the libraries:

<a href="/foo/bar/"
  onclick="alert('You clicked: ' + this.innerHTML); return false;">
Click here
</a>

You can see that returning false is what you normally do anyway so, instead of encapsulating this, jQuery basically just lets you use the normal way of doing things. Ext, on the other hand, makes things more programmatic and Java-esque by having an extra configuration option to the event handler.

I am still developing web applications with both of them so I can tell you that both libraries are suitable for RIA development, it’s mostly just a question of whether you prefer developing apps entirely in JavaScript or using JavaScript for logic and a little layout, as well as whether or not you need all the advanced features Ext comes with. I think that I would normally pick jQuery because I prefer the simplicity of it and like more control when writing an application. Hopefully this little post has given you an idea of what the two libraries are like and encourage you to try them both out. I’d like to hear the experiences of others working with these libraries, as well as others like Prototype and Mootools, which I am also interested in.

First, IE8 will drop the use of hasLayout, meaning there should be a bit more consistency in renderings between browsers and less need to resort to conditional comments with IE-specific CSS. (It doesn’t help with current versions however.)

Second, WebKit now includes an implementation of getElementsByClassName, joining Firefox 3 and the next Opera version for support for this highly desired function. Benchmarks are given which show the staggering speed increase on this common operation. You can get some for Firefox 3 as well.

The WebKit guys especially seem to be keen to start pushing the limitations of current browsers so I think 2008 will be an exciting year.

I haven’t had any cause to use this system yet but I’ll be sure to write a review when I do. Anyone else taken this for a spin?

First of all, getting Ext running is slightly more complicated than getting jQuery running. jQuery is a simple matter of including jquery.js in your HTML and then writing your script. Ext requires first it’s own CSS file, then an adapter which uses another library (jQuery, YUI or Prototype) but can also use the newish ext-base.js which doesn’t depend on external libraries, and finally you include ext.js itself. I went with the pure Ext solution but tried out the jQuery adapter and found it didn’t work for me – I’m sure I was doing something wrong but didn’t care enough to fix it and went back to Ext.

Secondly, Ext is rather huge. Not surprising considering what it can do but the whole thing (ext.js, ext-base.js and stylesheet) still comes in uncompressed at just over 512KB. Sorry, I should mention that that’s with Ext’s default minification – the debug versions are a bit over 1MB! In comparison, jQuery is roughly 70KB before any minification is applied. So what do you get for all this size? Quite a bit actually.

The customer info area of my application is designed with a list of customers on the left and an area for details on the right. With pure HTML and CSS a nice-looking layout here, similar to a desktop app, is really difficult to achieve. With Ext it’s almost trivial and you can use a logical declarative style of recursive JavaScript objects to define the layout – similar to how it would be done in Java Swing, for example. With Ext you can also easily get “bonus” features like resizable panes, content areas that adjust to the size of the viewport and a default style that looks pretty damned good (and you have to option of using different themes). Without any trouble I was able to get a simple list working which allows clicking on customer names to load their details asynchronously in the details panel, as well as allowing dynamic updates and the like.

The standard things that I use with jQuery – selectors and AJAX support – are also well supported in Ext, even if they are slightly more verbose. Ext also includes a nifty feature in it’s simplistic load() method that allows you to set a loading message, something that I believe you have ot do manually in jQuery.

Ext also supports a wide range of widgets and the like out of the box. Data grids are all the rage now and Ext makes it simple to get them up and running. Tree views, buttons, colour pickers, date selectors and a bunch of others are provided as well. If there’s something missing you might be able to find a plugin for it.

Overall, I’m really enjoying working with Ext. It makes some fundamental yet complex things ridiculously easy and provides enough of a framework to get almost anything working with a bit of lateral thinking and liberal application of nested layouts and the like.

So I guess the obvious question now is if I prefer Ext or jQuery? Honestly, the two are just aimed at completely different areas. If you’re making a web site that needs some fancy JavaScript effects, a bit of AJAX and you want it to be light and accessible, then I’d say jQuery is the way to go. If you want a RIA with lots of advanced functionality and don’t care about those plebs who don’t have JavaScript then I’d say Ext is definitely the preferred option. If I had to pick I’d say I like jQuery a bit more since I prefer writing enhanced web sites rather than desktop application wannabes but this is really just a personal choice. Both libraries offer the same basic functionality and jQuery can certainly be extended to do pretty much what Ext does so choosing either will probably let you do what you want.

First of all, the default “file” mode is useless in practice for anything except viewing what files are in a directory. Uploading, changing permissions, renaming, etc all require that the web server user have write permissions to those files and directories which is almost always not the case. The “FTP” mode should get around these limitations but I haven’t successfully managed to get it working yet.

Logging in to the system exposes a completely trivial but insanely annoying bug: hitting the enter key doesn’t activate the “OK” button! Really, I can’t believe somebody managed to write a login screen and not pick that up. Another usability problem is the error screens since they give you absolutely no clue as to what went wrong, only that something did. For instance, I tried out uploading a file (which is actually a fairly nice process, if a little cluttered) but it failed telling me that, well, that it failed. It took me a few moments to realise the problem with file permissions. I must assume that no extra information is sent back to eXplorer on a failure? Even so, I think the permissions problem would be easy for the software to work out seeing as it reports file and directory permissions to the user.

When you log in as admin for the first time eXplorer dutifully asks you to change the admin password. Which is fine except that attempting to change the password results in yet another unknown error. I’m guessing that there’s a file somewhere that needs write permissions but I’ll be damned if I know which one. I got around this by doing a recursive chmod and setting everything to writable then setting it back. Something, I would like to point out, that is not possible through an FTP connection, leaving you with hours of work ahead of you if you’re using this on a remote connection with SSH access.

OK, so enough with the negative stuff for now, what’s good about this software? Well, most obviously, it looks really nice. This is thanks to using the ExtJS library for the entire system, which is quite apparent (you know, aside from the name) as the default Ext style is used. The layout will be familiar to anyone who has ever used a file manager before, with a couple of caveats. Only files are displayed by default in the “view” area but this can be changed by clicking “Show Directories” which, despite its appearance, is a glorified checkbox (it’s a button with on/off states). Secondly, if you do activate show directories then double clicking on them doesn’t open them – they can only be opened in the viewer which, naturally, shows nothing. To open a directory you need to use the tree on the left. Finally, eXtplorer only ever shows 50 files in a single “page” of a directory. You need to use the pagination buttons at the bottom to see more.

Doing operations on files is rather easy as you can double click on them (or right click) to bring up a context menu. You can also use the buttons in the toolbar which do the same thing. I like the viewer quite a bit as it does syntax highlighting on several different types of files, such as PHP. Images can also be viewed, which is quite convenient. You can also use drag-n-drop functionality for moving or copying files, which actually appears to be the only way to achieve those operations. Perhaps one of the most useful things is the ability to do “batch” operations by selecting more than one file – chmod is particularly good as you can recurse into subdirectories, something which gFTP doesn’t yet support.

Another problem you can run into is that the insane amount of Javascript being used results in the system being quite slow in some cases but this is probably still better than doing the same thing via FTP.

Overall, I’d say that eXplorer is a decent system but it suffers from some sharp edges that need to be fixed up before I’d consider using it more. In particular, before I allowed a client to use it.

Update: I got FTP working and it is better than file mode. Also, to change the admin password or add users you need to make config/.htusers.php writable. Damn those hidden files.