As we are moving to great new developments in Wappler 8, I want to make sure we are on the right track with your wishes as valuable Wappler users.
So tell us which existing Wappler features are most valuable to you and which new features would you like to see?
Thank you! With your help we will make sure the next Wappler suites your needs and wishes fully!
Bug submission through Wappler itself comes to mind. Hahahaha sorry. I've just incorporated a similar thing on one of our platforms. I can't complain about bugs if I'm guilty of the same thing of being caught up with a workload but I have to acknowledge their submission. I've handed this off to an 'agent' to order them by severity, inspect the code-base, smoke test for fixes, then suggest a fix, then I review it... Then I push it. Made my life so much easier! Damn it AI you are turning me in to a lazy... But productive, SOB. I can now be in three places at once!
The biggest thing for me is a replacement for Summernote. lol
For PHP:
Realistically, I know these won't happen but since you asked. These would put it over the top for me. 
Execution of JavaScript within the Design window too! So I can see all aspects of my applications running. This doesn't seem to work in Wappler. Especially with stuff like i18 integrations and third party libraries etc.
Ability to edit files like docker deploy files, middlware.js, index.js, routes.js etc. So I don't keep getting the Updater appearing. I'd like the ability to be able to modify them. Or inject my own variables in to them?
This should be pinned @George?
Would it be possible to internationalize the wappler interface and applications created with wappler 8?
A BIG help and something that would clear up a lot of confusion for many Users would be:
One area for database connections. To test connections and refresh schema's etc. The current implementation is confusing. Globals, Database Manager, Targets. Could really do with some real improvement. Maybe move the database connection out of Targets all together for one... Show production in Red and Development in Green, at least some degree of colour separation so Users know (or call them simply Production and Development) and allow the User to define their database connections beneath each (as all may not have a database for each Target and may be using a single database for example).
I've walked more people through this than anything else.
Not just in the Resource Manager (not everyone uses it). This should be in the Project settings and allow Users to import keys (then select them in a Target for example). Once again another area I've helped dozens of Users with is getting the correct keys to work for their respective Targets etc. Green keys in use, red not in use? Again more colours so people know what is being used. Maybe have a confirmation dialogue if they ever make a mistake in deleting them?
Currently if you close a Target I believe it deletes it? Or it used to (the Team can try that one out hahaha). With no warning. This needs to show a dialogue. Are you sure you want to delete this Target etc.
I'm sure more ideas will come to me but just thought of these. Two of them come up today while in a Zoom meeting with a User who needed help. Their confusion was understandable especially with database connections. I'm quite well seasoned and that still drives me mad!
I miss @Antony at times like this. I hope he is well and good wherever he may be (I did notice his Project was retiring so hope all is OK with him, he put a ton of effort in to Workshop Angel).
That is a great idea! Was thinking of something like this for long time but because of all the old implementations we were never able to do it.
Together with a whole new targets panel maybe we can unify things indeed
That would be great George! Will go a long way to simplifying things for many Users. Including myself. Yesterday helping a fellow Community member resolve some issues with their database we had to go back and fourth clearing things up. In the end I said 'lets just delete them all and start again'... Was like a database connection boxing match.
First thoughts:
From day 1 i have felt that target switching has been problematic when setting up database connections.
Switching target with settings screens open leave old settings visible often causing me to overwrite the target settings.
I think the server connect/ database manager settings need to be integrated into a single settings panel, probably best within the project definition.
Better email template support. The email components have not seen any attention since day one and are a significant weak spot for Wappler users. We need to natively integrate repeats in particular for product orders etc.
A grid control similar to that produced by Roney Dsilva allowing inplace editing of tables linked to the generator component family.