Graphical Display of 100,000 objects

On 28.03.2006, at 20:18, Ron Teitelbaum wrote:

Best would be to have Kedama as an external package to load. But this
was not possible to do: Either SqueakLand with Kedama or no  
SqueakLand sync.
Refactoring Kedama was not possible to do in the short time (and it  
is, to be honest, not
my job). Thus I decided for adding Kedama for now.

As for the vm-plugin: I think you just need to get the kedama plugin  
and put
it into the path where the other plugins are and it should work.

To have it part of VMaker, Yoshiki would needs to coodinate that with
Tim, if he's interested in having the plugin be part of the standard vm.

      Marcus

On 28-Mar-06, at 11:04 AM, Marcus Denker wrote:
>
> As for the vm-plugin: I think you just need to get the kedama  
> plugin and put
> it into the path where the other plugins are and it should work.
That *should* be generally true. The plugin mechanism was designed to  
allow for internal and external plugins and all of them should work  
either way. For example, win32 VMs are typically delivered with all  
plugins made internal and this linked into the single .exe file. This  
is done because we know most win32 users are going to be terribly  
confused by a large number of files and wold probably delete most of  
them and then complain about stuff not working. Mac VMs come with  
most plugins made internal but some as external, which is probably  
historical - the osx bundle idea makes it easy to have a large  
collection of files hidden in what looks like a single file. The RISC  
OS vm application comes with all plugins external and uses the  
original application bundle idea to hide all the complexity. The unix  
vm... ech, I don't have the patience to care about unix anymore.

Note that an external plugin will override an internal one; so we can  
distribute bug fixes in plugins by sticking an external copy of (say)  
FilePlugin in the right place and next time FilePlugin is *loaded*  
the external one will be found and bound in. Note the *loaded*  
qualifier. If you are running an image that has done anything to use  
FilePlugin then the plugin is bound and you would have to explicitly  
unload it - SmalltalkImage current unloadModule: 'FilePlugin' -  
before it could be replaced with the new version. Plugins are  
*supposed* to be unloadable but I'd bet there is at least one that  
isn't, just on general principles.

>
> To have it part of VMaker, Yoshiki would needs to coodinate that with
> Tim, if he's interested in having the plugin be part of the  
> standard vm.
In general if a plugin is reasonably stable and reasonably broadly  
useful then it would be sensible to add it to the VMMaker package. A  
plugin still in early stages of development and undergoing rapid  
changes would not be a good candidate. A plugin for connecting to an  
obscure database only used by tapeworm biologists in Elbonia would  
probably not be.


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Make sure your code "does nothing" gracefully.

  Ron,

> The problem is that it appears that 10,000 turtles are still randomly
> placed.  I have blanks spots.  I tried 100,000 turtles and still had some
> blank spots.  Is there a way to remove the random placement of turtles and
> get an even distribution?  (I could probably figure this out on my own [I
> assume it's in the add turtle code], but if you have a trick up your sleeve,
> or a place to start, that makes it easier please let me know)

  The easiest thing is to drop a painting onto a Kedama World.  Draw a
big (bigger than 200x200) blob by the painting tool, and drop it onto
a Kedama World so that the painting covers it.  Then turtles are
created at all grid point of the Kedama World.

-- Yoshiki

On 28-Mar-06, at 11:30 AM, tim Rowledge wrote:

> Note that an external plugin will override an internal one; so we  
> can distribute bug fixes in plugins by sticking an external copy of  
> (say) FilePlugin in the right place and next time FilePlugin is  
> *loaded* the external one will be found and bound in.

To clarify on the  mac vm universal series of VMs 3.8.11bx  the  
plugin is first looked for in the bundle's resource folder, then  
externally in the Plugins folder outside the bundle. This was changed  
from 3.8.10 or earler because likely loose plugins floating about are  
powerpc only and won't load on the MacIntel boxes thus causing mass  
confusion. Therefore to override the supplied plugin  you need to  
read this note or earlier notes...

--
========================================================================
===
John M. McIntosh <[hidden email]> 1-800-477-2659
Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
========================================================================
===

Yoshiki,

Thank you.  That is a nice trick!

Ron Teitelbaum

  Tim,

  I couldn't have made up my mind, but now I think it is good idea to
include the Plugin into the VMMaker.  Especially because the
redesigned new version in Tweak is working so the old one can be frozen^^;

  Would you include the attached changeset?  Thank you!

-- Yoshiki