seaside-dev April 2014

seaside-dev@lists.squeakfoundation.org

15 participants
23 discussions

"Bootstrap" project for Seaside with separated Magritte support in a new project "BootstrapMagritte" on STHub
by Torsten Bergmann 16 Jul '18

16 Jul '18

Hi, The bundling with magritte polluted the repo and the Bootstrap project with stuff that was not really needed for "Seaside + Bootstrap" only. Also a "Bootstrap-Demo" package appeared that was more a demo for magritte than for Bootstrap. Since there already was an "Bootstrap-Examples" package this added more confusion (at least on my side). I now took action and cleaned up the Bootstrap project again to remove the magritte stuff. If one wants to to use Bootstrap with Seaside he does not necessarily have to go the Magritte path, so IMHO this was necessary. The magritte stuff for Bootstrap is now hosted as an own separate project on STHub which would also help to see to which part code additions really belong. As a result: ============ 1. The Bootstrap project now again only contains and loads the initial three packages: - Bootstrap-Core - Bootstrap-Tests-Core - Bootstrap-Examples assembled by the known ConfigurationOfBootstrap 2. The Magritte support on top of Bootstrap is now separated in an own project to avoid too much mixin. See "BootstrapMagritte" on SmalltalkHub. The new repo "http://smalltalkhub.com/#!/~TorstenBergmann/BootstrapMagritte" has the same commiters as the old one, so feel free to continue with your work. This project includes two packages: - Bootstrap-Magritte-Core (former Bootstrap-Magritte) - Bootstrap-Magritte-Examples (former Bootstrap-Demo) assembled by a new ConfigurationOfBootstrapMagritte for this particular project 3. The Bootstrap/ConfigurationOfBootstrap is now available as - a release version 0.4.0 for Seaside 3.0.9 - a release version 0.5.0 for Seaside 3.0.10 - a release version 0.6.0 for Seaside 3.1.0 (#stable) - a development version 0.7.0 for Seaside 3.1.0 for new stuff 4. The CI for Bootstrap is green for Pharo 2.0 and now also Pharo 3.0 5. The config browser is updated for Pharo 2.0 and Pharo 3.0 with the "Bootstrap" package So you can now also open a fresh Pharo 3.0 image, open World menu -> Configuration Browser to load "Bootstrap". Then run ZnZincServerAdaptor startOn: 8080 and start coding your web application with the latest Seaside 3.1.0. Next steps: Setting up a CI for the new project "BootstrapMagritte"/ConfigurationOfBootstrapMagritte Have fun! Bye Torsten

3 7

HTTP 302 vs 303
by Philippe Marschall 07 Jun '14

07 Jun '14

Hi I came upon this HN thread [1]. The linked article suggests we should use HTTP 303 instead of 302 (because we want a change from POST to GET). [1] http://insanecoding.blogspot.ch/2014/02/http-308-incompetence-expected.html Cheers Philippe

3 3

Build failed in Jenkins: Seaside » 30,bleedingEdge,vm #461
by ci-pharo-contribution＠inria.fr 25 Apr '14

25 Apr '14

1 1

WAUrl gap analysis
by Philippe Marschall 22 Apr '14

22 Apr '14

Hi I finally found time to read [1]. It looks to me as if these are the tests that we should pass but currently fail: "serialization" url := WAUrl new. url host: 'example.com'. url addToPath: 'blue+light blue'. url queryFields at: 'blue+light blue' put: nil. self assert: url greaseString = 'http://example.com/blue+light%20blue?blue%2Blight+blue' "parsing" url := (WAUrl absolute: 'http://example.com/blue+light%20blue?blue%2Blight+blue') decodedWith: GRNullCodec new. self assert: url path first = 'blue+light blue'. self assert: (url queryFields includesKey: 'blue+light blue'). url := (WAUrl absolute: 'http://example.com/blue%2Fred%3Fand+green') decodedWith: GRNullCodec new. self assert: url path first = 'blue/red?and+green' [1] http://blog.lunatech.com/2009/02/03/what-every-web-developer-must-know-abou… Cheers Philippe

2 1

[Pharo-Dev] [Squeak-Dev] [vwnc] [VA-Smalltalk] [GemStone-Smalltalk] [Glass] [Seaside] [Seaside-Dev] Chalten little survey
by Maximiliano Taborda 21 Apr '14

21 Apr '14

Hello fellow smalltalkers. First of all, if you don't know what Chalten is, here you could discover it https://github.com/mtaborda/chalten. Is a time model that allows to use dates, months, years, etc. in an easy way. After some sabbatical years, I decided to finalize my thesis and get my degree. And, as part of the last part of the investigation, I be very grateful if you, users of Chalten (if there anyone anywhere), could answer these few questions: 1. What kind of use you give? (personal, in company, both) 2. Where you use it? (bussines area, company name if you can tell me that) 3. What for? (name of the system, or proyect with a brief description if it's possible) Please, include my personal email, mtaborda(a)gmail.com, in your reply. Excuse me if you receive this email more than once, I' sending to all the email lists that I have. Thank you very much for your answers. Kind Regards. Maxi.

