[SceneBuilderKit]

Eric Le Ponner eric.le.ponner at oracle.com
Thu Jul 10 15:11:38 UTC 2014


Also missed the reply all…

Eric

Le 9 juil. 2014 à 14:51, Eric Le Ponner <eric.le.ponner at oracle.com> a écrit :

> 
> Le 9 juil. 2014 à 13:58, Sven Reimers <sven.reimers at gmail.com> a écrit :
>> My train of thought is more along expressiveness... The revision is a general trigger and the API user has to check for the actual state of the different properties. I thought it may be more natural to just listen to the real changes..
>> 
>> What I am looking for is a simple way to bridge undo/redo to NetBeans undo/redo including detection if scene has changed...
>> 
>> 
> 
> When revision changes, this means
>     - currentJob has changed
>     - undoStack has changed
>     - redoSack has changed
>     - canUndo has (potentially) changed
>     - canRedo has (potentially) changed
> 
> In that situation, I must recognized that I prefer one single observable point
> even if it’s a bit less expressive I agree.
> 
> Having played a lot with observable properties on Node instances, 
> I end up in situation where I missed a single well defined observable point
> (like Swing events of the old time). That’s why I intentionally limited the
> observables in SB to their strict minimum.
> 
> Eric
> 
> 
>> -Sven
>> 
>> Am 09.07.2014 09:59 schrieb "Eric Le Ponner" <eric.le.ponner at oracle.com>:
>> Hi Sven,
>> 
>> There is already JobManager.revisionProperty() available.
>> Isn’t it enough for Netbeans plugin to update its state ?
>> Scene Builder App does everything with this observable prop.
>> 
>> Eric
>> 
>> 
>> Le 8 juil. 2014 à 23:28, Sven Reimers <sven.reimers at gmail.com> a écrit :
>> 
>> > Hi guys,
>> >
>> > I am still working on integration SceneBuilder into NetBeans. To
>> > enable/disable some of the icons present it would be helpful if
>> >
>> > 1. currentJob would be an observable read only property
>> > 2. undoStack would be an observable immutable collection
>> > 3. redoStack would be an observable immutable collection
>> > 4. canRedo would be an observable ready only property
>> > 5. canUndo would be an observable ready only property
>> >
>> > Does this make sense?
>> >
>> > Shall I file an issue and prepare a patch?
>> >
>> > Thanks
>> >
>> > -Sven
>> >
>> > --
>> > Sven Reimers
>> >
>> > * Senior Expert Software Architect
>> > * NetBeans Dream Team Member: http://dreamteam.netbeans.org
>> > * Community Leader  NetBeans: http://community.java.net/netbeans
>> >                              Desktop Java:
>> > http://community.java.net/javadesktop
>> > * JUG Leader JUG Bodensee: http://www.jug-bodensee.de
>> > * Duke's Choice Award Winner 2009
>> > * Blog: https://www.java.net//blog/sven
>> >
>> > * XING: https://www.xing.com/profile/Sven_Reimers8
>> > * LinkedIn: http://www.linkedin.com/in/svenreimers
>> >
>> > Join the NetBeans Groups:
>> > * XING: http://www.xing.com/group-20148.82db20
>> > * NUGM: http://haug-server.dyndns.org/display/NUGM/Home
>> > * LinkedIn: http://www.linkedin.com/groups?gid=1860468
>> >                   http://www.linkedin.com/groups?gid=107402
>> >                   http://www.linkedin.com/groups?gid=1684717
>> > * Oracle: https://mix.oracle.com/groups/18497
>> 
> 



More information about the openjfx-dev mailing list