Seaside not loading css styles (but our fault)

Cool.

Don't use Swazoo, it doesn't work and some tests are broken. Use Kom or Zinc.

Lukas

On Friday, 23 September 2011, Martin Dias <[hidden email]> wrote:
> Hey! good news :) The styles are fine with latest version (of fuel package loader). We was doing something wrong when materializing classes.
> Now... we have some red tests in Seaside, and even worse, a test in Swazoo crashes my VM... so we have more debug to do!
> Thank you very much for your help. 
> Martín
>
> On Fri, Sep 23, 2011 at 2:09 AM, Philippe Marschall <[hidden email]> wrote:
>>
>> 2011/9/22 Mariano Martinez Peck <[hidden email]>:
>> > Well...
>> >
>> > http://localhost:2323/
>> >
>> > ->
>> >
>> > [22:50:51.466] GET http://localhost:2323/ [HTTP/1.1 200 OK 4ms]
>> > [22:50:51.513] GET http://localhost:2323/files/JQDeploymentLibrary/jQuery.js
>> > [HTTP/1.1 404 Not Found 2ms]
>> > [22:50:51.522] GET
>> > http://localhost:2323/files/JQUiDeploymentLibrary/jQueryUi.js [HTTP/1.1 404
>> > Not Found 12ms]
>> > [22:50:51.528] GET
>> > https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.16/themes/ui-lightness/jquery-ui.css
>> > [HTTP/1.1 304 Not Modified 85ms]
>> > [22:50:51.535] GET http://localhost:2323/files/WAWelcomeFiles/welcome.css
>> > [HTTP/1.1 404 Not Found 24ms]
>> > [22:50:51.554] GET
>> > http://localhost:2323/files/WAWelcomeFiles/syntaxHighlighting.css [HTTP/1.1
>> > 404 Not Found 36ms]
>> > [22:50:51.571] GET
>> > http://localhost:2323/files/WADevelopmentFiles/development.css [HTTP/1.1 404
>> > Not Found 37ms]
>> > [22:50:51.633] Error in parsing value for 'filter'.  Declaration dropped. @
>> > https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.16/themes/ui-lightness/jquery-ui.css:22
>> > [22:50:51.709] Unknown property 'zoom'.  Declaration dropped. @
>> > https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.16/themes/ui-lightness/jquery-ui.css:330
>> > [22:50:51.822] GET
>> > http://localhost:2323/files/JQUiDeploymentLibrary/jQueryUi.js [HTTP/1.1 404
>> > Not Found 1ms]
>> > [22:50:51.881] GET http://localhost:2323/files/WAWelcomeFiles/welcome.css
>> > [HTTP/1.1 404 Not Found 1ms]
>> > [22:50:51.892] GET
>> > http://localhost:2323/files/WAWelcomeFiles/syntaxHighlighting.css [HTTP/1.1
>> > 404 Not Found 12ms]
>> > [22:50:51.903] GET
>> > http://localhost:2323/files/WADevelopmentFiles/development.css [HTTP/1.1 404
>> > Not Found 23ms]
>> >
>> >
>> > And if I go to http://localhost:2323/files   I see NOTHING. EMPTY.
>>
>> You'll have to debug, the call three should look something like this:
>> HttpService
>>  WAComancheAdaptor
>>    WADispatcher
>>      WAFileHandler
>>
>> There are unfortunately several class instance variables involved :-(
>>
>> Cheers
>> Philippe
>> _______________________________________________
>> seaside mailing list

>> [hidden email] <[hidden email]>
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside <http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside>
>
>

--

Lukas Renggli
www.lukas-renggli.ch

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

On 23 Sep 2011, at 09:41, Mariano Martinez Peck wrote:

> I mean, which is the equivalent to WAKomEncoded startOn: 5555   in Zinc ?

"Start Zinc"
(ZnZincServerAdaptor port: 8080)
       codec: GRPharoUtf8Codec new;
       start.

There are alternatives, but the above is OK.

Sven

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

On 23 Sep 2011, at 10:05, Mariano Martinez Peck wrote:

> Thanks Sven. I am doing:
>
>    Gofer new squeaksource: 'MetacelloRepository'; package:
> 'ConfigurationOfSeaside30'; load.
>                (Smalltalk at: #ConfigurationOfSeaside30) project latestVersion
> load: #('Base Tests' 'Zinc-Seaside')
>
> And then what you say:
>
> (ZnZincServerAdaptor port: 4567)
>        codec: GRPharoUtf8Codec new
>        start.
>
> But then in the browser: http://localhost:4567/
>
> -> Error: you are forbidden to access "/"
>
> Any ideas?

It looks like the server is just not running, first try something simpler:

(ZnServer defaultOn: 1701)
       logToTranscript;
       start.

And look at the Transcript and the Process Browser. Stop with:

ZnServer stopDefault.

This is a way to enable Zn logging when using Seaside (you won't see the actual startup, but that's OK).

| adaptor |
(adaptor := ZnZincServerAdaptor port: 4567)
       codec: GRPharoUtf8Codec new;
    start.
adaptor server logToTranscript.
adaptor

Have a look at the Seaside Control Panel as well (it is in World Menu > Tools).

Good luck !

Sven

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

>> > Any clues of what can be the problem ?
>>
>> Likely there is something messed up with the configurations.
>>
>> You can reinitialize all code with the following Gofer helper:
>>
>>     WADevelopment reinitializePackages: WADevelopment allPackages
>>
>> Similarly, you can see if there are any code differences:
>>
>>     WADevelopment localPackageChanges: WADevelopment allPackages
>
> That's doesn't help, because I am NOT loading seaside with
> Metacello/Gofer/Monticello/MZC. Instead, we are experimenting with Fuel ;)
> So...I am sure there must be a problem somewhere in our code, but I cannot
> understand what.

Sure, the two above expressions do not care how the code is loaded.

They only care about everything being there as it should. If they do
not work I doubt that anything is going to work.

Did you try running the tests?

Lukas

--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On Thu, Sep 22, 2011 at 10:58 PM, Lukas Renggli <[hidden email]> wrote:

>> > Any clues of what can be the problem ?
>>
>> Likely there is something messed up with the configurations.
>>
>> You can reinitialize all code with the following Gofer helper:
>>
>>     WADevelopment reinitializePackages: WADevelopment allPackages
>>
>> Similarly, you can see if there are any code differences:
>>
>>     WADevelopment localPackageChanges: WADevelopment allPackages
>
> That's doesn't help, because I am NOT loading seaside with
> Metacello/Gofer/Monticello/MZC. Instead, we are experimenting with Fuel ;)
> So...I am sure there must be a problem somewhere in our code, but I cannot
> understand what.

 

