Where to report Dolphin Swzoo unimplemented msg port problems?

Who supports the ports of Swazoo to Dolphin - or where do I report potential
problems?

I am using the package that came with the Aida port - which I think is one
of the latest.  In packaging a little app in Dolphin I was reminded of the
BrowseUnimplemented command and notice a few unimplemented messages in that
port. (Alternatively I could check that I am using the latest port - but
again not sure how?).

e.g. that browser shows me things like:

#acceptConnection - sends #errorString to an exception (which is not defined
in Dolphin)


Tim

Tim M escribió:
> Who supports the ports of Swazoo to Dolphin -

I did the last port, but I didn't test it in production, that's why the
status is "development".

> or where do I report potential problems?

If is dolphin related here or at swazoo mailing list.
<swazoo-devel at lists.sourceforge.net>

> I am using the package that came with the Aida port - which I think is
> one of the latest.  

I don't know if it uses the latest version, probably it's not.
<http://www.swazoo.org/download.html>

You can download the latest from:
<http://emaringolo.users.dolphinmap.net>

> In packaging a little app in Dolphin I was reminded
> of the BrowseUnimplemented command and notice a few unimplemented
> messages in that port. (Alternatively I could check that I am using the
> latest port - but again not sure how?).
>
> e.g. that browser shows me things like:
>
> #acceptConnection - sends #errorString to an exception (which is not
> defined in Dolphin)

In the latest port this method doesn't exist. Swazoo 1.1.4 uses SpError
and it's subclasses to handle exceptions.

Regards,

--
Esteban.

Hi Esteban,

> Tim M escribió:
>
>> Who supports the ports of Swazoo to Dolphin -
>>
> I did the last port, but I didn't test it in production, that's why
> the status is "development".


Hey thanks for doing this! Dolphin needs this kind of stuff to make it a
success (and thanks for running with the Seaside stuff too).

I have quickly loaded it in (a big thanks for providing STP files too!) however
I do notice one error in the transcript (after loading Sport and then Swazoo
- I'm also not too keen on the offending VW Filenames.pac living in the root
directory - do we know where it came from?):

Loading in package SPort 0.4 from repository
Error: SpFilename>>named: at line 5: undeclared 'VWFilename'
Loading in package VW Filenames 8 from repository
Loading in package MD5 0.001 from repository
Loading in package SPort Tests 0.4 from repository
Loading in package Swazoo-Compatibility 1.1.4 R1 from repository
Loading in package Swazoo-Headers 1.1.4 R1 from repository
Loading in package Swazoo-Server 1.1.4 R1 from repository
Loading in package Swazoo-Resources 1.1.4 R1 from repository
Loading in package Swazoo-Examples 1.1.4 R1 from repository
Loading in package Swazoo-Tests 1.1.4 R1 from repository

Thanks Tim

p.s. Ironically, I'm doing this to integrate CruiseControl.net with dolphin
to automate these kinds of clean loads a test for this kinds of transcript
errors ;-)

Tim M escribió:
> I have quickly loaded it in (a big thanks for providing STP files too!)
> however I do notice one error in the transcript (after loading Sport and
> then Swazoo - I'm also not too keen on the offending VW Filenames.pac
> living in the root directory - do we know where it came from?):

VW Filenames.pac is borrowed from Steve Waring's goodies, VisualWorks
reifies the concept of a Filename, which could be "a description" of the
file, SpFilename wraps a Filename (in VW), and emulates it's behavior,
so the straight path was to reuse what Steve already did.


Yes, there is an error in the order of the Packages. VW Filenames and
MD5 should be loaded before SPort. I have it fixed, i'll try to upload
it later.


> p.s. Ironically, I'm doing this to integrate CruiseControl.net with
> dolphin to automate these kinds of clean loads a test for this kinds of
> transcript errors ;-)

I don't know what cruise control is, but if adds value to Dolphin,
great! :-)

Regards,

--
Esteban.