Sponsored Content
The Lounge What is on Your Mind? A Choice: Draggable Editors or Smilie Box on Quick Editor Post 303027003 by Neo on Thursday 6th of December 2018 11:17:34 PM
Old 12-07-2018
Hmm... I don't see any real benefit for having sections of the web site draggable using jQuery-UI except, perhaps, for the ability to drag the Quick Reply Editor (QRE) when composing a reply. Not sure if this "minor goodness" has much value compared to the added overhead of adding the relatively sizable jQuery-UI Javascript library. Of course, this is more code to maintain and another JS library to maintain.

I doubt anyone here will use "draggable" in any useful way. Will let this experiment run for a bit longer but I may turn it off sooner than later.

Better, I think, to add some VueJS - Bootstrap apps or components to the site.

Of some minor interest to note is that the jQuery-UI libs currently override the site's Bootstrap tooltips. These tooltips look good in some places and not so good in others, and also I'm having some trouble controlling the tooltip format (for example, getting rid of the shadow box) in the Advanced Stats. So, I'm not a huge fan of these jQuery-UI tooltips. This is another reason to remove the jQuery-UI libs from the site, sooner than later.

At this point in time, jQuery-UI seems more value-subtracted than value-added compared to other JS libs and frameworks.
 

6 More Discussions You Might Find Interesting

1. Programming

editors?

Just started out with C and are looking for a good editor in *nix that marks the code with colors. This is maybe a newbie thing to have the C code in colors but i like it and you can almost always se when you are typing wrong. :) Ive heard that emacs should have that option but i havent... (3 Replies)
Discussion started by: hexdoctor
3 Replies

2. UNIX for Dummies Questions & Answers

Editors for UNIX

Where can i find editors for UNIX? thanks (5 Replies)
Discussion started by: Inbal
5 Replies

3. UNIX for Dummies Questions & Answers

Mail utilities and editors.

I was wondering what other mail utilities besides 'mutt, unix mail, PINE and elm' are available for unix. Also, what other editors are around besides 'VI, pico, vim and emacs'... I've been searching the net looking for some answers, but nothing much has come up.. thanx! (1 Reply)
Discussion started by: Shonnie
1 Replies

4. UNIX and Linux Applications

opinions on video editors

What is everyones opinions on these video editors? PiTiVi Avidemux Cinelerra Kdenlive Kino Linux Video Editing: Top Five Linux Video Editors (0 Replies)
Discussion started by: cokedude
0 Replies

5. What is on Your Mind?

Small bug in the Quick Editor function in postbit

Hey, There was a small bug in the Quick Editor function in postbit, but I fixed it (basically a double quote was missing from an element id): <div id="post_message_$post" class="neo-message-area">$post</div> Was <div id="post_message_$post class="neo-message-area">$post</div> Should... (1 Reply)
Discussion started by: Neo
1 Replies

6. Web Development

New Font Awesome Icons in Quick Reply Editor

Working on the Quick Reply Editor, I have replaced a number of icons (see image below) with Font Awesome Icons. Was planning to replace all of them, but for some reason, replacing a few of them causes the script / template to break (which is odd) so I left them for now. ... (6 Replies)
Discussion started by: Neo
6 Replies
Jifty::Manual::jQueryMigrationGuide(3pm)		User Contributed Perl Documentation		  Jifty::Manual::jQueryMigrationGuide(3pm)

NAME
jQueryMigrationGuide - How to migrate your code to use jQuery. Migrate your jifty app to jquery Application developers may start the migration by modifying config.yml, setting the "ConfigFileVersion" to 4. If you did not write any custom javascript code for your app, then you're done. Everything should just work. If you did write some javascript code, but you did not use any of the functions defined in jifty*.js, prototype.js or scriptaculous.js, then you're still good to go. Otherwise, your code might need to be modified a little bit. Since both prototype.js and scriptaculous.js are removed by default, one trivial choice is to simply bring them back. That is as easy as adding the Prototypism plugin to your Jifty application. If you dislike Prototypism like we do, you can choose to re-write your code with jQuery. In the section "From Prototype to jQuery" below, we provide some common patterns that can be applied to rewrite Prototypism code with jQuery, or with just normal javascript. If you hack on Jifty's internals, please make sure you've read the following "Jifty API" section and Jifty::Manual::JavaScript to catch the Javascript API updates since the removal of "prototype.js". Although we've removed "prototype.js", we still prefer to use the non-conflict mode of jQuery. That is, "$" function is now undefined instead of an alias to jQuery. This is to ensure that it's not conflicting with Prototypism anywhere. If you'd like to use "$" function, create that alias in your "app.js" like this: $ = jQuery; However, instead of making a global alias, it's always recommended to localize this alias within a closure: (function($) { // $ is an alias to jQuery only inside this closure $(".message").show(); })(jQuery); Jifty API We re-architected Jifty's javascript libraries to use jQuery. Especially the internal functions to process form elements. The old, Prototype-based way is to extend Form object and the Form.Element object. Since the removal of the Prototype library, it is dangerous to name those functions under Form because loading the Prototype library can destroy those Jifty functions. The new jQuery-based way is to always extend internal functions under the Jifty object. "Form" becomes "Jifty.Form", "Form.Element" becomes "Jifty.Form.Element", and so on. The detailed list of these functions are given in Jifty::Manual::Javascript. Most of those functions are internal functions that you probably should not use directly. From Prototype to jQuery If you've ever written javascript code for your Jifty applications, and you'd like to remove the PrototypeJS library, here are some mechanical rules to re-write prototype.js-based javascript code with jQuery. Array iteration From: A.each( function( $_ ) { ... } ) To: jQuery.each(A, function(index, value ) { // "this" is an alias to current value. }) Hash key iteration From: H = new Hash({...}); H.each(function( pair ) { // pair.key is the key // pair.value is the value }); jQuery.each is designed to work on both "Array" and "Object" in the same way. So there's not much difference. To: // H can be any kind of "Object" jQuery.each(H, function(key, value) { // "this" is an alias to current value. }) Object extend From: obj.extend({ ... }} To: jQuery.extend( obj, { ... } ) JSON jQuery does not ship with the JSON stringify function, but since it neither altered the native Array, nor defined its own Hash, it's acceptable and preferred to just use "JSON.stringify" from "json.js". From: // obj need to be one of those objects defined in C<prototype.js> obj.toJSON(); To: JSON.stringify( obj ) Effects jQuery has a small set of default effects built into its core. They have different names then those defined in "scriptaculous.js". The internal way to specify effects is using the "Jifty.Effect" method. Please see the detailed usage documentation in Jifty::Manual::JavaScript. perl v5.14.2 2010-12-08 Jifty::Manual::jQueryMigrationGuide(3pm)
All times are GMT -4. The time now is 08:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy