Which I find funny because the one commercial grade swing app I did, I
ended up building all that stuff because it was the only way I could
see to get multiple views synced to the model without writing tons of
glue code. Also, swing widgets don't like having null values as their
data sources so the value models would keep them from throwing null
pointer exceptions all the time.
On Jun 20, 2009, at 4:25 AM, Steve Wirts wrote:
I did a talk(attached) at OOPSLA several years ago to explain the
benefits of ValueModels to java programmers, it was way over their
heads.
It's unfortunate as today I've yet to see anything in java that
approaches the productivity they provide.
2009/6/20 Schwab,Wilhelm K <[email protected]>
Steve,
Interesting that you mention value models. I just ran into a use
for a ValueHolder, and discovered that Dolphin's #value, #value:
protocol was not present. In fact ValueHolder>>value answers the
receiver! I added an override to my Dolphin compatibility package.
I exepect to add AspectValueAdapter and perhaps some converters as
need arises.
None of this takes away from Magritte; I share your interest in it
and willingness to consider it as potentially powerful tool for GUI
building.
Bill
From: [email protected] [mailto:[email protected]
] On Behalf Of Steve Wirts
Sent: Friday, June 19, 2009 8:01 PM
To: [email protected]
Subject: Re: [Pharo-project] Making GUI'S
Value Models, TypeConverter library, SubCanvas support(super
powerful idea here), etc... some really wonderful idioms long lost
in OO guis.
VisualWorks had some really nice frameworks that were discarded due
to them being undervalued.
I hope to eventually re-introduce some of these fun frameworks into
pharo given my time constraints and interest from potential users.
see
http://c2.com/ppr/vmodels.html
Magritte seems like it might be a superior alternative to
VisualWorks ValueModels; I haven't explored it enough to really
know yet.
Pharo is the most exciting thing to come along for me in quite awhile!
On Fri, Jun 19, 2009 at 4:42 PM, Stéphane Ducasse <[email protected]
> wrote:
>
> I don't know what I am waiting for -- except more time -- because I
> guess I should build such a thing. (Are there any Pharo/squeak
coders
> available for part-time consulting over the next year? ...At student
> level pay I must add.)
>
> I too want a GUI builder.
me too :)
So may be we could have a kind of bounty system for pharo.
Frankly we are rather full and we (the core) have not that much time
for
extensions but we would support any work in the direction of
UIBuilder
TestServer
Package....
FileWrite-Rio kind of integration
Better MC support (yes I should look at MC1.5)
Better SUnit
Better tools (for example like the newInspector)
Stef
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
<value models.ppt>_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
