<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Georgia">The pool approach is probably good, but I'm
always a little leery of things stored in different ways and
places. Since the system browser, optimized for looking at classes
and methods, is the primary tool </font>for most of us, I tend to
prefer ways to work within that context. Defining pool variables and
then defining methods to return those variables does seem a bit
much, but what about dispensing with the pool variables and
auto-generating methods like:<br>
<br>
brownWool <br>
<br>
^#(35 12)<br>
<br>
These methods could be grouped in categories to facilitate browsing
for interesting textures/objects/whatchamacallums. For most of us
browsing for senders is a bit more natural than browsing for
references to pool variables. FWIW.<br>
<br>
Cheers,<br>
Bob<br>
<br>
<br>
<div class="moz-cite-prefix">On 3/6/13 9:43 AM, Louis LaBrunda
wrote:<br>
</div>
<blockquote cite="mid:t2lej8pad48tcafueoq2qa3h47uheofm5d@4ax.com"
type="cite">
<pre wrap="">Yes it is. But at the time I thought (my mistake) Bert wanted/suggested
that I create instance side messages to his Minecraft class. That would
require it having the pool dictionary defined before the methods could be
added and I kind of wanted it to be all automatic. As it turns out Bert is
happy with just the pool dictionary and people can add/use it wherever they
like.
</pre>
</blockquote>
<br>
</body>
</html>