-
-
Notifications
You must be signed in to change notification settings - Fork 582
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
Feature request: Free move style #1525
Comments
Hello Mahmoud Great that you tried v3 on your own, are you a developer ? What's your use case? Thank you for the feedback, i'll think about it and i'll need to read about GrapesJS "free move mode", I know it has one but i'm not sure how it handles responsiveness In silex v2 there is a complex mechanism to allow free move + responsive, but:
In general it is best practice in html to use elements in the flow instead of (absolute) positioned / free move. But i'll read about GrapesJS free move feature to understand if it is feasable In the mean time you can make an element "position: absolute" with the v3 ui, would that be ok for you? You will need to set the top/left values in the properties too, no drag and drop without the real free move feature |
Also you have to know that in the v3 i plan to integrate admins / cms so that non technical users can edit the content without breaking the design This is only possible with elements in the flow as you never know the size of the content in advance, everything has to be in the flow |
This doesn't mean that a free move feature can not be created and optional... Let me think about it 😄 I wonder what is your use case Have a nice day |
Hello,
Have a nice day, Keep working on this nice editor |
I take a look at grapesjs free move mode and it is very buguy for now... I believe @artf would be glad to have some help on that |
Hello
The dev version based on grapesjs is great but the free position and move style is missed
Can you please tell me how to make it free style move like in https://editor.silex.me/
Thank you
The text was updated successfully, but these errors were encountered: