Tim, Janko,
Post by TimMHow are you doing this?
Create a new directory. Unzip the stuff that Janko posted into it (creates two
sub-directories).
Fire up a clean D6 Pro pl1 image (I would expect that pl2 is just as good, but
haven't actually tried it). Saved that as a new image (called Aida) in my new
directory.
Explicitly loaded package Swazoo/Swazoo.pac. Accepted the warning[*].
Explicitly loaded package Swazoo/Swazoo-Resources.pac (don't know if that's
necessary).
([*] Actually. at this point I went and found the offending duplcate methods,
removed them from the package, saved it, and then started again from scratch --
but I can't see why that should make any difference to your problems. Janko,
you may not realise that it's important to fix this problem -- it's not just
cosmetic in Dolphin since the system doesn't restore the original versions of
these methods when you unload the package).
Explictly loaded package AIDAWeb/AIDAWeb.pac. Explictly loaded package
AIDAWeb/Swazoo-AIDA.pac. Explictly loaded package AIDAWeb/AIDA System
Changes.pac. (I didn't bother with the tests package)
(Janko, you may not know that you can add to the prerequisites of a package
explicitly if you want. The system automatically computes prerequisites by
tracking things like class references, but does not track dependencies which
are only via message sends. So you can add "manaual prerequisites" by right
clicking on a Package in the Package Browser, selecting "properties", selecting
the manualPrerequisites item in the list of properties, and then using the new
item (red asterix) button in the right-hand pane of the inspector). I have no
idea why OA still make this operation so obscure. It would seem much more
sensible for the manual prerequisites to be settable directly from the
"Prerequsites" tab -- as was suggested years ago ;-)
Tried the:
SwazooServer demoStart.
mantra. Found it didn't work. Started investigating by making the changes
detailed in my earlier post. In the process rediscovered Janko's fix for
#collection:tokensBasedOnAll:)
Having made those changes (without restarting or anything) the example now
works as advertised -- I could log in as admin/password (all lower-case). That
shows a fairly blank-looking screen until I select one of the options in the
sidebar -- Statistics, for instance.
If I don't log in then I can't get to any of the side-bar pages, but just keep
coming back to the login page.
Post by TimMOr are you just trying the tutorial, which doesn't look to have any of
the password stuff (interestingly, I guess the website demo doesn't
either?)
I have tried the tutorial /too/. I have to log in as admin before it will work
(the tutorial does mention that).
Post by TimMMyabe Chris has a thought - or do you have a suggestion as to how I can
help debug this...
Make the changes that I suggested earlier, and keep an eye on your Transcript.
You may (depending on your browser) find that you'll get occasional spontaneous
debug halts. That's just the system working correctly (for its current,
pre-alpha, state). It happens when Firefox (and maybe other browsers) time out
and close the persistent connections they use to multiplex HTTP 1.1 requests
over a single TCP/IP connection. Swazoo/AIDA seems to handle multiplexing
fine, but the error handling code gets confused by the SocketClosed exception.
You can just "resume" the dialogs when they pop up.
If you want to debug through the login attempt, then one place you could put a
breakpoint is in AIDASite>>answerTo:.
-- chris