Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Orion/Planning Meeting/High Value Integration Points"

Line 19: Line 19:
 
* SCM for look and feel related changed files
 
* SCM for look and feel related changed files
  
== JQuery plugin ==
+
== Library-aware plugins (JQuery, Dojo, etc.) ==
 
* JSDoc-based code completion
 
* JSDoc-based code completion
 
* go to the source of a plugin
 
* go to the source of a plugin
Line 32: Line 32:
  
 
== Testing ==
 
== Testing ==
* Jasmine/QUnit/JSUnit/JSTestDriver - unit testing stuff
+
* Jasmine/QUnit/DOH/JSUnit/JSTestDriver - unit testing stuff
 
* Selenium - UI testing
 
* Selenium - UI testing
 +
* Being able to get to the source quickly from a test result

Revision as of 14:41, 18 March 2011

High Value Integration Points for Orion

Mockups (Balsamiq, Mockingbird)

  • Compare running site/prototype to mockup/wireframe
  • Store wireframe file in Orion
  • simplify import/export scenarios

GitHub

  • Make and share Gists
  • Links in Orion to GitHub Pages
  • button in github to edit in Orion

Boilerplates/Project Generation

  • initializr.com
  • startupphonegap.org

Drupal/Joomla/Wordpress

  • embed Orion editor for theme edits (CSS, HTML, etc.)
  • SCM for look and feel related changed files

Library-aware plugins (JQuery, Dojo, etc.)

  • JSDoc-based code completion
  • go to the source of a plugin
  • which js file? which CSS file?
  • metadata for plugins @ openajax

node.js

  • and Perl, Python, PHP, Ruby, Java syntax highlighting

PHP/mod_orion

  • easy to install

Testing

  • Jasmine/QUnit/DOH/JSUnit/JSTestDriver - unit testing stuff
  • Selenium - UI testing
  • Being able to get to the source quickly from a test result

Back to the top