[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[orion-dev] Visual plugins
- From: John J Barton <johnjbarton@xxxxxxxxxxxxxxx>
- Date: Sun, 29 Jan 2012 21:17:59 -0800
- Delivered-to: email@example.com
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=OAqP1xOJCduEPHyEp3MFgV87nmwMvneeHOaqoUcsZVs=; b=LrdEw6LuaCKlDbhpisoiiV4zDc1r6fDuUSHt1w8F2RfwKRCcqW12J3Ot9IVMKMoeDc Ei+KLZdKsJa69qnDcIqr8dodCcuVBkDAw4MlgCUc55wD66k3uRKizRFPht4+Tma1YmSn 135NldWv7S6eVsPgWhoxt96vU331EzLGJepPE=
I am trying to figure out how to write visually integrated Orion
plugins. I want the footer, global command header, banner, and
(optional) page actions, but the I want the ContentPane to be an
iframe given as a plugin.
My motivation is to be able to create tool UIs without modifying the
orion code base and without using dojo (sorry, not a fan).
I worked on this a bit and it seems very feasible. I created
"orion.pluginPlayer" to host visual plugins. But it has one major
problem: the pluginPlayer would have to be in the Orion code base. So
if the Orion team never wants to allow this I can stop now.
For now, the pluginPlayer URL can be mapped into the Orion space by
extending a self-hosting config to add the player project. So maybe
there is away to do this in general? That is, a different kind of
'plugin' that is uploaded and mapped into the server space.
Or maybe there is yet another way?