SlickEdit Community

SlickEdit Product Discussion => SlickEdit® => SlickEdit® Core for Eclipse™ => Topic started by: mwilkins on February 25, 2011, 09:46:28 am

Title: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: mwilkins on February 25, 2011, 09:46:28 am
I am looking at purchasing the core plugin for use with the QNX environment , but I cannot update to the lastest version of the development IDE , as I need the older version of the QNX suite for compatibility with some custom hardware.
When I try and install the Trial of Slickedit core, I get an error "requires plugging "org.eclipse.php.debug.core"".  Is there anyway I can install this extra plug in, and if so, where from? I have managed to get an older version of Slickedit core 3.3.1 from a thread on this forum which points to https://customer.slickedit.com/update/secore/ ,which installs fine, but the trial licence does not work for this older version, it is asking for a number, not a licence file. Any help getting this going would be great, as I hate going back to the eclipse editor ( we used Slickedit 2010 at my old position), and am keen to get the plug in going, but obviously don't want to purchase without knowing it is going to work.

Thank you
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: mwilkins on February 25, 2011, 11:58:59 am
To be more precise , it says

PHP (SlickEdit Integration with PDT) (3.6.1) requires plug-in "org.eclipse.php.debug.core".

Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: Ryan on February 25, 2011, 04:14:30 pm
What version of Eclipse is this QNX IDE based on?  Is it Eclipse 3.3 or earlier?

If this is the case ( man, that is old :( ) then I will have to figure out how to get you a trial license key, because as you've already discovered, SlickEdit Core 3.3.1 and earlier used a different licensing mechanism.

If this is not the case, you shouldn't be getting that error from the installer...I'll have to figure that out.

- Ryan
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: Ryan on February 25, 2011, 04:30:16 pm
I think I figured out something that should allow you to use the trial license file you have with the 3.3.1 product, even though Core 3.3.1 expects a key not a file.  Close Eclipse and create an environment variable in Windows called VSFLEX_LICENSE_FILE and set the value to the full path to your trial license file that you downloaded, ie. C:\path\to\license\slickedit.lic.

Now start Eclipse...does this work?

- Ryan
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: mwilkins on February 25, 2011, 05:45:36 pm
I think I figured out something that should allow you to use the trial license file you have with the 3.3.1 product, even though Core 3.3.1 expects a key not a file.  Close Eclipse and create an environment variable in Windows called VSFLEX_LICENSE_FILE and set the value to the full path to your trial license file that you downloaded, ie. C:\path\to\license\slickedit.lic.

Now start Eclipse...does this work?

- Ryan

Thanks Ryan, yes it is very old it is eclipse
Release 3.2.2
Last revised January 19, 2007.

So is this the newest version of Slickedit core that will work with this version of eclipse? or is there a version that would be better than this one between the  3.3.1 and 3.6.1. releases tha I could try?

The licencing file worked great with the Environment variable you suggested. So if this is the best that I can use, can I get a reduction in the lincencing fee as the program is about 4 years old, or is there a licencing option that is not a yearly subscription that would suit me better for the older version?

PM me if needed,

Thanks
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: Ryan on February 25, 2011, 07:20:07 pm
SlickEdit Core 3.3.1 only officially supports Eclipse 3.3.x :/.  But...that is probably the closest you will get.

On the other hand, since you are trying to use our plugin in such an old version of Eclipse, you might want to just go ahead and try the latest version of our plugin (3.6.1) and see if it works.  It is far superior to our 3.3.1 version.  If you do want to try this, as you've already encountered, you will have some trouble installing because Eclipse has changed the installation mechanism so much between 3.2 and 3.6...what you will probably have to do is install the JDT, CDT, and PDT plugins even though you might not need them.  The reason for this is that we have 3 plugins which are dependent on these plugins (JDT, CDT, and PDT).  We we mark them as "optional" for install, but I don't think the Eclipse 3.2-based plugin installation mechanism can even recognize that they are optional, so it's trying to force you to install them...and thus, complaining that "org.eclipse.php.debug.core" isn't there.

So if you have the time and feel like trying it out, and don't mind the wasted space of installing plugins that you don't need, give it a shot.  If it works, you'll probably be really happy that you tried it.  I can mess around in Eclipse 3.2 and see if I can get our 3.6.1 plugin to install without installing CDT/JDT/PDT if I have some time.

I'm glad the environment variable trick works...but I don't think you are going to get a reduction in cost just for using an older version :).  Feel free to contact our sales department and ask, though: sales@slickedit.com.

- Ryan
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: mwilkins on February 25, 2011, 10:07:51 pm
Thanks Ryan, if you could try and get 3.6.1 going with 3.2 that would be great.
Where can I get the 3 plugins you mention from , the JDT, CDT, and PDT plugins? What exactly are they? so I can have a go myself, because like you say, your new plugin is more superior, and if I am paying full price for  for it , obviously I would like the new version, not the 3 year old version.

