Tangaloor, The OB dependency in Seaside3.0 is only for the one package Seaside-Tools-OmniBrowser which gives you a window to control your adaptors. Without Seaside-Tools-OmniBrowser you need to use an expression like the following to start the web service: WAKomEncoded startOn: 8080 There is no 'load everything except this package' function in Metacello (maybe I'll add that) so to get all of Seaside excluding the one package means that you have to explicitly load the other packages ... this is the step that I need to spend some time on ... the best answer is to add a group to the config... Dale ----- Original Message ----- | From: "Tangaloor" <tanga@tanga.org> | To: pharo-users@lists.gforge.inria.fr | Sent: Wednesday, October 12, 2011 5:01:10 AM | Subject: Re: [Pharo-users] Loading Seaside 3.0 cripples System browser | | | Thanks, Dale. | | I saw one of those threads: | http://forum.world.st/seaside-stable-on-pharo-13-td3746815.html | | And I'm sure I can find more detailed instructions when I go digging. | That thread above refers to me as a naive user, which is pretty | accurate. I'm pretty willing to learn how to configure using | command-line, though, so that doesn't bother me. The development | environment is one of the things that has attracked me to Squeak and | Pharo, though, and it would seem kind of a loss to not get the | benefits of the RefactoringBrowser, which I think depends on OB. | Also, how many of those naive benefits, besides the component | configuration, will go away? Do you lose the component halos and | other development tools? | | | From: Dale Henrichs [via Smalltalk] [ml-node+ [hidden email] ] | Sent: Wednesday, October 12, 2011 12:56 AM | To: Joel E. Wilson | Subject: Re: Loading Seaside 3.0 cripples System browser | | | | Tangaloor, | | Other systems have conditional compilation and Smalltalk has | conditional loading ... | | OmniBrowser and its eco system is very brittle ... it seems that they | OB is constantly breaking when the underlying system changes (not | surprising at one level), but that causes particular problems for | Seaside, because it must have one window that is written against OB | ... I think that the OB configuration is no longer maintained so it | is a shame that this is affecting the use of Seaside30... | | one can load without that particular OB dependency but you need to | understand a little more about Seaside and Metacello (you must | decide which packages you want over and above the Base system). | | I never load the full system anymore, because of the headaches that | OB causes ... it does seem to be constantly broken ... If I had my | druthers I would change the Seaside30 configuration so that it was | easy to exclude OB, but I am not the only one making decisions about | the config ... | | I am a bit busy for the next few days, but if you ping me at the end | of the week, I will publish the instructions for loading Seaside30 | without OB ... if you google around a bit you will probably find | several threads on this topic (and even quite possibly instructions | on how to load Seaside30 without OB:)... | | Dale | | | View this message in context: RE: Loading Seaside 3.0 cripples System | browser | Sent from the Pharo Smalltalk Users mailing list archive at | Nabble.com. |