seaside June 2017

seaside@lists.squeakfoundation.org

20 participants
9 discussions

isolate
by recursive68＠gmail.com 26 Nov '19

26 Nov '19

Hi, Given it looks like the isolate method is never going to added back to the current or future versions of Seaside as it's been an open bug issue for the last 5 years, how in general would go about replicating it's behaviour ? I think it's a shame as I think this sort of functionality made Seaside standout from the crowd as a web framework. Thanks

4 5

Seaside 3.2.0 final
by Johan Brichau 16 Aug '17

16 Aug '17

Hi everyone, Seaside 3.2.0 is now final: https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog <https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog> Check out the Github pages for more information: - https://github.com/SeasideSt/Seaside <https://github.com/SeasideSt/Seaside> - https://github.com/SeasideSt/Seaside/wiki <https://github.com/SeasideSt/Seaside/wiki> If you experience issues, do not hesitate to report an issue via Github. Special thanks goes to all those who have helped, tested or contributed in some other way!

14 26

JQueryWidgetBox, Seaside 3.2, Pharo 6
by Pierce Ng 03 Jul '17

03 Jul '17

Hi all, I'm trying to load JQueryWidgetBox into Seaside 3.2 on a fresh Pharo 6 image. Current ConfigurationOf on STH defines version 2.8, which hardcodes dependency on Seaside 3.1. I made a local version 2.9, changing said dependency to Seaside 3.2, and do-it'ed (heh), which led to a debugger when loading JQWidgetBox-FullCalendar-Dev-PaulDeBruicker.6 with the error "Instance of WAMutualExclusionCache did not understand #expiryPolicy". Finder did not locate #expiryPolicy anywhere in the image. I commented out that line in the debugger and ploughed on. Loading completed without further event. Test Runner reports 98 run, 97 passes, and 1 failure in JQGridSearchResponseTest's #testCreateJson, which looks immaterial going by the error message. Clicking around these widges in the web browser shows that a number of them don't work. Pierce

2 3

Seaside and HTTPS (for testing locally)
by Torsten Bergmann 30 Jun '17

30 Jun '17

Today web development for mobile devices is very common. So one possible scenario is to develop with Seaside on a computer and checking the result page directly with a browser on the phone in the same network. This works perfectly in a quick and simple setup (with seaside running on port 80). One just opens the IP address of the developer computer to access the seaside page over HTTP and can check how it looks on mobile. But in recent times Google is pushing to get all website using their APIs to move from HTTP to the HTTPS protocol. So for same client side browser APIs (for instance for geolocation) the mobile chrome on Android mobile devices now returns "Only secure origins are allowed". So such functionaliy is only allowed in the client browser when the server is on a secure HTTPS connections. While this makes sense for production setups one usually does not have a local HTTPS connection out of the box with Seaside when testing and developing an application. What is the best way and most easy Way to locally serve Seaside with HTTPS for testing? How to set this up? What do people use? Thanks T.

4 3

HTML templating
by Siemen Baader 22 Jun '17

22 Jun '17

Hi all, I use an external program to design & update my HTML pages and would like to use them as templates in Seaside. In the front end, I used to extract elements by IDs and then added content to them using jQuery. That left the templates as valid HTML and felt very consistent to me. Is there a similar approach to use within Seaside? Eg. getting a canvas cursor inside a specific element of the HTML file? Other approaches welcome, I just want to keep my templates as valid HTML outside the image so I can use external dev tools on them. -- Siemen

4 6

Seaside Still has an issue in a clean Pharo6 image
by Tim Mackinnon 20 Jun '17

20 Jun '17

Hi - inspired from Pharo days I’ve been relearning how to write web apps in Pharo. Anyway, I’ve noticed that in a clean Pharo 6 image, when I load the latest Seaside (that now correctly shows the control panel) - I still get an error if I browse the counter configuration (and any configurations I make as well). I get a walkback - "Seaside Walkback Deprecation: The method Object>>#name called from WAClassListAttribute>>#stringForValue: has been deprecated. Implement your own domain representation of an object, or use #asString or #printString instead.”? This error is because Pharo 6 has deprecated the use of #name in object, and it looks to me that WAObject should now override this method to avoid the deprecation. I am also confused why in a new image there doesn’t seem to be a web server that is started automatically. I thought loading Seaside started one for you, but it seems that I have to launch my own eg. ZnZincServerAdaptor startOn: 8080. Is this correct? This seems to go agains the assumptions of pharocloud.com <http://pharocloud.com/> as well - as they mention that seaside automatically starts a server for you. Is this something that has changed? Do I need to provide my own “autostart” class if I want to try pharocloud (I’m guessing there is a startUp method somewhere that I need to override?) Tim

3 5

ConfigurationOfSeaside3 not working with Pharo 6 ?
by Cyrille Delaunay 13 Jun '17

13 Jun '17

I'm trying to do the following: - Download latest pharo 6 image from Pharo website (Pharo 6.0 Latest update: #60499) - From the catalog browser, load the configuration of Seaside3 project. - From the versionner, try to open project Seaside3 I get an "Error: Name not found: Seaside-Pharo-Development" This is an error I already saw few time in some build logs. Does anyone know from where it could come from ? -- Cyrille Delaunay

5 14

[ANN] Pharo 6.0 released!
by Esteban Lorenzano 06 Jun '17

06 Jun '17

