Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Today's Messages (on)  | Unanswered Messages (off)

Forum: TMF (Xtext)
 Topic: xtext editor hanging for long time
Re: xtext editor hanging for long time [message #1736713 is a reply to message #1736710] Fri, 01 July 2016 09:47
Ed Willink is currently offline Ed WillinkFriend
Messages: 4803
Registered: July 2009
Senior Member
Hi

Does the Xtext auto-build actually do anything for you? If not, then
there is a very simple solution; remove the Xtext nature.

From my observations, the Xtext nature/builder contributes to a variety
of time wasting activities, so I only use it in:
- plugins with a *.xtext file
- plugins with a *.xtend file
- plugins with a *.mwe2 file
I endeavour to keep those plugins simple. In partcular, I do not use the
Xtext nature on plugins with a *.ecore file and I isolate build *.mwe2's
from *.xtext.

Regards

Ed Willink



On 01/07/2016 10:36, Sachin Samaram wrote:
> What's your suggestion for me to fix this issue?
Forum: Java Development Tools (JDT)
 Topic: Trying out External Annotations for null analysis, but Annotate does nothing
Re: Trying out External Annotations for null analysis, but Annotate does nothing [message #1736692 is a reply to message #1736656] Fri, 01 July 2016 08:06
Ed Willink is currently offline Ed WillinkFriend
Messages: 4803
Registered: July 2009
Senior Member
Hi

It is not really a documentation problem.

IMHO a tool is always at fault if it offers a facility and then silently
does nothing. In this case there is a missing diagnostic popup informing
about the inappropriate activation context.

IMHO a tool is also at fault if it hides a facility and fails to explain
the hiding. So if a menu option is greyed out, we really should have a
hover text to explain why. (And disabled menu options should be greyed
out rather than removed.)

Regards

Ed Willink



On 30/06/2016 23:27, Stephan Herrmann wrote:
> Sorry for my silence, I just didn't have any quick ideas how to proceed.
> Glad you figured it out.
> Since not every user will dive into the debugger, let me know if the
> http://help.eclipse.org/topic/org.eclipse.jdt.doc.user/tasks/task-using_external_null_annotations.htm&anchor=create
> could be improved.
>
> Stephan
>
Re: Trying out External Annotations for null analysis, but Annotate does nothing [message #1736714 is a reply to message #1736692] Fri, 01 July 2016 09:56
Michael Vorburger is currently offline Michael VorburgerFriend
Messages: 86
Registered: July 2009
Member
> let me know if the (doc) could be improved.

Upon re-reading it, "select the type (method parameter or method return type)" is actually fairly clear... Wink

> missing diagnostic popup informing about the inappropriate activation context
> a menu option is greyed out, we really should have a hover text to explain why

In an ideal world, that would be cool. Realizing that this is a volunteer driven effort, I wouldn't say it's a high priority though (compared to spending time on ironing out any remaining bugs in null analysis, if there are any).

Most importantly is probably finish up the tooling story, e.g. incl. (a) establishing a repository with null annotations for commonly used FLOSS libs, with an open culture inviting many to contribute; and (b) auto. loading and associating *.eea, through Maven (and, later, Gradle). IMHO these two points are maybe what's missing most now. I'll see if I can perhaps contribute to both of those in the coming weeks & months; and will let you know when I have something to show, or discuss.
Forum: e(fx)clipse
 Topic: EMF-Edit - mapping features to table columns
EMF-Edit - mapping features to table columns [message #1736711] Fri, 01 July 2016 09:44
Robert Onslow is currently offline Robert OnslowFriend
Messages: 17
Registered: March 2016
Junior Member
Looking at http://git.eclipse.org/c/efxclipse/org.eclipse.efxclipse.git/tree/demos/org.eclipse.fx.demo.contacts.app/src/org/eclipse/fx/demo/contacts/views/ContactsTableView.java

which is the line which specifies which feature of the EObject is shown in which TableColumn?

I can see that, for editing, this is in the line

firstNameCellFactory.addCellEditHandler(new EAttributeCellEditHandler(ContactsPackage.eINSTANCE.getContact_FirstName(),
				editingDomain));


But without editing?

Robert
 Topic: Tycho build compiler cannot find javafx classes
Re: Tycho build compiler cannot find javafx classes [message #1736673 is a reply to message #1736640] Fri, 01 July 2016 06:20
Matthias F is currently offline Matthias FFriend
Messages: 19
Registered: June 2011
Junior Member
Hi,

@Dirk: running from eclipse works fine with the osgi.framework.extensions argument. Using -Dorg.osgi.framework.bundle.parent=ext causes a ClassNotFound(FXCanvas) when I open the FX-Part.

@Tom: Would this just be needed during compile time? I think shipping the jar itself would not be possible (legally). If so, how would I do this? My tycho build is pom-less.

Which of the target features do I actually need here? The rest of my target platform is already working, so all the e4 bundles etc. are already coming from other sites. Is the minimal JavaFX integration eneough?
Re: Tycho build compiler cannot find javafx classes [message #1736686 is a reply to message #1736673] Fri, 01 July 2016 07:30
Thomas Schindl is currently online Thomas SchindlFriend
Messages: 6164
Registered: July 2009
Senior Member
You don't ship that jar - it's only a compile time depdency, at runtime
the AdapterHooks take care to find the jar.

Take a look at our tycho config [1] eg for the IDE build where we
reference FXCanvas.

Just modify your the following to your root pom.xml:

> <pluginManagement>
> <plugins>
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-compiler-plugin</artifactId>
> <version>${tycho-version}</version>
> <configuration>
> <encoding>UTF-8</encoding>
> <extraClasspathElements>
> <extraClasspathElement>
> <groupId>com.oracle</groupId>
> <artifactId>javafx</artifactId>
> <version>8.0.0-SNAPSHOT</version>
> <systemPath>${java.home}/lib/jfxswt.jar</systemPath>
> <scope>system</scope>
> </extraClasspathElement>
> </extraClasspathElements>
> </configuration>
> </plugin>



Tom

[1]http://git.eclipse.org/c/efxclipse/org.eclipse.efxclipse.git/tree/releng/org.eclipse.fx.ide.releng/pom.xml

On 01.07.16 08:20, Matthias F wrote:
> Hi,
>
> @Dirk: running from eclipse works fine with the
> osgi.framework.extensions argument. Using
> -Dorg.osgi.framework.bundle.parent=ext causes a ClassNotFound(FXCanvas)
> when I open the FX-Part.
>
> @Tom: Would this just be needed during compile time? I think shipping
> the jar itself would not be possible (legally). If so, how would I do
> this? My tycho build is pom-less.
>
> Which of the target features do I actually need here? The rest of my
> target platform is already working, so all the e4 bundles etc. are
> already coming from other sites. Is the minimal JavaFX integration eneough?
Re: Tycho build compiler cannot find javafx classes [message #1736715 is a reply to message #1736686] Fri, 01 July 2016 09:56
Matthias F is currently offline Matthias FFriend
Messages: 19
Registered: June 2011
Junior Member
Thanks, now the build is working Smile

Running with -Dorg.osgi.framework.bundle.parent=ext still doesn't work. Any ideas on that? I don't have any required bundles or imports, like you mentioned here: https://www.eclipse.org/forums/index.php/t/1063826/

As said above I added the RCP e4 Target Platform Feature to my target. Which *.fx.* plugins do I need to add to my product definition?

I tried searching the git but didn't find anything that could show my how to do it.



Current Time: Fri Jul 01 10:02:51 GMT 2016

Powered by FUDForum. Page generated in 0.77665 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software