1 0

Fwd: [Seaside Issues] Issue 789 in seaside: Running WAFilelibraryTest on Pharo3 leaves Seaside-Tests-Core package in a dirty state
by Johan Brichau 19 Apr '14

19 Apr '14

Anybody knows why GRPharoPlatform>>removeSelector:from: was sending #removeSelectorSilently: rather than #removeSelector: to the class? Running method removal ‘silently’ breaks something in GRPackage in Pharo3.0. It seems GRPackage code is listening to announcements and when the removal runs silently, it is not being notified. When you remove a loaded file from a WAFileLibrary using the Seaside infrastructure, the package would remain dirty and you get an error trying to check for its changes in Monticello. I made a fix for it, basically cancelling the silent running of the removal in GRPharoPlatform. I also made the Seaside testcases that compile methods run silently. Though not necessary anymore, this avoids that the compiled method gets registered in GRPackage, this avoiding the problem alltogether. More info: http://code.google.com/p/seaside/issues/detail?id=789 Begin forwarded message: > From: seaside(a)googlecode.com > Subject: Re: [Seaside Issues] Issue 789 in seaside: Running WAFilelibraryTest on Pharo3 leaves Seaside-Tests-Core package in a dirty state > Date: 19 Apr 2014 17:23:30 GMT+2 > To: issues(a)lists.seaside.st > Reply-To: seaside-dev(a)lists.squeakfoundation.org, codesite-noreply(a)google.com > > > Comment #2 on issue 789 by jo...(a)yesplan.be: Running WAFilelibraryTest on Pharo3 leaves Seaside-Tests-Core package in a dirty state > http://code.google.com/p/seaside/issues/detail?id=789 > > I also changed GRPharoPlatform>>removeSelector:from: to use #removeSelector instead of #removeSelectorSilently: because it will also occur when removing methods from WAFileLibrary subclasses > > I actually don't really understand why this was #removeSelectorSilently: > > -- > You received this message because this project is configured to send all issue notifications to this address. > You may adjust your notification preferences at: > https://code.google.com/hosting/settings > > _______________________________________________ > issues mailing list > To unsubscribe, email issues-leave(a)lists.seaside.st > http://lists.seaside.st/listinfo/issues

1 0

Travis builds all green
by Johan Brichau 19 Apr '14

19 Apr '14

I finally managed to get the Travis CI builds for Seaside 3.1 green for all platforms: Pharo1.4, Pharo2.0, Pharo3.0, Squeak4.4, Gemstone3.1 https://github.com/glassdb/Seaside31

3 2

[ANN] FontAwesome for Seaside
by Torsten Bergmann 19 Apr '14

19 Apr '14

Hi, FontAwesome is (as you may know) an iconic font designed for the user with Twitter Bootstrap. I now created a "FontAwesome for Seaside" project - which is a small Seaside wrapper for the FontAwesome project (using the latest version 4.0.3). This is intended as an addition to the already available "Bootstrap for Seaside" [2] project that I wrote and both should allow you to give your Smalltalk based web application a nice stylish look. The project is located on STHub, see [1] where you will also find the documentation. A live demo can be found on http://pharo.pharocloud.com/fontawesome. To try yourself load it from the Pharo config browser or read the docu to see what is required. Thx T. [1] http://smalltalkhub.com/#!/~TorstenBergmann/FontAwesome [2] http://smalltalkhub.com/#!/~TorstenBergmann/Bootstrap

3 2

image form: broken in Pharo3.0 > fix
by phil＠highoctane.be 18 Apr '14

18 Apr '14

In fact, the GifReadWrite class seems to be broken or something like that. Changing the Form>>defaultMimeType to: defaultMimeType ^ WAMimeType imagePng fixes the problem. Phil

2 1

Re: WAFileLibrary has issues with GRPharoPlatform>>localNameOf:
by Stephan Eggermont 18 Apr '14

18 Apr '14

Missing a pathString. WAWelcomeFiles addFileAt: (FileSystem disk workingDirectory / 'Cards.png') pathString works for me

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev April 2014