Classic Menu vs Icon Menu Selection

Are the component menus used in Wappler an element of Bootstrap 4 or are they programmed separately and specifically for the app? The reason I’m asking is that I find the classic text menu structuring used in the DMX tutorial videos far more intuitive and less confusing than the relational popup menus (displaying component icons rather than text) used in Wappler.

Soooo… could a future version of Wappler app eventually include a user-select choice of menu style (like Dreamweaver’s Classic, Coder, App Developer, etc.) to accommodate personal preferences?

I prefer this menu structure:

I find this structure unintuitive and confusing:

Just an observation and personal preference for the wish list.

1 Like

I agree. I am very happy with wappler so far but the menu really annoys me a bit. It is very counterproductive.

So here are a few suggestions from my side:

  1. Automatic filtering by typing without having to click in the search field
  2. Back button. Not only home as it is now. Navigating through folders would be much faster and easier that way.
  3. Integrate general commands such as copy, rename or delete. Right now, the item has to be selected in the app structure and then you have to move all the way to the top for the sought action. If you think that one step further: It would be really awesome to be able to select multiple items in the app structure.

In the end it is all about how much clicking and mouse-moving is involved.

Nonetheless a great job has been done so far and I really appreciate it, that there is a possibility for the end user to bring in suggestions.


We were already looking on how to improve the insert elements menu so you ideas are very welcome.

I will be posting soon some screenshots of possible layout improvements as well.

The idea is to have like a main category vertical sidebar on the left of the menu and items on the right so it will be more stronger categorized and clear.


This would eliminate the need for a complicated navigation including home or back button. Hovering over the main categories for switching between them is also a possibility.
Only problem would be sub-folders as far as I understand.

1 Like

Well I think we should avoid sub-folders - just try to define as much as possible in like 7 main categories.

a bit like:

Ideally for with more larger preview for the more complicated components, maybe in a tooltip

Well feel free to contribute a mockup if you have more ideas on the optimal design :slight_smile:

I will move this post to “request for comments” category as on going discussion

I agree! One level is enough to categorize all items without complicating the navigation.

1 Like

The old DMX way would be so much better… my 2 cents

1 Like

Autocomplete for css in code mode is very essential.

This is what I had in mind when @George said vertical sidebar with items.
Like I already mentioned, it would be great to just hover over the categories to switch. Also automatic search focus as soon as I hit a key.
What makes me a headache is the bottom area with the additional options. I’m not satisfied with that there has to be a better way. But it would be great to implement all options at all time. No matter if I navigate through server actions or in the app structure, all options which are provided in the top bar right now should be accessible through the context menu. Along with the multiple selection option as I also mentioned before.


Hey @jowhiskey - can you read minds or so ? :slight_smile:

This is exactly what I had in mind :slight_smile:

Only i’m thinking in 7 more general categories, something like:

  • Children - special shortcut category, for smart direct children elements
  • Layout & Grid
  • Text / typography
  • Navigation
  • Status
  • Media
  • Forms
  • Components
1 Like

I like the idea of the smart category!
My mockup represents server actions. They are already pretty well categorized imo.

Indeed the categories I meant are for the client side only.

Server Actions are already pretty well categories, but exactly as you redesigned them above - will be way much more accessible, and clear

What came to my mind, is to shrink the search bar to the right. This way different buttons can be positioned on the top left. Like insert after/before and copy, delete etc…
For searching, only up to 5 letters will be used anyway. By then, the right item is already highlighted.

This is my second attempt to integrate general commands in the context menu. This time with the app structure.
I’m still not 100% satisfied with my mockup but I hope my idea has some use to the wappler devs. I don’t know what others exactly would like to see in the new context menu but as far as I’m concerned, it has to reduce the amount of clicks and the distance for the mouse to travel, to achieve commands in a shorter time.

Your mackuos are definitely of great use!

Some comments:

  • The categories in the left should be 1 line height, maybe prefixed with icons
  • the actions (copy/paste/delete) has always being in logical to this dialog as they concern the elements selected below in design view and not what you see in the dialog… so maybe we should remove them all together from the insert dialog and provide other means for them directly on the underlinening ui
  • the insert position (arrows top right) are also a bit weird and people don’t get them at first. So we need to find more logical place for them too
1 Like
  1. By line height you mean the hight of the actual icons? I like that, it would make the menu a little sleeker. So a maximum of 8 rows could be displayed on the right side.

  2. I get what you mean, app structure has different options than server actions which again have different options than the action steps them self. And then there is the file manager which already has a normal menu integrated. I could think of some sort of keyboard shortcuts as appropriate replacement.

  3. Hm it has to be some kind of toggle since the menu is context sensitive.