Hello,
I got that working, and a bit more besides, and things are starting to look
pretty good. However, I've run into another issue I'm not sure how to
resolve. Recognizing that, as you mentioned, nested builders are something
of a bleeding edge feature, I'm happy to try to contribute code if wha
Hi Evan,
You are indeed on the edge of what Roassal can do. This is a situation that I
have tried to fix. Please play with the solution I propose and complain if this
is not what you expect.
Try this:
-=-=-=-=-=-=-=-=-=-=-=-=
v := RTView new.
es := RTShape withAllSubclasses collect: [ :cls |
Hi!
In that case you can create a normalizer and use it after all the elements have
been added.
For example (__you need to update Roassal since I’ve just fixed a bug__):
-=-=-=-=-=-=-=-=-=
v := RTView new.
data := #((1) (2) (1 2)).
es := data collect: [ :d |
b := RTPieBuilder new.
Hello,
Many thanks for the reply. This indeed solves part of my problem, and does
what I expect (although in the smalltalkhub / ObjectProfile / development
code, only RTView has #asElement, not RTBuilder). Given this, I think I can
give an example of the real stumbling block I'm facing (although w
Hello,
I am working with Roassal and trying to write a cell-layout builder that
uses RTPieBuilders internally as its nested objects. The nesting docs cover
nesting RT elements, but not builders. The composition docs cover composing
builders, but not nesting them. I have a partial solution, but it