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

L10N - Fix RTL rendering of blocks #34

Closed
thisandagain opened this issue Feb 2, 2016 · 6 comments
Closed

L10N - Fix RTL rendering of blocks #34

thisandagain opened this issue Feb 2, 2016 · 6 comments
Assignees
Milestone

Comments

@thisandagain
Copy link
Contributor

In the process of quickly implementing the horizontal grammar we broke RTL in a number of places:
image

Depends on #31

@rachel-fenichel
Copy link
Collaborator

@carljbowman what's the reference point for positioning the icons? (Start, end, centered, etc.) Are we ever going to have horizontal blocks that could have multiple icons? Will there be C-shaped blocks that have an icon at the beginning instead of the end?

@NeilFraser should I try to make this generalizable (for horizontal blockly with arbitrary blocks/arbitrary numbers of images) or implement it specifically for the scratch jr cases?

FYI in the existing code "icon" refers to the little gear for mutators, exclamation mark for the few errors, etc.

@NeilFraser
Copy link
Collaborator

Blockly attempts to be general-purpose. No matter what Frankenstein block configuration you give it, Blockly will render it properly. But the result is a rather complicated codebase.

Scratch Jr has an exceedingly small number of shapes. Therefore I think it is best for Scratch Jr to take the more limited approach of just rendering what it needs to. This leads to simpler code, though every time a new block shape is added (e.g. if/else), Scratch Jr will need more code. Since Scratch Jr does not have an open-ended set of blocks, non-generalized code should be an easier path in my opinion.

Scratch on the other hand is much more expressive and should be fully generalized.

@thisandagain thisandagain modified the milestone: April 28 Feb 29, 2016
@tmickel tmickel closed this as completed in 3287fa3 Mar 3, 2016
@rachel-fenichel
Copy link
Collaborator

Not fully there yet.

@tmickel
Copy link
Contributor

tmickel commented Mar 3, 2016

yeah, that automatic closing gets you sometimes :P

@tmickel
Copy link
Contributor

tmickel commented Mar 7, 2016

Still to do: rendering the field/input in the right place.
screen shot 2016-03-07 at 12 00 05 pm

@tmickel
Copy link
Contributor

tmickel commented Apr 6, 2016

Closing this now as it's actually fixed I think. Let's revisit in new bugs if there are new problems.

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

4 participants