Re: seaside Digest, Vol 191, Issue 14

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

Re: seaside Digest, Vol 191, Issue 14

Eitan Rosa
Cool,😎😎😆😆🤔🤔😑😑😶😶🙂🙂☺☺

On Thu, Nov 22, 2018 at 8:24 PM, [hidden email]
Send seaside mailing list submissions to

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to

You can reach the person managing the list at

When replying, please edit your Subject line so it is more specific
than "Re: Contents of seaside digest..."


Today's Topics:

  1. Re: wait for callback and use results of return value
      (Sabine Manaa)
  2. Re: Material Design Lite for Squeak? (Stephan Eggermont)
  3. Re: Material Design Lite for Squeak? (Cyril Ferlicot)
  4. Re: Material Design Lite for Squeak? (Cyril Ferlicot D.)
  5. Re: WAFileLibrary deployFiles then what? (gettimothy)


----------------------------------------------------------------------

Message: 1
Date: Thu, 22 Nov 2018 06:19:07 -0600 (CST)
From: Sabine Manaa <[hidden email]>
Subject: Re: [Seaside] wait for callback and use results of return
    value
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=us-ascii

Yesterday I was asking this question and also asked in discord.
In discord I wrote today with Johan Brichau.
He gave the solution to me and I want to share it here because when I have a
problem, I often look here.
The solution was like this (I remove the script brackets for the mailing
list).

Thanks a lot, Johan!

The task is to call a javascript method and return a result from somewhere
in the javascript.
Clicking on the button opens an inspector in the smalltalk image.

renderTestOn: html
    html
        html:
            'script       