Sure, the two above expressions do not care how the code is loaded.

Are you sure?
I have a problem because the monticello packages are not present. Check the attached screenshot.

Thanks
 

They only care about everything being there as it should. If they do
not work I doubt that anything is going to work.

Did you try running the tests?

Lukas

--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

--
Mariano
http://marianopeck.wordpress.com

On Fri, Sep 23, 2011 at 3:23 AM, Martin Dias <[hidden email]> wrote:

On Fri, Sep 23, 2011 at 3:16 AM, Lukas Renggli <[hidden email]> wrote:

Cool.

Don't use Swazoo, it doesn't work and some tests are broken. Use Kom or Zinc.

Great, so without counting Swazoo, we have 9 tests of Seaside and Grease to look at.

:D

It's ready! welcome app works fine and all tests are green (except swazoo who still crashes). Now I have to sleep we will show details about "the experiment" very soon.

Cheers,

Martín

 

 

Lukas

On Friday, 23 September 2011, Martin Dias <[hidden email]> wrote:
> Hey! good news :) The styles are fine with latest version (of fuel package loader). We was doing something wrong when materializing classes.
> Now... we have some red tests in Seaside, and even worse, a test in Swazoo crashes my VM... so we have more debug to do!
> Thank you very much for your help. 
> Martín
>
> On Fri, Sep 23, 2011 at 2:09 AM, Philippe Marschall <[hidden email]> wrote:
>>
>> 2011/9/22 Mariano Martinez Peck <[hidden email]>:
>> > Well...
>> >
>> > http://localhost:2323/
>> >
>> > ->
>> >
>> > [22:50:51.466] GET http://localhost:2323/ [HTTP/1.1 200 OK 4ms]
>> > [22:50:51.513] GET http://localhost:2323/files/JQDeploymentLibrary/jQuery.js
>> > [HTTP/1.1 404 Not Found 2ms]
>> > [22:50:51.522] GET
>> > http://localhost:2323/files/JQUiDeploymentLibrary/jQueryUi.js [HTTP/1.1 404
>> > Not Found 12ms]
>> > [22:50:51.528] GET
>> > https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.16/themes/ui-lightness/jquery-ui.css
>> > [HTTP/1.1 304 Not Modified 85ms]
>> > [22:50:51.535] GET http://localhost:2323/files/WAWelcomeFiles/welcome.css
>> > [HTTP/1.1 404 Not Found 24ms]
>> > [22:50:51.554] GET
>> > http://localhost:2323/files/WAWelcomeFiles/syntaxHighlighting.css [HTTP/1.1
>> > 404 Not Found 36ms]
>> > [22:50:51.571] GET
>> > http://localhost:2323/files/WADevelopmentFiles/development.css [HTTP/1.1 404
>> > Not Found 37ms]
>> > [22:50:51.633] Error in parsing value for 'filter'.  Declaration dropped. @
>> > https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.16/themes/ui-lightness/jquery-ui.css:22
>> > [22:50:51.709] Unknown property 'zoom'.  Declaration dropped. @
>> > https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.16/themes/ui-lightness/jquery-ui.css:330
>> > [22:50:51.822] GET
>> > http://localhost:2323/files/JQUiDeploymentLibrary/jQueryUi.js [HTTP/1.1 404
>> > Not Found 1ms]
>> > [22:50:51.881] GET http://localhost:2323/files/WAWelcomeFiles/welcome.css
>> > [HTTP/1.1 404 Not Found 1ms]
>> > [22:50:51.892] GET
>> > http://localhost:2323/files/WAWelcomeFiles/syntaxHighlighting.css [HTTP/1.1
>> > 404 Not Found 12ms]
>> > [22:50:51.903] GET
>> > http://localhost:2323/files/WADevelopmentFiles/development.css [HTTP/1.1 404
>> > Not Found 23ms]
>> >
>> >
>> > And if I go to http://localhost:2323/files   I see NOTHING. EMPTY.
>>
>> You'll have to debug, the call three should look something like this:
>> HttpService
>>  WAComancheAdaptor
>>    WADispatcher
>>      WAFileHandler
>>
>> There are unfortunately several class instance variables involved :-(
>>
>> Cheers
>> Philippe
>> _______________________________________________
>> seaside mailing list

>> [hidden email] <[hidden email]>
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside <http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside>
>
>

--

Lukas Renggli
www.lukas-renggli.ch

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

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

On 23 September 2011 11:43, Mariano Martinez Peck <[hidden email]> wrote:
>
>
> On Fri, Sep 23, 2011 at 11:41 AM, Mariano Martinez Peck
> <[hidden email]> wrote:
>>
>>
>> On Thu, Sep 22, 2011 at 10:58 PM, Lukas Renggli <[hidden email]> wrote:
>>>
>>> >> > Any clues of what can be the problem ?
>>> >>
>>> >> Likely there is something messed up with the configurations.
>>> >>
>>> >> You can reinitialize all code with the following Gofer helper:
>>> >>
>>> >>     WADevelopment reinitializePackages: WADevelopment allPackages
>>> >>
>>> >> Similarly, you can see if there are any code differences:
>>> >>
>>> >>     WADevelopment localPackageChanges: WADevelopment allPackages
>>> >
>>> > That's doesn't help, because I am NOT loading seaside with
>>> > Metacello/Gofer/Monticello/MZC. Instead, we are experimenting with Fuel
>>> > ;)
>>> > So...I am sure there must be a problem somewhere in our code, but I
>>> > cannot
>>> > understand what.
>>>
>>
>>>
>>> Sure, the two above expressions do not care how the code is loaded.
>>
>>
>> Are you sure?
>> I have a problem because the monticello packages are not present. Check
>> the attached screenshot.
>>
>
> Sorry...PharoDebug.log. And here it is.

