Experience has shown at once corebase starts to reach 4000 lines of code, it becomes too large to maintain locally, and version control system is required. This becomes even further important when doing cross-platform development, which involves copying codebase around different systems. Thus, I checked in the current GUI codebase to svn yesterday; not because it's ready for public testing, but because it's easier for me to maintain it that way. Nonetheless, if you're feeling adventorous, you can check out the codebase and compile it yourself. Or you could just browse it.

Today I also made the first full bundle of Hydranode and submitted to the testing team. The final rar package turned out to be roughly 6 MB of size, but it will decrease slightly, since in this package, the engine was compiled with mingw (~50% larger binaries on average). That version runs Hydranode as child process, eliminating the console window completely. Also, I introduced the top-right-corner statistics panel, as discussed before; no screenshot yet though, since it's merely for testing purposes only, and doesn't look too pretty.

Overall, we seem to be on schedule, with less than two weeks left before public testing, and most functionality is in place. Main focus over the next weeks will be improving the existing functionality, such as getting the RSS support user-customizable, adding progress graphs, re-doing graphics and so on. As I mentioned in a comment of previous post, the icons/graphics are in their first incarnation, and those that have followed this project longer know that no component stays in it's first version - nearly all important components of Hydranode have been rewritten at least once, since you don't truly understand the problem until the first time you implement a solution; on the second time, you can hope to get it right.

Madcat.