Loading Seaside 3.0 cripples System browser
Locked
Loading Seaside 3.0 cripples System browser
 
|
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 |
Re: Loading Seaside 3.0 cripples System browser
|
|
Charles,
I seem to remember that there was an issue revolving around latestVersion, so out of curiosity what is the result of printing: ((Smalltalk at: #ConfigurationOfSeaside30) project latestVersion) If it is not 3.0.6 then try an explicit load of version 3.0.6... ((Smalltalk at: #ConfigurationOfSeaside30) project version: '3.0.6') load If it is 3.0.6 then that is curious because when 3.0.6 was released it loaded cleanly into Pharo 1.3 (that was current at the time) .... Presumably the configurations have changed since then in such a way to break the Seaside load on Pharo1.3 ... I looked on the Pharo Jenkins server but apparently Pharo1.3 is no longer tested? So it's not possible to tell when the problem might have been introduced... When you see messages complaining about missing dependencies you have to be aware that things are not likely to be functional when the load finishes ... I think there have been some recent issues with the RFB configuration so presumably all of the problems haven't been ironed out yet. Dale ----- Original Message ----- | From: "Charles Monteiro" <[hidden email]> | To: [hidden email] | Sent: Thursday, October 6, 2011 8:01:24 PM | Subject: [Pharo-users] Loading Seaside 3.0 cripples System browser | | 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-tp3880813p3880813.html | Sent from the Pharo Smalltalk Users mailing list archive at | Nabble.com. | | |
Re: Loading Seaside 3.0 cripples System browser
|
|
When you see messages complaining about missing dependencies you have to be aware that things are not likely to be functional when the load finishes ... Yes, Dale, I understand that. I was only hoping it was stuff I didn't care about :). I have to say that every time I decide to play with Squeak I almost invariably have been unlucky and I encounter pre-req issues. Need to play with it more , I'm sure I don't have a properly large sample set to make any conclusions.
Anywho, let me be more detailed : Indeed, we are dealing with 3.0.6 see here: http://screencast.com/t/8bdHUciSw2S
First pre-req error: After proceeding thru error, second pre-req error: and for those that care, the pre-req loading issues have for one affected the browser so: re: Seaside I was able to setup an adaptor thru the Seaside control panel , and confirmed I could get to it via a browser , Seaside counter app worked fine. I'm also able to pop a class browser thru Seaside.
Let me know what I should do , thanks -Charles On Fri, Oct 7, 2011 at 12:04 AM, Dale Henrichs [via Smalltalk] <[hidden email]> wrote: Charles, Charles A. Monteiro www.monteirosfusion.com sent from the road |
|
|
In reply to this post by Charles Monteiro
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.
|
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 ----- Original Message ----- | From: "Tangaloor" <[hidden email]> | To: [hidden email] | 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-tp3880813p3896760.html | Sent from the Pharo Smalltalk Users mailing list archive at | Nabble.com. | | |
Re: Loading Seaside 3.0 cripples System browser
|
|
For OB in 1.3 you still need to load #bleedingEdge I think.
Norbert Am 12.10.2011 um 07:56 schrieb Dale Henrichs <[hidden email]>: > 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" <[hidden email]> > | To: [hidden email] > | 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-tp3880813p3896760.html > | Sent from the Pharo Smalltalk Users mailing list archive at > | Nabble.com. > | > | > |
|
|
In reply to this post by Dale Henrichs
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 |
|
|
In reply to this post by NorbertHartl
Thanks, Norbert.
If I explicitly load #bleedingEdge from ConfigurationOfOmniBrowser, will then running a load of latestVersion on ConfigurationOfSeaside30 override the loaded version of OmniBrowser?
From: Norbert Hartl [via Smalltalk] [ml-node+[hidden email]] Sent: Wednesday, October 12, 2011 2:44 AM To: Joel E. Wilson Subject: Re: Loading Seaside 3.0 cripples System browser For OB in 1.3 you still need to load #bleedingEdge I think.
Norbert Am 12.10.2011 um 07:56 schrieb Dale Henrichs <[hidden email]>: > 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 > |
Re: Loading Seaside 3.0 cripples System browser
|
|
In reply to this post by Tangaloor
> 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. FYI: No. In fact there is no such thing as the "Refactoring Browser". People common refer to the "Refactoring Engine" as the "Refactoring Browser". The original "Refactoring Browser" was broken for decades (nobody used it) and I removed it about 3 years ago from the refactoring code. The refactoring engine is just a model. OmniBrowser is independent of the refactoring engine and vice-versa. Only if you load the package OmniBrowser-Refactoring you connect the two and give the refactoring engine a view. AFAIK, OmniBrowser is the existing view for the refactoring engine at the moment. Lukas -- Lukas Renggli www.lukas-renggli.ch |
Re: Loading Seaside 3.0 cripples System browser
|
|
In reply to this post by Tangaloor
Am 12.10.2011 um 14:09 schrieb Tangaloor: No, it won't. Metacello does not downgrade...well, for all cases that I understand. Norbert
|
Re: Loading Seaside 3.0 cripples System browser
|
|
In reply to this post by Tangaloor
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" <[hidden email]> | To: [hidden email] | 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. | |
|
|
Well, I got past most of the RB and OB issues by doing this:
Gofer new
squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMetacello'; load. ((Smalltalk at: #ConfigurationOfMetacello) project version: #stable) load. Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load. ((Smalltalk at: #ConfigurationOfSeaside30) project version: #stable) load. Apparently, it's just a good idea to upgrade Metacello before doing anything else. Being new and using the One-Click Pharo image, I was just following the instructions that pop up when you evaluate 'DEVImageWorkspaces
openExternalProjectWorkspace.' It would maybe be a good idea if the instructions were updated to recommend upgrading Metacello before doing anything else.
Now, however, I'm getting this from ConfigurationOfOmniBrowser version122:
SmallInteger(Object)>>doesNotUnderstand: #add:
From: Dale Henrichs [via Smalltalk] [ml-node+[hidden email]] Sent: Wednesday, October 12, 2011 10:53 AM To: Joel E. Wilson Subject: Re: Loading Seaside 3.0 cripples System browser 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 |
«
Return to Pharo Smalltalk Users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |