Yes and No.
My priorities are in this order: schedule, stability, and a smooth transition.
In order to achieve the top priority of getting something out and in your hands as soon as possible, it means making as few changes as possible, and keepin the app to the most essential features.
My goal is to be able to cover 80% of the projects of 80% of the users.
So the first version will be all about keeping things the same. The Stacks core will be 99% the same. Where I might make a few tweaks in the UI is to make the Stacks library a more integral part of the app overall.
Outside of the Stacks core, the app will be quite different – but hopefully similar enough and recognizable enough, that I can meet that “smooth transition” goal.
But I want to make sure I set expectations correctly: the first versions will be stable and functional, but there will be no new features beyond what’s absolutely necessary.
New features take months to build and months to tests – I’d much rather have something in your hands – even if very limited – than nothing in your hands. There will be a lot of skeptics – native Mac apps aren’t often built in 6 months by a single engineer – they usually take several engineer-years.
The best way for me to show that Stacks is more than vaporware is to ship it!
That said, once this version is out an in your hands, I don’t intend to let up, we’ll try to follow as quickly as possible to fill in the gaps and begin adding new features.
Have you been limited by RW in the past as to what the Stacks UI could do?
Oh man. I don’t think this forum can really convey the magnitude here…
By in large the Realmac devs and I worked well together over the many years to bring new features for both the app and all the plug-ins – especially Stacks.
So for times like the big 32-64 bit architecture shift we had to work closely so that 32/64 bit versions could be bundled together in a way to keep the automatic updater simple and straightforward.
This made the transition largely transparent to users – and little more than a couple dialog boxes, even though it was a huge change underneath. This kind of stuff required us to work very closely together to solve the problems as a single team.
But around 2016 or 2017 or so… around the time of the RW 7.1 I guess – things really broke down. It felt to me like Realmac was making impossible demands, changing APIs without warning or deprecation, and became completely deaf to all my requests.
The practical takeaway is that it was almost impossible to get access to things like the resources window, the file-list, or other app-level features.
I’m really really looking forward to Stacks BECOMING the app – not just being INSIDE the app.
This will give things like Foundation and Foundry first-class position to not just add/configure UI inside of Stacks – but allow for the configuration of the UI of the ENTIRE APP.
I’m not at all sure what that means today – I just know that there is SO MUCH that we want to do – and now we can finally begin.