Since 2011, the forums have been read-only since there was not much activity except for spammers. I am cleaning up all unnecessary old software after this site was compromised via a PHP exploit in the past few days. As the domain has been read only for 10 years, I have decided to shut down forums.gillius.org.
I developed a Pointing Poker backend and frontend web application (GitHub Page) that works well enough for an internal team to use. It requires nodejs on the backend. The front end was built with React.
I built it because I was frustrated with the performance and reliability of public servers, and because I wanted to learn more how to use React beyond a trivial tutorial. It's based on websockets, and all data is immediately replicated between all clients. There's no code to reconnect if the websocket fails or if websockets don't work, but it's worked without a single flaw within an internal network, which is how I've used it.
Thanks to Mischa Berlin for a submission allowing random name generation!
Read on for more details on the implementation.
I made a project ("lunchbus") to play with Spring Boot + websockets + AngularJS 1.5 + Groovy + Redis. This may be interesting to those who are interested to see how these are set up. The project also has the configuration to run on Heroku.
The lunchbus app keeps track of who owes lunches and to whom, a list of people and places that can be selected, a button to randomly select a place, a chat functionality, and a demonstration of high-speed log output from backend. Persistence is provided by Redis. Due to how it uses Redis, it's just almost ready for horizontal scaling with multiple servers, for that time that you have over 100,000 people going to lunch with you. All that's needed for that is to integrate Spring Boot to Redis pubsub.
My goal is to learn Spring Boot and websockets primarily, and also to see what does an application relying solely on websockets look like and its strengths/weaknesses.
The jalleg binding for Allegro covers essentially the entire library now, with all of the major parts tested. It is at the point I believe it is good enough to start using. Any feedback is appreciated, and if no issues arise, I will probably make a 0.1 release, although the binding itself is more like "1.0 beta". The library has been tested on both Windows and Linux (Ubuntu) at this point. I've also set up a wiki page on getting started in Windows and Linux.
There are a few examples but the default one that runs is a ball and paddle game using a handful of Allegro features:
jalleg is a JVM binding for Allegro 5.2 to be used by any JVM language (Java obviously, but also other languages such as Groovy, Kotlin, JavaScript, Scala, Jython, JRuby, and Clojure).
I've just put up a new repository for those interested in following the progress. Currently I have a working but not fully tested JNA-based binding auto-generated by JNAerator.
Allegro was a library I originally worked with a lot when I was learning C/C++ development in DOS in the late 1990s, and has always had a special meaning to me. Allegro 5 is a modern, cross-platform variation of the library supporting hardware rendering and even mobile development. Allegro is a simple library to use and programming a game is a great way to get into learning programming. My hope is that jalleg expands the Allegro fun to Java and all the JVM languages.
Version 1.0 of JFXUtils is released now.
JFXUtils is now available on Maven Central, so no custom repository settings are needed! The maven coordinates for this release are org.gillius:jfxutils:1.0.
A special thanks goes to gforman44, who contributed a lot of code and ideas for this release and encouraged me to finish to 1.0. Also thanks go to Daniel Weil for bug fixes.
You can find more information at the GitHub Project Page.
Continue reading for the full list of changes.
I have a problem with Thunderbird. For some reason when I try to move a few thousand e-mails, in the destination folder the majority of messages get duplicates. Some could get 2 duplicates. I have no idea why. But I created https://github.com/gillius/imap-dupe-delete to clean up the mess. I built it for my own use and used it only on my own account. But it might be useful to others in the same situation or as an example of JavaMail usage from Groovy (as that is the language I used). I also used the GMavenPlus plugin to build from Maven. If you have Java and Maven it will be easy to run.
Version 0.3 of JFXUtils is released now, with only two real changes:
You can get it at the GitHub project page, or directly from the Gillius.org Maven Repository. You can also view documentation online.
I released version 0.2 of the JFXUtils project I started recently, and now there is code for chart panning, and zooms are now animated. With panning and zooming working, I noticed that the default NumberAxis was not working at all how I would like. The tick positions remain in the same place no matter what the graph's bounds, and the values of the ticks then change to reflect the value. Well, with zooming and panning you will get for example a lower bound of "1432.34234", and this is exactly what NumberAxis will display. So, I created a replacement axis type called StableTicksAxis that keeps the ticks at the same data location for the given zoom level, which has a drastically better UI feel when the graph is changing rapidly during panning and zooming operations. It automatically computes the number and distance between tick marks based on the size of the graph, the graph label font, and the range of data displayed to maximize the number of tick marks without having the labels run into each other. When auto-ranging, it can force zero in the view like NumberAxis, and also like NumberAxis it can add some padding around the data, but unlike NumberAxis the amount of padding (as a percentage of graph size) is configurable.
I wrapped up some of the JavaFX code I've been working with into a library org.gillius:jfxutils, which is hosted at github (project page). The artifact is also published in my Maven repository. It offers the following now:
I plan on adding panning compatibility in a future release.