Feature #104

Finish the plug-in architecture in Weave

Added by Andy Dufilie almost 6 years ago. Updated about 3 years ago.

Status:OpenStart date:06/30/2011
Priority:NormalDue date:
Assignee:Andy Dufilie% Done:

67%

Category:Internal Code Refactoring
Target version:-
Complexity:High OIC Priority:No
Required by:

Description

The plug-in architecture will allow loading new tools at runtime without re-compiling the existing code. It also allows faster start-up times if it is known ahead of time that only a few .swc files are needed.

There is now code (currently disabled) that loads a list of plug-ins at startup.
The code that reads the FlashVars and loads a session state file at startup needs to be separated from VisApplication and put into WeaveAPI or WeaveCore. All the Weave libraries except WeaveAPI and WeaveCore should be loaded as plug-ins. When loading an old session state, it would have to load a default set of plug-ins for backwards compatibility.


Subtasks

Feature #105: Allow admin to specify which .swf plug-in files to load on startupResolvedAndy Dufilie

Feature #106: Allow .swf plug-ins to be downloaded on-demand at runtime to load new toolsResolvedAndy Dufilie


Related issues

Related to Weave - Feature #67: Add an option to export session history to a file Resolved 06/29/2011
Related to Weave - Other #107: when a plug-in is loaded, new tools should be registered so the system knows they are available Resolved 06/30/2011
Related to Weave - Feature #1424: Create a plugin for a client-side SQLite data source (using Adobe AIR) Open 04/12/2014

History

#1 Updated by Andy Dufilie almost 6 years ago

  • Description updated (diff)

#2 Updated by Andy Dufilie almost 6 years ago

  • Description updated (diff)

#3 Updated by Andy Dufilie almost 6 years ago

  • Assignee deleted (Andy Dufilie)

#4 Updated by admin account almost 6 years ago

  • Description updated (diff)
  • Assignee set to Pat Stickney

#5 Updated by admin account almost 6 years ago

Use ClassUtils.loadSWF() to load each plug-in.

#6 Updated by Andy Dufilie almost 6 years ago

  • Complexity set to Medium

#7 Updated by admin account almost 6 years ago

  • Complexity changed from Medium to 2-Medium

#8 Updated by admin account almost 6 years ago

  • Complexity changed from 2-Medium to ** Medium **

#9 Updated by admin account almost 6 years ago

  • Complexity changed from ** Medium ** to Medium

#10 Updated by Pat Stickney over 5 years ago

  • Assignee changed from Pat Stickney to Andy Dufilie

#11 Updated by Andy Dufilie over 5 years ago

  • Status changed from Open to In Progress

#12 Updated by Andy Dufilie over 5 years ago

  • Complexity changed from Medium to High

#13 Updated by Andy Dufilie about 4 years ago

  • Subject changed from Create a plug-in architecture in Weave to Finish the plug-in architecture in Weave
  • Description updated (diff)
  • Status changed from In Progress to Open
  • OIC Priority set to No

#14 Updated by Mike Smyser over 3 years ago

Would be great to have this fully operational and have documentation which gives an example as to how load and make the plug-in work. For example, perhaps something could be chosen from something like the D3 gallery on GitHub (https://github.com/mbostock/d3/wiki/Gallery). One example, we'd be interested in would be how to add the treemaps in the gallery (http://bl.ocks.org/mbostock/4063582) and the zoomable treemap (http://mbostock.github.io/d3/talk/20111018/treemap.html)

#15 Updated by Andy Dufilie about 3 years ago

The plugin architecture is an ActionScript feature and has nothing to do with JavaScript. If you want to link up JavaScript tools with Weave, you can already do that using the JavaScript API.

Also available in: Atom PDF