seaside June 2010

seaside@lists.squeakfoundation.org

44 participants
52 discussions

Installing and testing Seaside 2.8.4, Magritte and Pier in Pharo 1.1
by Mariano Martinez Peck 03 Jul '10

03 Jul '10

Hi seasideers. I was loading all this stuff of PharoCore 1.1 and see if everything seems to be working. At this is the case :) However, I have 2 tests with errors and this is due to send to BlockClosure >> fixTemps which is deprecated in Pharo 1.1 The fix is easy, just remove the send of fixTemps, but I am not sure the impact of this in other dialects. But would be cool not to have the deprecated warning when loading. The places are Amb >> oneOf: aCollection and Amb >> valueOfOneOf: blockCollection Then I have two failing but I don't understand why: WABacktrackingTest >> testOrderedCollection I don't know why here, but after "original removeLast." snapshot has the elements "1" and "nil" instead of "1" and "2", and thus, it fails in self assert: original asArray = #(1 2) The other is: WABacktrackingTest >> testDictionary It is failing in "self assert: (original at: 1 ifAbsent: []) = #a." because original shows -> a Dictionary(2->#b 3->#d ) I know your effort is now in Seaside3 but having all green tests with Pharo 1.1 would be really cool :) Last thing, if you want to test it, just take a PharoCore 1.1 image, for example: https://gforge.inria.fr/frs/download.php/26995/PharoCore-1.1-11357-UNSTABLE… And then evaluate: (Smalltalk at: #Gofer) new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside'; load. ConfigurationOfSeaside project latestVersion load: 'Seaside 2.8'. and run tests :) Thanks Mariano

7 9

[ANN] ESUG Awards 2010
by Luc Fabresse 01 Jul '10

01 Jul '10

Dear Smalltalkers, You are invited to submit your nice Smalltalk based software to the 7th ESUG Innovation Technology Awards. The top 3 teams with the most innovative software will receive, respectively, 500 Euros, 300 Euros and 200 Euros during an awards ceremony at the 18th International Smalltalk Joint Conference 2010 in Barcelona, Spain. No constraints are put on the software except that it should be Smalltalk-based or Smalltalk-related and all flavours of Smalltalk are accepted. More details on the web (submission process, ...): http://www.esug.org/Conferences/2010/Innovation+Technology+Awards Results of the 2009 edition: http://www.esug.org/Conferences/2009/Innovation+Technology+Awards/Winners+a…

3 2

How do I update seaside beta code in 1-click installer?
by Pat Maddox 29 Jun '10

29 Jun '10

I'm going through the seaside book and am using the 1-click installer which is Seaside-3.0a5. Radio button callbacks don't seem to work, and after some googling I found http://code.google.com/p/seaside/issues/detail?id=538 which says I "need to update to make it work." Only problem is, I'm not sure how. I pulled up Monticello and tried to load the most recent version of Seaside-Core but got "this package depends on the following classes: GROrderedMultiMap". Also, there are like 20 different packages that I *think* I would need to update, which is cumbersome. After I got through as many as I could, I got various errors when hitting the web server. Anyway, is there some generic update script I can use to get the latest code? Would be nice to keep up to date so I can use radio buttons :) Thanks! Pat

3 4

Seaside 3.0 without Partial Continuations
by Diogenes Moreira 29 Jun '10

29 Jun '10

