Skip to main content

Home/ javascript/ Group items tagged extension

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Julian Knight

Chickenfoot - 0 views

groups.csail.mit.edu/...index.php

automation firefox greasemonkey javascript scripting

shared by Julian Knight on 29 Aug 08 - Cached
  • Julian Knight on 29 Aug 08
     
    Scripting extension to Firefox. Adds direct Javascript plus extensions & a macro recorder. Seems to lack a built in security option. Manipulates the DOM object once rendered in FF. Complements Greasemonkey See also: CoScripter and iMacros
Mike Chelen

Bespin » Code in the Cloud - 0 views

bespin.mozilla.com

mozilla html bespin editor programming javscript ide web

shared by Mike Chelen on 16 Feb 09 - Cached
  • Mike Chelen on 16 Feb 09
     
    Bespin is a Mozilla Labs experiment on how to build an extensible Web code editor using HTML 5 technology.
Hussain M Elius

Creating a "Filterable" Portfolio with jQuery - NETTUTS - 0 views

nettuts.com/...lterable-portfolio-with-jquery

portfolio jquery javascript images

shared by Hussain M Elius on 04 Feb 09 - Cached
  • Hussain M Elius on 04 Feb 09
     
    If you have worked in your field for a while, there is a pretty good chance that you have a rather extensive portfolio. To make it a little easier to navigate, you will probably be tempted to break them into different categories. In this tutorial, I will show you how to make "filtering by category" a little more interesting with just a little bit of jQuery
Julian Knight

Xinha - Trac - 0 views

xinha.webfactional.com

development html javascript programming scripting

shared by Julian Knight on 29 Aug 08 - Cached
  • Julian Knight on 29 Aug 08
     
    Xinha (pronounced like Xena, the Warrior Princess) is a powerful WYSIWYG HTML editor component that works in Mozilla based browsers as well as in MS Internet Explorer. Its configurabilty and extensibility make it easy to build just the right editor for multiple purposes, from a restricted mini-editor for one database field to a full-fledged website editor. Its liberal licence makes it an ideal candidate for integration into any kind of project.
Ivan Pavlov

FUEL - MozillaWiki - 0 views

wiki.mozilla.org/FUEL

javascript

shared by Ivan Pavlov on 29 Aug 07 - Cached
  • Ivan Pavlov on 29 Aug 07
     
    Firefox User Extension Library) is a JavaScript Library designed to help developers build extensions using terminology and interfaces that are familiar to them.
Zehra Nasif

Google+ History API in Chrome Extensions - 0 views

life.scarygami.net/historyextensions

shared by Zehra Nasif on 02 Oct 12 - No Cached
    • Zehra Nasif
      Zehra Nasif on 02 Oct 12
       
      Is the activity type is given by Google or we can create our own as many as possible? If it is user driven label--like gmail labels--, this can work out as G+ label I wanted to have.
Hussain M Elius

Prototype extension: Carousel - 0 views

dev.victorstanciu.ro/...en

prototype carousel coda slider

shared by Hussain M Elius on 16 Dec 08 - Cached
  • Hussain M Elius on 16 Dec 08
     
    Coda Slider like script for prototype
Ivan Pavlov

wForms - A Javascript Extension to Web Forms - 0 views

www.formassembly.com/wForms

javascript

shared by Ivan Pavlov on 10 Jul 08 - Cached
  • wForms is an open-source, unobtrusive javascript library that adds commonly needed behaviors to traditional web forms without the need for any programming skill.
Ivan Pavlov

JNEXT - JavaScript Native Extensions - 0 views

jnext.org

javascript

shared by Ivan Pavlov on 06 Oct 08 - Cached
  • JNEXT is an open source (triple MPL, GPL, LGPL license), small footprint, cross platform and cross browser framework for extending Web browser Javascript (for more background and motivation check this blog entry). With JNEXT it is possible to utilize existing Web browsers to host full and self contained applications that do not depend on external Web servers for the application logic (although they are free to make use of them). This is acheived by enabling Javascript controlled access to the full range of native operating system resources (such as TCP/UDP sockets, files, databases, threads etc).
Javier Neira

Why REST ? | /var/log/mind - 0 views

