-
Notifications
You must be signed in to change notification settings - Fork 3
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
[CLOSED] Robust object positioning #3
Comments
Comment by wiardjorritsma I made a new version of init_grid to address this issue. Please check if this is a good solution. Then I'll fix the new layout issues it has created :) |
Comment by matrxs Looks good! Only points which might become an issue is that all sizes and such are defined using the
According to here, Other issue is that it is not responsive yet, but that might fall under the new layout issues which you mentioned :) I would also think making the grid screen filling, while keeping the aspect ratio, would be best. However, if that is difficult with css we might also be able to do it with JS. |
Comment by jwaa @wiardjorritsma can this issue be closed? As it has been reviewed and approved, and no branch or merge request is linked to this. |
Comment by wiardjorritsma Yes it can be closed |
Issue by matrxs
Tuesday Jan 14, 2020 at 08:05 GMT
Originally opened as matrxs/MATRXS#2
Right now in the new frontend the grid is a set of aligned divs, which get their relative position from the div html position. However, in MATRXS multiple objects can occupy 1 cell in MATRXS. How can this be achieved in the new frontend?
This issue is related to when the objects are going to move. In that case, a more robust / free-floating positioning of objects seems to be required. E.g. absolute positioning?
The text was updated successfully, but these errors were encountered: