EDIT: Aaand I forgot that this was in the same topic as the bug that I linked to in this post and commented on two hours earlier... There a way to merge posts?
EDIT (clarification): I'm posting this to see what people think... How many people want newer, more up-to-date JS v.s. how many people are just fine with the current system and don't see the need for refactored code. TBH I didn't anticipate getting enough replies to start a new topic...
Remember back when I started that JS revamp? Well, now I have something to show for it. (And again, I don't expect it to be used, or mind if it's not... It's just something I'm throwing out here -- an option, an alternative.)
The revamp includes a relatively-developer-friendly modal system. Here's a modal for posting YouTube videos. As a bonus, it'll extract the video ID from a URL. A user need only copypasta the URL.
And the result:
(Not shown is an in-modal notification if the URL is malformed.)
Tired of having to click through massive, inelegant, tedious, and clunky chains of one-line prompt boxes just to type in a trigger or a list? Having a hard time memorizing the BBCode for it? Well, the modal system is versatile enough to eliminate the first problem and render the second immaterial.
And, of course, the result.
In the modal, the Conditions and Actions sections are both lists of one-line textboxes, with buttons ("Add Condition"/"Add Action") that add more rows. So someone can add as many of each as they like. Should they add too many condition or action rows, they need only leave the excess rows blank -- they will be ignored.
If you're wondering, "Why should we use this? All you did was add modals!"... The cosmetic changes, of course, are miniscule. However, nearly everything under the hood is different. The code is structured to be more efficient, more developer-friendly, and the way it's structured will prevent problems like
this from ever occurring. (Screenshot #1 shows this in action -- since everything is compartmentalized, there is zero risk of variable overlaps. Unlike the current version, where pretty much the only way to prevent variable conflicts with 100% certainty is to have some kind of list of every variable and function ever used in the code at any period of time ever, or to code your stuff anyway and remove any arising conflicts through trial and error.)
I do, of course, plan on adding many more cosmetic enhancements, making the more clunky JS-based parts of the site better-looking and more usable. I've also been testing this using Greasemonkey userscripts and Stylish userstyles, so when it's polished enough, I could even release a kind of optional public beta.
So... yeah. Just throwing that out there, in case anyone's interested.
Post has been edited 3 time(s), last time on Mar 14 2010, 2:42 am by DavidJCobb.
None.