I note that #become: is not in the ANSI Smalltalk standard (am I the last
person in the world to care about that? Probably) and that several of the
Smalltalk systems I have on my machine don't support it.
In Squeak 5.2, there were 17 references to #become:. Four of those were
just testing it. One
Hi,
I would use an ad-hoc solution, modeling the Plant tree structure as a
document tree in Grafoscopio [1]. The root of the plant representation
would be the root of the document, the branches and sub-branches would
be nodes and sub-nodes in the documents, respectively. And each node
would contai
Hi Esteban,
In the present model, the plant has a tree-like structure. It is a well
suited structure, even for a dandelion since the leaves are connected on
a shoot. The plant root system has a tree structure as well !
Thank you,
Loïc
Le 16/01/2019 à 13:52, Esteban Maringolo a écrit :
This
Being a fan of DDD and Event Sourcing as I am, I'd implement your domain
using Aggregates and Events.
Basically, your aggregate (Plant?) would respond to external information
(or based on a schedule) and as a result, new events are generated ("Flower
sprung", "Plant died", ...).
If only we had prop
+1 about become:
Don’t use it for business stuff. Plus it can be very problematic when it comes
to persistence mechanisms like O/R mappers...
> Am 16.01.2019 um 19:01 schrieb Esteban Maringolo :
>
>> El mié., 16 ene. 2019 a las 14:49, Ben Coman via Pharo-users
>> () escribió:
>
>>
>>
>>> On
El mié., 16 ene. 2019 a las 14:49, Ben Coman via Pharo-users (<
pharo-users@lists.pharo.org>) escribió:
>
>
> On Wed, 16 Jan 2019 at 17:16, Loïc Pagès wrote:
>
>>
>> Maybe a naive question ?
>>
>
> Maybe #become: ...
> https://gbracha.blogspot.com/2009/07/miracle-of-become.html
>
>
Although mirac
On Wed, Jan 16, 2019 at 9:05 AM Loïc Pagès wrote:
> Hi Richard,
>
> You are in the south hemisphere, so ! Temperatures are low here in France.
>
> Thank you for your comments.
> I agree that development is slow if you look at the plant every day, and
> in this case we perceive continuous changes.
Hi Richard,
You are in the south hemisphere, so ! Temperatures are low here in France.
Thank you for your comments.
I agree that development is slow if you look at the plant every day, and
in this case we perceive continuous changes. But in models, it might be
convenient to define discrete sta
--- Begin Message ---
On Wed, 16 Jan 2019 at 17:16, Loïc Pagès wrote:
> Dear Pharo users,
>
> I develop software dedicated to the simulation of plant development and
> 3D architecture.
>
> In the past, I used Java,
but I am very interested in translating code
> in Pharo. I appreciated very much
This is a challenging modelling issue, life progress or any other
dissipative/emergent structure are "restricted" by the boundaries of your
objects (e.g. if you model a flock, and it divides into two flocks, and
then merges again, which flock remains? Note: I wouldn't model the Flock at
all).
So i
It seems to me that in the real world, a bud does not get replaced by a
flower
nor a flower by a fruit, nor is there a definite point at which a thing
stops
being a bud and starts being a flower, and so on. It's summer now, but
spring
wasn't that long ago, and I enjoyed watching the imperceptible
Hi Joachim,
Thank you for your reply and for your ideas. I will reply to your
questions below.
Le 16/01/2019 à 10:25, jtuc...@objektfabrik.de a écrit :
Loïc,
Am I correct in assuming you are thinking about a model in which a
plant can have a growing and shrinking list of organs over time an
Loïc,
Am I correct in assuming you are thinking about a model in which a plant
can have a growing and shrinking list of organs over time and some of
them even have (a growing list of) stages?
I am not an expert on the matter, but to me the stages idea sounds good.
It even allows for historic
13 matches
Mail list logo
