Yes, that might be possible as well. We don't really have to pick one
strategy. Different component sets can have different strategies. We could
have an "all em" set if we wanted. It would be nice to share code in UIBase,
but not a requirement. Hopefully, IUIBase doesn't really presume pixels
(although it still wants width/height to be a Number), and hopefully we don't
have lots of expectations on UIBase instead of IUIBase.
Another way to think about Royale is that our components (really the beads)
spit little bits of JS, CSS, and HTMLElements into the browser. So, for any
website you could build without Royale, you should be able to fashion Royale
components that automate and encapsulate the building of that site and similar
sites. So whatever pattern needs to be added to the final JS/CSS/HTML, we
should be able to encapsulate anything that isn't a one-off and provide
parameters to tweak the pattern.
My 2 cents,
-Alex
On 1/14/19, 12:26 PM, "Mark Kessler" <kesslerconsult...@gmail.com> wrote:
As a comment on the helper functions, we could also just have
something that does on the fly conversion. In other words if I say
300 pixels, I want it to translate that into EM / other unit in the
background. The reason I bring that up is to allow exact PX still be
used for the Flex / Air side and converted for the js/css side.
pixelTotal / fontSize = em
300 / 14 = 21.429 (rounded)
Soo 300px for flex and 21.429 for JS side.
-Mark K
