custom controls in SceneBuilder

[Tom Schindl]

Like I said we are using this informations already when you open the 
FXML file in the preview where we push a specialized URLClassloader to 
the FXMLLoader.

If you define that FXMLs are always opened through e(fx)clipse then one 
could work with command line args and/or PIs (similar to the CSS stuff).

I'm not a fan of the PI stuff but I guess it is used exactly because of 
the fact that SB has no way to store extra informations like:
* classpath
* css
* translation

IMHO the correct way to integrate SB would be to create embedd design 
view programmatically into an EditorPart (don't know how it is called in 
Netbeans/IntelliJ) and this API needs to provide a way to pass on the 
classpath.

Anyways: SB is not opensource and unless the SB-devs provide 
informations I'm kind of lost.

Tom

On 02.05.13 17:13, Werner Lehmann wrote:
> Well, I hoped for e(fx)clipse having that project notion. It could
> prepare a classpath consisting of whatever output directories and
> libaries are specified in the project containing the fxml file, and in
> its dependency projects.
>
> Without this it will be quite tedious to construct and provide the
> classpath manually. Of course, developers would then also have to
> dismiss the SceneBuilder error about unknown controls first. I don't see
> anybody wanting to work like that...
>
> Werner
>
> On 02.05.2013 17:06, Tom Schindl wrote:
>> I've not looked into SB since a long time but I doubt there's an API for
>> this. The main problem is that SB has no notion of a "project" as far as
>> I know so I guess it is hard to configure it