[Seaside-dev] MyFirstComponent Bugged in Squeak Download

[Julian Fitzell]

The general pattern I'm advocating is to extend Grease first from the
package that requires the functionality (so in this case in the
Welcome package). As soon as we find multiple things using it, we can
move it and will have a better clue where to move it up to.

In either case, I suggest adding methods with a #seaside prefix
initially. If at some point we're confident with the interface and
feel it is generally useful, we can add non-prefixed versions and
deprecate the original methods to call the new ones.

Julian

On Sat, Nov 6, 2010 at 1:03 PM, Nick Ager <nick.ager at gmail.com> wrote:
>>
>> > Note too that even though MyFirstComponent in the Pharo image, it is
>> > clumsy because the user has to enter a username in the Smalltalk environment
>> > window, but there is no warning of this in the
>> > browser._______________________________________________
>>
>> http://code.google.com/p/seaside/issues/detail?id=610
>
> I'm happy to fix this. Should I handle the cross-dialect differences by
> adding Grease. In which case, which Grease object should I augment?
>
> Pharo 1.1:
> Author class>>#fullNamePerSe
> Author class>>#fullName:
> Squeak 4.1:
> Utilities class>>#authorInitialsPerSe
> Utilities class>>#authorName:
> Suggested Grease interface
> #isAuthorNameSet
> #setAuthorName
> Nick
>
>
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
>