Sponsored Content
Full Discussion: JavaScript code - UNIX grep?
Top Forums Web Development JavaScript code - UNIX grep? Post 303041013 by simpsa27 on Tuesday 12th of November 2019 09:15:36 AM
Old 11-12-2019
Yes all works good & I understand! Thanks for your help guys!
This User Gave Thanks to simpsa27 For This Post:
 

8 More Discussions You Might Find Interesting

1. Cybersecurity

Function of Javascript within Unix Network

What attacks can a Unix box get through Javascript? Is the Web Client secure against Javascript attacks if any? Do we have a Trojan horse made in JavaScript? (3 Replies)
Discussion started by: netass
3 Replies

2. 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

3. UNIX for Dummies Questions & Answers

| help | unix | grep - Can I use grep to return a string with exactly n matches?

Hello, I looking to use grep to return a string with exactly n matches. I'm building off this: ls -aLl /bin | grep '^.\{9\}x' | tr -s ' ' -rwxr-xr-x 1 root root 632816 Nov 25 2008 vi -rwxr-xr-x 1 root root 632816 Nov 25 2008 view -rwxr-xr-x 1 root root 16008 May 25 2008... (7 Replies)
Discussion started by: MykC
7 Replies

4. UNIX for Dummies Questions & Answers

| help | unix | grep (GNU grep) 2.5.1 | advanced regex syntax

Hello, I'm working on unix with grep (GNU grep) 2.5.1. I'm going through some of the newer regex syntax using Regular Expression Reference - Advanced Syntax a guide. ls -aLl /bin | grep "\(x\)" Which works, just highlights 'x' where ever, when ever. I'm trying to to get (?:) to work but... (4 Replies)
Discussion started by: MykC
4 Replies

5. Homework & Coursework Questions

Report on Javascript attacks on Unix

1. The problem statement, all variables and given/known data: Prepare a report discussing from an administration and security perspective, role and function of a JavaScript within a UNIX network. You should illustrate your answer with practical examples. In particular attention should me paid to... (1 Reply)
Discussion started by: afdesignz
1 Replies

6. Shell Programming and Scripting

How to use javascript code in unix shell?

Hi Need help...I have wrritten one code for html through shell scripting in that i am using java scripts to validate some condition and open the html page without clicking the button.... Code Details echo "<script type="text/javascript">" echo "function exec_refresh()" echo "{" ... (4 Replies)
Discussion started by: l_gshankar24
4 Replies

7. Shell Programming and Scripting

How to use JavaScript in UNIX Shell scripting?

I want to navigate through a webpage and save that page in my system local automatically. How can I do that by using JavaScript in a Unix shell script. Any suggestions are welcome! (3 Replies)
Discussion started by: abhi3093
3 Replies

8. Web Development

Path to javascript source code at local browsing

Where should I put my javascript source code in order to run it "locally" by file not by http?---not sure this "locally" is the appropriate word here. My test is when my javascript code (test.js) is put in the site default folder as the test.html in /var/www/html both worked as expected with... (2 Replies)
Discussion started by: yifangt
2 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 09:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy