Thought might be nice to carry on the discussion here. As a sort of post Meetup warm down...
Quite a few very valid points bought up:
Concern for backward compatibility in Wappler 8
Support for Wappler 7 during the Wappler 8 rollout
Wappler 7 Bug fixes timeline
Significant changes planned for Wappler 8
Planned UI Updates and changes in Wappler 8
Planned Framework support outside of Bootstrap in Wappler 8
Great presentation by @Hyperbytes on his PayPal Extension! So if you missed it be sure to look out for the YouTube video which will no doubt be available very soon on the Wappler official YouTube Channel. Bridging the gap between the complexity of Stripe implementation and PayPal payment facilitation. No rocket science degree required. Straight forward PayPal payments in one Extension with server side validation.
I've made it my personal mission not to miss another one, I've totally rescheduled my usual Friday workflow to try and accommodate this - I think its important for cohesion amongst our peers.
@Hyperbytes You did well today, its always a pleasure to hear your dulcet tones, and benefit from your wisdom - you've got a great talent for this type of presentation. Oh, nice extension too - I think that will grow legs and end up to be an important tool for a lot of people, your work on this is appreciated.
@Cheese - great idea making this post, gives a decent chance to discuss anything missed in the meeting.
As for V8? For me personally, backwards compatibility is always top of my mind. The stuff I normally work on tends to be on the more complex side of things, so when updates happen its always a worry if something major is going to break. Having a major version change results in a huge amount of work testing out existing systems across many domains so its a big deal.
I'm sure Team Wappler are on top of this so that does inspire a bit of confidence moving forward.
Anyway, it was great to see you all today, I'll sign off now as its nearly wine-o-clock...
We will keep background compatibility as much as possible. On the Frameworks side App Connect and Server Connect sites will just keep on running.
We plan even to superate core extensions even more and offer them as separate extensions with full semver version control and npm publishing with dependencies so you can lock your extensions versions to your project and stay on the same source even if Wapper updates more and new versions come by.
Yes we will be keeping Wappler 7 updated during the Wappler 8 beta, updates will come just not that often and with mostly bug fixes
See above
Well we have big plans as explained earlier and will be rebuilding and reorganizing the ui from the ground up to introduce new generator and editing paradigma’s and be future ready.
As said before will be isolating the extensions from the Wappler version so those can be updated separately and are not Wappler version dependent
As said we will be having pretty big ui overhaul but we will try to keep Wappler’s core straights and easy visual editing that you are familiar with but will be also introducing some new paradigms
As we building the ground work, it will be fully extendable and useful for any design and code framework, so it will depend on the demand and popularity what we will be add as supported frameworks
I’m sure everyone appreciates this can be difficult and could perhaps restrict the changes you can make. Wouldn’t it be possible to allow users to run versions 7 and 8 on the same computer, after v8 is released? Of course this could be on the understanding that development and support for v7 would not continue.
It will be possible to run both versions at the same time during the beta, we actually encourage this so beta testing feedback can be done more extensively in comparison with the previous version.
After the release you won’t be able to run both version at least not at the same time.
That would be fine. I have some projects which were developed in earlier versions of Wappler. It’s difficult or impossible to make changes using the current version, so I usually end up editing the code manually.
@TMR While PayPal does not natively deal with discount codes i have added functionality to pass a discount level to the checkout.
In my head, discount code would be passed as $_post variable, i.e. "CODE2026", validated against a database of codes and then the amount passed to the PayPal module.
I have made provision for passing an absolute value i.e. 5.50 or a percentage i.e 5%. The value is passed as string and evaluated accordingly to be applied to the entire basket .
Also added some additional custom fields as requested.
