seaside September 2017

seaside@lists.squeakfoundation.org

18 participants
17 discussions

Start a nNew thread

Is there a standard way to render the number 3000 as 3, 000 ?
by PAUL DEBRUICKER 18 Sep '17

18 Sep '17

And other larger ints and floats?

6 5

Re: [Seaside] Problem with visited links
by David Pennington 15 Sep '17

15 Sep '17

So, if I hand carve the links, I should be able to get this working. It is bugging my customer so I have to do something! Thanks Joachim. --------- Original Message --------- From: "jtuchel(a)objektfabrik.de" <jtuchel(a)objektfabrik.de> To: "David Pennington" <david(a)totallyobjects.com>, "Seaside - general discussion" <seaside(a)lists.squeakfoundation.org> Subject: Re: [Seaside] Problem with visited links Date: 09/14/2017 20:55:14 (Thu) David, you are not doing anything wrong. Open your web browser's Developer tools and look at the links that were rendered by seaside: they contain URL parameters that are unique for every render (the part after the ? in the href parameter), so technically, the link is never visited, because every time you render that page, the URL parameters will be different (this is a simplification with edge cases and people can start picking on me, but you get the picture). There are ways to make Seaside use "nice" URLs, but out of the box, this is just the way it works. Joachim Am 14.09.17 um 21:50 schrieb David Pennington: Hi there. I have a hybrid site where some pages are rendered by Seaside (using Instantiations VisualAge) and some are straight HTML. In the HTML pages, I use the following in a css: a:link { color: red; } and a:visited { color: yellow; } This works fine. In my Seaside pages, I use a css method with the same content but the visited links all turn up in a dark red, no matter which colour I say to use. This is the same on all browsers tested across both Windows and Macs Safari, Firefox, Edge. Am I doing something wrong? David Message sent using Winmail Mail Server _______________________________________________ seaside mailing list seaside(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1 http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 Message sent using Winmail Mail Server

3 3

Problem with visited links
by David Pennington 14 Sep '17

14 Sep '17

Hi there. I have a hybrid site where some pages are rendered by Seaside (using Instantiations VisualAge) and some are straight HTML. In the HTML pages, I use the following in a css: a:link { color: red;}anda:visited { color: yellow;}This works fine. In my Seaside pages, I use a css method with the same content but the visited links all turn up in a dark red, no matter which colour I say to use. This is the same on all browsers tested across both Windows and Macs Safari, Firefox, Edge. Am I doing something wrong? David Message sent using Winmail Mail Server

2 1

[squeak-dev] Seaside question won't post to Seaside news group
by Max Leske 13 Sep '17

13 Sep '17

Forwarded to seaside(a)lists.squeakfoundation.org. On 9 September 2017 at 14:00:04, squeak-dev-request(a)lists.squeakfoundation.org ( squeak-dev-request(a)lists.squeakfoundation.org) wrote: Date: Fri, 08 Sep 2017 11:30:25 -0400 <http://airmail.calendar/2017-09-08 17:30:25 GMT+2> From: Louis LaBrunda <Lou(a)Keystone-Software.com> To: squeak-dev(a)lists.squeakfoundation.org Subject: [squeak-dev] Seaside question won't post to Seaside news group Message-ID: <ipc5rchghu20meho39r22picl3e92abl4q(a)4ax.com> Content-Type: text/plain; charset=us-ascii Hi, I'm very sorry for posting this here but I have tried to post two messages to the Seaside news group that don't show up and I don't get any kind of rejection notice. I know Seaside is more a Pharo project than a Squeak project but I know I can post here (at least I have before). I want to register a sub-class of WARequestHandler as '..'. '...' works but '..' doesn't. I'm trying to use the same URL that one would use with Apache like "../folder/filename.txt". The request handler then reads and returns the file. Thanks for any ideas as to where to look. Lou -- Louis LaBrunda Keystone Software Corp. SkypeMe callto://PhotonDemon

2 1

Better selectors for jQuery script builders
by Esteban A. Maringolo 11 Sep '17

11 Sep '17

Hi all, >From some time now, I want to have a consistent naming criteria for the selectors that return a JSObject or a JSFunction, and I'd like to know other ideas about naming them. I name all the HTML rendering methods with the `renderSomething...On:`, so "render" is always the prefix and the canvas (html) the last argument (being it a single argument, or more than one). And because of that I don't want to use 'render' as a prefix for the methods that create a script. So lately I'm using the "create...On:" pattern for these selectors. E.g. when you have something like: renderContentOn: html html anchor onClick: (self createClickScriptOn: html); with: 'Click to toggle'. createClickScriptOn: html ^(html jQuery id: 'foo') toggle What is your criteria, if any, for this? Regards! Esteban A. Maringolo

3 3

Force Reload of Javascript
by jtuchel＠objektfabrik.de 11 Sep '17

11 Sep '17

Hi there, this may seem like a stupid question, but it seems I am struggling with the Browsers' cache handling of Javascript Code. Let me start by describing what happens: I change some javascript code in my Seaside app, deploy it onto the server and restart the image. For many (but not all) users, the changes don't get downloaded for days. They need to go to a page, press the Browser's reload button and from then on they are fine. This is both good to know and bad at the same time for several reasons: * some users never call and are frustrated * the number of support cases causes high cost The effect shows up both for Javascript that gets served from the file system (using rewrite rules) and for code served directly from Seaside in the render* methods. For the file system stuff, we have to work on the caching settings on Apache. But I am really helpless in case of "freshly rendered" JavaScript code. How could that even be cached by a Browser??? Any hints are welcome Joachim -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1 http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1

2 2

Porting from 2.8 to 3.0+
by Ramon Leon 07 Sep '17

07 Sep '17

Anyone know any good resources, blog posts, or reads out there for porting a Seaside 2.8 app to something more modern? Interested in any lessons learned to headaches to expect. Figure it'd be easiest to go to 3.0 and then once stable to 3.1. -- Ramon Leon

5 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside September 2017