Page 1 of 1

Plugin Strategy

Posted: Mon 11. Oct 2010, 08:06
by Kennedy Tony
Hi

I'm producing a proof of concept for the introduction of jReality into the eclipse modelling project AMP to support our legacy Agent Based Models many of which use jReality as the principle display method, this involves embedding jReality as a series of Eclipse plugins and a general conversion to SWT controls. I've completed the conversion of most components to plugins based on the general decomposition of your code as described by the file structure, test harness and and a demo RCP have been produced and it is now proposed that I produce an RCP that imitates your swing front end, this is now under way however I'm not certain of your final goal with the plugin decomposition is this documented anywhere or could your give me a hint as to the intended final decomposition.

thanks

Re: Plugin Strategy

Posted: Mon 11. Oct 2010, 09:26
by Andre
Hi Kennedy Tony,

we're using the jtem-project jrWorkspace for our Plugin-System.

e.g. the jReality scene Panel (de.jreality.plugin.scene) is a bunch of shrink-panel (Avatar, Terrain, Sky etc.) where each has his own task.

We are using the GridBagLayout.

Re: Plugin Strategy

Posted: Mon 11. Oct 2010, 09:45
by Kennedy Tony
Hi

Yes but I was wondering about the target plugin decomposition so far it is basic, content, help and scene do you plan any further decomposition/refactoring of the present components or is this its final state?

Re: Plugin Strategy

Posted: Mon 11. Oct 2010, 10:06
by Andre
Actually we are working on other parts so I guess this is the final decomposition for the next few years.

Re: Plugin Strategy

Posted: Mon 11. Oct 2010, 11:03
by Kennedy Tony
OK

I will follow this decomposition

Re: Plugin Strategy

Posted: Fri 2. Aug 2013, 10:30
by Andre
What kind of problems do you have?

Maybe the plugintutorials can help you:

http://www3.math.tu-berlin.de/jreality/ ... _interface