Path to javascript source code at local browsing


 
Thread Tools Search this Thread
Top Forums Web Development Path to javascript source code at local browsing
Prev   Next
# 3  
Old 06-27-2017
Thanks!
Ahh, back slash "/" - that is the root!


Last edited by yifangt; 06-27-2017 at 06:13 PM..
 
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Migrate /export/home from storage path to local

I am newbies in solaris, hope u guys can help me, I need to transfer /export/home directory that currently mount at storage and migrate into local disk. may i know the best way to do it? Thanks (6 Replies)
Discussion started by: Deeo
6 Replies

2. Shell Programming and Scripting

Generate class path dynamically based on source path

Hi experts, I have multiple file names ending with .jsp located in $SOME_DIR, $SOME_DIR/f1/,$SOME_DIR/f2/test,$SOME_DIR/f3/fa and there are equivalent class files in $SOME_DIR/WEB-INF/classes/_pages,$SOME_DIR/WEB-INF/classes/_pages/_f1,... (0 Replies)
Discussion started by: oraclermanpt
0 Replies

3. Shell Programming and Scripting

I am trying to merge all csv files from source path into 1 file

I am trying to merge all csv files from source path into one single csv file in target. but getting error message: hadoop fs -cat /user/hive/warehouse/stage.db/PK_CLOUD_CHARGE/TCH-charge_*.csv > /user/hive/warehouse/stage.db/PK_CLOUD_CHARGE/final/TCH_pb_charge.csv getting error message:... (0 Replies)
Discussion started by: cplusplus1
0 Replies

4. Shell Programming and Scripting

Set variable to path that does not exist on local host

Can anyone suggest a workaround zone_5.org='/qaz/qwe/path/tns.osn' output /home/bingo/XXX_script.sh: line 180: zone_5.org=/qaz/qwe/path/tns.osn: no parent The path does not exist on the local machine, the allocation used to work till the server was upgraded. Red Hat Enterprise Linux... (2 Replies)
Discussion started by: squrcles
2 Replies

5. UNIX for Dummies Questions & Answers

Source path

what is the command for moving a file with it's original source path ? (8 Replies)
Discussion started by: Oggie25
8 Replies

6. UNIX for Advanced & Expert Users

SCP wihout a source path

Hi, I hope someone can explain if this is the right behaviour. I regularly use scp to copy files between hosts like this: scp -prv user@remotehost:/path/to/copy . However, today, I made a mistake and typed this instead: scp -prv user@remotehost: /path/to/copy . This started copying... (6 Replies)
Discussion started by: zlowryder
6 Replies

7. Linux

rpmbuild, how to specify a different source and destination path for files

I'd like to specify a different build and deployment path for files, by default the same path is used for both build and install, I wasn't able to find a way to make these different. With Solaris pkgadd, one can specify different paths in prototype, so I would assume something like that is possible... (0 Replies)
Discussion started by: tiburblium
0 Replies

8. Shell Programming and Scripting

Save page source, including javascript

I need to get the source code of a webpage. I have tried to use wget and curl, but it doesn't show the necessary javascript part of the source. I don't have to execute it, only to view the source. How do I do that? (1 Reply)
Discussion started by: locoroco
1 Replies

9. Shell Programming and Scripting

clear complex javascript code

Hi, Please advise how can we clear the following javascript content from a file commandline, probably using awk or sed File before removing the content. ################################ root@server1 # cat index.html This is a test page <script language=JavaScript>function d(x){var... (6 Replies)
Discussion started by: fed.linuxgossip
6 Replies
Login or Register to Ask a Question
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)