Yes, but very slowly and incrementally, from bottom up.  I was hoping to
provide a command pattern interface to the base and allow others to add the
functionality to the browser as they need.  But my first job is test.
(Actually my first job is my day job.  Then comes test.)  I want to
eliminate ambiguity from the vw version and also understand how I can factor
out the platform dependencies between the versions.  Then, with all that
solved, you'll see me add the functionality into the whisker browser while
others can add it to the regular browsers.

This all depends on continued existence of free time under my new job.  It's
also hard to work against a moving target, so when I finish test I'm going
to take the most readily available release and implement it there.  So by
the time I'm done, it may take some effort to bring the code into the newer
versions.  There are other important things to handle, i.e., namespaces.
Even VW/BR haven't figured these problems out.

-John

> -----Original Message-----
> From: A.Kuckartz at lilly.ping.de [mailto:A.Kuckartz at lilly.ping.de]
> Sent: Sunday, June 18, 2000 2:51 PM
> To: squeak at cs.uiuc.edu
> Cc: A.Kuckartz at ping.de
> Subject: Refactor browsers (Re: Wanna do something?)
>
>
> > Refactor browsers
>
> I am working on this. I am especially interested
> in removing duplicate code and decreasing method sizes
> in Browser and PackageBrowser and adding Drag-and-Drop
> support to PackageBrowser.
>
> Please send suggestions for a better name than
> PackageBrowser by private mail.
>
> Is anyone working on the Refactoring Browser?
>
> Andreas
>
>