blog.dhananjaynene.com/...why-rest

data integration protocols ftp rpc http analysis

shared by Javier Neira on 09 Jun 09 - Cached
  • ‘ls’ or ‘List Directory’
  • ‘cd’or ‘Change Directory’
  • ‘put’ or ‘Upload’
  • ...26 more annotations...
  • you soon realise that every file and directory is uniquely addressable by its fully qualified path (either absolute or relative) and you can refer to each file and directory by its path. You are also aware that a valid path will uniquely resolve to only one directory or file.
  • the server allows you to retrieve the list of subdirectories and files within your current directory. It always shows you the current state of that directory.
  • following elements
  • A shared understanding of where the files will be uploaded, how they will be uniquely named, their specific file extensions (optionally) and the specific format of the file eg.
  • daemon process on the central office computer (the FTP server) which regularly scans the directory, parses each file as it comes it, does the relevant processing on it, and generates the appropriate result files and places them in the appropriate directories using the shared understanding of the directory structure and the file naming convention to communicate back the results of the processing.
  • RPC allowed you to invoke remote procedures by supporting an ability to pass messages which included the message name and the values for all the parameters necessary to be supplied to the message. Unlike FTP which was meant to do data transfer across a network, RPC was geared to do things remotely.
  • FTP required understanding of very few basic verbs (ls, cd, get, put). Thus the training required to understand FTP semantics was far less than that for RPC. This was partially due to the fact that RPC had a programmatic interface.
  • Moreover each time, new procedures were added or parameters added, these required programmatic changes
  • HTTP protoco
  • Unlike FTP and email, this required the authors to understand a new language, but used a simple markup syntax to keep the learning curve to the minimum
  • get/view/download/save a document
  • Along with RPC, these were essentially different technical manifestations of Service Oriented Architecture (SOA) principles.
  • Many services were usually expected to “do something” though quite often some services would simply return the requested data. Usually but not necessarily the services were identified by using ‘verbs’.
  • allow us to use the web to ‘do something’
  • Resource and media types as the basic units
  • Unique resource identifiers
  • Each resource has often one default manually readable representation
  • Each resource representation optionally includes contextually relevant hyperlinks to other resources
  • REST encourages a uniform interface
  • GET, PUT, POST and DELETE
  • Default Rendering
  • a default HTML rendering capability
  • Aspects such as non maintenance of conversational state, greatly increase the scalability of REST applications even if they do incur a minor cost in efficiency (which can be due to repeated redundant communication of data elements, or additional processing requirements due to preclusion of conversation state).
  • is much easier to understand from a data perspective than an invoice processor API.
  • However the simpler, cleaner and minimalistic abstractions often are far more important than feature richness. A point I would want to make in favour of REST even as I admit that conventional SOA technologies are far more feature rich than REST.
  • REST encourages you to view and model your architecture as a set of resources rather than services.
Javier Neira

JQuery HowTo: Create callback functions for your jQuery plugins & extensions - 1 views

jquery-howto.blogspot.com/...llback-functions-for-your.html

howto jquery callback function

shared by Javier Neira on 14 Nov 09 - Cached
  • $.extend({  myFunc : function(someArg, callbackFnk){    // do something here    var data = 'test';     // now call a callback function    if(typeof callbackFnk == 'function'){      callbackFnk.call(this, data);    }  }});$.myFunc(someArg, function(arg){  // now my function is not hardcoded  // in the plugin itself  // and arg = 'test'});
  • Javier Neira on 14 Nov 09
     
    $.extend({ myFunc : function(someArg, callbackFnk){ // do something here var data = 'test'; // now call a callback function if(typeof callbackFnk == 'function'){ callbackFnk.call(this, data); } } }); $.myFunc(someArg, function(arg){ // now my function is not hardcoded // in the plugin itself // and arg = 'test' });
mikhail-miguel

jQuery - 0 views

jquery.com

jquery javascript webdev

shared by mikhail-miguel on 05 Mar 18 - No Cached
  • mikhail-miguel on 05 Mar 18
     
    jQuery: The Write Less, Do More, JavaScript Library
1 - 15 of 15
Showing 20▼ items per page