I am working on GWT2.3 with Eclipse Ganymede version 3.4.
While working with UIBinder, the auto complete feature (suggestions) is very slow.
I am not getting what to do in this situation. I need to add some plugins or files.
It too slow to work.
Comment out the DOCTYPE as a work around. It resolved the issue for me.
There's a discussion about this issue here:
http://code.google.com/p/google-web-toolkit/issues/detail?id=6262
And the solution posted by cave (comment #27) seems to be the easiest solution.
Related
i am wondering about eclipse's possibility to make breakpoints in .xsl-files.
It does not look like the debugger is able to stop on the line in xslt, while rendering... is there any hidden xsl-debugger?
Some time ago i did a lot of work with xslt. I was using the (commercial) Oxygen XML Editor which has xslt debugging capabilities and a lot of other features which helped me handling XSLT. As i remember correctly they actually offer oxygen as an eclipse plugin.
Yes, It's supporting ...
Please refer the below links
https://wiki.eclipse.org/XSLT_Project/UserGuide/Launching
http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.wst.xsl.doc%2Fhtml%2Flaunching%2Flaunching.html
I'm looking for resources to learn how to use effectively Eclipse forms within an Eclipse RCP application. I was trying to use the newest SWT Window Builder plugin on Indigo but building forms this way doesn't really work for me eg. cannot put anything inside expandable composite etc. (I have Swing background with Netbeans designer) and I'm new to SWT.
All I can find so far is this quite old tutorial from 2005.
Any help, point to good tutorial/book/source code sample will be highly appreciated.
I've found http://www.vogella.de/ to be invaluable.
Not much changed actually since the old 2005 tutorial so it's still very usable.
Check these out in addition too:
Eclipse Forms: New in 3.3
DeveloperWorks article on making forms Web-like
Cheers,
Max
I've also got the hint to start with vogella but after the first 2 topics I realized It's to hard to start with.
What helped me much more was to create each example/sample project and look for the source. Once you understood how all works you can lookup at vogella what you exactly need.
This my seem a little odd but I want to start eclipse (v3.5) in the most minimal version possible. Pherhaps just the core and the ui component without anything else. I'm new to eclipse Plugin Development so I don't really know if this is possible at all?
I googled this topic but there seems to be no useful info out there. Perhaps someone can help me...
Thanks
I found the solution. On this webpage in Section 3 "Create your first RCP application". There a minimal application based on the Extensions
org.eclipse.core.runtime.apllications
org.eclipse.ui.perspectives
is created.
How do I get smarty syntax highlighting in Eclipse PDT?
The only project I was able to find is SmartyPDT, but it's outdated and isn't working with my current Eclipse install (PDT All in one, with Eclipse 3.5).
EDIT:
I recently found this post asking the same question from a long time ago. But the plugin linked in the accepted answer there is out of date now.
EDIT: removed "(no accepted answer)" from title. it was misleading.
I've used both SmartyPDT and SSE*.
SmartyPDT is finicky and it took some time for me to get it working. Unfortunately, after an OS reinstall my custom jars don't work anymore, so I've been using SSE.
It is quite basic but better than nothing.
It is described in English at bar54.
Download it from Google's translated version.
Update:
Example of SSE http://www.freeimagehosting.net/uploads/1c07de77d7.png
*I guess this is what it's called, the page is in Japanese.
About Using Aptana + Eclipse: They removed support for Smarty in Aptana Studio 2 because they were going to "join forces with the eclipse PDT team", but with "unknown schedule as to when or whether smarty support will come to pdt".
Anyways, they also offer to download the "old" Aptana Studio, which works for me like a charm, I wouldn't want to miss smarty support ever again:
https://aptanastudio.tenderapp.com/faqs/installing-aptana-studio/downloading-aptana-studio-151-and-aptana-php
It works in parallel with PDT2, cause for some reason the php support of Aptana is not so good in 1.5.1 - but the smarty support is cheesy :).
what does Aptana use? I think its Smarty enabled..and it integrates with Eclipse PDT and the other choice is Zend Studio which is built on top of Eclipse PDT
Great article about integration Eclipse Helios + PDT + Smarty
http://www.ikravets.com/computers-life/programming/2010/09/27/eclipse-helios-pdt-smarty (Use translation to English on this page)
I use SmartyPDT, as suggested in this related question.
Just follow as strictly as possible the installation procedure. Worked for me without too much hassle.
The Eclipse Visual Editor project seems to be dead, no commits, no updates. Any one know what is happening?
Update 2: The project has been archived (i.e. dead) since June 2011 again.
Update: The project has been revived and is now under active development again.
Its pretty much dead due to a lack of developer support. Here are some recent posts from their mailing list talking about a lack of movement on the project.
What's happening? It's called NetBeans, and it's already happened.
I'm going to get voted down for this but they know it's true. I love eclipse and have used it religiously since I started Java. I'm not saying I like Netbeans, it's just all I hear whenever the concept of a Java visual editor is brought up.
The Jigloo plug-in for Eclipse is a pretty great alternative to the Visual Editor. Though still not quite as nice as the Netbeans GUI editor it is fairly robust and fully featured, especially compared to what was available in the Visual Editor plug-in. Definitely should give it a shot.
Actually NetBeans has gotten MUCH MUCH better. I've used Eclipse, Netbeans and IntelliJ for a few years each, and NetBeans is at least as good (performance, usability & features) as the others now.
It's also improving more quickly than the others are.
They have people working full time on alternate language support, so you'll find they have the best Ruby support in the industry, and I believe Python is about to become that good as well.
Of course, Eclipse still has that crazy-cool todo list that remembers which files you worked on for each bug and can take you back to the set of files/edits for any bug you've worked on, that's really amazing to use and I don't think it's available on either of the other platforms.
--- Revision from years in the future ---
I have used Netbeans more and really have to give the award to Eclipse. The difference has been in vertical programming environments--most will target Eclipse and ignore netbeans. You rarely need these, but when you need them there is often no way around them. If Netbeans does have an equivalent, it's often buggy to the point of not being usable, generally the biggest issue is emulator support.
You won't run into these unless you are working in a specific industry--Android development is one, the primary drive was to support Eclipse, NB seems to trail. Another I've worked on is in the TV/Cable industry.
For raw java development, however, I'd still give Netbeans a little edge because it's the environment that was targeted and supported by sun.
Visual Editor is doing a new release, 1.4, on September 16. Installation instructions for the RC are here:
http://wiki.eclipse.org/VE/Update
FWIW, the project did stall for a while. But there is a new, and relatively diverse group of folks working on it again. Most of the recent work is concerned with making the new release compatible with Eclipse Galileo.
It's officially dead as of May 2011. It's archived here, but slow to download and tricky to install. Instead, there's a new editor, WindowBuilder Pro.
Currentlty Google have Open Sourced the Windows Builder Pro. It seems nice
yeap,
http://www.eclipsezone.com/eclipse/forums/t91368.html
Yes, sadly, it is dead. Looking at the aforementioned email threads regarding it's revival I get the feeling that even if it does get picked up it will quickly collapse under the weight of some new requirements ("make it universal, edit everything from SWT to HTML").
WindowBuilder can be a good alternative. I had several problems with VE and I end up with WindowBuilder who worked for me perfectly.
http://www.eclipse.org/windowbuilder/