[Seaside] The session in the debugger
Ron at USMedRec.com
Sun Feb 4 23:44:49 UTC 2007
+1 I hit that all the time.
Better yet it would be great to have a direct connection between the
instance of Component/application and the session that created it. I
implemented a stack that keeps track of which application I'm currently in
just to do this!
In case the question of why comes up. I added an automatic object
registration. Each application responds to handlesCommit. When an object
is created it automatically finds the application in the stack that is
currently handling the commit and registers itself in a dirtySet.
> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Philippe Marschall
> Sent: Sunday, February 04, 2007 1:19 PM
> To: The Squeak Enterprise Aubergines Server - general discussion.
> Subject: [Seaside] The session in the debugger
> One of the most annoying things about Seaside for me is that you can't
> access the session in the debugger. Often when debugging code that
> needs to access some session data I find myself writing code like
> "some code"
> session := self session.
> self halt.
> "more code"
> and then restarting the method. I am sick of it. This just sucks. So
> recently I meant someone with too much time who would like to make a
> valuable contribution to Seaside. I told him about this and he said he
> would do it if I find at least 5 people to whom it is important.
> Personally I don't care how ugly the solution is as long as Seaside
> still works. It doesn't have to be a general solutions. It can be a
> very evil changeset that causes famine, plague, small pocks and
> shortens life by 10 years. That desperately I want it.
> If you feel the same way raise your hand now.
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
More information about the Seaside