seaside-dev September 2014

seaside-dev@lists.squeakfoundation.org

7 participants
18 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

Deprecation of TimeStamp now in Pharo 4
by Stephan Eggermont 20 Sep '15

20 Sep '15

In Pharo4, TimeStamp now is deprecated and should be replaced by DateAndTime now. (SPTimestamp, WAProfilerItem, WAUpTimeTracker 2*) Stephan

3 4

WAAdmin clearConfigurationCaches not working
by Philippe Marschall 23 Dec '14

23 Dec '14

Hi As part of fixing Issue 820 [1] I have to change some configurations. I though that if I do WAAdmin clearConfigurationCaches all the configuration caches should be cleared. However that is not what is happening. #preferenceAt: in WAApplication instances still return the old value. [1] https://code.google.com/p/seaside/issues/detail?id=820 Cheers Philippe

3 10

Javascript Condition with else decoration
by Esteban A. Maringolo 01 Oct '14

01 Oct '14

I was trying to implement a classical "if {...} else {...}" object using JSDecorations. Then I found there is a JSCondition, but there is no way to describe an "else" statement. Also there is an JSIfThenElse decoration, but it is implemented as a ternary operator (x ? y : z) instead of 'if(x){ y} else {z}' So I added an extension to JSObject, named #condition:else: and also a JSConditionElse decoration which produces the expected output. Can this be added to the main trunk of the Javascript-Core package? The changes are attached. With these modifications I was able to transform this Javascript: $('#ajaxId tbody').on( 'click', 'tr', function () { if ( $(this).hasClass('selected') ) { $(this).removeClass('selected'); } else { $('#ajaxId tr.selected').removeClass('selected'); $(this).addClass('selected'); } } ); Into this: | selClass | selClass := 'selected'. ^ (html jQuery: '#' , self ajaxId , ' tbody') on: 'click' selector: 'tr' do: ((html jQuery this removeClass: selClass) condition: (html jQuery this hasClass: selClass) else: (JSScript new add: ((html jQuery: '#' , self ajaxId , ' tr.' , selClass) removeClass: selClass); add: (html jQuery this addClass: selClass); yourself)) Esteban A. Maringolo ps: An alternative solution would be to modify the JSIfThenElse, but this would require adding returns to the trueStatement and falseStatement of this class.

4 8

Seaside-FileSystem in Seaside 3.2 ?
by Johan Brichau 01 Oct '14

01 Oct '14

The Seaside-FileSystem package currently resides in the Seaside30LGPL repository. What exactly is the reason for applying the LGPL license to this package? In addition, it depends on Sport but I now refactored it so it adds platform-specific extensions to the Grease Platform class. In Pharo3+, this means we can drop the loading of the FileSystem-Legacy package (which is dragged in by Sport). It also means every platform should be able to implement the platform-specific parts. Since I still find this package the easiest for serving external js and css files in development, I would want to include with Seaside 3.2 in the same repository. That would also mean all authors (Philippe, Julian and Lukas) have to agree with the relicensing to MIT. Opinions? Johan

2 3

Twitter Bootstrap examples interfering with WAExampleBrowser
by phil＠highoctane.be 16 Sep '14

16 Sep '14

I had a look and classes beginning with TBS are preventing WAExampleBrowser to work. Fix in attach. I can't commit to Seaside repo in STH. Phil

3 7

Fixing 3.1.3
by Johan Brichau 15 Sep '14

15 Sep '14

Hi, As you notice from the CI emails, I’m trying to finish up 3.1.3 for tagging it as the release31. We’ve got the WABrowser test failing in Pharo2.0, which actually is a DNU is the WANautilusBrowser itself (aka a Pharo20 bug). Given that this is a test of the browser-based development tools examples, I propose just marking it as an expected failure in Pharo2.0. Johan

2 6

Re: Seaside 3.1.3 loading
by Johan Brichau 14 Sep '14

14 Sep '14

Hi Torsten (cc: Seaside-dev), I discovered that these two load expressions are not semantically equivalent. > Gofer it > url: 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; > configurationOf: 'Seaside3'; > load. > > (Smalltalk at: #ConfigurationOfSeaside3) project stableVersion load loads 3.1.3, and the loading follows the normal symbolic version definitions but: > Gofer it > url: 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; > configurationOf: 'Seaside3'; > loadStable loads the last version that was blessed #stable. For some reason, we have changed from #stable to #released in the 3.1 branch (which is probably my doing). So, both are not semantically identical expressions… Now, this is probably not know by anyone. I will change the last version blessing to #stable instead of #released cheers, Johan

1 0

Seaside on github
by Johan Brichau 13 Sep '14

13 Sep '14

Hi guys, One url: https://github.com/SeasideSt/Seaside master branch is the stable release (3.1.3) dev/seaside32 is the development of 3.2.0 I will copy some additional repositories over. For now, they are mirrors of the smalltalkhub one. All is built using Travis CI, check out the builds. As agreed, this is experimental but the idea would be to develop here, create as many branches as we want and encourage people to contribute via pull requests (which are automatically verified using a Travis CI build + we can discuss in the pull request). In addition, the Gemstone repository would be a fork of this one. cheers, Johan

1 0

Re: Twitter Bootstrap examples interfering with WAExampleBrowser
by Stephan Eggermont 12 Sep '14

12 Sep '14

I've added you Stephan

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev September 2014