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

Improve GLSP UI Extension mechanism for easier re-use of HTML elements #516

Merged
merged 1 commit into from Mar 21, 2024

Conversation

martin-fleck-at
Copy link
Contributor

@martin-fleck-at martin-fleck-at commented Mar 20, 2024

  • Allow more fine-grained definition of container and parent
  • Allow more fine-grained definition of container within parent
  • Replace hard-coded styles with 'hidden' class
  • Rework index file to define structure and use grid for layouting
  • Properly align ALL index files with same structure, loading and style
  • Remove workaround for toolbar height (48px adjustment)
  • Ensure Quick Action UI is still rendering correctly

Minor fix:

  • Ensure that mouse move is only ever executed on drag

Copy link
Member

@ivy-lli ivy-lli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good 👍

inset: 0;
width: 100%;
height: 48px;
background: var(--glsp-tool-bar-bg);
box-shadow: var(--glsp-box-shadow);
z-index: 10;
container: toolbar / inline-size;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why remove this?
without the container query at the bottom of this file will no longer work I think...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point! I think I may have committed that by mistake. I'll push an update as soon as the other change is merged cause I'll need to rebase anyway, thank you!

@martin-fleck-at
Copy link
Contributor Author

@ivy-lli I pushed an update that should fix the issue and align the HTML structure and layout styles across ALL integrations (standalone, viewer, Eclipse -- I could test standalone and viewer but not Eclipse). Could you please have another look?

I also fixed the issue we saw with the moving of an element even though it wasn't being dragged.
The issue with not being able to copy/paste from the color box, however, I could not reproduce - neither in Chrome nor in Firefox, could you please re-test?

@ivy-lli
Copy link
Member

ivy-lli commented Mar 20, 2024

@ivy-lli I pushed an update that should fix the issue and align the HTML structure and layout styles across ALL integrations (standalone, viewer, Eclipse -- I could test standalone and viewer but not Eclipse). Could you please have another look?

I also fixed the issue we saw with the moving of an element even though it wasn't being dragged. The issue with not being able to copy/paste from the color box, however, I could not reproduce - neither in Chrome nor in Firefox, could you please re-test?

I will quickly test the eclipse integration and check the copy paste bug.

@ivy-lli
Copy link
Member

ivy-lli commented Mar 20, 2024

started the build pipelines

@ivy-lli
Copy link
Member

ivy-lli commented Mar 20, 2024

image
😆

the process dom node no longer has the id=sprotty:
image

To test the eclipse integration:

  • Start designer
  • Open process in it
  • Eclipse menu: process -> open in external browser
  • Copy parameters to integration

@ivy-lli
Copy link
Member

ivy-lli commented Mar 20, 2024

The move bug seems to be solved, thanks for that 👍

@ivy-lli
Copy link
Member

ivy-lli commented Mar 20, 2024

Quickly tried to reproduce the copy+paste problem:

  • Seems only to be a problem in 10.0.x
  • Only in the integrated swt browser (eclipse integration)

@martin-fleck-at
Copy link
Contributor Author

image 😆

the process dom node no longer has the id=sprotty: image

To test the eclipse integration:

  • Start designer
  • Open process in it
  • Eclipse menu: process -> open in external browser
  • Copy parameters to integration

Dang, will fix in a minute.

@ivy-lli
Copy link
Member

ivy-lli commented Mar 20, 2024

and a lot of failing tests :)

@martin-fleck-at martin-fleck-at force-pushed the features/ui-extensions branch 3 times, most recently from daf2b31 to fb40d45 Compare March 20, 2024 14:40
@martin-fleck-at
Copy link
Contributor Author

@ivy-lli I fixed the Eclipse issue and the regular tests failing, now I'm working on the web tests but for some reason Playwright generates gigabytes of temporary data so it is a bit harder to investigate. Hope to push an update soon!

@martin-fleck-at
Copy link
Contributor Author

@ivy-lli Could you please re-trigger the CI?

- Allow more fine-grained definition of container and parent
- Allow more fine-grained definition of container within parent
- Replace hard-coded styles with 'hidden' class
- Rework index file to define structure and use grid for layouting
- Properly align ALL index files with same structure, loading and style
- Remove workaround for toolbar height (48px adjustment)
- Ensure Quick Action UI is still rendering correctly

Minor fix:
- Ensure that mouse move is only ever executed on drag
@martin-fleck-at
Copy link
Contributor Author

@ivy-lli Ok it was one test that I fixed wrongly because it behaves differently locally but I'm hopeful that the next test run should go through. Could I ask for one more trigger?

@martin-fleck-at
Copy link
Contributor Author

@ivy-lli Finally :D

Copy link
Member

@ivy-lli ivy-lli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool thanks! I will merge :)

@ivy-lli ivy-lli merged commit 17db562 into axonivy:master Mar 21, 2024
6 checks passed
@martin-fleck-at
Copy link
Contributor Author

@ivy-lli Thank you for your patience! I'll push an update to the VS Code extension in the next 2-3 hours :-)

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