[Seaside] Brushes and state
marianomontone at gmail.com
Thu Jun 18 14:47:24 UTC 2009
I think I looked at your code once, but you didn't have callbacks and
implemented it only with brushes , didn't you? If you didn't, do you have
callbacks? And how did you implemented them? I'm supporting callbacks now
and am considering creating a component.
On Thu, Jun 18, 2009 at 11:30 AM, James Foster <Smalltalk at jgfoster.net>wrote:
> I did a Seaside package for Google Maps. Check out
> http://seaside.gemstone.com/ss/GoogleMaps.html. If you'd like to
> contribute to that project just register as a developer and I'll add you to
> the project.
> On Jun 18, 2009, at 5:51 AM, Mariano Montone wrote:
>> I'm implementing an API for rendering Google Maps. I've decided
>> code. But now I have a problem: when adding support for callbacks, I need to
>> hold some state; for example, the map the callback refers to. But I think
>> brushes are not meant to hold state, that is something left for the
>> components mechanism, isn't it? So I would like to know what would be the
>> correct way of implementing it in the framework. Should I implement maps as
>> components, or should I add state to my brushes; I may hold a state in the
>> callback block too, but I don't think that's good.
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside