Load failure of Seaside3 into Squeak 5.2alpha

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

Load failure of Seaside3 into Squeak 5.2alpha

timrowledge
Just tried loading seaside into the current near-release squeak 5.2. It failed.

The problem occurs in MetacelloVersionConstructor>>#calculate:project: because the symbolicVersionMap dictionary looks like this -
a Dictionary(#bleedingEdge->'1.3.0-baseline' #development->'1.3.0-baseline' #'release1.0'->'1.0.12' #'release1.1'->'1.1.13.1' #'release1.2'->'1.2.7' #'release1.3'->'1.3.0' #stable->#release1 )
When doing the little dance near the end of the method we have block params 'symbolic' = #stable & 'original' = #release1 but then try to look up #release1 only to find it isn't there. I'm guessing that it should actually be #'release1.0', which would then find '1.0.12'.

But I really don't think I ought to mess a lot with this bit of code, since I've never had anything to do with mc development before. Best not to break everything for everyone...

In the debugger I risked 'fixing' the dictionary and seeing if things might proceed happily. It went on for a while and stopped during 'Loading Seaside-CoreJohanBrichau.875' because #greaseInteger is not implemented for Character. It is installed for Integer, Number and String, though the last would of course fail due to no Character implementation. So I added a wild guess of '^self asInteger' and proceeded.

This got me as far as initializing WAKeyGenerator class a bit later in the same package. This failed because
a) GRPlatform had not been initialized and thus returned nil for #current, which meant dNU: #newRandom was inevitable
b) Looks like there is no platform subclass to even make the following #newRandom work.

So there I am stuck. Current googling is not showing me anything that appears to explain the apparently missing class(es) etc.

Pointers?

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: PNG: Pass Noxious Gas


_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Reply | Threaded
Open this post in threaded view
|

Re: Load failure of Seaside3 into Squeak 5.2alpha

timrowledge


> On 2018-10-03, at 3:04 PM, tim Rowledge <[hidden email]> wrote:
>
> Just tried loading seaside into the current near-release squeak 5.2. It failed.

Eventually google-found http://forum.world.st/About-loading-Seaside-into-Squeak6-0a-17082-td4944271.html and tried loading into a 5.1 image. This appears to have worked after using HJH's defaultPlatformAttributes hack.

I guess the remaining question is really whether that will/should be incorporated.


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Useful random insult:- Hypnotized as a child and couldn't be woken.


_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Reply | Threaded
Open this post in threaded view
|

Re: Load failure of Seaside3 into Squeak 5.2alpha

Max Leske
Thanks Tim,

Interestingly, our build for Squeak 5.2 appears to work, with the
exception of one failing test. I'll investigate over the weekend.
Hopefully, your description well make initial debugging a bit easier for
me.


Cheers,
Max

On 4 Oct 2018, at 2:21, tim Rowledge wrote:

>> On 2018-10-03, at 3:04 PM, tim Rowledge <[hidden email]> wrote:
>>
>> Just tried loading seaside into the current near-release squeak 5.2.
>> It failed.
>
> Eventually google-found
> http://forum.world.st/About-loading-Seaside-into-Squeak6-0a-17082-td4944271.html 
> and tried loading into a 5.1 image. This appears to have worked after
> using HJH's defaultPlatformAttributes hack.
>
> I guess the remaining question is really whether that will/should be
> incorporated.
>
>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> Useful random insult:- Hypnotized as a child and couldn't be woken.
>
>
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Reply | Threaded
Open this post in threaded view
|

Re: Load failure of Seaside3 into Squeak 5.2alpha

Johan Brichau-2
In reply to this post by timrowledge
Can you confirm that the loading instructions you follow are these: https://github.com/SeasideSt/Seaside#install-in-squeak ?

It’s also probably best to install using the snippet that loads from github. That’s the one that is tested using CI, so it’s possible something got broken somewhere in the smalltalkhub configuration universe (as appears to be the case). We’re deprecating the load from smalltalkhub anyways in the upcoming release, 

Johan

On 4 Oct 2018, at 00:04, tim Rowledge <[hidden email]> wrote:

Just tried loading seaside into the current near-release squeak 5.2. It failed.