Hi Folks, I remember a mail about the topic, but i'll ask again. Exist a way to use SS 3.0 without Partial Continuations ( with Full Continuations Only..).?? I'm working with dolphin 6.x and this VM don`t support partial continuations... Any Clue or tip will be welcome. Best Regards

3 2

New structure for Seaside30, Magritte2, and Pier2 Metacello configurations
by Dale Henrichs 28 Jun '10

28 Jun '10

I am looking for a little feedback on the changes that I have made to the latest configurations of Seaside30, Magritte2, and Pier2. I have new versions for each of these configurations queued up for release (#development blessing), but before releasing them I'd like to hear if the changes I've made will cause trouble for folks using Magritte2 and/or Pier2 in their applications. In the past, when you referenced Seaside30 from a configuration, the entire Seaside3.0 release would be loaded, including development tools, examples, both adaptors (on Squeak/Pharo and GemStone)...basically the whole kitchen sink. With the 3.0.0-alpha5.15 release I've defined several groups for Seaside3.0 (with feedback from the Seaside devs:): Base, Base Tests, Development and Development Tests. I will also add a One-click group to shdow the one-click release. Without going into too much detail, the Base group defines the set of packages that are needed for a production release, while the Development group defines the set of packages that are useful in development (on top of the Base). To see how these new groups work out, I have created new versions of the configurations for Magritte2 and Pier2 that reference the Base group (plus any other packages that were needed) instead of bringing in the entire Seaside3.0 release...This is the big change. After loading the Magritte2 or Pier2 configuration you will need to load from the Seaside30 configuration any and all packages that you may need for your own application. I haven't released the changes yet, but if you are curious or concerned you can try out the releases ahead of time ... depending upon feedback I may go with a different scheme. In a fresh image, you can see what will be loaded for production by executing one or more of the following expressions (note you need to get the latest version of each of the configs from the SqueakSource MetacelloRepository...oh and for best results use Metacello 1.0-beta.27.1): (ConfigurationOfMagritte2 project version: '2.0.5') load. (ConfigurationOfPier2 project version: '2.0.6') load. (ConfigurationOfPierAddOns2 project version: '2.0.6') load. Once you've loaded one of these configs, there will be no development tools nor any adaptors so at a minimum you'll need to load one of the following depending upon which adaptor you want to use: "All platforms" (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') load: #('Seaside-Adaptors-Swazoo'). "Squeak and Pharo" (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') load: #('Seaside-Adaptors-Comanche'). "GemStone" (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') load: #('Seaside-Adaptors-FastCGI'). If you want to load in the Seaside development environment then you would evaluate the following expression: (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') load: #('Development'). So at this point you can see the direction I'm going with this ... the Magritte2 and Pier2 configurations are currently aimed at loading the bare minimum needed for functionality from Seaside3.0 for Magritte2 and Pier2 with the idea that you'd load the additional functionality that you want by dealing directly with Seaside30 configuration (like loading adaptors and development)... Pier2 already depends upon the following javascript packages: 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' 'JQuery-UI' but if you're currently using Magritte2 and javascript, then you'll need to explicitly load the javascript package(s) that you are using. There are other ways that the configs could be structured. This approach minimizes the coupling between the Seaside3.0 and Magritte2/Pier2 configurations, which I think is a good thing. I've taken the bare minimum step: loading what is required... it would be reasonable to add 'Dev' groups to both Magritte2 and Pier2 that would bring in Seaside30 dev support on the other hand, I don't think it is reasonable to add support for loading the various Adaptors to Magritte2 and Pier2, so if you're going to have to deal with the Seaside30 config directly anyway why bother with adding dev groups ... Anyway this is what _I_ think and I am interested in what you folks think... For GemStone folks ... the answer is yes, Magritte2 and Pier2 have been ported to GemStone/S 64 2.4 finally:). If you've been working with Seaside3.0 already, you can load the Magritte2/Pier2/PierAddOns2 configs into a fresh 1.0-beta.8....otherwise I'll ask you to wait until I announcement. Dale

3 3

non-specific dependencies
by Julian Fitzell 27 Jun '10

27 Jun '10

On Sun, Jun 27, 2010 at 6:54 PM, Dale Henrichs <dhenrich(a)vmware.com> wrote: > Once you've loaded one of these configs, there will be no development tools > nor any adaptors so at a minimum you'll need to load one of the following > depending upon which adaptor you want to use: > > "All platforms" > (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') > load: #('Seaside-Adaptors-Swazoo'). > "Squeak and Pharo" > (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') > load: #('Seaside-Adaptors-Comanche'). > "GemStone" > (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') > load: #('Seaside-Adaptors-FastCGI'). This, of course, is why package management systems like RPM and Deb end up having "provides". This would allow Seaside-Base to require "http-adaptor" or something and each of those packages to provide "http-adaptor". The package manager can then look for possibilities and prompt if it finds more than one. Not saying you need to go that route, but it's probably the "traditional" solution. Julian

2 1

jQuery history plugin
by Jan van de Sandt 27 Jun '10

27 Jun '10

Hello list, I am trying to add support for the jQuery history plugin ( http://github.com/tkyk/jquery-history-plugin) to Seaside. The API of the plugin looks pretty simple but I don't know how to integrate it with the Seaside jQuery support. In the onLoad on ready function you should register a callback function using $.history.init(callback). This callback function gets called with a url hash value as an argument. This function should get the new content from the server using an AJAX request. For the AJAX links on your page that should be bookmarkable and should support the backbutton you must use the $.history.load('#some_anchor') function. In Seaside this should look something like: html anchor onClick: (html jQuery history load: '#link1'); with: 'Link 1'. And the init function can be called as part of the onLoad scripts: html document addLoadScript: (html jQuery history init: [ :anchor | self updateUsingAnchor: anchor ]) This second fragment is probably totally wrong. The update method needs something to render on. Can anybody push me in the right direction? Jan.

1 0

Test vs. production servers
by Schwab,Wilhelm K 25 Jun '10

25 Jun '10

Hello, Is there a slick way to have various Seaside apps register themselves based on where they "wake up?" Decisions to be made include http vs. https, maybe where files get stored[*], and deployment vs. development mode. [*] at least for ODBC, I have had success with creating identically named connections but pointing them at the appropriate production/test database based on the machine's purpose. Bill

2 1

Seaside app crashing - does it sound familiar?
by Schwab,Wilhelm K 24 Jun '10

24 Jun '10

Hello all, I am trying to pick up after a few months on a Seaside app. A lot has happened in that time, and I am not certain of its state, except to say that I recall seeing it display some pages. Now it's not working. At least some other Seaside apps are working, and going back to my 1.0 image, it is crashing with "scheduler could not find a runnable process." Are there any common mis-configurations or programming errors that can lead to that? I'll keep digging, but I wanted to post this just in case it's a known punishment for a common crime. Bill

2 2

disconnecting Comet?
by Bob Arning 24 Jun '10

24 Jun '10

Hi, Once I have connected Comet to a page, is there a way to disconnect it without completely re-rendering the page? I have this in my response generating code: needPusher ifTrue: [ html document addLoadScript: (html comet pusher: mainPusher; connect) ] ifFalse: [ html document addLoadScript: (html comet pusher: mainPusher; disconnect) ]. and it will start a pusher, but doesn't seem to be able to stop one (like make the browser loading indicator stop spinning). Thoughts? Thank, Bob

3 9

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 2010