Better performance on startup

The startup performance is now better due to the classpath scanner now using up to 4 CPU cores, up from 1.

Java 11 Compatibility and several build issues fixed

1.0.0-beta6

Upgrade Gradle wrapper, add Java 11 compatibility

New help mechanism, new webpages, new beta

The title says it all.

The old Help mechanism was a bit old, so I created a new one using the JavaFX WebView. It's a lot better now.

Other than that, this beta will now check things in the correct URLs for the new repository/web pages.

Beta 4 and now we use Lombok

Lombok is quite cool to make classes less bloated and still provide the kind of isolation having Getter/Setter methods provide instead of publicly accessible properties.

Plus, equals and hashCode methods get to have stable, surely correct implementations.

Minor fixes, better performance, new icons and restored docs

Some dependency updates granted better performance during some initial tasks. Plus, I reduced the number of string replacements used to resolve project classes.

I've redone the icons. The reason is that my icon was actually an improvised attempt to do something like the old-old-old-icon but with a better resolution. This one was constructed from the actual logo, using SVG. It doesn't "look better" but it's more accurate.

Great news for those who need the old documentation! Since Sinalgo's website was removed, the online tutorials were lost -- or so did I think. Using the Web Archive I managed to restore them and, some meddling with the HTML and CSS files later, they've been mostly restored to their former glory. They're in the docs folder and can be accessed as GitHub Pages at https://andrebrait.github.io/sinalgo/.

Dependency updates and small version bump

FastClasspathScanner was updated from version 2.18.2 to 2.19.0, and now Sinalgo will consider 1.0.0-beta2 as a possible upgrade from a previous version.

I'm keeping this at beta but this should be production ready, in fact.

Version 1.0 because we now have freedom!

So, Sinalgo had two big issues:

1. A debugger would not attach to the actual simulation process and that was bad - very bad.
2. Sinalgo resorted to scanning the actual file system (including the source code folder) for model and node implementations. This led to some not-so-cool effects such as depending on having the source code there at all times, in very well defined folders, etc. and actual class loading would be done by loading the class files from the file system.

This made developing a simulation on Sinalgo somewhat difficult. These were solved by:

1. Sinalgo's simulation process is now launched with the same debug flags as used by the main process, with a random port selected. You still need to attach the debugger manually but it's pretty easy to do so in IDEs such as IntelliJ or Eclipse.
2. Using FastClasspathScanner Sinalgo now has the ability to scan the ClassPath without loading classes, just like it would do before by reading the .class files from the file system. But this has some advantages. First, we don't need to be in a file system. Sinalgo can now be distributed in jar files. And you can also add jar files to the ClassPath and, provided the packages match, it will load the projects from it too! This frees us from the file system and that's pretty cool!

As an extra, Sinalgo now doesn't crash when you change the resolution of a monitor while on Windows. This was caused by a very nasty bug in AWT but it's being ignored by our exception handler. Because it doesn't actually have any bad effects.

Ps.: This is feature-complete but I'm releasing it as a beta because it needs a bit of testing.

New version checking mechanism and custom configs work!

In this release, I fixed lots of things in the exception handling mechanism, now custom configs work and now Sinalgo will check if you have the latest version against this repository. Hurray!

Well, that's it, basically. Still some lots of improvements need to be done, but it's working very well for now.

Important fixes and Java 8

Well, basically, I broke the application after moving it to Gradle. This fixes most of the issues.

Plus, I fixed a lot of small issues and ported many things to Java 8. So Java 8 is now a requirement to run Sinalgo.

Sinalgo now uses Gradle!

When I started using Sinalgo, I knew it was a bit old. Not the developer's fault. For the time they developed Sinalgo, I must say they came up with some pretty clever ways to make it work.

That being said, it's 2018 and while modifying Sinalgo to make it more modern will take some time, a change to the build system was overdue.

Using Gradle is one of the most pleasant experiences I've had as far as build systems go and so I decided to take a shot at porting Sinalgo to it. And it worked! After running into some problems, I mean.

Well, that's it. Everything seems to be running just fine, except for a little Perl script in sample 1. All I need is to adapt the commands it's issuing so it should be a breeze to fix — but I don't have the time for that now.