The problem occurs in MetacelloVersionConstructor>>#calculate:project: because the symbolicVersionMap dictionary looks like this -
a Dictionary(#bleedingEdge->'1.3.0-baseline' #development->'1.3.0-baseline' #'release1.0'->'1.0.12' #'release1.1'->'1.1.13.1' #'release1.2'->'1.2.7' #'release1.3'->'1.3.0' #stable->#release1 )
When doing the little dance near the end of the method we have block params 'symbolic' = #stable & 'original' = #release1 but then try to look up #release1 only to find it isn't there. I'm guessing that it should actually be #'release1.0', which would then find '1.0.12'.

But I really don't think I ought to mess a lot with this bit of code, since I've never had anything to do with mc development before. Best not to break everything for everyone...

In the debugger I risked 'fixing' the dictionary and seeing if things might proceed happily. It went on for a while and stopped during 'Loading Seaside-CoreJohanBrichau.875' because #greaseInteger is not implemented for Character. It is installed for Integer, Number and String, though the last would of course fail due to no Character implementation. So I added a wild guess of '^self asInteger' and proceeded.

This got me as far as initializing WAKeyGenerator class a bit later in the same package. This failed because
a) GRPlatform had not been initialized and thus returned nil for #current, which meant dNU: #newRandom was inevitable
b) Looks like there is no platform subclass to even make the following #newRandom work.

So there I am stuck. Current googling is not showing me anything that appears to explain the apparently missing class(es) etc.

Pointers?

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: PNG: Pass Noxious Gas


_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev


_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Reply | Threaded
Open this post in threaded view
|

Re: Load failure of Seaside3 into Squeak 5.2alpha

timrowledge
In reply to this post by Max Leske


> On 2018-10-03, at 10:17 PM, Max Leske <[hidden email]> wrote:
>
> Thanks Tim,
>
> Interestingly, our build for Squeak 5.2 appears to work, with the exception of one failing test. I'll investigate over the weekend. Hopefully, your description well make initial debugging a bit easier for me.

I'll try to do a load test with a plain 5.2 image and the changed defaultPlatformAttributes method. Squeak 5.2 is very near release so it would be good to have Seaside ready to go. I see that there is an actual SqueakMap entry for release 3.2 which I didn't even get to notice before.

The very basic stuff certainly works and I offered a fix for the 'browse' button problem in the control panel doohickey.

The load instructions I followed were *not* found on the github site (though the actual metacello invocation was the same) but via the squeak.org projects page (the 'quick install' link). It's worth noting that they are there and will need updating if/when anything changes. The install-for-squeak link in seaside.st leads to that squeak.org page. It might be better to refer to the SqueakMap entry?

As ever, when looking for information there is chaos in your googling. So many out of date pages get listed, confusion can ensue and live is not as much fun as it should be.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
In /dev/null no one can hear you scream


_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Reply | Threaded
Open this post in threaded view
|

Re: Load failure of Seaside3 into Squeak 5.2alpha

Max Leske
Hi Tim,

I've tested loading of Seaside with all of the methods you described:
- GitHub: works (3.2.5)
- Quick Install: works (3.2.5)
- SqueakMap: works (3.2.5)

I've tested this by creating an up to date Squeak-trunk image with
SmalltalkCI locally.
Can you give me a step by step instruction on how and wher you obtain
your 5.2 image until the point where you get an error? I didn't see a
single one and definitely did not have to hack the platform attributes.


We'll have to update the installation instructions for 3.3 to pull from
GitHub and not from SmalltalkHub. We'll also have to create a new
SqueakMap entry that fetches from GitHub.

