[Seaside] Seaside 2.9: Seaside Walkback

[Julian Fitzell]

perhaps - that would help in a pinch alright. what's supposed to
happen is that when you load the dev tools package, the default is
changed to use the debug handler. i don't recall if it's just failing
to work or if there was an issue that made that difficult to implement
but it's one of the two. I'll try to take another look and at least
make sure there's an issue filed. If we don't get to it before, I
imagine we can get this nailed at the ESUG sprint.

julian

On Thu, Jul 30, 2009 at 9:19 AM, Boris Popov<boris at deepcovelabs.com> wrote:
> self registerAsDevelopmentApplication: 'counter'? I still think most people would want development setup to be the default as that's usually the starting point for anyone new to Seaside. Once someone is comfortable enough to do a deployment, that's where you can ask a little more of them on the configuration side.
>
> -Boris
>
> --
> +1.604.689.0322
> DeepCove Labs Ltd.
> 4th floor 595 Howe Street
> Vancouver, Canada V6C 2T5
> http://tinyurl.com/r7uw4
>
> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Julian Fitzell
> Sent: Thursday, July 30, 2009 9:16 AM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Seaside 2.9: Seaside Walkback
>
> The trick being that in 2.9, you have to configure it on the
> ExceptionFilter attached to the application rather than on the
> application itself. If you go into the app's configuration, there is a
> list of filters near the top and a link to configure them.
>
> This is still one of the major pain points in the 2.9 alphas and is
> holding us up from going to beta. It's basically a result of the tools
> needing to be updated to hide what is, programmatically, a better
> factoring of code but more complex to configure.
>
> Julian
>
> On Thu, Jul 30, 2009 at 9:08 AM, John Toohey<johnptoohey at gmail.com> wrote:
>> Hi,
>> You need to add the walkback or debug Exception handler to you app. In the
>> Config UI for your app, click on Filters (config), and then select the
>> Exception handler that you want in the General Settings. WADebugErrorHandler
>> will start the debugger in your image, and WAWalkbackErrorHandler will give
>> you the stack trace page.
>>
>>
>> On Thu, Jul 30, 2009 at 00:13, Eric Hochmeister <erichochmeister at gmail.com>
>> wrote:
>>>
>>> Hi,
>>>
>>> Is there something I need to setup in Seaside 2.9 to get a walkback?
>>>
>>> I am hitting a MNU message but I'm not getting a walkback or an option
>>> to bring up the debugger.  What am I missing?
>>>
>>> All I see is a partially rendered page with the following displayed...
>>>
>>> "MessageNotUnderstood: UndefinedObject>>context
>>>
>>> Your request could not be completed. An exception occurred."
>>>
>>> Thanks,
>>>
>>> Eric
>>> _______________________________________________
>>> seaside mailing list
>>> seaside at lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>>
>>
>> --
>> -JT
>>
>>
>>
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>