thanks
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: Ryan on February 25, 2011, 10:51:40 pm
Those are the development toolkits for Java, C, and PHP...respectively...they are written by groups at Eclipse.  You should be able to find and install them through the update manager in Eclipse...they should be available on some eclipse.org site that you can access through the update manager.  I just don't know how to tell you to find them exactly because I don't have Eclipse 3.2 installed on my system right now...but I am working on that.

- Ryan
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: mwilkins on February 26, 2011, 05:46:43 pm
Thanks Ryan,
I had a go at trying to download the plugins, but the only versions I could find were already embedded into a copy of eclipse. I tried copying their components from the plugin and feature folders , and placing into the plugin and feature folders on my copy, but it still complains that "org.eclipse.php.debug.core""is not present, so I must need it to go through some proper install process. Does anyone know where and how I can install these plugins? Its strange, because if I try and add Slickedit core 3.6.1 to the newer QNX suite ( which I cannot use) , it installs fine , even though "org.eclipse.php.debug.core"" is not present ? How come that works then without it?

If you could get it working Ryan, I would be extremely grateful

Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: mwilkins on February 26, 2011, 10:22:36 pm
I have tried several sources for PDT, but I have problems with them all

http://download.eclipse.org/releases/helios/

just fails at 6% when asking for an update

http://downloads.zend.com/pdt/

wants Zend Debugger Feature (5.2.15.v20081217) requires feature "org.eclipse.php_feature (1.0.2)", or equivalent.

http://download.eclipse.org/tools/php/updates/

complains PDT Feature (1.0.5.v20081126-1856) requires feature "org.eclipse.wst (3.0.0)", or compatible.

I just don't seem to be getting anywhere, I have been trying for hours today. Are these the right sites? Am I doing something wrong?

Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: Ryan on February 27, 2011, 08:05:44 pm
I tried two things...and neither worked :/.  I'll tell you what I tried in case you are curious, or want to try for yourself.  But from what I can see, I can't get SlickEdit Core 3.6.1 to work in Eclipse 3.2.x.

