[Grok-dev] testing apps with grok-1.1a1

Carlos de la Guardia carlos.delaguardia at gmail.com
Mon Nov 30 19:16:57 EST 2009


Hello,

I tried the demo app for the Grok book, which will be coming out soon.
It doesn't work because it uses megrok.form and as you know there are
various problems with that, plus it requires an earlier version of
z3c.widget.

I'd like to be able to say covers Grok 1.1 in the book, so if I
anybody can tell me more or less what needs to be done to fix
megrok.form to work with the ZTK I will try my hand at that.

Thanks for the great work,

Carlos de la Guardia

On Mon, Nov 30, 2009 at 1:40 PM, Jan-Wijbrand Kolman
<janwijbrand at gmail.com> wrote:
> Hi,
>
> I'd like to hear from you guys... :-)
>
> Are your apps running on grok-1.1a1, based on ZTK?
>
>
> Our applications are. It took little a bit of work, but not much:
>
>
> * hurry.query:
>
> The 0.9.2 release of hurry.query still uses the "old" zapi imports.
> These are gone in ZTK. Today I released hurry.query 1.0 since the trunk
> already had the clean ups required to make it "ZTK compatible".
>
>
> * (Functional)tests that rely on repr() of folder and sites:
>
> zope.app.folder.folder.Folder has been moved to zope.site.folder.
>
>
> * Testbrowser/mechanize error messages have changed slightly:
>
> What used to be:
>
>   httperror_seek_wrapper: HTTP Error 403: Forbidden
>
> Now is:
>
>   HTTPError: HTTP Error 403: Forbidden
>
> And other HTTP error message have changed in a similar fashion.
>
>
> * zope.session cookie-setting behaviour has changed slightly.
>
> In some of our functional tests we checked the HTTP response headers,
> and saw that the headers related to setting cookies (by the client id
> manager) were a bit different. As it turns out, zope.session will
> trigger this cookie only when it actually is needed and when it does, it
> will also set a series of response headers that shoudl prevent any
> caching of the response. NO biggy, but we had to play around a little to
> get our test output correct again.
>
>
> Tomorrow I'll migrate another bigger app to grok-on-ZTK and see what
> happens there. So far, the migration is rather painless. Good!
>
> Do people have more test results? What about doing an second alpha
> quickly, where hopefully some of the deprecated imports have been removed?
>
> regards,
> jw
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev
>


More information about the Grok-dev mailing list