I changed the widget mechanism a coupe of weeks ago.
Now the idea is that the interpreter use a default set of bindings (by default
Morphic, but can be changed) and then you can specify for a widget build to use
a specific set of bindings.
Then this bindings is used for the whole build phase, then the default bindings
are reset as default.
I will experiment with your package and see :)
Thanks,
Ben
On Dec 6, 2012, at 3:01 PM, Pavel Krivanek wrote:
> Gofer new
> smalltalkhubUser: 'PavelKrivanek' project: 'Periscope';
> package: 'Periscope';
> load.
>
> Nautilus pluginClasses add: {(Smalltalk at: #NautilusPeriscopePlugin). #none}
>
> Look at PeriscopeMorphicBindings and references.
> Spec needs to find a way how to specify custom widgets needed by an
> application based on some UI while on other UIs the default widgets will be
> used (or the programmer will need to create this widget for the new UI too).
> The main problem with bindings was that it was not shared with subwidgets so
> if you created the window widget with specific binding, you had to manually
> set this binding for the elements in the window too.
>
> Cheers,
> -- Pavel
>
> On Thu, Dec 6, 2012 at 2:36 PM, Benjamin
> <[email protected]> wrote:
> Now the bindings are provided to the interpreter and not to the model it self.
>
> Can you point me where to load your code, like that I have an interesting use
> case :)
>
> Thanks
> Ben
>
> On Dec 6, 2012, at 9:28 AM, Pavel Krivanek wrote:
>
> > Hi Ben,
> >
> > what was changed in the Spec bindings assignment in the new Spec versions?
> > Because Periscope uses own subclass of MorphicBindings to provide own
> > widgets including window widget but now only standard widgets are used and
> > the different binding is not taken into account.
> >
> > Cheers,
> > -- Pavel
>
>
>
