| Re: [eavp-dev] Geometry Editor integration |
Robert,
Thanks for the update. I'm happy to see progress here.
In the future, it would be best to work in a branch until you get the build worrying. If you need to put a branch under CI on Hudson, you can do that by copying either the master our next builds and changing the branch. My concern here is the emails I get saying our builds is broken from other developers. It hasn't happened this time, but it very well could. This would apply to both EAVP and ICE of course.
Jay
All,
I'm currently working on getting the build to run in environments other than Eclipse, where the Xtext code was being build by the IDE. Currently, the EAVP-next and ICE-next builds are broken. Once the build issues are resolved, the new Geometry Editor should be in the finished binaries. I'll update the EAVP issue tracker to reflect what is done and what still needs improvement tomorrow morning or when I fix the build, whichever comes later. However, two known issues are that the new material capability on the FXColorDecorator is preventing shapes form being colored correctly and operators currently aren't showing up in the tree view.
Robert
_______________________________________________
eavp-dev mailing list
eavp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eavp-dev