Looks interesting. Have you got an ETA for the vuMailKit?
Thanks
Rohan
Hi Rohan,
It is getting closer every day, and honestly I need it too.
At first, the plan was to build a Clarion wrapper DLL so existing vuMail calls would stay compatible, with the wrapper translating those calls into the new engine under the hood. But the farther we got, the more it made sense to take the long-term route: write the new code using the exact same names, parameters, data types, and return values as vuMail, then add the new features and behind-the-scenes support on top of that. The goal is drop-in compatibility wherever possible.
The other big time sink has been security. We needed a solid way to store OAuth tokens and related security data securely, and also provide a clean migration path so developers do not have to rely on the old vuMail Registry storage, since that approach is not secure.
On top of that, we have been rebuilding the documentation in our ProHelp Studio format so we can publish it online the same way we did with vuFileTools, ProPath, and the rest.
If all goes to plan, I am hoping to wrap the basic version within the next week or so.
After that, the Pro version will follow with IMAP support and a reusable mail client component you can integrate and resell.
Then comes the Back Office Edition. That one adds the heavier-duty mail service features like throttling (mails per hour), retry rules, logging controls, and the backend tools for handling bounces, unsubscribes, and related tracking. It is the kind of thing that saves you from having to roll your own full mailout system.
I am really looking forward to using it myself.
Hi Charles
The IMAP component sounds very interesting. Also, any ETA on ProHelp Studio?
Cheers
Rohan
Hi Rohan,
IMAP should be a really useful component. A lot of people depend on IMAP for syncing and server-side folders, and we want vuMailKit to cover the real-world setups people actually have.
One nice side effect of rebuilding vuMailKit from the ground up using the current Microsoft-recommended components is that it let us design a complete mail ecosystem end to end, instead of patching around older assumptions. That gives us room to do things the right way, especially around modern authentication and secure credential storage.
ProHelp Studio is coming along nicely too. Right now the docs we have done so far are running on an internal proof-of-concept version, and we are actively building out the commercial version.
As with several of our current projects it is actually not built in Clarion because we wanted to be able to deploy it in non-Windows OS environments.
In the spirit of âbuild once and reuse oftenâ, we are also working on a layered core that lets us create and manage stacks of pages, including metadata. That core will feed several projects on our side, and ProHelp Studio is one of the main ones.
ETA-wise, I am aiming for next month, assuming everything keeps tracking the way it is now.
Charles