Merge App Structure and DOM views

Feature Request
#21

@Teodor, this is a feature request…

I’m sure you can see the reason why I asked that question…

para is also a html element, and it’s still available as a bootstrap component…

I’m very surprised why you shut people up so quickly (not everyone of course) when we are trying to give constructive feedback… and trying to involve in healthy discussion…

I don’t really see this happening in other forums where there is a great amount of professionalism…

It’s quite painful to pay my subscription every month when I have been struggling with a bug-filled product… it doesn’t matter you release a hundred new features, if we can’t use the basics on a day-today basis, then what’s the point…

#22

that’s quite new to us - the “Bug filled” part of your message. Looking at the showcases we receive almost weekly i was not aware that the product is bug filled.
If there are bugs we are fixing them in our weekly updates as quickly as possible :slight_smile:

1 Like
#23

I get it, i’m not here to argue with you… but you have to understand there are lot of things getting broken every release… I have rolled-back multiple times in the past 6 months…

There are still many outstanding… fundamental ones getting fixes after more than a month or two delay… You have no idea how much time and effort gets wasted and it’s really painful to see my $ going out every month… Especially variables were broken for a long time, and I have raised multiple bugs on it… It takes a lot of effort for me to identify, isolate and report a bug clearly and get to live with it and get things moving…

Wappler is amazing product, but we need to be appreciative of each other… you can take this feedback either positively or otherwise, but clearly this community expects more professionalism from the main staff like you… not the first time this has been flagged in this forum…

FYI, here are some i have raised that are still outstanding…

Only 6 months old…

https://community.wappler.io/t/nested-repeat-region-data-binding-issue-in-the-2nd-level/15709

Only 4 months old…

https://community.wappler.io/t/api-action-component-json-data-not-taking-dynamic-data/18605

One month old ones…

https://community.wappler.io/t/flows-global-variable-issue/20175
https://community.wappler.io/t/inline-flow-runjs-data-binding-closing-single-quote-issues/20174
https://community.wappler.io/t/api-schema-editor-issue/20603
1 Like
#24

Back on the topic I must say that I rarely use any more the App Connect or DOM panel. I was losing too much focus moving from to another.

So basically I just use code view and select elements in the code which will render the AC properties or the html properties.

Maybe we are a just a minority that relies on switching from AC to DOM.

But the fact that I browse the code and don’t use AC or DOM tree just proves how I unproductive I am when using AC and DOM trees.

Therefore this FR to merge both and add filters to select what type of nodes are shown. Just AC, just html or both.

2 Likes
#25

I totally agree with you @JonL!

For several (paid and free) BS themes and UI kits I tried, the templates always contain div and span elements which can be identified in code view or DOM panel of course, but don’t appear in the AC components tree.

A lot of switching from code view or DOM panel to AC is required to use and populate these templates and convert html elements to components that can be recognized and managed by AC, which makes using external custom themes very inefficient. As you mentioned here using external themes will never be a plug&play thing, but a single view tree with node filters would definitely make this a lot easier. You got my vote :smiley:

1 Like