The first thing I tried was just to bypass the "optional" features which have the dependencies on the PDT/CDT/JDT plugins by manually installing SlickEdit Core.  I grabbed the archive file for offline installation (which is available at http://www.slickedit.com/trial/slickedit-core via the download link at the bottom of the page), and unzipped it.  Then I unzipped all the required plugins and features jar files into their respective folders.  For example, I unzipped com.slickedit.core_3.6.1.jar into com.slickedit.core_3.6.1/.  I did this for:


Then I dragged/dropped the plugins directories that I just extracted into the ECLIPSE3.2/plugins directory, and the features directory into the ECLIPSE3.2/features directory...and started Eclipse.  I thought this would work, but then when I tried to activate SlickEdit Core by going to Help > About SlickEdit Core, it wouldn't activate :/.  There was no error thrown but I checked the .log file for the workspace and I saw an exception that didn't make sense.  If Core 3.6.1 was compatible with Eclipse 3.2-based software I would expect this to work.

My second attempt was to install CDT, JDT, and PDT in order to use the Eclipse installation mechanism at Help > Software Updates > Find and Install to installed SlickEdit Core.  JDT came with the version of Eclipse 3.2 I downloaded, and CDT was easily downloaded/installed.  But I couldn't get PDT to install...I kept getting the same exception installing the same required plugin for PDT.  Here are the directions I found for installing PDT in Eclipse 3.2.x: http://wiki.eclipse.org/PDT/Installation#Eclipse_3.2_.2F_Callisto_.2F_PDT_0.7 .  You can see if you can get that to work, and the try installing Core 3.6.1.

Sorry I don't have better news,

Ryan

Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: mwilkins on February 27, 2011, 10:12:06 pm
Thanks Ryan for all your help. I Tried your method 1 as above, and all the slickedit menu items appear, but nothing happens when I select them. I assume this is what you have seen.

I cannot get the second method you outline to install the PDT, as no matter what I do, there is always something else that is missing first that needs to be installed.

If you do manage to make any headway and get any help on the exception you are seeing, please get back to me, and this week I will try testing the 3.3.1 trial with what I have got. I have contacted your sales department to see if they can do a reduction for the 3 year old product as you suggested for when the trial expires.

I can't thank you enough for getting me going at least for now, you are a star!


Cheers

Martin
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: mwilkins on February 27, 2011, 10:13:18 pm
oh and are there any hotfixes for 3.3.1 that may be handy? and if so, where could I obtain them from?...thanks
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: mwilkins on February 28, 2011, 11:20:52 am
Hi Ryan,
I have started using 3.3.1 today, but am finding there seems to be a problem with the Preview window. It seems to work OK for a bit, but then after a while, if I select a variable or a method, the Preview window does not update with the relevent information.... until I drop the cursor in the Preview Window itself... its like it has stopped updating itself. I'm sure if this was the case there would have been a hotfix for it, or it there anything else I can do to sort it? I'm sure a couple of years ago Slickedit 2009 or some version like that did the same and it was sorted later.

Also ( again after a while of using it) the information from the tagging seems slow too  I have tried upping the size of the tag cache nand buffer size to twice their original size, but it seems to make no difference....

I am using a Pentium 4 3.0 GHz with 1.5 g of ram Windows XP, which I am asuming is a good spec for an old piece of software like this


......Oh for a working 3.6.1



Sorry I have just come back to edit this post as I have found out more about the Preview Problem

The Preview works fine if you only select items in say one cpp file.... as soon as you then go to another cpp file, it starts messing arround ( ie you now have to put the cursor in the Preview window to refresh.... or as below, it locks up completely)
Sometimes the preview window also locks up after a while too. At this point all I can do is close the preview window, and open it again to get it slightly working again. This is one of the features of Slickedit which I use the most, one of the main reasons for wanting to purchase it. Is there a quick way to close and open the Preview window, to save having to go to the Window->Show View->Other to open and close the window? I tried to bind both the activate Preview and Toggle Preview commands to keys, but neither of them seem to work, or do what I want.

Any suggestions?
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: Ryan on February 28, 2011, 03:35:13 pm
I looked around for hotfixes on our share drive and also on these forums and didn't find any...sorry :(.  I was really hoping to find something that would affect the Preview window b/c, as you've discovered, the Preview window in Core 3.3.1 seems really buggy.  I've now seen this for myself.  If I can get some time to see if I can figure this one out, I'll let you know...but I can't make any promises since you are working in an unsupported setup.

There is no command for quickly activating the Preview window in that version of Core.

I know...it sucks that QNX is on such an old Eclipse platform...if it was just on even 3.4 we wouldn't have to deal with this :/.  We deal with a lot of Eclipse based IDEs (RDz, Adobe Flex, etc.) and they all are on 3.4 or later...

- Ryan
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: mwilkins on February 28, 2011, 04:24:17 pm
Thanks,
Is the Preview window controlled by code in the Macros folder? If I swapped the file in there (is it the tagwin.e file) for the new 3.6.1 version, would that maybe work?

Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: Ryan on February 28, 2011, 04:27:10 pm
It is, but that won't work.  That code is definitely incompatible with the 3.3.1 macro codebase, and while I would love to think that the entire functionality of the preview window is modularized enough that it is contained completely within one SlickC file...I know that is not the case :(.  You would have to make a lot of changes...

- Ryan
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: mwilkins on March 08, 2011, 12:10:44 pm
Hi Ryan,
I don't suppose you had any more time to try get3.6.1 running for me? Your sales dept have told me that I will still have to pay full price for 3.3.1 even though it is years old and I will get no support for it. Before I pay $100 would be nice to get 3.6.1 working, or I may just look into what other options I have to add some more slickedit functionality though free plugins. They have given me another week trial for now

Thanks
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: Ryan on March 08, 2011, 02:58:49 pm
Hi,

I haven't had any more time to look into it after my first attempts.  I don't have a lot of confidence that SlickEdit Core 3.6.1 is going to work in an Eclipse 3.2-based IDE :/.

Sales was right that you wouldn't have support, technically, but we will always "help" users who have older setups.  Even our support staff will.  This means if you are having usability issues or bugs that need to be reported that you can still rely on us for that.  The fact that you wouldn't have maintenance & support with your setup means that we won't necessarily fix bugs for that older version.  And I'll always be here on the forums helping where I can.

I understand the frustration...and we are moving towards supporting as many Eclipse versions as we can with our latest plugin.  Core 3.6.1 is the first version of the plugin to officially support multiple versions of Eclipse...3.4, 3.5, and 3.6.  I'll let you know if I come up with anything else...check back before your trial expires if you are still interested and you haven't seen anything from me.

- Ryan
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: mwilkins on March 10, 2011, 12:24:14 pm
Hi Ryan,
If I say go into a menu item...say Format-> Beautify and click on the help button, there is no help given. Is there a help file that is missing from the install or something?

Cheers
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: mwilkins on March 10, 2011, 02:03:00 pm
Another Problem

I have the Preview window, and the slickedit search windows undocked ( detached so I can place on a 2nd monitor) I minimize the QNX IDE. I then maximise the IDE.
The Preview and search windows are no longer visible. If I go to

"Window -> Show View -> Other -> Slickedit -> Preview "

And select, the windows is still not visable. All I can do to get the windows back is to close and reopen the QNX IDE. Its as if when re maximizing the IDE, it is not restoring the Visable flag for any window that is detached.
Any ideas on how to fix this. Are you sure there was no hotfixes for this version.... I can't believe people have not complained about this and other bugs I have seen so far before?

Thanks
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: Ryan on March 10, 2011, 03:24:25 pm
There aren't any hotfixes lying around...I checked.  I also tried a different method of getting Core 3.6.1 installed into Eclipse 3.2...by using the zip file for offline installation and manually deleting the optional features/plugins that cause dependency problems.  It installed fine but I was having the same problems where the plugin will not activate due to exceptions/errors.  I'm pretty certain at this point that it is just incompatible.

As for this bug, it definitely doesn't occur in Eclipse 3.6 w/ Core 3.6.1...I didn't check in any other previous versions of Eclipse.  It's always shocking to users that no one has reported a bug before them, but I did grep through Bugzilla and couldn't find anything.  It could be that it was just fixed in a subsequent release of Eclipse, and it wasn't reported before then.  Preview isn't one of our more popular views I don't think, so I could see it also being the case that there weren't too many users using it back when it was first released.

Sorry I don't have better news :(.

- Ryan
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: mwilkins on March 10, 2011, 09:20:55 pm
Thanks anyway Ryan,
As I said its not just the preview window, it is any of the slickedit windows such as slickedit search etc. I can't believe you think the preview isn't popular, the preview window is about the best thing about slickedit! When being introduced to code developed by another developer , it is great to be able to see where a piece of code lives without searching.

You can see why I really don't want to be paying full price for an unsupported piece of software. I know its not slickedits fault the QNX is using an old version of eclipse and you can only really support the latest version. I am also unhappy that I will have to pay for a subscription type licence, when the licence originally sold with 3.3.1 was a pay once licence, the guy in your sales department did not want to know really, I was very disappointed with his response to be honest. I'm sure an original 3.3.1 licence could be rustled up if they wanted to.
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: Ryan on March 11, 2011, 01:20:53 am
Heh...I didn't mean it isn't popular, I'm sure it is widely used.  I guess all I meant is that I think there is a difference between that and something like References, or Outline.  If those had bugs...we would hear about them in about 3 seconds.  I agree that Preview is a great tool...I helped write the spec for it.

I definitely understand about not wanting to buy a product that is over 3 years old and unsupported.  The thing about the old, more expensive perpetual licenses, is that we can't sell them anymore because that product doesn't exist.  I'm very sorry that you had a bad experience with a sales rep here...and I'll see what the deal is with that.  That should not happen, and I know that they all work very hard here and take their jobs very seriously...so they will want to know that someone was disappointed with their service.

Let me know if I can help with anything else, or if QNX ever moves on to something as "new" as Eclipse 3.4.  Then you should have no problems running Core 3.6.1, or whatever our latest version of the plugin is at that time.

- Ryan
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: mwilkins on March 28, 2011, 02:38:33 pm
Hi Ryan
I had another problem with the editor. If I go into debug mode on the QNX editor, and step through the code, then I cannot see variable values by adding watches etc and floating over the variable. I know this would be tricky for you.But my best solution would be get the editor to go back to  eclipse editor mode ( by clicking Switch to C/C++editor from the menu on right mouse click), the only problem was that when I stepped in the code, then the slickedit editor would kick back in. Is there any way to turn off the slick edit editor temporarily without having to quit eclipse and come back in again?

cheers
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: Ryan on March 28, 2011, 06:21:21 pm
We have added the ability to see the values of variables while debugging via hover over tooltips...at least for C++, Java, and PHP.  But this isn't implemented for the version of Core you are using, as you discovered.

The best solution I see for you is to change the file association for C++ files before you start debugging, and then change it back after debugging.  This isn't great, but I think it's the only way this is possible :/.  To change what editor is used for C++ files go to Window > Preferences > General > Editors > File Associations and find the extension you use for your C++ files in the list...ie *.cpp.  Change the default editor from SlickEdit to whatever the normal QNX C++ Editor is, and then hit OK.  Now when files are automatically opened in debugging (or at any time), they will open with the other editor.  You can change the default back to SlickEdit afterward.

- Ryan
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: mwilkins on March 28, 2011, 07:03:54 pm
Thanks Ryan, I don't suppose a macro could be written to do it?
Title: Re: older version of Eclipse requires plug-in "org.eclipse.php.debug.core"
Post by: Ryan on March 29, 2011, 02:33:17 pm
No...we don't have a SlickC API for that functionality.  It would be possible to write a small, custom, Eclipse plugin which contained a command, I think.  You could then bind that command to a key.  That's the only way I can think of to get something that would do this automatically.