We have just released a browser extension (Firefox only for the time being) which is aimed at making common authoring and development tasks a little bit easier.
Drag and Drop File Uploads;
[*]Seamless Saving;
[*]Inline syntax highlighting for RAW bodycopies (e.g Designs, CSS and JavaScript files);
[*]Enhancements to the user interface when using certain asset types (e.g. Asset Listings);
[*]Keyboard shortcut reference and
[*]WYSIWYG replacement (experimental).
It's 100% open source, is licensed under GPL v3 and does not require you to install anything on the server. The source code is available on github.
We would love to hear as much constructive feedback as possible so that we can continue to improve it. You can fork, send through pull requests, log bugs and feature suggestions all through github and of course directly in this thread.
I debated about this one quite a bit as well, especially since (as you say) Matrix already has a built-in lock refresh interval (the magic little pop-up). The problem that this plugin tries to address is when you're working in an environment that has that timer configured incorrectly or overly aggressively (has happened to me very frequently). When this happens, if the user hits the save button they will actually lose all of their content changes. If you're like me, there's nothing worse then losing all your JS code in one big hit :\
As an alternative, perhaps it should just display when your locks have expired and the refresh interval timer never kicked in? Or maybe it should just renew the locks automatically if it detects a user has tried to save changes on an asset they aren't holding locks for anymore?
[quote]
Your work definitely looks great.
Just let you know Matrix team will build this enhancement in the core:
I’ve gotta say I’m a bit bothered by the scary countdown as well – plus I’ve noticed that it gets the lock duration wrong fairly often.
I also noticed that I was unable to see the div properties dialog when the WYSIWYG has been replaced. Was that a deliberate decision or an oversight?
Of course, since you can turn features on and off as you wish, I don’t have to miss out on the other good stuff A nice start!
[/quote]
Hi Raena,
Thanks for the feedback. We’re currently reviewing the lock count down and will probably tone down the UI treatment on it for the next release.
The div properties for the WYSIWYG replacement was definitely not an oversight. It’s currently an issue and is being worked on. This is why the WYSIWYG replacement plugin is in “experimental” mode and is not enabled by default.
Thanks for the feedback. We’re currently reviewing the lock count down and will probably tone down the UI treatment on it for the next release.
The div properties for the WYSIWYG replacement was definitely not an oversight. It’s currently an issue and is being worked on. This is why the WYSIWYG replacement plugin is in “experimental” mode and is not enabled by default.
Its so weird that a colleague and i were discussing these very issues not 2 days prior to the release! Line-Numbers, Syntax Highlighting, TABBING IN PARSE FILES!!!
A nice start!