seaside-dev May 2013

seaside-dev@lists.squeakfoundation.org

3 participants
2 discussions

Fwd: [Pharo-project] [Pharo-users] the future of squeaksource
by Johan Brichau 15 May '13

15 May '13

What do the Seaside developers think about migrating? Go to SmalltalkHUB ? Begin forwarded message: > From: stephane ducasse <stephane.ducasse(a)free.fr> > Subject: Re: [Pharo-project] [Pharo-users] the future of squeaksource > Date: 8 May 2013 09:50:29 GMT+02:00 > To: A friendly place where any question about pharo is welcome <pharo-users(a)lists.gforge.inria.fr> > Cc: Pharo Development <pharo-project(a)lists.gforge.inria.fr> > Reply-To: Pharo-project(a)lists.gforge.inria.fr > > > On May 7, 2013, at 5:19 PM, Andrei Vasile Chis <chisvasileandrei(a)gmail.com> wrote: > >> Hi all, >> >> Given that SmalltalkHub is now stable we were considering to discontinue SqueakSource. >> Our idea is to provide a grace period of a couple of months to allow the current active users to migrate their projects to the new service and then simply put squeaksource in read-only mode (simply exposing the directory structure and allowing downloads). >> >> What do you think about it ? >> Are there any good reasons to still keep SqueakSource alive? > > Keep it alive so that we can slowly migrate. Because migrating takes a lot of time. > > > >> >> Cheers, >> The SCG Team > >

3 2

Fixing 754 in 3.0?
by Philippe Marschall 07 May '13

07 May '13

Hi As you can probably tell from the mails I've been fixing some bugs today (Workers' Day). One of the more interesting ones was Issue 754 [1]. The underlying problem is that in 3.0 the JSON support builds on top of the JavaScript support. So the JavaScript string escaping is used for escaping JSON. The JavaScript string escaping make use of some "optimisations" like \0 zero for or \xXX for unnamed ASCI control characters. These are not valid in JSON, JSON wants \uXXXX. If we want to fix this in 3.0 we have to change the way string escaping is done for JavaScript and always use \uXXXX for unnamed ASCI control characters (which is still valid JavaScript). How do people feel about this? (in 3.1 this was easy to fix because JSON and JavaScript are separate) [1] http://code.google.com/p/seaside/issues/detail?id=754 Cheers Philippe

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev May 2013