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

Create mrtkv3 button [Contnued] #12989

Merged

Conversation

tayomadein
Copy link
Contributor

@tayomadein tayomadein commented Sep 16, 2022

This is a continuation of the work started in this PR: #12707:
Assets PR: BabylonJS/Assets#67

Preview:

The design team is currently working on creating an interactive documentation for showcasing graphics tools components. This PR creates a TouchHolographicV3Button which mirrors the visual design of the MRTK v3.0 button.
For the time being, we would be using snapshots from this experimental PR and other PRs to create this documentation pending when we figure out the best way to release these new designs.

TODO

  • Figure out how to handle versioning between this button and the TouchHolographic button. As new designs for MRTK components are released, we might need to figure out the best way for users to switch from one version to the other. Otherwise, the growing list of varying components like the button might become confusing to use. - Solution: Create mrtkv3 button #12707 (comment)

Playground ID - /#UHMKE6#1

image

image

@tayomadein tayomadein mentioned this pull request Sep 16, 2022
1 task
@azure-pipelines
Copy link

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

@azure-pipelines
Copy link

Copy link
Member

@RaananW RaananW left a comment

Choose a reason for hiding this comment

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

A few nits and a general question -

The PR contains a lot of static values that cannot be changed - colors, sizes, scaling factors, positions and so on. Shouldn't the dev be able to change these values if required?
Same thing in the animations loop - there are many static values there that are unconfigurable

Otherwise - LGTM

@RaananW RaananW merged commit 049e37d into BabylonJS:master Oct 5, 2022
RaananW pushed a commit that referenced this pull request Dec 9, 2022
* create vertex and fragment shaders for different parts of button

* create materials for different parts of button

* create v3button class

* add new line at end of backglow material file

* update property docs for used materials

* remove unused pinched property from frontplate

* fix lint issues with prettier

* fix right hand system problem with button animations

* align text and image for button horizontally

* use common radius and offset for frontplate and innerquad

* use absolute sizing for backplate material

* prettier fix spacing

* move import to top

* rename V3Button to TouchHolographicV3Button

* adjust radius of innerquad

* adjust positioning for quad, frontplate and glow

* group private variables

* fix bug with collision size

* fix positioning of frontplate, innerquad and backglow

* align text and image according to width to height ratio

* adjust button text padding

* update comment for tooltiptext

* use grid for text and subtext instead of stackpanel

* rename speed to speedRatio

* prettier format

* add observers for pointer enter and pointer out

* fix issue with isBackplateVisible behaviour

* fix toggle interaction issue

* change design for tooltip

* format fix

* move MRTKv3 components to its own folder

* code fixes and cleanup

* nits + PR comments

* use MRTK3 name format

* fix code comment

* fix lint issues

Co-authored-by: Chineze Nwosu <chinezenwosu@microsoft.com>
Former-commit-id: 2e37e3d95161fa2a564d55b38b2f21a33d3f7197
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants