Matthew Ballance

I've added a basic 'index.html' just to avoid Github reporting the 400 error. Please also confirm that you're able to install from the update site (ie add https://sveditor.github.io/update as an update site from which to install software). Thanks, Matthew

Ah, yes, Bintray removed support for hosting Eclipse update sites. Unfortunately, that was where SVEditor's site was hosted. I've been working on a migration to hosting the update site on GitHub. The new update site will be: https://sveditor.github.io/update/. Perhaps you could try this out to confirm it works for you? Thanks for raising this issue! -Matthew

Hello, I believe Mars should work, and you should be able to use the most-recent SVEditor, but you may need to install Gef3 in order for it to work. Are you able to confirm whether the org.eclipse.draw2d.feature.group feature is installed in your Eclipse installation? I believe Mars may include some aspects of Gef built-in (ie other feature groups), but not all. Best Regards, Matthew On Thu, Oct 29, 2020 at 6:30 PM BigKuma bigkuma@users.sourceforge.net wrote: I am working in a very restrictive environment....

Hi Felix, There's not exactly a way to ignore this error in SVEditor. At the moment, probably the best way to accomplish this would be to place ifndef SVEDITOR /endif around the `uselib directive. I'm not sure if you could do that in your code, but it is an option. I will also look into recognizing this directive in SVEditor directly. Thanks for your feedback! Best Regards, Matthew On Wed, Jan 29, 2020 at 10:16 AM Felix Dube fdube@users.sourceforge.net wrote: Hi Matthew, When I use the uselib compiler...

Hello Brandon, Great to hear that you're looking to use the parser API again! Okay, sounds like you're trying to use both Xtext and SVEditor in a headless non-Eclipse configuration. There certainly are some complexities running the parser standalone (outside Eclipse). One thing you might try is the SVEditorVlogIndexFactory.vlog_loc method (the class is in the net.sf.sveditor.core.batch package). This method the same set of arguments you would pass in an argument file (eg -f, +incdir+, source files,...

Hi Felix, That's a good point. Documentation generation via the GUI has always been package-centric. I believe it should be possible, but I'll have to dig into the code. For your purposes, would enabling doc-generation for all modules be sufficient, or do you have a reason to filter out certain modules/interfaces? Thanks, Matthew On Wed, Dec 4, 2019 at 6:48 AM Felix Dube fdube@users.sourceforge.net wrote: First of all, thanks Mathew for you hard work!! I would like to know if it is possible to document...

Hi Jonathan, Unfortunately, Eclipse doesn't make it easy (possible?) to coordinate activity like this across multiple editor instances. Especially when it comes to cursor location, which what drives the brace-highlighting code, each editor maintains its own notion. Sorry to not have better news... Best Regards, Matthew

Hi Andi, One thing you can do now is to disable project auto-build (Project->Build Automatically). The SVEditor indexer is driven off the Eclipse automatic project builder, so this will stop the SVEditor indexing messages, as well as all other auto building. What can you tell me about the SVN messages? Are these shown in the same console that the SVEditor indexing messages are? Thanks, Matthew