Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[18.0] web_responsive and main page apps #2984

Open
bealdav opened this issue Nov 8, 2024 · 1 comment
Open

[18.0] web_responsive and main page apps #2984

bealdav opened this issue Nov 8, 2024 · 1 comment

Comments

@bealdav
Copy link
Member

bealdav commented Nov 8, 2024

Thanks for your fantastic work on responsive module

Just a question.

main page app

image

community drop down app list

image

Describe the solution you'd like
Related to the migration of web_responsive in 18.0.
This module is complex to migrate because of many features.

When a new version arrives it could be good to have a main app page earlier in the migration process to demonstrate to new customers that community version is nice.

Then is it possible to extract the main page app with nice icons from web_responsive module, because you may want to have only this main page apps. Months later you might want responsive features without this main page app with only community drop down app according to your choice.

The drop down is fine to directly select your menu in a productive way, while the main page let your eyes spread anywhere on the page to find the right app.
Having the choices is good.

I probably forgot contributors here, please alert them

cc @yajo @legalsylvain @etobella @Tardo @angelmoya @chienandalu @SplashS

@legalsylvain
Copy link
Contributor

legalsylvain commented Nov 8, 2024

Hi. context : I never worked on web_responsive and I have limited skills in Javascript / CSS.

In fact, I don't understand in which case we want the community drop down list.

  • I see it very poor
  • there is no possibility to search, so it requires more click
  • I don't see it very beautiful. (matter of taste on that topic).
  • maintain 2 (or more) modules is more work in each migration.

So I'm in favor to keep this module as it.

Basically this module takes part of the "must have" modules and tools that should be migrated each year by the OCA. I prefer to work on the topic of how the OCA sustains financialy that work (cf talk in the OCA days).

My two cents.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants