headers
Nigel Hamilton | 17 Jan 2006 08:00

Developments

HI,

 	It's great to see everything that's happened since I've been away.

 	Uwe had a "power" Friday night and it seems we're well on the road 
to a Catalyst version of the Care-O-Meter. It's looking really good and 
I'm learning lots about Catalyst / TT etc.

 	Marcel is plowing away on the Thing Registry and 
downloading/install subsystem.

 	So it's all coming along! ;-)

 	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.

;-)

Nigel Hamilton
Turbo10 Metasearch Engine
(Continue reading)

Permalink | Reply |
headers
Marcel Holan | 20 Jan 2006 18:45

Re: Developments

On Tue, Jan 17, 2006 at 07:00:32AM +0000, Nigel Hamilton wrote:
> 	Marcel is plowing away on the Thing Registry and 
> downloading/install subsystem.

Yeah! This is just to tell you, that I'm still at it. Hopefully with a
commit this weekend.

It does already handle both tgz and zip archives, does disambiguation
(if there are more things of the same name), and installs the thing
under ~/.goo/things/

Right now I have just made some well formed and some malformed tgz and
zip archives for test purposes. Real things would help. This is what
I'd need most now, because only some reference things will enable me
to finish the tests.

Marcel
Permalink | Reply |
headers
Marcel Holan | 21 Jan 2006 19:43

Re: Developments

On Fri, Jan 20, 2006 at 05:45:40PM +0000, Marcel Holan wrote:
> Yeah! This is just to tell you, that I'm still at it. Hopefully with a
> commit this weekend.

commit is in svn.

The API for installing anything that's in store or a specific thing to
~/.goo/things is in place. Ignore debug messages as of now. I guess
we'll have to implant the call to the installation API to the goo.pl
anyway.

any thing that's in store
------------------------------------------------------------
mh <at> sol:~/Goo> goo -i
INSTALL HOOK
Filename:
[1] Name:   sth.goo
    Author: Marcel Holan (mh@...)
    URL:    http://admin.petamem.com/goo-things/sth/sth-1.4.ZIP

[2] Name:   bad.goo
    Author: Marcel Holan (mh@...)
    URL:    http://admin.petamem.com/goo-things/bad/bad-0.0.1.tar.gz

[3] Name:   pm.goo
    Author: Marcel Holan (mh@...)
    URL:    http://admin.petamem.com/goo-things/pm2/pm-0.4.zip

[4] Name:   pm.goo
    Author: Marcel Holan (mh@...)
(Continue reading)

Permalink | Reply |
headers
Marcel Holan | 18 Jan 2006 15:06

goo vs. goo.pl

Hi Nigel,

could you please anlighten me about the goo vs. goo.pl status in the
bin directory? It seems both mean the same thing, but have forked.
Moreover, I'm not able to get goo.pl to run, always get a

sol:/tmp/Goo-0.09 # goo.pl -i pm.goo
No action handler found in /root/.goo/things/goo/goo.goo config file
for action: i. Add a new action handler.

I'll finish the thing DL mechanism in goo but then we probably need to
backport/"forward-port" some code and get rid of one of the
goo-binaries.

Marcel
Permalink | Reply |
headers
Nigel Hamilton | 18 Jan 2006 15:54
Favicon

Re: goo vs. goo.pl

HI Guys,

>
> could you please anlighten me about the goo vs. goo.pl status in the
> bin directory?

 	I think we had "goo" so the user could type "goo" instead of 
"goo.pl". We will always need a "goo" alias to the main action dispatcher. 
However, this is changing dramatically right now. In the new Care[O]Meter 
goo.cgi is playing the role of dispatcher (i.e,. like goo.pl) and Uwe is 
now putting this mechanism into the MVC Catalyst dispatching mechanism. So 
this is in a state of flux at the moment.

 	But we need to unify the mechanism for performing actions on 
Things. I think/hope we can unify the commandline action dispatcher (i.e., 
goo.pl / goo) with the URL dispatcher (i.e., goo.cgi) - I'm sure there is 
a sweet solution here. ;-)

 	I'm currently working on getting Perl Module Things working again 
and I plan to integrate my changes into the pre-Catalyst version of the 
CareOMeter here:

 	http://thegoo.org/svn/index.cgi/Goo/browse/Goo/web/

 	And then with Uwe's help (?) port it to Catalyst if it looks like 
a good fit? I hope to get basic functions ([C]ompile, [R]un, [E]dit) 
working by the end of the week. I'm really missing coding with The Goo -- 
so this is care_factor 10 on my Care[O]Meter!! ;-)

 	I can see already I need to pack up some supporting modules (e.g.,
(Continue reading)

Permalink | Reply |
headers
Uwe Voelker | 18 Jan 2006 16:12
Picon
Picon

Re: goo vs. goo.pl

>     And then with Uwe's help (?) port it to Catalyst if it looks like a
> good fit? I hope to get basic functions ([C]ompile, [R]un, [E]dit)
> working by the end of the week.

Of course I will help you. But not before the 25th. I stopped working on
the Catalyst port (I think edit is broken and sending mails is missing).
Sorry.

I will be back at the end of January.

> mechanism for distributing the core Goo. If we go for Catalyst I wonder
> if there is a clear/clean way to package an application? And a clean way
> of adding extra registered Things to it? Any ideas?

Devel::ebug (http://search.cpan.org/~lbrocard/Devel-ebug-0.45/) is a
Catalyst application too. So it is possible :-)

Extra Things would be Models (right?) which are like normal perl
modules. I see no problems in making them pluggable.

Bye,
Uwe
Permalink | Reply |
headers
Nigel Hamilton | 18 Jan 2006 16:26
Favicon

Re: goo vs. goo.pl

Hi Uwe,

>>     And then with Uwe's help (?) port it to Catalyst if it looks like a
>> good fit? I hope to get basic functions ([C]ompile, [R]un, [E]dit)
>> working by the end of the week.
>
> Of course I will help you. But not before the 25th. I stopped working on
> the Catalyst port (I think edit is broken and sending mails is missing).
> Sorry.
>
 	Cool! Ok. No probs. This gives me time to get the full Perl Module 
Thing working.

> I will be back at the end of January.
>
>> mechanism for distributing the core Goo. If we go for Catalyst I wonder
>> if there is a clear/clean way to package an application? And a clean way
>> of adding extra registered Things to it? Any ideas?
>
> Devel::ebug (http://search.cpan.org/~lbrocard/Devel-ebug-0.45/) is a
> Catalyst application too. So it is possible :-)
>

 	OK. I'll check out the packaging of it.

> Extra Things would be Models (right?) which are like normal perl
> modules. I see no problems in making them pluggable.
>
 	OK. More learning to be done here --- but in theory could we make 
a Catalyst-plugabble-Thing-Registry-Thing? Is there an existing "format"
(Continue reading)

Permalink | Reply |

Gmane