[Seaside-dev] Re: Seaside2.8a1-mb.487

[Philippe Marschall]

2007/10/2, Martin Kobetic <mkobetic at cincom.com>:
> Philippe Marschall wrote:
> > As a long term solution I don't think it makes much sense to force
> > this artificial complexity to the user. Hence I propose a selector
> > that combines the advantates of #asString and #displayString.
> >
> > #toString
> > - returns a String always, no Symbol, no Text
> > - understood by all objects
> > - no conflicts with existing methods
> >
> > Yes, this is like Rails implementing unicode because Ruby doesn't.
>
> I don't think this is sufficient definition of #toString.

We'll have to define the behavior by tests anyway.

> Presumably it shouldn't return just an arbitrary String for any object. What exactly should the return value convey ? Is it a "string equivalent" of the object (like asString),

yes

> is it a description for application user (like #displayString), is it a description for application developer (printString),

no

> or something completely different ?

no

Cheers
Philippe

> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>