[Seaside-dev] Seaside 3.0b1 release schedule

[Philippe Marschall]

2009/9/19, Lukas Renggli <renggli at gmail.com>:
>>> The
>>> functional tests of JQuery and JQueryUI use similar things to display
>>> the source code.
>>
>> So does WABrowser which we made platform specific because it can not
>> be done in a portable way.
>
> WABrowser uses Browser as the model, which is specific to Pharo.
>
> The browser in JQuery, JQueryUI and Scriptaculous is different. It
> displays only a set of selectors of a specific class. I think on all
> platforms #selectors returns a list of selectors and #sourceCodeAt:
> returns the source code (if not, that could be added).

Up until now it has been your policy to not force Squeakisms on other people.

SUBrowser besides the listed method also does:

aClass organization categories
aClass organization listAtCategoryNamed:

> WABrowser is more complicated: it displays all classes, which are
> organized very different on all platforms (some have categories,
> packages, namespaces, etc). Furthermore it provides the possibility to
> edit code, something that is also handled very different on all
> platforms.
>
> I would like to avoid extra packages if possible. If the JQuery,
> JQueryUI and Scriptaculous code display is a problem, that could also
> be extracted to platform methods. First, however, somebody has to
> speak up that has a real portability problem with this, otherwise the
> problem does not exist IMHO.

Well somebody did:
http://code.google.com/p/seaside/issues/detail?id=466

Cheers
Philippe