Hi nullPointer
I was wondering what would be the actions to take at the level of your code and
at the level of Pharo to
support a good and easier integration in the future?
Context: We are discussing with alain about a list of actions to clean and move
on the UI of Pharo
- merging/integrating polymorph
- removing useless leaf in the widget trees
- better Event (both Morphic and system)
...
Now my fear is that if we do not take action now about thinking about pushing
changes that can benefit to everybody
from your system to pharo then the integration (I would like to avoid yet
another level of widgets and yet another layer
of announcement/events....)
So the message and question is how can we improve the infrastructure so that
your system is easier to build?
what is the code that you would push from your code to the infrastructure?
The same question applies to the HPI framework.
It is important to understand that each time we improve the infrastructure, the
overall system gets better and easier to build
solution on top.
So I'm eager to read your answers.
Stef
On Mar 6, 2011, at 2:21 AM, nullPointer wrote:
> I added basic bindings mechanism on CLFramework, for connect data with
> widgets.
>
> First, a ObservableCollection; any change on the collection have
> representation on the data showed for the widget:
>
> http://www.youtube.com/watch?v=m8nC2gB4SUk
>
> For the moment the ObservableCollection only works with CLListview widget.
> Later will work with CLGrid too.
>
> Second, basic value bindings of a model (a person) with the GUI:
>
> http://www.youtube.com/watch?v=hYX2NCav_ZE
>
>
> Regards.
>
>
> --
> View this message in context:
> http://forum.world.st/Binding-data-to-controls-widgets-in-CLFramework-tp3337252p3337252.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
