I have seen that the Wappler team is working on a redesign of the graphical interface in many areas and it occurred to me to see that the front end part has not received some love for a long time, so I bring some ideas to the table that may be of interest. I don’t really have much time these days s…

1 and 3 would be good additions. [image] Max_Saravia: Perhaps the most profound change in my proposal is to separate what are items that correspond to data, components, framework and personally I would also add variables, in this way I think we can order better and when editing we can access mo…

[image] Max_Saravia: The first thing I thought was important to add was a search field This would certainly be very useful. I think it could work in two ways. It would be very useful if the search term would highlight the matching component(s) in the tree, and refine the filtering as more is…

[image] JonL: On the other side, instead of separating and removing them from the tree I would suggest adding them as a direct link that takes the user to the specific node. Full solidarity with this. Sometimes the element tree grows so large that referencing certain elements might solve the …

As for the search bar, I personally would prefer a tree element filter. It works very simply and clearly: select the modal window in the filter and only the modal windows remain. We select the forms and only the forms remain. Personally, I think it would work much better than search. Faster, more re…

+1 for a search tool. May not be a popular suggestion but I’d love to see the Dynamic & static events/attributes perhaps as tabs at the top of the properties window rather than hidden as a expand/close list near the bottom. I loath having to scroll down every time to reach those.

I already do something similar to that by simply using sections and giving them an id. [Screen Shot 2021-06-07 at 9.03.21 AM]

I used to do that too, but then I refused. This is bad practice, I think. The “Section” element is a full-fledged html tag, with all the ensuing consequences - it gets into the DOM and also into the route path to the nested elements when the binding is done. This question was also raised quite a lo…

[image] Moving Element in App Structure and DOM Also Move Comment Above Feature Request Let me expand on the request. An alternative could be. For App Connect components add a comment field in the properties of it. So people can add the html comment they want. Then you c…

Some ideas for the front-end app structure panel

Feature Request

JonL June 7, 2021, 4:59pm 9