Checking for the Debugger Window

We have a web site that is currently under development but is running on an unattended server. We are using WebConnect to run the site.

As it is under development, we are running the development image.

We would like to send ourselves an e-mail if the Debugger Window opens.

I know that I can get a list of windows using EtWindow allWindows but how do I determine the Debugger window from the list.

This is probably a trvial question but it is giving me a bit of grief.

David
Totally Objects

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/VjLV4gy3H_wJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

Hi David,

Long time, no see.

If I inspect 3/0, I get a debugger. If I then inspect EtWindow allWindows, I get an orderedCollection with one of its entries being an StsDebugger.

How's that? Or have I completely misunderstood?

Donald [|]

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/6O1eCFI3JlsJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

Hi Donald

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

How about 'self select: [:each | each class name = #StsDebugger]'?

Donald

On Sunday, March 11, 2012 5:30:28 PM UTC-4, Totally Objects wrote:

Hi Donald

If I iterate over the windows - what essage do I send them all to find out that one is the debugger?

Thanks for responding

David Pennington

Totally Objects

The Smalltalk Specialists

On 11 Mar 2012, at 21:17, Donald MacQueen wrote:

Hi David,

Long time, no see.

If I inspect 3/0, I get a debugger. If I then inspect EtWindow allWindows, I get an orderedCollection with one of its entries being an StsDebugger.

How's that? Or have I completely misunderstood?

Donald [|]

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/6O1eCFI3JlsJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/hEyvgDEhHwMJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

How about 'self select: [:each | each class name = #StsDebugger]'?

Donald

On Sunday, March 11, 2012 5:30:28 PM UTC-4, Totally Objects wrote:

Hi Donald

If I iterate over the windows - what essage do I send them all to find out that one is the debugger?

Thanks for responding

David Pennington

Totally Objects

The Smalltalk Specialists

On 11 Mar 2012, at 21:17, Donald MacQueen wrote:

Hi David,

Long time, no see.

If I inspect 3/0, I get a debugger. If I then inspect EtWindow allWindows, I get an orderedCollection with one of its entries being an StsDebugger.

How's that? Or have I completely misunderstood?

Donald [|]

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/6O1eCFI3JlsJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/hEyvgDEhHwMJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

On 3/11/2012 6:55 PM, David Pennington wrote:

Why is it that the blindingly obvious is only blindingly obvious when someone else tells you!

That's the great humbling thing about dealing with computers -- no matter how much experience you have, there are still regular opportunities to get mentally wrapped around the axle.  Happens to me at least once a month.

Glad I could help.

Thanks

David

On 11 Mar 2012, at 21:36, Donald MacQueen <[hidden email]> wrote:

How about 'self select: [:each | each class name = #StsDebugger]'?

Donald

On Sunday, March 11, 2012 5:30:28 PM UTC-4, Totally Objects wrote:

Hi Donald

If I iterate over the windows - what essage do I send them all to find out that one is the debugger?

Thanks for responding

David Pennington

Totally Objects

The Smalltalk Specialists

-- 
Donald [|]

A bad day in [] is better than a good day in {}

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

Perhaps because it is not obvious and obviously not a good practice.
If you were to install the RjsDebugger (which doesn't actually exist), your implementation breaks horribly. Your original question was much more appropriate: what behaviour tells me it is a debugger window?

Conversely, do you really want a debugger window at all? Why not replace the debugger with a stack dumper and a mail sender? (If the information you choose to capture would allow you to recreate the problem, you would have all you need.)


On Sunday, March 11, 2012 11:55:57 PM UTC+1, Totally Objects wrote:

Why is it that the blindingly obvious is only blindingly obvious when someone else tells you!

Thanks

David

Sent from my iPad

On 11 Mar 2012, at 21:36, Donald MacQueen <[hidden email]> wrote:

How about 'self select: [:each | each class name = #StsDebugger]'?

Donald

On Sunday, March 11, 2012 5:30:28 PM UTC-4, Totally Objects wrote:

Hi Donald

If I iterate over the windows - what essage do I send them all to find out that one is the debugger?

Thanks for responding

David Pennington

Totally Objects

The Smalltalk Specialists

On 11 Mar 2012, at 21:17, Donald MacQueen wrote:

Hi David,

Long time, no see.

If I inspect 3/0, I get a debugger. If I then inspect EtWindow allWindows, I get an orderedCollection with one of its entries being an StsDebugger.

How's that? Or have I completely misunderstood?

Donald [|]

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/6O1eCFI3JlsJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/hEyvgDEhHwMJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/y91ojwdU62YJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

This is only whilst we are going through the implementation phase. We can check the system using Chicken of the VNC (don't you just love those macintosh program names) but this way we know when to do so, we don't have to keep checking. Once we have cleared the issues, we will drop the facility.

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.