Ahh, maybe you should create at least MCWorkingCopies?

Lukas

--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On 23 Sep 2011, at 11:47, Mariano Martinez Peck wrote:

> Cool Martin. Now I could do it as well. I have exported the groups 'Core', 'Tests' and 'Zinc-Seaside'.
> Then I materialize it a clean image and all tests (1567) are green. And it only takes 7 seconds :)

Great !

I want to try this myself soon.

Sven

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

On 23 September 2011 11:50, Mariano Martinez Peck <[hidden email]> wrote:
>
>
> On Fri, Sep 23, 2011 at 11:46 AM, Lukas Renggli <[hidden email]> wrote:
>>
>> On 23 September 2011 11:43, Mariano Martinez Peck <[hidden email]>
>> wrote:
>> >
>> >
>> > On Fri, Sep 23, 2011 at 11:41 AM, Mariano Martinez Peck
>> > <[hidden email]> wrote:
>> >>
>> >>
>> >> On Thu, Sep 22, 2011 at 10:58 PM, Lukas Renggli <[hidden email]>
>> >> wrote:
>> >>>
>> >>> >> > Any clues of what can be the problem ?
>> >>> >>
>> >>> >> Likely there is something messed up with the configurations.
>> >>> >>
>> >>> >> You can reinitialize all code with the following Gofer helper:
>> >>> >>
>> >>> >>     WADevelopment reinitializePackages: WADevelopment allPackages
>> >>> >>
>> >>> >> Similarly, you can see if there are any code differences:
>> >>> >>
>> >>> >>     WADevelopment localPackageChanges: WADevelopment allPackages
>> >>> >
>> >>> > That's doesn't help, because I am NOT loading seaside with
>> >>> > Metacello/Gofer/Monticello/MZC. Instead, we are experimenting with
>> >>> > Fuel
>> >>> > ;)
>> >>> > So...I am sure there must be a problem somewhere in our code, but I
>> >>> > cannot
>> >>> > understand what.
>> >>>
>> >>
>> >>>
>> >>> Sure, the two above expressions do not care how the code is loaded.
>> >>
>> >>
>> >> Are you sure?
>> >> I have a problem because the monticello packages are not present. Check
>> >> the attached screenshot.
>> >>
>> >
>> > Sorry...PharoDebug.log. And here it is.
>>
>> Ahh, maybe you should create at least MCWorkingCopies?
>>
>
> That's being dependent on how the code is loaded ;)

That depends on your definition of "the code is loaded".

I assume that the image/changes file is in *exactly* the same state as
if the code would be loaded with Monticello.

Lukas

--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside