I am determined to 'just finish this' build and get it into 100% testing and polishing faze. It has taken longer than I thought, with a couple roadblocks that have been highly frustrating. Still, I'm nearly there -- and will be releasing the next beta build very soon. If this next build isn't a release candidate, the following one will be (I hope).
Sunday, 19 September 2010
Wednesday, 15 September 2010
I am about to get to the final cosmetic changes, but v3.99.24 continues a trend of improving the licensing and protection systems on Process Lasso. Version 4 is an important release, as I've stated many times, and I'm going to great lengths to ensure that it is done right.
These things remain before v4 release candidate 1:
These things remain before v4 release candidate 1:
- New graph of memory load
- Graph tooltips over ProBalance events
- About 50 little things
So, we aren't far... I *intend* to have rc1 released this week. I am so tired of being in beta (as is everyone I'm sure).
Sunday, 12 September 2010
Version v3.99.20 beta is now available. This version includes the revamped system tray notification balloons, which I've further improved since my last posting. To show off the new capability, I've changed the default 'Show balloons' setting to TRUE for non-server editions of Process Lasso. I also renamed the pertinent configuration file setting.
This build also makes some good improvements to the process context menu. I personally thinks it puts the commonly used stuff where they are easy to find, and moves the less commonly used stuff off into submenus. Maybe after the 10th try I've nearly got it organized optimally ;).
I expect two more builds and there will be a release candidate. The graph tooltips will appear in the next build, for those who wonder. At least, that is plan now. They will come before final, no doubt about that - That is why I've been working so hard rewriting so much of the core of the software.
Some semi-large cosmetic improvements are also coming, and they may surprise you. It will really give you that new version 'feel'.
One thing is certain, with a change log this long nobody can say version 4 isn't a major upgrade, lol.
This build also makes some good improvements to the process context menu. I personally thinks it puts the commonly used stuff where they are easy to find, and moves the less commonly used stuff off into submenus. Maybe after the 10th try I've nearly got it organized optimally ;).
I expect two more builds and there will be a release candidate. The graph tooltips will appear in the next build, for those who wonder. At least, that is plan now. They will come before final, no doubt about that - That is why I've been working so hard rewriting so much of the core of the software.
Some semi-large cosmetic improvements are also coming, and they may surprise you. It will really give you that new version 'feel'.
One thing is certain, with a change log this long nobody can say version 4 isn't a major upgrade, lol.
Friday, 10 September 2010
I've finished and extended the new system tray balloon tooltips in the as yet unreleased v3.99.20 beta. You'll see merged notifications, such as:
I've also added notifications for every type of event possible, and they are broadcast better (the new inter-process communication framework). Merging similar events that occur about the same time allows for much clearer representation of what is going on, and gives the user a chance to read them during 'rapid fire' ;). Even better, this is offloaded to another worker thread. Process Lasso is growing in threads every day it seems, lol. Fortunately, I've also improved the efficiency of the thread synchronization objects - so the overhead is lower than ever before.
I'm going to add more things to v3.99.20 before release, and do some testing -- but it is coming. After this, there will only be a couple more additions to make, then we'll just need to finish testing.
I've also added notifications for every type of event possible, and they are broadcast better (the new inter-process communication framework). Merging similar events that occur about the same time allows for much clearer representation of what is going on, and gives the user a chance to read them during 'rapid fire' ;). Even better, this is offloaded to another worker thread. Process Lasso is growing in threads every day it seems, lol. Fortunately, I've also improved the efficiency of the thread synchronization objects - so the overhead is lower than ever before.
I'm going to add more things to v3.99.20 before release, and do some testing -- but it is coming. After this, there will only be a couple more additions to make, then we'll just need to finish testing.
Thursday, 9 September 2010
v3.99.19 beta is released. All inter-process communication has now been consolidated into the new mechanism. The system tray balloon tips (off by default) have been rewritten and revamped. Much work remains, but we're getting there. An array of other improvements and beta2beta fixes were made as well.
Version 4 is my top priority until it is released. I will continue to work as hard as I can until it is finally ready.
Version 4 is my top priority until it is released. I will continue to work as hard as I can until it is finally ready.
Sunday, 5 September 2010
I hit a 'block' last night, perhaps it was due to malnutrition, perhaps overwork, or perhaps stupidity. Nevertheless, it took about 5 minutes to fix the problem today when I took a fresh look.
v3.99.18 is being released. The most prominent change is something you won't see or notice -- that improved inter-process communication I've mentioned. Process Lasso will now function much better in more complicated multi-user environments and in cases where the Governor is running as a service. Yea, most companies wouldn't bother, and probably have released v4 weeks ago to maximize profits (ready or not). For me it's personal though, I want things right -- and I want to finish what I've promised. I'm about 95% there.
I do still have to finish integrating the old code with this new code. The systray balloon tooltips, for instance, will use this method, instead of their older method. This will greatly improve performance, particularly in high loads, and particularly on multi-threaded systems. Yes, you read right.... Process Lasso is becoming increasingly multi-threaded. It always has been, but now it is more than ever. I'm offloading work to threads left and right (while not going overboard). On multi-core systems, this will be a great advantage.
v3.99.18 is being released. The most prominent change is something you won't see or notice -- that improved inter-process communication I've mentioned. Process Lasso will now function much better in more complicated multi-user environments and in cases where the Governor is running as a service. Yea, most companies wouldn't bother, and probably have released v4 weeks ago to maximize profits (ready or not). For me it's personal though, I want things right -- and I want to finish what I've promised. I'm about 95% there.
I do still have to finish integrating the old code with this new code. The systray balloon tooltips, for instance, will use this method, instead of their older method. This will greatly improve performance, particularly in high loads, and particularly on multi-threaded systems. Yes, you read right.... Process Lasso is becoming increasingly multi-threaded. It always has been, but now it is more than ever. I'm offloading work to threads left and right (while not going overboard). On multi-core systems, this will be a great advantage.
Saturday, 4 September 2010
Under development is a rewrite of the inter-process communication between the core engine and instances of the GUI in its entirety. This will allow improved handling of cases where there is a single instance of the core engine and multiple instances of the GUI. Further, it will improve efficiency of the governor and GUI, and create a robust framework for future additions.
The first thing the new framework will be used for is tooltips for highlighted portions of the graph. Sure, I could have done this all the 'simple' way, but I figured I'd go ahead and create a robust and efficient framework to allow for easy expansion later. It might be that this code is useful for other projects as well, who knows.
The first thing the new framework will be used for is tooltips for highlighted portions of the graph. Sure, I could have done this all the 'simple' way, but I figured I'd go ahead and create a robust and efficient framework to allow for easy expansion later. It might be that this code is useful for other projects as well, who knows.
Subscribe to:
Posts (Atom)