As long as Formloom 4 can be installed alongside version 3 I’m fine with adding new hotness.
This way sites built with v3 won’t be broken and I can update them to v4 manually whenever I want.
I agree that the new version should have all you can throw into it at the cost of backwards compatibility. For those that must have compatibility, they can continue to use the old version. For me, I want all the bells and whistles you can throw at me.
Whatever you do, please make sure you are not pulling any libraries from outside CDNs, please use the built in libraries from stacks or provide all resources within your solution. Looking at the GDPR I would have to state each and every library used in the privacy agreement and - if pulled from outside EU - have a special agreement in place with the CDN to make sure they follow the EU privacy laws…
Add new features to Formloom 4, but allow Formloom 3 to be able to run alongside Formloom 4. I have several very long Formloom 3 forms that I don’t want to re-do, but would use Formloom 4 for new stuff. Alternately, allow Formloom 4 to import Formloom 3 forms (have fun with that -
Indeed … Im will the other geeks … charge ahead with new Foomloom 4 – alongside Formloom 3 would be ideal. I love the idea of usability accross foundation / foundry frameworks if possible.