Erros with Pharo 3 and Seaside 3

you need to change your app error strategy to debug walback or something like that. 

look in your app config.

Esteban 

On 30 Dec 2013, at 16:18, sergio_101 <[hidden email]> wrote:

I just started playing with seaside and pharo 3 after a long time away from them.

one of the things i have found is that when i hit an error, i get an error notification in my browser, but that's all.

one of the things i loved about seaside was that i received a full stack, plus, the app was halted in the image, and i could just edit away.

is this a by product of using a new pharo with seaside 3, or is this how seaside now works?

thanks!

--

----
peace,
sergio
photographer, journalist, visionary

#BitMessage BM-2D8VWUJSS41RFKh1ec83preVabHrnniExa

http://www.ThoseOptimizeGuys.com
http://www.CodingForHire.com
http://www.coffee-black.com
http://www.painlessfrugality.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Sergio,

The idea is that you can customize how to handle errors. See subclasses of WAErrorHandler and their class comments for more info.

While developing, it’s more useful to choose the WAWalkbackHandler but your image might become a bit too clogged with debuggers when you would use that one in production.

I guess it would actually make sense that it’s part of the WADevelopmentConfiguration… we should check that.

Cheers,

Johan

 

On 30 Dec 2013, at 16:52, sergio_101 <[hidden email]> wrote:

ahh! thanks!

is there any reason i would want to keep the error strategy this way?

On Mon, Dec 30, 2013 at 10:43 AM, Esteban Lorenzano <[hidden email]> wrote:

you need to change your app error strategy to debug walback or something like that. 

look in your app config.

Esteban 

On 30 Dec 2013, at 16:18, sergio_101 <[hidden email]> wrote:

I just started playing with seaside and pharo 3 after a long time away from them.

one of the things i have found is that when i hit an error, i get an error notification in my browser, but that's all.

one of the things i loved about seaside was that i received a full stack, plus, the app was halted in the image, and i could just edit away.

is this a by product of using a new pharo with seaside 3, or is this how seaside now works?

thanks!

--

----
peace,
sergio
photographer, journalist, visionary

#BitMessage BM-2D8VWUJSS41RFKh1ec83preVabHrnniExa

http://www.ThoseOptimizeGuys.com
http://www.CodingForHire.com
http://www.coffee-black.com
http://www.painlessfrugality.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

--

----
peace,
sergio
photographer, journalist, visionary

#BitMessage BM-2D8VWUJSS41RFKh1ec83preVabHrnniExa

http://www.ThoseOptimizeGuys.com
http://www.CodingForHire.com
http://www.coffee-black.com
http://www.painlessfrugality.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside