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 ----- Original Message ----- | From: "Tangaloor" <tanga@tanga.org> | To: pharo-users@lists.gforge.inria.fr | Sent: Tuesday, October 11, 2011 8:59:56 PM | Subject: Re: [Pharo-users] Loading Seaside 3.0 cripples System browser | | I'm also having this issue. I'm fairly new to Smalltalk and Pharo. | I've | used the Seaside One-click installer and don't remember there being | issues | with the System Browser there. I have tried running: | | Gofer new | squeaksource: 'MetacelloRepository'; | package: 'ConfigurationOfOmniBrowser'; | load. | | (ConfigurationOfOmniBrowser project latestVersion) load. | | and | | (ConfigurationOfOmniBrowser project version: #stable) load. | | And that seems to have a similar set of dependency issues. Also, | when you | dig into the version specs, it seems like it's grabbing #stable of | ConfigurationOfOmniBrowser. I admin that I don't know enough about | Metacello to know if that's just the version for the | ConfigurationOfOmniBrowser or if it calls out the specific Monticello | versions that it is supposed to be grabbing. It does seem like the | #stable | label would seem to be a moving target, though, and shouldn't | necessarily be | called out inside these package recipes. I'm new to this framework, | but | other systems that use auto-build and deployment delivery systems | often seem | to try and be very specific about the versions that are depended | upon. | | | Charles Monteiro wrote: | > | > I downloaded the Pharo 1.3 one click. | > | > I then attempted to load Seaside using the following mechanism: | > | > Gofer new | > squeaksource: 'MetacelloRepository'; | > package: 'ConfigurationOfSeaside30'; | > load. | > | > ((Smalltalk at: #ConfigurationOfSeaside30) project latestVersion) | > load. | > | > It complained twice about some package dependencies i.e. related to | > RBxxx | > packages. I proceeded through both and it seemingly terminated | > fine. | > Seaside was loaded including the Seaside control panel. However, | > doing a | > right mouse over the leftmost panel (Categories) resulted in an | > MNU. | > Also stuff like syntax highlighting became inactive. | > | > Is there a way to load the latest and greatest Seaside into Pharo | > 1.3 with | > "all" pre-req dependencies resolved ? i.e. how can I load Seaside | > clean ? | > | > | > thanks in advance | > | > -Charles | > | | | -- | View this message in context: | http://forum.world.st/Loading-Seaside-3-0-cripples-System-browser-tp3880813p... | Sent from the Pharo Smalltalk Users mailing list archive at | Nabble.com. | |