We have a rough roadmap for what we want to work on with the current QT Software, and about 9 medium sized items out we do have a placeholder for a UI update. What exactly that is I'm not sure yet. The items near the front of the list are more clearly defined. There are a few factors that will affect it too. If we can get the front end QT components contracted out reliably and affordably, we could focus on the logic side and back end of the application. However if we end up building or re-skinning the UI components with our existing limited developer resources, then we'll probably want to keep the UI refresh conservative, so we can get back to adding larger features sooner. We're working with some fantastic QT developers at the moment which has really sped up development.
Now as I see right you have started to add new features to the "old" Qt based Logic, (which I found very cool) rather than pushing out the new HTML5 based one. Would it be possible to reconsider the "any features, such as cosmetics, would be added to our new software " approach for this particular feature too?
Sorry for the trouble with this. We're designing the new architecture with deep extensibility in mind, and API-first, so that contributions like this can be made using public APIs. I really want to bring that extensibility all the way to the UI layer, but we'll see - we're primarily focused on the data processing architecture and the graph display right now, which is still very early on. We're not considering opening the existing code base to third parties though, even under NDA. I'm sorry I don't have a short term solution for this.
Okay, so if I understand correctly you give up adding new features to the current Qt based version, but the new version is still far away. It is okay, I know you are a small company, and focusing is important and I appreciate your work on it.
Would not be there any way to contribute to the old software? For e.g. signing up an NDA with you or open sourcing code partially.
I would rather spend the time spent by placing measurement markers manually with patching the scripting API with this feature for example.
I can't give out estimates for this, because historically, we've always been way off, and I'd hate to set expectations and then fail to meet those expectations. Whether or not current analyzers will support new features is dependent on what migration path we take when we start pulling those into the new system, which is still pretty far ahead of us, unfortunately.
I am very disappointed to hear this.
Do you have any estimation when will the new UI available?
Will the new UI work with the current analyzers?
We are working on the new UI now, so I don't think we will add this in to the next revision of the current software. For the current software, we are mainly focusing on fixing major bugs that get discovered, and keeping it stable.
Otherwise, any features, such as cosmetics, would be added to our new software UI once we make some more progress on it.
Any news on this one?
This feature would make my life much more easier.
I know that you are working on the new UI, but adding this to the Analyzer SDK would be a rather easy thing, and would my (and I think a lot other folks) life easier.
I agree. originally, the analyzer bubble color was set by the channel color, and in the current software, it's all blue. In the future we would like to offer a more comprehensive set of annotation features.
You won't be notified about changes to this idea.