The "Quick Install" thing seems out of place. Can we change that either
to the new invocation (the one that will point to GitHub) or,
preferrably, to point to GitHub instead? I can change the entry on
seaside.st but I don't know how I'd refer to the SqueakMap entry (or are
you suggesting to edit the Quick Install script to reference SqueakMap?
That would also be good, I guess. Still, I wouldn't know how).



Cheers,
Max

On 5 Oct 2018, at 4:57, tim Rowledge wrote:

>> On 2018-10-03, at 10:17 PM, Max Leske <[hidden email]> wrote:
>>
>> Thanks Tim,
>>
>> Interestingly, our build for Squeak 5.2 appears to work, with the
>> exception of one failing test. I'll investigate over the weekend.
>> Hopefully, your description well make initial debugging a bit easier
>> for me.
>
> I'll try to do a load test with a plain 5.2 image and the changed
> defaultPlatformAttributes method. Squeak 5.2 is very near release so
> it would be good to have Seaside ready to go. I see that there is an
> actual SqueakMap entry for release 3.2 which I didn't even get to
> notice before.
>
> The very basic stuff certainly works and I offered a fix for the
> 'browse' button problem in the control panel doohickey.
>
> The load instructions I followed were *not* found on the github site
> (though the actual metacello invocation was the same) but via the
> squeak.org projects page (the 'quick install' link). It's worth noting
> that they are there and will need updating if/when anything changes.
> The install-for-squeak link in seaside.st leads to that squeak.org
> page. It might be better to refer to the SqueakMap entry?
>
> As ever, when looking for information there is chaos in your googling.
> So many out of date pages get listed, confusion can ensue and live is
> not as much fun as it should be.
>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> In /dev/null no one can hear you scream
>
>
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Reply | Threaded
Open this post in threaded view
|

Re: Load failure of Seaside3 into Squeak 5.2alpha

Tobias Pape

> On 07.10.2018, at 11:00, Max Leske <[hidden email]> wrote:
>
> Hi Tim,
>
> I've tested loading of Seaside with all of the methods you described:
> - GitHub: works (3.2.5)
> - Quick Install: works (3.2.5)
> - SqueakMap: works (3.2.5)
>
> I've tested this by creating an up to date Squeak-trunk image with SmalltalkCI locally.
> Can you give me a step by step instruction on how and wher you obtain your 5.2 image until the point where you get an error? I didn't see a single one and definitely did not have to hack the platform attributes.

Thanks Max for the effort!

>
>
> We'll have to update the installation instructions for 3.3 to pull from GitHub and not from SmalltalkHub. We'll also have to create a new SqueakMap entry that fetches from GitHub.
>
> The "Quick Install" thing seems out of place. Can we change that either to the new invocation (the one that will point to GitHub) or, preferrably, to point to GitHub instead? I can change the entry on seaside.st but I don't know how I'd refer to the SqueakMap entry (or are you suggesting to edit the Quick Install script to reference SqueakMap? That would also be good, I guess. Still, I wouldn't know how).

It's here: https://github.com/squeak-smalltalk/squeak.org/blob/master/_projects/seaside.md

Full quote: =-=-=-=-=-=-=-=-=-=-=-=


---
title:          Seaside
img-src:        projects/seaside.png
href:           http://www.seaside.st/
quick-install: >
    Metacello new
        configuration: 'Seaside3';
        repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
        version: #stable;
        load: 'OneClick'.
quick-install-notes: >
    Make sure you have <a href="https://github.com/dalehenrich/metacello-work" target="_blank">Metacello</a> installed.
---
A layered set of abstractions over HTTP and HTML, that let you build highly interactive web applications.

<!--
It is ported to and maintained for several Smalltalk dialects.
-->


I'd propose =-=-=-=-=-=-=-=-=-=-=-=


---
title:          Seaside
img-src:        projects/seaside.png
href:           http://www.seaside.st/
quick-install: >
    Metacello new
        baseline:'Seaside3';
        repository: 'github://SeasideSt/Seaside:master/repository';
        load: 'OneClick'.
quick-install-notes: >
    Make sure you have <a href="https://github.com/dalehenrich/metacello-work" target="_blank">Metacello</a> installed.
---
A layered set of abstractions over HTTP and HTML, that let you build highly interactive web applications.

<!--
It is ported to and maintained for several Smalltalk dialects.
-->


Best regards
        -Tobias

>
>
>
> Cheers,
> Max
>
> On 5 Oct 2018, at 4:57, tim Rowledge wrote:
>
>>> On 2018-10-03, at 10:17 PM, Max Leske <[hidden email]> wrote:
>>>
>>> Thanks Tim,
>>>
>>> Interestingly, our build for Squeak 5.2 appears to work, with the exception of one failing test. I'll investigate over the weekend. Hopefully, your description well make initial debugging a bit easier for me.
>>
>> I'll try to do a load test with a plain 5.2 image and the changed defaultPlatformAttributes method. Squeak 5.2 is very near release so it would be good to have Seaside ready to go. I see that there is an actual SqueakMap entry for release 3.2 which I didn't even get to notice before.
>>
>> The very basic stuff certainly works and I offered a fix for the 'browse' button problem in the control panel doohickey.
>>
>> The load instructions I followed were *not* found on the github site (though the actual metacello invocation was the same) but via the squeak.org projects page (the 'quick install' link). It's worth noting that they are there and will need updating if/when anything changes. The install-for-squeak link in seaside.st leads to that squeak.org page. It might be better to refer to the SqueakMap entry?
>>
>> As ever, when looking for information there is chaos in your googling. So many out of date pages get listed, confusion can ensue and live is not as much fun as it should be.
>>
>> tim
>> --
>> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
>> In /dev/null no one can hear you scream
>>
>>
>> _______________________________________________
>> seaside-dev mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Reply | Threaded
Open this post in threaded view
|

Re: Load failure of Seaside3 into Squeak 5.2alpha

timrowledge
In reply to this post by Max Leske


> On 2018-10-07, at 2:00 AM, Max Leske <[hidden email]> wrote:
>
> Hi Tim,
>
> I've tested loading of Seaside with all of the methods you described:
> - GitHub: works (3.2.5)
> - Quick Install: works (3.2.5)
> - SqueakMap: works (3.2.5)
>

Hmm, interesting.

> I've tested this by creating an up to date Squeak-trunk image with SmalltalkCI locally.
> Can you give me a step by step instruction on how and wher you obtain your 5.2 image until the point where you get an error? I didn't see a single one and definitely did not have to hack the platform attributes.

Well it is/was just a recent (#18199 update level) squeak image. I loaded Metacello via the 'quick install snippet proffered on the squea.org/project page

Installer swasource
  project: 'SwaUtilities';
  addPackage: 'ConfigurationOfMetacello';
  install.

"Bootstrap Metacello Preview, using mcz files (#'previewBootstrap' symbolic version"
((Smalltalk at: #ConfigurationOfMetacello) project version: #'previewBootstrap') load.

and then went to load Seaside with the similar snippet
 
Metacello new
    configuration: 'Seaside3';
    repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
    version: #stable;
    load: 'OneClick'.

The only difference I can see with https://github.com/SeasideSt/Seaside#install-in-squeak is the last line using #load: 'OneClick' instead of #load. (As in https://github.com/squeak-smalltalk/squeak.org/blob/master/_projects/seaside.md)

>
>
> We'll have to update the installation instructions for 3.3 to pull from GitHub and not from SmalltalkHub. We'll also have to create a new SqueakMap entry that fetches from GitHub.

Sounds sensible. Don't forget to update the entires on SmalltalkHub (and any other places you can find!) to reflect this.

>
> The "Quick Install" thing seems out of place. Can we change that either to the new invocation (the one that will point to GitHub) or, preferrably, to point to GitHub instead? I can change the entry on seaside.st but I don't know how I'd refer to the SqueakMap entry (or are you suggesting to edit the Quick Install script to reference SqueakMap? That would also be good, I guess. Still, I wouldn't know how).

The squeak.org page is on github so you can do the usual edit and PR stuff. Personally, I think pointing people to SqueakMap is a better idea since that can automagically make sure Metacello is installed etc.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: CEQ: Corrupt and Erase Queue


_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Reply | Threaded
Open this post in threaded view
|

Re: Load failure of Seaside3 into Squeak 5.2alpha

Tobias Pape
Hi all

> On 07.10.2018, at 19:37, tim Rowledge <[hidden email]> wrote:
>
>
>
>> On 2018-10-07, at 2:00 AM, Max Leske <[hidden email]> wrote:
>>
>> Hi Tim,
>>
>> I've tested loading of Seaside with all of the methods you described:
>> - GitHub: works (3.2.5)
>> - Quick Install: works (3.2.5)
>> - SqueakMap: works (3.2.5)
>>
>
> Hmm, interesting.
>
>> I've tested this by creating an up to date Squeak-trunk image with SmalltalkCI locally.
>> Can you give me a step by step instruction on how and wher you obtain your 5.2 image until the point where you get an error? I didn't see a single one and definitely did not have to hack the platform attributes.
>
> Well it is/was just a recent (#18199 update level) squeak image. I loaded Metacello via the 'quick install snippet proffered on the squea.org/project page
>
> Installer swasource
>  project: 'SwaUtilities';
>  addPackage: 'ConfigurationOfMetacello';
>  install.
>
> "Bootstrap Metacello Preview, using mcz files (#'previewBootstrap' symbolic version"
> ((Smalltalk at: #ConfigurationOfMetacello) project version: #'previewBootstrap') load.

Yea. So the problem here is, that the Metacello Bootstrap somehow loads an old version of WebClient, which can cause all sort of problems.

This is the version I use when Preparing pre-made images for our in-house use:

"-=-=-=-=-="
Installer gemsource
        project: 'metacello';
        addPackage: 'ConfigurationOfMetacello';
        install.

"Bootstrap Metacello Preview, using mcz files (#'previewBootstrap' symbolic version"
((Smalltalk at: #ConfigurationOfMetacello) project
        version: #'previewBootstrap') load.

"Quickfix"
Installer squeak
        project: 'squeak51'; "<<<<<<<<<<<<<<<<<<<<<<<< or trunk. depending on the base image"
        install: 'SqueakSSL-Core';
        install: 'WebClient-Core';
        yourself.
       

"Load the Preview version of Metacello from GitHub"
(Smalltalk at: #Metacello) new
        configuration: 'MetacelloPreview';
        version: #stable;
        repository: 'github://dalehenrich/metacello-work:configuration';
        load.

"Now load latest version of Metacello"
(Smalltalk at: #Metacello) new
        baseline: 'Metacello';
        repository: 'github://dalehenrich/metacello-work:master/repository';
        get.
(Smalltalk at: #Metacello) new
        baseline: 'Metacello';
        repository: 'github://dalehenrich/metacello-work:master/repository';
        onConflict: [:ex | ex allow];
        load.

"This one is important because we have a minor issue with pragma-based Preferences going away without the Preferences noticing..."

"-=-=-=-=-="
Preferences removeAllPreferencesSuchThat: [:ea | ea provider == MCGitBasedNetworkRepository].
"-=-=-=-=-="


HTH
        -Tobias


>
> and then went to load Seaside with the similar snippet
>
> Metacello new
>    configuration: 'Seaside3';
>    repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
>    version: #stable;
>    load: 'OneClick'.
>
> The only difference I can see with https://github.com/SeasideSt/Seaside#install-in-squeak is the last line using #load: 'OneClick' instead of #load. (As in https://github.com/squeak-smalltalk/squeak.org/blob/master/_projects/seaside.md)
>
>>
>>
>> We'll have to update the installation instructions for 3.3 to pull from GitHub and not from SmalltalkHub. We'll also have to create a new SqueakMap entry that fetches from GitHub.
>
> Sounds sensible. Don't forget to update the entires on SmalltalkHub (and any other places you can find!) to reflect this.
>
>>
>> The "Quick Install" thing seems out of place. Can we change that either to the new invocation (the one that will point to GitHub) or, preferrably, to point to GitHub instead? I can change the entry on seaside.st but I don't know how I'd refer to the SqueakMap entry (or are you suggesting to edit the Quick Install script to reference SqueakMap? That would also be good, I guess. Still, I wouldn't know how).
>
> The squeak.org page is on github so you can do the usual edit and PR stuff. Personally, I think pointing people to SqueakMap is a better idea since that can automagically make sure Metacello is installed etc.
>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> Strange OpCodes: CEQ: Corrupt and Erase Queue
>
>
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Reply | Threaded
Open this post in threaded view
|

Re: Load failure of Seaside3 into Squeak 5.2alpha

Max Leske
In reply to this post by Tobias Pape
Thanks Tobias.

https://github.com/squeak-smalltalk/squeak.org/pull/24

Cheers,
Max


On 7 Oct 2018, at 19:15, Tobias Pape wrote:

>> On 07.10.2018, at 11:00, Max Leske <[hidden email]> wrote:
>>
>> Hi Tim,
>>
>> I've tested loading of Seaside with all of the methods you described:
>> - GitHub: works (3.2.5)
>> - Quick Install: works (3.2.5)
>> - SqueakMap: works (3.2.5)
>>
>> I've tested this by creating an up to date Squeak-trunk image with
>> SmalltalkCI locally.
>> Can you give me a step by step instruction on how and wher you obtain
>> your 5.2 image until the point where you get an error? I didn't see a
>> single one and definitely did not have to hack the platform
>> attributes.
>
> Thanks Max for the effort!
>
>>
>>
>> We'll have to update the installation instructions for 3.3 to pull
>> from GitHub and not from SmalltalkHub. We'll also have to create a
>> new SqueakMap entry that fetches from GitHub.
>>
>> The "Quick Install" thing seems out of place. Can we change that
>> either to the new invocation (the one that will point to GitHub) or,
>> preferrably, to point to GitHub instead? I can change the entry on
>> seaside.st but I don't know how I'd refer to the SqueakMap entry (or
>> are you suggesting to edit the Quick Install script to reference
>> SqueakMap? That would also be good, I guess. Still, I wouldn't know
>> how).
>
> It's here:
> https://github.com/squeak-smalltalk/squeak.org/blob/master/_projects/seaside.md
>
> Full quote: =-=-=-=-=-=-=-=-=-=-=-=
>
>
> ---
> title:          Seaside
> img-src:        projects/seaside.png
> href:           http://www.seaside.st/
> quick-install: >
>     Metacello new
>         configuration: 'Seaside3';
>         repository:
> 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
>         version: #stable;
>         load: 'OneClick'.
> quick-install-notes: >
>     Make sure you have <a
> href="https://github.com/dalehenrich/metacello-work"
> target="_blank">Metacello</a> installed.
> ---
> A layered set of abstractions over HTTP and HTML, that let you build
> highly interactive web applications.
>
> <!--
> It is ported to and maintained for several Smalltalk dialects.
> -->
>
>
> I'd propose =-=-=-=-=-=-=-=-=-=-=-=
>
>
> ---
> title:          Seaside
> img-src:        projects/seaside.png
> href:           http://www.seaside.st/
> quick-install: >
>     Metacello new
>         baseline:'Seaside3';
>         repository: 'github://SeasideSt/Seaside:master/repository';
>         load: 'OneClick'.
> quick-install-notes: >
>     Make sure you have <a
> href="https://github.com/dalehenrich/metacello-work"
> target="_blank">Metacello</a> installed.
> ---
> A layered set of abstractions over HTTP and HTML, that let you build
> highly interactive web applications.
>
> <!--
> It is ported to and maintained for several Smalltalk dialects.
> -->
>
>
> Best regards
> -Tobias
>
>>
>>
>>
>> Cheers,
>> Max
>>
>> On 5 Oct 2018, at 4:57, tim Rowledge wrote:
>>
>>>> On 2018-10-03, at 10:17 PM, Max Leske <[hidden email]> wrote:
>>>>
>>>> Thanks Tim,
>>>>
>>>> Interestingly, our build for Squeak 5.2 appears to work, with the
>>>> exception of one failing test. I'll investigate over the weekend.
>>>> Hopefully, your description well make initial debugging a bit
>>>> easier for me.
>>>
>>> I'll try to do a load test with a plain 5.2 image and the changed
>>> defaultPlatformAttributes method. Squeak 5.2 is very near release so
>>> it would be good to have Seaside ready to go. I see that there is an
>>> actual SqueakMap entry for release 3.2 which I didn't even get to
>>> notice before.
>>>
>>> The very basic stuff certainly works and I offered a fix for the
>>> 'browse' button problem in the control panel doohickey.
>>>
>>> The load instructions I followed were *not* found on the github site
>>> (though the actual metacello invocation was the same) but via the
>>> squeak.org projects page (the 'quick install' link). It's worth
>>> noting that they are there and will need updating if/when anything
>>> changes. The install-for-squeak link in seaside.st leads to that
>>> squeak.org page. It might be better to refer to the SqueakMap entry?
>>>
>>> As ever, when looking for information there is chaos in your
>>> googling. So many out of date pages get listed, confusion can ensue
>>> and live is not as much fun as it should be.
>>>
>>> tim
>>> --
>>> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
>>> In /dev/null no one can hear you scream
>>>
>>>
>>> _______________________________________________
>>> seaside-dev mailing list
>>> [hidden email]
>>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>> _______________________________________________
>> seaside-dev mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Reply | Threaded
Open this post in threaded view
|

Re: Load failure of Seaside3 into Squeak 5.2alpha

Max Leske
In reply to this post by timrowledge
Hi Tim, Tobias,

I've let this issue lie around after the change to Squeak website and
I'm not entirely sure if I need to do anything more. Tim, is this still
an open issue for you?


Cheers,
Max

On 7 Oct 2018, at 19:37, tim Rowledge wrote:

>> On 2018-10-07, at 2:00 AM, Max Leske <[hidden email]> wrote:
>>
>> Hi Tim,
>>
>> I've tested loading of Seaside with all of the methods you described:
>> - GitHub: works (3.2.5)
>> - Quick Install: works (3.2.5)
>> - SqueakMap: works (3.2.5)
>>
>
> Hmm, interesting.
>
>> I've tested this by creating an up to date Squeak-trunk image with
>> SmalltalkCI locally.
>> Can you give me a step by step instruction on how and wher you obtain
>> your 5.2 image until the point where you get an error? I didn't see a
>> single one and definitely did not have to hack the platform
>> attributes.
>
> Well it is/was just a recent (#18199 update level) squeak image. I
> loaded Metacello via the 'quick install snippet proffered on the
> squea.org/project page
>
> Installer swasource
>   project: 'SwaUtilities';
>   addPackage: 'ConfigurationOfMetacello';
>   install.
>
> "Bootstrap Metacello Preview, using mcz files (#'previewBootstrap'
> symbolic version"
> ((Smalltalk at: #ConfigurationOfMetacello) project version:
> #'previewBootstrap') load.
>
> and then went to load Seaside with the similar snippet
>
> Metacello new
>     configuration: 'Seaside3';
>     repository:
> 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
>     version: #stable;
>     load: 'OneClick'.
>
> The only difference I can see with
> https://github.com/SeasideSt/Seaside#install-in-squeak is the last
> line using #load: 'OneClick' instead of #load. (As in
> https://github.com/squeak-smalltalk/squeak.org/blob/master/_projects/seaside.md)
>
>>
>>
>> We'll have to update the installation instructions for 3.3 to pull
>> from GitHub and not from SmalltalkHub. We'll also have to create a
>> new SqueakMap entry that fetches from GitHub.
>
> Sounds sensible. Don't forget to update the entires on SmalltalkHub
> (and any other places you can find!) to reflect this.
>
>>
>> The "Quick Install" thing seems out of place. Can we change that
>> either to the new invocation (the one that will point to GitHub) or,
>> preferrably, to point to GitHub instead? I can change the entry on
>> seaside.st but I don't know how I'd refer to the SqueakMap entry (or
>> are you suggesting to edit the Quick Install script to reference
>> SqueakMap? That would also be good, I guess. Still, I wouldn't know
>> how).
>
> The squeak.org page is on github so you can do the usual edit and PR
> stuff. Personally, I think pointing people to SqueakMap is a better
> idea since that can automagically make sure Metacello is installed
> etc.
>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> Strange OpCodes: CEQ: Corrupt and Erase Queue
>
>
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Reply | Threaded
Open this post in threaded view
|

Re: Load failure of Seaside3 into Squeak 5.2alpha

timrowledge


> On 2018-11-11, at 6:30 AM, Max Leske <[hidden email]> wrote:
>
> Hi Tim, Tobias,
>
> I've let this issue lie around after the change to Squeak website and I'm not entirely sure if I need to do anything more. Tim, is this still an open issue for you?

I've run test loads just to see how it works for me now. Again, Squeak 5.2, RaspberryPi.

SqueakMap - dead easy; update the list of course. Pick Seaside. Click install.
I see it was even updated yesterday. Starts loading metacello etc. Loads Seaside. No problems. Web browser connects immediately. A+++ would install again.

Github, as pointed to by the https://squeak.org/projects/  page, where it points on to https://github.com/SeasideSt/Seaside page, where it points to https://github.com/dalehenrich/metacello-work, which points to https://github.com/dalehenrich/metacello-work where finally it tells me to 'Installer ensureRecentMetacello.'
Ok, that starts metacello loading. Wait a while. Oh, yes, go back to the github page for Seaside, copy & paste
 'Metacello new
baseline:'Seaside3';
 repository: 'github://SeasideSt/Seaside:master/repository';
 load'
Seaside control panel is *not* helpfully initialised and the only 'adaptor' offered (a WATestServerAdaptor) does not appear to allow a browser to connect. The SqueakMap install provides a helpfully usable WAWebServerAdaptor.
C - would like to whine at vendor about delivery options.

'Quick Install' as pointed to by the https://squeak.org/projects/  page - where one is advised to use the same metacello incantation as above, but not given the nice simple 'Installer ensureRecentMetacello.' advise. In fact the metacello quick install on the same page is quite different, a bit confusing and possibly now out of date. Further, the project page is, as mentioned above, pointing to the wrong github and potentially worse, it is anchored such that you won't see the advice to jump to the current github page unless you scroll around.
D - offputting confusion and possible incorrect code loaded by following advice. Complain to credit card company and demand refund.

Looks like some improved stuff in the project & quick install texts are needed, probably something improved in the githup load script, and correcting of the links to the metacello github stuff. But the SM part is just clickalicious!

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
My computer NEVER cras


_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Reply | Threaded
Open this post in threaded view
|

Re: Load failure of Seaside3 into Squeak 5.2alpha

Max Leske
Thanks a lot for the effort Tim!

I'll try to improve the situation and let you know when I have done so.


Cheers,
Max

On 12 Nov 2018, at 2:31, tim Rowledge wrote:

>> On 2018-11-11, at 6:30 AM, Max Leske <[hidden email]> wrote:
>>
>> Hi Tim, Tobias,
>>
>> I've let this issue lie around after the change to Squeak website and
>> I'm not entirely sure if I need to do anything more. Tim, is this
>> still an open issue for you?
>
> I've run test loads just to see how it works for me now. Again, Squeak
> 5.2, RaspberryPi.
>
> SqueakMap - dead easy; update the list of course. Pick Seaside. Click
> install.
> I see it was even updated yesterday. Starts loading metacello etc.
> Loads Seaside. No problems. Web browser connects immediately. A+++
> would install again.
>
> Github, as pointed to by the https://squeak.org/projects/  page, where
> it points on to https://github.com/SeasideSt/Seaside page, where it
> points to https://github.com/dalehenrich/metacello-work, which points
> to https://github.com/dalehenrich/metacello-work where finally it
> tells me to 'Installer ensureRecentMetacello.'
> Ok, that starts metacello loading. Wait a while. Oh, yes, go back to
> the github page for Seaside, copy & paste
>  'Metacello new
> baseline:'Seaside3';
>  repository: 'github://SeasideSt/Seaside:master/repository';
>  load'
> Seaside control panel is *not* helpfully initialised and the only
> 'adaptor' offered (a WATestServerAdaptor) does not appear to allow a
> browser to connect. The SqueakMap install provides a helpfully usable
> WAWebServerAdaptor.
> C - would like to whine at vendor about delivery options.
>
> 'Quick Install' as pointed to by the https://squeak.org/projects/ 
> page - where one is advised to use the same metacello incantation as
> above, but not given the nice simple 'Installer
> ensureRecentMetacello.' advise. In fact the metacello quick install on
> the same page is quite different, a bit confusing and possibly now out
> of date. Further, the project page is, as mentioned above, pointing to
> the wrong github and potentially worse, it is anchored such that you
> won't see the advice to jump to the current github page unless you
> scroll around.
> D - offputting confusion and possible incorrect code loaded by
> following advice. Complain to credit card company and demand refund.
>
> Looks like some improved stuff in the project & quick install texts
> are needed, probably something improved in the githup load script, and
> correcting of the links to the metacello github stuff. But the SM part
> is just clickalicious!
>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> My computer NEVER cras
>
>
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Reply | Threaded
Open this post in threaded view
|

Re: Load failure of Seaside3 into Squeak 5.2alpha

Max Leske
In reply to this post by timrowledge
Hi Tim,

Thanks again for you help.

On 12 Nov 2018, at 2:31, tim Rowledge wrote:

>> On 2018-11-11, at 6:30 AM, Max Leske <[hidden email]> wrote:
>>
>> Hi Tim, Tobias,
>>
>> I've let this issue lie around after the change to Squeak website and
>> I'm not entirely sure if I need to do anything more. Tim, is this
>> still an open issue for you?
>
> I've run test loads just to see how it works for me now. Again, Squeak
> 5.2, RaspberryPi.
>
> SqueakMap - dead easy; update the list of course. Pick Seaside. Click
> install.
> I see it was even updated yesterday. Starts loading metacello etc.
> Loads Seaside. No problems. Web browser connects immediately. A+++
> would install again.
>
> Github, as pointed to by the https://squeak.org/projects/  page, where
> it points on to https://github.com/SeasideSt/Seaside page, where it
> points to https://github.com/dalehenrich/metacello-work, which points
> to https://github.com/dalehenrich/metacello-work where finally it
> tells me to 'Installer ensureRecentMetacello.'
> Ok, that starts metacello loading. Wait a while. Oh, yes, go back to
> the github page for Seaside, copy & paste
>  'Metacello new
> baseline:'Seaside3';
>  repository: 'github://SeasideSt/Seaside:master/repository';
>  load'
> Seaside control panel is *not* helpfully initialised and the only
> 'adaptor' offered (a WATestServerAdaptor) does not appear to allow a
> browser to connect. The SqueakMap install provides a helpfully usable
> WAWebServerAdaptor.
> C - would like to whine at vendor about delivery options.

I've improved the loading instructions for Squeak and opened an issue
for control panel initialisation and adaptor installation:
https://github.com/SeasideSt/Seaside/issues/1074.

>
> 'Quick Install' as pointed to by the https://squeak.org/projects/ 
> page - where one is advised to use the same metacello incantation as
> above, but not given the nice simple 'Installer
> ensureRecentMetacello.' advise. In fact the metacello quick install on
> the same page is quite different, a bit confusing and possibly now out
> of date. Further, the project page is, as mentioned above, pointing to
> the wrong github and potentially worse, it is anchored such that you
> won't see the advice to jump to the current github page unless you
> scroll around.
> D - offputting confusion and possible incorrect code loaded by
> following advice. Complain to credit card company and demand refund.

I've created a pull request for squeak.org with improvements:
https://github.com/squeak-smalltalk/squeak.org/pull/26.


Cheers,
Max

>
> Looks like some improved stuff in the project & quick install texts
> are needed, probably something improved in the githup load script, and
> correcting of the links to the metacello github stuff. But the SM part
> is just clickalicious!
>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> My computer NEVER cras
>
>
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev