[Seaside] Re: [Pharo-dev] Pharo{2,3} problems with seaside3.1

Craig Johnson craig at hivemind.net
Thu Jan 8 20:59:41 UTC 2015


I'm using Seaside 3.1 in Pharo 4 image 40423.  When I put an error in my
code and execute it, I get the Seaside walkback in the browser with a Debug
link.  If I click that link, the debugger launches in the Pharo window.

Is that not what you see?


-----Original Message-----
From: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Sanjay
Sent: 08 January 2015 07:24 PM
To: seaside at lists.squeakfoundation.org
Subject: [Seaside] Re: [Pharo-dev] Pharo{2,3} problems with seaside3.1

Hi Johan,

The issue is that I am simply unable to get Seaside 3.1 debugger to work
completely with Pharo 3 & 4 - For Pharo 4 it even shows an error while
loading and Halos debugger just does not work. There is a post about not
working with Opal compiler

I would like to know if there are Pharo 3 / 4 + Seaside 3.1 or later users
and why this is not really a concern with them. 

I have embarked on a small commercial project as a Pilot / PoC which is to
lead to a much larger commercial project and practically the only "tool" I
am using as a debugger is "self halt". I want to know what I am missing


Regards, Sanjay
View this message in context:
Sent from the Seaside General mailing list archive at Nabble.com.
seaside mailing list
seaside at lists.squeakfoundation.org

More information about the seaside mailing list