Colin Putney wrote:

Here's what I do:

1. Install Seaside
2. Install Swazoo-HTTP
3. Install Swazoo-Listener
4. 'SwazooSeaside startOn: 8000'

Much simpler than Comanche.

Colin

Hi Colin:

I've tried today (first time) with Swazoo and made your steps without problems, but after step 4 how is supposed I access to Seaside?

I've tried with http://localhost:8000/seaside/config, http://localhost:8000/SwazooSeaside/seaside/config, http://localhost:8000/SwazooSeaside, etc but ever I get a 404 Not Found.

I'm trying in a 3.9 image.

Thanks in Advance.

gsa.

Benjamin Pollack wrote:

On Wed, 22 Dec 2004 06:54:19 -0300, German Arduino gsa@softhome.net wrote:

...

I've tried today (first time) with Swazoo and made your steps without problems, but after step 4 how is supposed I access to Seaside?

The configuration pane is at http://localhost:8000/confg . Basically, all the URLs are the same as Comanche, except without the /seaside part. You can chancge that by modifying the adaptor class if you wish.

--Benjamin

Thanks Benjamin.

Totally not my experience - you apparently need Dynamic-something first, (but Monticello before all that), then KomancheServices, but not KomanchePackages, before KomancheHttpServer, then Seaside

I don't understand YTF I can't say "I want a web server" and get a web server.

Incidentally, does swazoo not set itself up as a startup/shutdown class? I just saved and quit, then reloaded the image and the UI is frozen.

Starting over......

On Dec 19, 2004, at 1:38 PM, Cees de Groot wrote:

Strange. I usually just grab it through SqueakMap and everything works as advertised...

On Sun, 19 Dec 2004 13:10:48 -0800, Todd Blanchard tblanchard@mac.com wrote:

...

I've setup seaside with komanche in the past using squeak. But Komanche has become really insane to get installed right. So many pre-requisites. I'd say 9 out of 10 times I leave something out in the install chain and have to start over. So I'm sick of komanche.

---

Seaside mailing list Seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/listinfo/seaside

Fixed it - perhaps someone would be good enough to add this to the package?

On Dec 19, 2004, at 2:14 PM, John Pierce wrote:

...

Incidentally, does swazoo not set itself up as a startup/shutdown class? I just saved and quit, then reloaded the image and the UI is frozen.

Yep -- that was my experience too. I guess I would have figured out what was going on and submitted a changeset or the like, but I just went back to the web server that seems to be out of favor here (Komanche) -- because it works when restarting an image -- sorry for being lazy on this one -- if I get a moment, maybe I will look at Swazoo again.

Regards,

John _______________________________________________ Seaside mailing list Seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/listinfo/seaside

On Sun, 19 Dec 2004 14:05:46 -0800, Todd Blanchard tblanchard@mac.com wrote:

Totally not my experience - you apparently need Dynamic-something first, (but Monticello before all that), then KomancheServices, but not KomanchePackages, before KomancheHttpServer, then Seaside

Surely this is just a matter of someone putting together a script that issues a few install commands to SqueakMap, and posting it as "Comanche Installer" or something like that?

Avi

Hi fellas!

"Germán S. Arduino" gsa@softhome.net wrote:

Komanche was installing without problems a lot of time......until certains changes to "enhance" dependences and "published", and so (I believe that nothing related to his functionality) ..........I suspect Göran has a response and knows with detail this history, but don't know if he read this list.

I read it. :)

Yes, I repackaged KomHttpServer (with help of others) as clean Monticello packages to get away from old stuff Stephen had made that interfered with SM. But I can't say I find it *that* hard to install. The description on KomHttpServer says:

"Prerequisite packages: KomServices (which in turn needs DynamicBindings and, if you are using a pre-3.7-image, Named Process) "

So to get KomHttpServer installed in 3.7+ you just:

1. Install DynamicBindings. 2. Install KomServices. 3. Install KomHttpServer.

That should work. Also note that there are other packages depending on KomServices so there is a clear point in keeping these three packages separate.

regards, Göran

PS. Single install will come to us when I get the dependency stuff out. Yes, working on it.

Hi!

German Arduino gsa@softhome.net wrote:

goran.krampe@bluefish.se wrote:

...

pre-3.7-image, Named Process) "

So to get KomHttpServer installed in 3.7+ you just:

1. Install DynamicBindings.
2. Install KomServices.
3. Install KomHttpServer.

Hi Göran!

A long time without "seeing" you (at IRC I mean).

