Eclipse 4.4 Luna pinning editor tabs - eclipse

I've found this question: Eclipse - How to pin editor tabs? and I've installed "Extended VS Presentation plugin for Eclipse", but it's not working.
How it should look (from http://andrei.gmxhome.de/skins/index.html):
How it actually looks on my Eclipse 4.4 (on Ubuntu):
As you can see, "Current presentation" setting is missing.
When I've installed this plugin (via eclipse), it was in "Eclipse 3.6 - 3.8 plugins", so maybe it's incompatible with 4.4 Luna? However, it was possible to install it, so it should work, right?
Also, if you know any plugin that would allow pinning tabs in eclipse, feel free to post your answer and describe it.

Support eclipse versions for this plugins:
Eclipse Versions:
Juno (4.2, 3.8), Previous to Juno (<=4.1)
This plugin NOT works(See this) in eclipse 3.x on Linux.(But here author says it support Linux platform. Contact author for more details)
This plugin NOT works in eclipse 4.x on any platform.
Please note, that the skin, tab actions and lists are available for Eclipse 3.x only! Eclipse 4.x is not supported.

That first Appearance dialog is how it looks in Eclipse 3.x. The appearance code was completely rewritten for Eclipse 4.x.
The fact the plugin installs may just mean the install is not careful enough about specifying the versions of Eclipse it supports.
You should try and contact the plugin author to see if it supports Eclipse Luna.

In my point of view, everything is fine.
As you can see in the images below, (Check bottom (console) ).
The above page is updated on 06-25-2014
But the screenshot in that page is taken on 06-02-2008 , (Check bottom (console) ).
The screenshot given in that page is a screenshot of very very old version. The plugin is updated, but the screenshot in the page is not yet updated.
The new plugin will work as shown in the image in the question
Alternative
In Eclipse 4.4.0 there You'll find a pin symbol in the default toolbar of Eclipse on the right side. After clicking it, the Java Editor Tab symbol gets changed indicating this editor is pinned now. Unfortunatelly I could not find a corresponding entry in the popup menu. But it is easy to assign e.g. the keys Ctrl-P to "Pin Editor" in the key bindings of Eclipse. (Don't forget to unbind Ctr-P = Print).
In Eclipse Neon 4.6.0 Pin is not functioning.

Related

Changing theme in Apache Netbeans 9.0

I have installed Apache Netbeans 9.0 recently in Mac running macOS Mojave. I am trying to change the Netbeans theme to "Dark Look And Feel Themes" but I can't find the options.
Previously, I have used the older versions (8.2, 8.1, 8.0.2) of Netbeans. To change the theme, I navigate to
Tools -> Plugins -> Available Plugins
Install the "Dark Look And Feel Themes" plugin and restart the IDE to reflect the change.
But, I don't find this plugin in the Apache Netbeans 9.0
I also checked whether these plugins are available to download from online. So that I can add them using 'Downloaded' option. But, they are only available for older versions.
http://plugins.netbeans.org/plugin/62424/darcula-laf-for-netbeans
http://plugins.netbeans.org/plugin/52624/netbeans-dark-theme
So, I am a bit stuck here. Any help will be much appreciated. There are few similar stack overflow questions raised earlier, but they all talk about the old version of Netbeans.
Updated 4/11/19:
Based on a comment from #superbiji below, Darcula + Norway Today works fine with NetBeans 11.0.
Updated 2/7/19:
Note that the answer below applies only to NetBeans 9.0. The situation is a little different on NetBeans 10.0 where the Dark Look and Feel plugin (themes "Dark Metal" and "Dark Nimbus") also worked fine. See Projects, Files, Services, Navigator color background.
I tried to download then manually install those two plugins on NetBeans 9.0, but it didn't work for me:
Download the plugins as zip files, and unzip them.
Tools > Plugins > click the Downloaded tab > click Add Plugins...
The Add Plugins dialog opens, but it requires you to select a jar or nbm file, and no files of those types exist in the downloaded zip files.
However, there is an alternative approach that works for Darcula (but not for Dark Look And Feel Themes). It is a simple two step process:
Make the Darcula plugin available.
Automatically install the plugin, just as you would on NetBeans 8.2.
To make the plugin available:
Tools > Plugins > Settings tab > Click the Add button.
In the Update Center Customizer dialog that opens:
Enter some descriptive value in the Name field such as NetBeans 8.2 plugins
Enter http://plugins.netbeans.org/nbpluginportal/updates/8.2/catalog.xml.gz in the URL field.
Click OK to make the plugins associated with that URL available for installation.
Now click the Available Plugins tab. You should see a lot of new entries, including one for Darcula LAF for NetBeans:
Check that entry and click Install, just as you would on NetBeans 8.2.
NetBeans 9.0 should restart using the Darcula theme:
Notes:
I don't think this approach is formally supported by NetBeans or the plugin author, but it works fine.
To customize Darcula settings: Tools > Options > Appearance > click the Darcula Look and Feel tab.
To switch from Darcula to one of the built in NetBeans look and feel options: Tools > Options > Appearance > click the Look and Feel tab > select an entry from the Preferred look and feel drop list.
I can recommend you to check NetBeans Themes website. It allows you to design and download your own themes.
Twilight theme is a good example:

PyDev cause duplicated show of project in Eclipse J2EE perspecitve