function getS3Data(callback) {
    callback(''this goes back to the smalltalk image'' );   
}
/script       
'.
    html button
        onClick:
            ((html javascript alias: 'getS3Data')
                apply:
                    {((html jQuery ajax callback: [ :var | var inspect ] value: (html
javascript alias: 'value')) asFunction: #(value))});
        with: 'tedt'



--


------------------------------

Message: 2
Date: Thu, 22 Nov 2018 15:14:27 +0000 (UTC)
From: Stephan Eggermont <[hidden email]>
Subject: Re: [Seaside] Material Design Lite for Squeak?
Message-ID: <pt6h4j$mnp$[hidden email]>
Content-Type: text/plain; charset=UTF-8

Tobias Pape <[hidden email]> wrote:

>However, The Baseline requires Seaside3 with Zinc
but Zinc does not work with Squeak. Squeak currently uses
WebServer/WebClient (or Comanche).

I assume a PR with the needed baseline changes could be merged quickly?

Stephan





------------------------------

Message: 3
Date: Thu, 22 Nov 2018 16:22:18 +0100
From: Cyril Ferlicot <[hidden email]>
To: Seaside - general discussion <[hidden email]>
Subject: Re: [Seaside] Material Design Lite for Squeak?
Message-ID:
    <CAMyorgCo0pnWhVfuiWm6WOtctL3u7b3qZF1FZoXrc4F_m9+[hidden email]>
Content-Type: text/plain; charset="UTF-8"

On Thu, Nov 22, 2018 at 10:47 AM Tobias Pape <[hidden email]> wrote:
>
> Hi,
>
>
> Ok, I see.
>
> but Zinc does not work with Squeak. Squeak currently uses WebServer/WebClient (or Comanche).
>

I'll put on my todo list to add a part for squeak in the baseline.
I'll see to do that this evening or tomorrow evening.

> Best regards
>        -Tobias
>
>
> _______________________________________________
> seaside mailing list



--
Cyril Ferlicot


------------------------------

Message: 4
Date: Thu, 22 Nov 2018 23:45:56 +0100
From: "Cyril Ferlicot D." <[hidden email]>
Subject: Re: [Seaside] Material Design Lite for Squeak?
Message-ID: <[hidden email]>
Content-Type: text/plain; charset="utf-8"

Le 22/11/2018 à 10:47, Tobias Pape a écrit :
> Hi,
>
> Ok, I see.
>
> but Zinc does not work with Squeak. Squeak currently uses WebServer/WebClient (or Comanche).
>


> Best regards
>     -Tobias
>
>
> _______________________________________________
> seaside mailing list
>


--
Cyril Ferlicot

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature

------------------------------

Message: 5
Date: Thu, 22 Nov 2018 20:24:14 -0500
From: gettimothy <[hidden email]>
To: "Seaside - general discussion"
Subject: Re: [Seaside] WAFileLibrary deployFiles then what?
Message-ID: <[hidden email]>
Content-Type: text/plain; charset="utf-8"

Hi Joachim I was unclear.... For my immediate purposes, I am fine with being able to serve the existing apps from the image using their FileLibrary. What I was wondering/hoping for is that when running deployFiles, that 'somehow' instead of the FileLibrary serving the content it has stored in itself, would provide "pass thru" methods to access the files it deployed to the filesystem. hth. t ---- On Thu, 22 Nov 2018 02:41:38 -0500 <[hidden email]> wrote ---- Hi Timothy, still not sure I understand. You want to deploy files but serve them from the image? Isn't the whole idea of #deployFiles not to serve them from the image and use those CPU-Cycles in the Smalltalk image for something with more value...? Joachim Am 21.11.18 um 15:50 schrieb gettimothy: _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside Hi Joachim Thanks for the response. That what I was doing , but its a big job as I will be loading JQuery-ui, JQuery, Bootstrap, MaterialDesign, Seaside.... from the apps menu in SeasideDoc. However!!!! I found an acceptable work-around that bypasses NGINX completely. The base SeasideDoc files are referenced like:  SeasideDocLibrary baseUrl,'jquery-ui.js' ->'<a href="http://192.168.1.102/jquery-ui.js' " target=_blank onclick="return window.theMainWindow.showLinkWarning(this)">http://192.168.1.102/jquery-ui.js' and are  handled via Nginx. I figured out I could bypass NGINX completely by tacking on an :8080 to the url... (SeasideDocLibrary alternatePort: (SeasideDocLibrary baseUrl)) ,'bootstrap' --> '<a href="http://192.168.1.102:8080/bootstrap' " target=_blank onclick="return window.theMainWindow.showLinkWarning(this)">http://192.168.1.102:8080/bootstrap' This means the Show/Call stuff for apps will not be in the cards for the apps, but I think this is an acceptable tradeoff. cheers, t ---- On Wed, 21 Nov 2018 02:41:07 -0500 <[hidden email]> wrote ---- Timothy, not sure I am answering the right question here, but the idea of deploying files to the file system in a production system is that requests coming in for files never reach your smalltalk image, thus keeping load off your image. So what is needed is a definition for nginx that "catches" requests to /files/ and redirect them to files onyour filesystem, namely the path you deployed your files to. I am using Apache, so I cannot say what exactly needs to be done in nginx, Here's what's in my apache conf for this purpose:         Alias /files /var/www/app.kontolino         ProxyPass /files !         Alias /favicon.ico /var/www/app.kontolino/OfBuchhaltungFileLibrary/favicon.ico         ProxyPass /favicon.ico !         Alias /robots.txt /var/www/app.kontolino/OfBuchhaltungFileLibrary/robots.txt         ProxyPass /robots.txt ! So all you need to do is to transpile this for nginx ;-) HTH Joachim Am 21.11.18 um 08:32 schrieb gettimothy: _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside After you deploy the files, does Seaside have a "pass thru" to access those files automatically? or do I have to build one by hand? Here is the background/motivation. At <a href="http://menmachinesmaterials.com/SeasideDoc  " target=_blank>http://menmachinesmaterials.com/SeasideDoc  on left menu, under "apps" you will see that the css/javascript access for 'Zurb Foundation' works and neither work for the Twitter Bootstrap or Jquery apps. The reason is that I use NGinx locations to tell where to look for resources. My SeasideDoc and Zurb File ibraries all access their files relative to the nginx defintions.  So, 'ZurbExamplesLibrary foundation.css' will resolve to the correct path for Nginx to handle. The TBS and JQuery FileLibraries are 'self contained' and the css and js is not delivered via Nginx. I am in the process of creating an additional library for TBS that uses my convention...but... I just discovered the "deployFiles' method and it does do a nice dump of the files I need...but then what? Does Seaside standard dev practice include "switching to another library" that automatically routes to those urls that I am missing?  thx in advance. t _______________________________________________
seaside mailing list

_______________________________________________
seaside mailing list
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Subject: Digest Footer

_______________________________________________
seaside mailing list


------------------------------

End of seaside Digest, Vol 191, Issue 14
****************************************

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