On Everything applet code now available with CodeChat

This worked really well on my machine, the applet launched really quickly, and I found myself playing with it for an afternoon.
The codechat that goes along with it revealed a good deal of knowledge re. your code, and I think the project should be up for an award somewhere.
My own taste (and thats all it is) would prefer a more object oriented approach to the methods that get called. From a design pattern view the code on both the java applet and perl program would be easier to distribute if handled that way.
Interesting to see the 2 layers of a project. The presentation layer is cool, but I love the code view, it tells me more.

Great work,
Eric

Thanks Eric. Technically, yes. Most of what I do should be done in a
much more object oriented way. The coding is usually very sloppy. At
the end of the whole process, I could clean it up. Make it a bit more
presentable since I've been making the code available to the public
for a couple of years now. But leaving it in its messy state was
actually a conscious choice. Not just because it saves me the work of
cleaning it up but also because I feel that it reflects the way it's
created. That is, the fact that it starts as a rather simple idea but
then builds up over time. It's not a straightforward process but a
series of trial and error experiments. Some of the failures I even
leave in as commented lines just to give a hint at things I was
trying out. Indentation is frequently thrown off due to copying and
pasting bits of code from previous projects. The whole idea is to
handle the coding as something that will be seen and think about what
sort of messages you want to send with it. I don't release the code
to show off my programming skills. I don't think many people would be
very impressed. At least, I highly doubt that it's going to land me
any professional programming gigs. Perhaps there are elements that
benefit others by displaying my methods. But I don't think very many
people actually look at the code. I hope more people will, with the
CodeChat system but I also hope that others will show us their code
by using the CodeChat system.

best r.
Pall


On 16-Aug-07, at 2:28 AM, Eric Dymond wrote:

> This worked really well on my machine, the applet launched really
> quickly, and I found myself playing with it for an afternoon.
> The codechat that goes along with it revealed a good deal of
> knowledge re. your code, and I think the project should be up for
> an award somewhere.
> My own taste (and thats all it is) would prefer a more object
> oriented approach to the methods that get called. From a design
> pattern view the code on both the java applet and perl program
> would be easier to distribute if handled that way.
> Interesting to see the 2 layers of a project. The presentation
> layer is cool, but I love the code view, it tells me more.
>
> Great work,
> Eric
> +
> -> post: [email protected]
> -> questions: [email protected]
> -> subscribe/unsubscribe: http://rhizome.org/preferences/
> subscribe.rhiz
> -> give: http://rhizome.org/support
> +
> Subscribers to Rhizome are subject to the terms set out in the
> Membership Agreement available online at http://rhizome.org/info/
> 29.php
>




–
Pall Thayer
[email protected]

http://www.this.is/pallit

I think the evolution of the work that shows up in your codechat was what meade it so intriguing. It may not be *professional* code but it was really creative,and it gave me a chance to see how the work had evolved. This is so lacking in many presentationware projects where the artist hides behind the code.
In you're work we see the evolution of the creative work, and it leads to so many different streams of thought.
I can interrupt the development of the concept at any stage and think about it, react to it, and wonder.
Once again, great idea, and the applet is so weird in so many good ways. I love the way it forms itself, so slowly and in doing so creates anticipation and reveal-tion.
Eric