Yeah, but I am there now. :) At least on my day time.

I remember problems installing in 3.7, but can't test again right now.

However I've tested in a 3.9 image and step 3 *don't works*

Ok, I will retest 3.7, 3.8 and 3.9 now.

If I try to install KomHttpServer 7.x I get *key not found* and if I try with 6.x version I get: *bad signature 07000017 at position 18686*

Eh... ok.

This, without mention the *very* annoying msgs "not published ..."

That is because the 6.x sar file has scripts in it that doesn't play well with SM.

I personally think that is a bad thing to have that problems with a heavily used product as Komanche.

Sure, but I am trying my best here. I thought it was working fine.

Let my know if I can help in some manner.

I will get back to you when I have tested it myself.

regards, Göran

chris@workinglinux.com wrote:

Ummm, I have a 3.6 image that I did a 'load all code updates' and 'upgrade all installed packages' before I tried to install. I saw those instructions in the SqueakMap, and followed them.

It works fine under 3.7. I don't expect Tomcat to run under Java 1.2 anymore...Seaside/Comanche are of similar ilk. They generally stay with the latest stable version of Squeak...currently 3.7. Is there another factor motivating you to work with 3.6? If so, you can probably make things work but I wouldn't expect it to be as easy as under 3.7. It is likely that things can be made to work by loading an older version of KomHttpServer (and maybe other packages too?). Others would certainly know more about it than me...I'm just here to encourage you to keep at it.

When I tried to evaluate all that whole start up script, I got a message saying that Object didn't understand the initialize message. ModuleAssembly does 'super initalize', which got passed all the way to Object.

I vaguely recall that new now, as of 3.7, automatically sends initialize and Object has a default empty version. So, add:

initialize ^self

to Object...that will take care of this particular problem.

I commented out that 'super initialize', and got the same message from ModCore. At that point, I quit spending time on it - I figured I was missing something obvious since I am a n00b to all this.

Don't give up! Seaside is worth it :-) I hope you can either switch to 3.7 or find the determination to get things working under 3.6.

I must be a total dork, because when I try to use SwazooSeaside, my web browser reports 'page contains no data'. Sheesh.

Nope, or if so than I am too... The Universes effort seeks to remedy this for future releases of Squeak (then package releases will be more carefully tied to Squeak image versions).

*Sigh*

Been there... :-)

David

Hi!

Sorry for not noticing this thread earlier.

"C. David Shaffer" cdshaffer@acm.org wrote:

chris@workinglinux.com wrote:

...

Ummm, I have a 3.6 image that I did a 'load all code updates' and 'upgrade all installed packages' before I tried to install. I saw those instructions in the SqueakMap, and followed them.

It works fine under 3.7. I don't expect Tomcat to run under Java 1.2 anymore...Seaside/Comanche are of similar ilk. They generally stay with the latest stable version of Squeak...currently 3.7. Is there another factor motivating you to work with 3.6? If so, you can probably make things work but I wouldn't expect it to be as easy as under 3.7. It is likely that things can be made to work by loading an older version of KomHttpServer (and maybe other packages too?). Others would certainly know more about it than me...I'm just here to encourage you to keep at it.

...

When I tried to evaluate all that whole start up script, I got a message saying that Object didn't understand the initialize message. ModuleAssembly does 'super initalize', which got passed all the way to Object.

I vaguely recall that new now, as of 3.7, automatically sends initialize and Object has a default empty version. So, add:

initialize ^self

to Object...that will take care of this particular problem.

Yes, and that may very well be the only thing. But darn, yes - the releases of KomHttpServer obviously then aren't marked correctly. I will take a look (currently it seems all releases are marked for 3.6, which obviously is wrong - this initialize thing appeared in 3.7).

...

I commented out that 'super initialize', and got the same message from ModCore. At that point, I quit spending time on it - I figured I was missing something obvious since I am a n00b to all this.

Don't give up! Seaside is worth it :-) I hope you can either switch to 3.7 or find the determination to get things working under 3.6.

...

I must be a total dork, because when I try to use SwazooSeaside, my web browser reports 'page contains no data'. Sheesh.

Swazoo I know nada about. :)

Nope, or if so than I am too... The Universes effort seeks to remedy this for future releases of Squeak (then package releases will be more carefully tied to Squeak image versions).

Yes, and also the new dependency model will also have a similar positive effect.

...

*Sigh*

Feel free to email privately if you need my more immediate response, I am a bit flooded these days. :)

regards, Göran