Core vs Plugin

[Ryan]

Great post.

I'm concerned that if I switch to Core, I'll be back to dealing with an immature product and taking a step back in terms of functionality or stability...If Core truly is an improvement over the Plugin (and if so, how is it better?)

I don't think you will take a step back in terms of functionality or stability because, as Scott touched on earlier, the current versions of both products provide the same editing features and views.  Core was created so that we could provide a lower price point with a subscription, and better integration with the Eclipse environment (Update Manager support, no environment variable requirements on Linux, no 3rd party installer).  In this sense, Core is a more mature product. 

Going forward, Core will be updated to include new SlickEdit features, as well as increased integration with Eclipse functionality.  I appreciate how you have come to value increased stability, dealing with some of the issues in earlier versions of our old plug-in .  We will continue to make improvements in this area...it's our #1 priority.  One of the great things about our Eclipse plug-in is that it will always be based on a minor release of SlickEdit, .0.1 or later.  You don't have to deal with the bugs in SlickEdit features that get ironed out during our minor releases.

help in dialog boxes doesn't work

This one is a high priority for us right now, and fits well with our goal of better integration into Eclipse.  In 3.2.x we got our help "native" and indexed in the Eclipse Help system, and now I think we can look into fully integrating our SlickEdit Help buttons with Eclipse.

clicking any of the other Eclipse views often causes the cursor in the editor view to get reset to the top of the first buffer in the list

This I've not seen before...have you noticed is it always a certain view that causes this behavior?

reset line modify markers in the left margin doesn't work

Thanks for the report on this one...I assume you are talking about the Save option?  This looks like it's being ignored in the plug-in, I'll file a defect and get it fixed in a future release if I can't hotfix it.  In the meantime, if you would like to bind this function to a key it will do the job for you on demand:

Code: [Select]

_command void reset_modified_lines() name_info(','VSARG2_READ_ONLY|VSARG2_REQUIRES_EDITORCTL)
{
   save_pos(auto p);
   top(); up();
   while(!down()) {
      _lineflags(0, VSLF_MODIFY | VSLF_INSERTED_LINE);
   }
   restore_pos(p);
}

Anyways, I hope this helps to explain some of the "mystery" behind Core...and hopefully we can get some of your remaining issues straightened out soon.  Thanks for the interest and feedback.

- Ryan

[wsappington]

Quote
clicking any of the other Eclipse views often causes the cursor in the editor view to get reset to the top of the first buffer in the list

This I've not seen before...have you noticed is it always a certain view that causes this behavior?

It doesn't happen all the time and, it seems, not with every view.  I just ran a quick test.  I expanded a project in the Package Explorer view by clicking the '+' until the java source files were listed, and then opened a file "FileA.java".  Paged down a few pages and then used push_bookmark() to navigate to a symbol in another file, "FileB.java".  Then I expanded the '+' on another project in the Package Explorer view and the editor cursor popped to the top of the file (line 1, col 1) in FileA.java.  I normally keep the Package Explorer view minimized to maximize the editor view real estate, and I've had the same thing happen when I restore the P.E. view to look at another project.

In a second test I repeated the FileA and FileB open/navigation, and then restored the Outline view on the right side (I keep it minimized as well).  This had no effect on the editor view.  But when I went over to the P.E. view and expanded another project, the editor view changed as described above.  Other actions in the P.E. view (like minimizing or restoring) also have the same effect, but not always.  So it seems that the P.E. view is the main culprit, but I think I've seen it happen when clicking in other views, though not sure.

[Ryan]

reset line modify markers in the left margin doesn't work

Thanks for the report on this one...I assume you are talking about the Save option?  This looks like it's being ignored in the plug-in, I'll file a defect and get it fixed in a future release if I can't hotfix it.  In the meantime, if you would like to bind this function to a key it will do the job for you on demand:...

This has been fixed in 3.4...but is not in the beta.

- Ryan