Dear World, The time has come for Pharo 6.0! Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. This is our most significant release yet. Here are some highlights: - Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability (beware, 64bits version is a new technology and a small amount of tests is still failing) - A new code changes management system named Epicea for easier reviewing and recovering of your code easily - Integrated support for Git through an easy-to-use tool for repositories and commits management named Iceberg (as a preview for Pharo 6, it will be the default in Pharo 7) - The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved - The PharoVM is now part of OpenSmalltalk initiative - Introduction of object immutability, alternative bytecode sets and block closures independent of outer context - Pharo can now be bootstrapped from source code managed by Git - Pharo modularity is improved - Pharo is faster - The Dark Theme was improved and set as default color theme of Pharo These are just the more prominent highlights, but the details are just as important. We have closed 1474 issues in Pharo 6.0 (a more complete changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo60Change…). While the technical improvements are significant (starting the transition to 64bits is a remarkable achievement), still the most impressive fact is that the new code that got in the main Pharo 6.0 image was contributed by more than 80 people. Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei Syrel, Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, Bernhard Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, Cyril Ferlicot, Dale Henrichs, Damien Cassou, Damien Pollet, Dave Lewis, Denis Kudriashov, Dirk Roeleveld, Eliot Miranda, Esteban Lorenzano, Esteban Maringolo, Evan Donahue, Federico Balaguer, Franck Warlouzet, Glenn Cavarle, Guillermo Polito, Gustavo Santos, Henrik Johansen, Henrik Nergaard, Hilaire Fernandes, Holger Hans, Jan Kurs, Jan van de Sandt, Johan Fabry, Juraj Kubelka, K. K. Subramaniam, Ken Causey, Kris Gybels, Lionel Akue, Luc Fabresse, Lucas Godoy, Marcus Denker, Mariano Martinez Peck, Marion Noirbent, Martin Dias, Max Leske, Maxime Roelandt, Merwan Ouddane, Matteo Bellotto, Miguel Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai Hess, Nicolas Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo Tesone, Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, Sophie Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, Sven Van Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault Raffaillac, Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, Torsten Bergmann, Tudor Girba, Udo Schneider, Valentin Ryckewaert, Vincent Blondeau, Werner Kassens, Yuriy Tymchuk (If you contributed with Pharo 6.0 development in any way and we missed your name, please send us a mail and we will add you). Enjoy! The Pharo Team Try Pharo: http://pharo.org/download Learn Pharo: http://pharo.org/documentation

5 4

Re: [Seaside] [ANN] Pharo 6.0 released!
by Juan 06 Jun '17

06 Jun '17

Wooow great work! El 6 jun. 2017 12:43 PM, "Tudor Girba" <tudor(a)tudorgirba.com> escribió: Great work! Doru > On Jun 6, 2017, at 5:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Dear World, > > The time has come for Pharo 6.0! > > Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. > > This is our most significant release yet. Here are some highlights: > > - Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability (beware, 64bits version is a new technology and a small amount of tests is still failing) > - A new code changes management system named Epicea for easier reviewing and recovering of your code easily > - Integrated support for Git through an easy-to-use tool for repositories and commits management named Iceberg (as a preview for Pharo 6, it will be the default in Pharo 7) > - The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved > - The PharoVM is now part of OpenSmalltalk initiative > - Introduction of object immutability, alternative bytecode sets and block closures independent of outer context > - Pharo can now be bootstrapped from source code managed by Git > - Pharo modularity is improved > - Pharo is faster > - The Dark Theme was improved and set as default color theme of Pharo > > <Pharo6.jpeg> > > These are just the more prominent highlights, but the details are just as important. We have closed 1474 issues in Pharo 6.0 (a more complete changelog can be found at https://github.com/pharo- project/pharo-changelogs/blob/master/Pharo60ChangeLogs.md). > > While the technical improvements are significant (starting the transition to 64bits is a remarkable achievement), still the most impressive fact is that the new code that got in the main Pharo 6.0 image was contributed by more than 80 people. > > Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: > > Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei Syrel, Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, Bernhard Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, Cyril Ferlicot, Dale Henrichs, Damien Cassou, Damien Pollet, Dave Lewis, Denis Kudriashov, Dirk Roeleveld, Eliot Miranda, Esteban Lorenzano, Esteban Maringolo, Evan Donahue, Federico Balaguer, Franck Warlouzet, Glenn Cavarle, Guillermo Polito, Gustavo Santos, Henrik Johansen, Henrik Nergaard, Hilaire Fernandes, Holger Hans, Jan Kurs, Jan van de Sandt, Johan Fabry, Juraj Kubelka, K. K. Subramaniam, Ken Causey, Kris Gybels, Lionel Akue, Luc Fabresse, Lucas Godoy, Marcus Denker, Mariano Martinez Peck, Marion Noirbent, Martin Dias, Max Leske, Maxime Roelandt, Merwan Ouddane, Matteo Bellotto, Miguel Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai Hess, Nicolas Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo Tesone, Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, Sophie Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, Sven Van Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault Raffaillac, Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, Torsten Bergmann, Tudor Girba, Udo Schneider, Valentin Ryckewaert, Vincent Blondeau, Werner Kassens, Yuriy Tymchuk > > (If you contributed with Pharo 6.0 development in any way and we missed your name, please send us a mail and we will add you). > > Enjoy! > > The Pharo Team > > Try Pharo: http://pharo.org/download > Learn Pharo: http://pharo.org/documentation -- www.tudorgirba.com www.feenk.com “Software has no shape. Actually, it has no one shape. It has many." _______________________________________________ seaside mailing list seaside(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside June 2017