[Screencast] Using ZnLogEvents and GT Tools to look at HTTP traffic behind Monticello
Using ZnLogEvents and GT Tools to look at HTTP traffic behind Monticello. I love it when a plan comes together. Many small usability changes were added to GT Tools since they were included in Pharo 4. And a lot of small custom inspector presentations were added. http://youtu.be/rIBbeMdFCys (be sure to select the 720p version) This short screencast shows how to use ZnLogEvents and GT Tools in Pharo 4 to look at the HTTP traffic behing Monticello (more specifically, an MCSmalltalkhubRepository). This demonstrates how simple custom inspectors are combined to form a powerful tool - and how easy it is to learn about what is going on inside Pharo. Sven
Nice! :) Doru On Wed, Oct 15, 2014 at 3:55 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Using ZnLogEvents and GT Tools to look at HTTP traffic behind Monticello.
I love it when a plan comes together. Many small usability changes were added to GT Tools since they were included in Pharo 4. And a lot of small custom inspector presentations were added.
http://youtu.be/rIBbeMdFCys (be sure to select the 720p version)
This short screencast shows how to use ZnLogEvents and GT Tools in Pharo 4 to look at the HTTP traffic behing Monticello (more specifically, an MCSmalltalkhubRepository). This demonstrates how simple custom inspectors are combined to form a powerful tool - and how easy it is to learn about what is going on inside Pharo.
Sven
-- www.tudorgirba.com "Every thing has its own flow"
Nice! I'll try the Announcers thing on a Seaside session. How would you do that? I mean DynamicVariables in GT. âPhil
On 15 Oct 2014, at 21:57, phil@highoctane.be wrote:
Nice!
I'll try the Announcers thing on a Seaside session.
How would you do that? I mean DynamicVariables in GT.
âPhil
I am not sure I understand the question. I did/do Announcement based logging in Seaside, just firing them globally. But I did add a session ID to each log event so that you can keep them apart. My custom WASession subclass adds its #key and #username to the log event objects. I'll send you some example output in private. Sven
participants (3)
-
phil＠highoctane.be -
Sven Van Caekenberghe -
Tudor Girba