16 Mar 2006 07:41
[The Goo Blog] Goo Wobble
On the weekend I wondered if re-implementing the IDE-like features of The Goo was really a good idea? Was I wasting my time? Reinventing the wheel? Am I nuts?
So I downloaded "Eclipse", the IDE of the moment, and installed the Perl EPIC plugin. The raison d'etre of The Goo is to help programmers stick Things together, and there is one feature I simply can't do without: the ability to traverse the structural associations in your program. For example, I often want to traverse the inheritance hierarchy - what's in the superclass? When I clicked on the "Outline View" in Eclipse it took me no further than the program itself. I'm sure the class browser is more impressive for Java programs but for Perl programs I came to a deadend fast.
I don't know about you but my programs hardly ever work in isolation - they always involve other Things. When I write a program I often have to context switch between these Things (e.g., program -> output, program -> file, program -> database, program -> log, program -> shell, program -> other programs etc). The Goo should help you to make all these context switches - fast.
So I closed Eclipse, noted the stream of uncaught Java exceptions in my console, and jumped back into the bosom of The Goo. No more wobbles.
--
Posted by Nigel Hamilton to The Goo Blog at 3/16/2006 08:13:00 AM
So I downloaded "Eclipse", the IDE of the moment, and installed the Perl EPIC plugin. The raison d'etre of The Goo is to help programmers stick Things together, and there is one feature I simply can't do without: the ability to traverse the structural associations in your program. For example, I often want to traverse the inheritance hierarchy - what's in the superclass? When I clicked on the "Outline View" in Eclipse it took me no further than the program itself. I'm sure the class browser is more impressive for Java programs but for Perl programs I came to a deadend fast.
I don't know about you but my programs hardly ever work in isolation - they always involve other Things. When I write a program I often have to context switch between these Things (e.g., program -> output, program -> file, program -> database, program -> log, program -> shell, program -> other programs etc). The Goo should help you to make all these context switches - fast.
So I closed Eclipse, noted the stream of uncaught Java exceptions in my console, and jumped back into the bosom of The Goo. No more wobbles.
--
Posted by Nigel Hamilton to The Goo Blog at 3/16/2006 08:13:00 AM
It only took 1/2 an hour to get all the modules installed and
started. Catalyst does a good job of telling you what's going on including
timing the transaction:
[Thu Feb 16 10:51:29 2006] [catalyst] [debug]
**********************************
[Thu Feb 16 10:51:29 2006] [catalyst] [debug] * Request 19 (0.052/s)
[16592]
[Thu Feb 16 10:51:29 2006] [catalyst] [debug]
**********************************
[Thu Feb 16 10:51:29 2006] [catalyst] [debug] Found sessionid
"dcc4bc2b00b51da9985a465a02cf3f7939353ac9" in cookie
[Thu Feb 16 10:51:29 2006] [catalyst] [debug] "GET" request for
"thing/edit/241" from "127.0.0.1"
[Thu Feb 16 10:51:29 2006] [catalyst] [debug] Path is "thing/edit"
[Thu Feb 16 10:51:29 2006] [catalyst] [debug] Arguments are "241"
[Thu Feb 16 10:51:29 2006] [catalyst] [debug] Restored session
"dcc4bc2b00b51da9985a465a02cf3f7939353ac9"
[Thu Feb 16 10:51:34 2006] [catalyst] [debug] Rendering template
"thing/edit.html"
[Thu Feb 16 10:51:34 2006] [catalyst] [info] Request took 4.359979s
(0.229/s)
.------------------------------------------------------------------+-----------.
| Action | Time
|
+------------------------------------------------------------------+-----------+
| /auto |
0.000999s |
| /thing/edit |
4.336160s |
| /end |
0.005652s |
| -> Goo::View::TT->process |
0.004506s |
'------------------------------------------------------------------+-----------'
So rendering the edit page is taking 4.35 seconds? Any ideas? This
should take < 1 sec.
I'm trying to decide on going with Catalyst or our own bespoke
webserver: Sparky. I'd rather go with Catalyst but it must be quick.
Nige
Nigel Hamilton
Turbo10 Metasearch Engine
email: 
I'm going to start getting the development environment back by
bridging care-o-meter -> elinks -> nano/emacs -> perl .. and this will
then feedback into the refactoring that needs to happen when old-Goo meets
new-Goo (Catalyst, elinks, database things etc). So there's lots of design
knots to be tied back together but I'm sure there's a way.
Nige
p.s. there may be a FireFox extension that can perform local CGI execution
/ call external editor in-situ - if not we could always make one -
this means people who want to stay in a "graphical" environment could.
RSS Feed