I just installed the latest PyDev 4.4.0 plugin to my Eclipse Mars.1. I created a new Java project in a new workspace. And I add the project to a workingset. In the Eclipse JavaEE perspective, the project has duplicated show in the Project Explorer view when I show workingset as the top level element:
I uninstalled PyDev, now the project show is OK.
Anyone knows the root cause? Or a workaround?
Ref:
A possibly related link: Projects appearing twice in working sets - eclipse
A related Eclipse bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=373031
A related J2EE tooling bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=351764
Well, given that the original report on J2EE is still open: https://bugs.eclipse.org/bugs/show_bug.cgi?id=351764 I don't think this can be fixed at the PyDev side (although it makes the problem appear, it should be fixed on the J2EE side).
As a note, if anyone wants to take a look, on the PyDev side, this happens at: https://github.com/fabioz/Pydev/blob/development/plugins/org.python.pydev/src_navigator/org/python/pydev/navigator/PythonModelProvider.java, but it's done with the proper APIs (using IPipelinedTreeContentProvider), and I'm currently convinced the issue doesn't lie on the PyDev side (although if I'm proved wrong, I'd be happy to fix it).
A workaround would be disabling PyDev or J2EE (depending on which kind of content you use more) just at the explorer level (i.e.: in the explorer do Ctrl+F10, Customize View, Content, disable the PyDev Navigator Content or the Content related to J2EE).

How to hide/disable CDT launchbar?

I've updated my Eclipse IDE recently and a new launchbar appeared after the CDT update.
I really don't like it, which is why I'm trying to get rid of it. I haven't yet found a way to hide or disable it...
Do you know how I could do this ?
Here's a snapshot of the launchbar : https://wiki.eclipse.org/images/1/15/CDTLaunchBar.png
The LaunchBar (org.eclipse.launchbar.feature.group) comes as a dependency of "C/C++ Qt Support" (org.eclipse.cdt.qt.feature.group), so you need to either un-install the Qt Support CDT component, or disable the LaunchBar in Eclipse preferences:
The launchbar used to come as a plugin for the CDT, which is probably how you got it, but it was later (in the Mars release) was moved to be a standalone feature - which is probably what #Doug Schaefer refers to.
If you have the new version of the Launch Bar that is installed as a feature, you can go to Help -> About Eclipse and click the "Installation Details" button. In the "Installation Details" under "Installed Software" you should see the "Launch Bar" and be able to uninstall it. Note that if you had the Launch Bar installed previously as a plugin, it will still remain on your system after you have removed the Launch Bar feature.
Regardless if you have the feature version or the plugin version (or both), you can also just hide it using the Eclipse preferences: Run/Debug -> Launching -> Launch Bar, and there would be 2 or 3 check boxes - just uncheck all of them (or just the first actually) and you should be good to go.
I'm not sure how you got it. The LaunchBar isn't part of the CDT. Only the new Arduino CDT uses it.
To remove it, find the org.eclipse.launchbar feature and uninstall it.

Update Eclipse plugin from 2.x style to 4.x style (plugin.xml to manifest.mf/osgi bundle)

I have an Eclipse plugin that was originally written (not by me, and I don't have access to the original developer) that I'm trying to update for Eclipse Luna, because it stopped working when my team updated to Eclipse 4.4.
I downloaded the Luna Plugin development version, cleared a few warnings, updated some broken code, fixed a few bugs, and tested with "Run As -> Eclipse Application
This worked fine: all the views showed up, the preferences pages, etc.
So then I tried to export the plugin so I could test on a fresh installation of vanilla Eclipse Luna. I did that by using the Export Wizard:
And generated a deployable set of jars with said wizard:
I copied the generated folder (which contains all the jars appropriately) into the dropins folder of my fresh vanilla Eclipse Luna and started it up.
Unfortunately, I got the following error:
Which led me to this SO question and this Eclipse bug report, which explains that I have a 2.x style plugin that uses the plugin.xml instead of an OSGi style manifest.mf. Continuing my search, I found this SO question, which was directed at a 3.x version of Eclipse, but I used the 4.x equivalent:
Which I used with the following options checked:
And I accepted all the changes in the previous pane after the (long-running) changeset. However, upon deploying to my vanilla install, I got the same error about the plugin converter. That led me back to this SO question, which recommending installing the Eclipse 2.0 plugin support package. I did so and restarted Eclipse. The error in my error log did stop showing up, however the view/preferences/etc for my plugin are still not showing up. The plugin does show up under Help -> Installation Details -> Plug-ins, but doesn't seem to be interacting at all.
The text of the plugin.xml can be found here at Pastebin. The text of the MANIFEST.MF can by found at this other Pastebin link
Any suggestions for getting my plugin to work through the manual export so the other developers on my team can test my changes before I try releasing the update to the world?

Jess Editor Plugin not Appearing in Eclipse Luna

I have the Jess DE installed on an old version of Eclipse (Helios), and when I open any of my Jess files there, they are nicely displayed with appropriate colors, etc. I installed a newer version of Eclipse (Luna) in order to install PyDev, and meanwhile added all the Jess editor plugin files. I added them in exactly the corresponding subfolders as my older version of Eclipse, but have had no luck getting those files to open with the right editor. They'll open, but only as plain text, and trying to do an open with does not show the Jess Editor as an option. I restarted Eclipse a couple of times, but no luck. I also tried to follow these instructions:
"Help > Software Updates > Manage Configuration in Eclipse, and enable the JessDE feature"
but that menu doesn't actually seem to appear in Luna. Installation details under the plugins tab also doesn't seem to show the Jess editor.
Any ideas what could be going wrong here? I'd love to have just a single version of Eclipse running on my machine, instead of several...
Thanks!
I have your same problem. In mine Eclipse KEPLER version goes all right, but when I do the SAME installation in LUNA, something goes wrong.
Probably, the last version of JESS (7.1p2) doesn't is compatible with LUNA. I hope not.