Hi Chris,
Have you tried the OmniBrowser tools that come with 3.9?
I don't know Tracing Messages Browse, but it seems that the new OB
sender/implementor inspectors do exactly this...
Also, the classes in the selected category are displayed in a hierarchy.
It seems that people don't know these new tool very well although
they are very cool and should be pushed further. There are still a
few issues but after using them for a couple of months now, I
wouldn't want to go back to the old ones.
Adrian
On Feb 9, 2007, at 04:20 , Chris Muller wrote:
Hi Thierry, indeed, the breadth and depth of all the Squeak projects
and code out there is truly massive and intimidating.
One thing that has helped me grok others code and my own is having
improved the productivity of the tools for code exploration. The
Hierachy Browser and Tracing Messages Browser have served me well for
years for this. You can load Tracing Messages Browser from
SqueakSource for 3.9 or SqueakMap for 3.8 or earlier. There are
certainly other tools too, but the point is I've noticed how many new
(and some veteran!) Squeakers have developed a habit of using only
Package Browsers and then scrolling and clicking around in those to
browse and edit code.
And, sadly, this obsession with Package Browsers has gotten worse in
3.9 because you can't even make Hierarchy Browser the default anymore!
Its really boggling at how difficult it is to simply focus on the
*class-model* instead of always just the package-organization.. So I
usually find 3.8 better for groking code (at least until I get time to
fix up 3.9)..
There is one other small enhancement that has, in my dev image, paid
good dividends. "Code Editor Enhancements" on SqueakMap allow me to
browse *from* anywhere I might be, *to* anywhere I could logically
want
to go from that place. Like, if I'm viewing a method, update:
aCustomer, I can double-click the text, "aCustomer", press a hot key,
and the Customer hierarchy opens up..
The idea is by being able to navigate quickly without having to hunt,
scroll, click, click, scroll, and click, my train of thought is not
disrupted and I digest code much more quickly.
I think your idea about a skeleton application with base "user/role"
functionality is a good one; seems like most applications have that
doesn't it?
Cheers,
Chris
Date: Wed, 7 Feb 2007 23:03:44 -0700
From: "Thierry Thelliez" <[EMAIL PROTECTED]>
Subject: [Setools] Gjallar: extracting features
To: [EMAIL PROTECTED], "Software Engineering Tools for Squeak"
<[email protected]>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
For the last few days I have been trying to understand the Gjallar
code. I like the Seaside-Magma approach. As mentioned somewhere else
the code base could serve as an example for other applications.
Trying
to catchup with all this code is quite overwhelming.
From my point of view, it would be great to see a subset of the
application featuring just enought to have a user interface for the
administrator role to login and create other users (different roles).
The created users should be able to login/logout. This would be a
great starting point to demonstrate several aspects including the
Seaside-Magma approach. Most of the web applications I am interested
in start with these features.
Just some thoughts.
Thierry
------------------------------
_______________________________________________
Setools mailing list
[email protected]
http://lists.squeakfoundation.org/mailman/listinfo/setools
End of Setools Digest, Vol 9, Issue 2
*************************************
_______________________________________________
Setools mailing list
[email protected]
http://lists.squeakfoundation.org/mailman/listinfo/setools
_______________________________________________
Setools mailing list
[email protected]
http://lists.squeakfoundation.org/mailman/listinfo/setools
