FogBugz (Case [Issue]10386) Spec - Spec Suggestions

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

FogBugz (Case [Issue]10386) Spec - Spec Suggestions

Pharo Issue Tracker
A FogBugz case was opened by Sean DeNigris.

Case ID:      10386
Title:        Spec Suggestions
Status:       Work Needed
Category:     Enhancement
Project:      Spec
Area:         Misc
Priority:     3 - Must Fix
Milestone:    Pharo3.0: 29/04/2013
Assigned To:  Benjamin Van Ryseghem

URL:          https://pharo.fogbugz.com/default.asp?10386

I found this mailing list post [1] and wanted to capture the suggestions:

On Sat, Oct 13, 2012 at 1:43 AM, Igor Stasenko <[hidden email]> wrote:
> Pavel, since i am potential user of Spec, i would like to know more details.
> I know it takes more time to explain what exactly you don't like and
> propose better alternative,
> instead of just generic "i don't like it".

Well, some points:

- bindings management. Currently if you want to use different
binding/platform, you have to specify it for every single widget. It
doesn't use platform of the parent. Notice that I had to create own
binding even in case I wanted to use smaller font for lists or iconic
buttons.

- bindings extensions. Imagine the situation when you want to use some
special widget in Morphic, let's say some new button type. Currently
you create own binding class. But in case that you will want to use
something different from Morphic (eg. HTML) you are in trouble because
you already used custom binding mechanism for extension of set of the
widgets, not for UI framework independence. Spec should provide a way
how to offer both - UI independence and widgets extensibility (with
fallback mechanism in case that the special widget has no
implementation in the currently used UI - in our case a normal button
would be used).

- layout management. The layout management is taken directly from
Morphic. Imagine you should create a HTML binding. Direct ratios and
size values!!! are used everywhere. Why to specify how thick a bar
with buttons should be? Widgets should know their own optimal size.
Look at our current retina display issues. Flex mechanism from XUL is
quite nice here
(https://developer.mozilla.org/en-US/docs/XUL_Tutorial/Using_Spacers).

- Morphic... look at Nautilus (eg. buildMiddlePlugins message) how
Spec based tool must look now.

[1] http://forum.world.st/Interconnection-of-Morphic-and-Spec-was-ANN-Phobos-td4650812.html


You are subscribed to this case.  If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=10386) from this case.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker