seaside October 2014

seaside@lists.squeakfoundation.org

23 participants
26 discussions

Seaside 3.1.3
by Johan Brichau 23 Sep '15

23 Sep '15

Hi Seaside users, We have released Seaside 3.1.3 [1]. A big thanks to everyone involved for making this release happen! best regards, The Seaside Team [1] https://code.google.com/p/seaside/wiki/Seaside313Changelog

5 10

Re: Setup Pier environment
by Stephan Eggermont 05 Nov '14

05 Nov '14

Hi Dario, There are ci builds of Pier and PierAddons on ci.inria.fr. They are green, but not everything works. The easiest way to make things work is to add red tests so you break the build and then commit fixed versions and configurations. If you don't know how to fix, just adding red tests already helps a lot. Just ask in the pharo-dev list for an ci account, then you can log in and get a much better view on what exactly is loaded and tested in a build. What we are currently missing is tests that can pinpoint the use of deprecated methods/classes. As you noticed, most needed fixes are rather trivial. Our Pier3 installation works, but of course does not use all add-ons. We fixed the problems we encountered, and will (sometimes slowly, we have a week of holidays here) continue doing so. Do you plan on moving to a newer Pharo version soon? Stephan

5 12

Can I know if a WATask answered?
by Mariano Martinez Peck 03 Nov '14

03 Nov '14

Hi guys, There is an scenario that I don't know how to deal. I have a main component that displays tabs. Each tabs render a component. This component could be anything, including a task. The tab has correctly defined the #children. And the way the tab displays its current contents (a component) is via: "self activeTabComponent renderOn: html" The problem is if "activeTabComponent" is a Task. Since I am not doing not replacing anything (calling), I do not use #call: but #renderOn: as displayed above. The task can, at any point in time, or when the user clicks "Finish" do a "self answer: nil". I don't know what happens with this "self answer:" because I didn't do a #call: to that task. Anyway... I would like to hook from my main component and I would like to know if the task has answered or even if the #go method finished so that I can automatically close the tab and remove this task. Of course, I can pass the main component to the task, and then from the task itself tell the main component that he has finished...but I don't like this very much. Any idea? Thanks in advance -- Mariano http://marianopeck.wordpress.com

4 4

SeaSide REST
by Rubens Gomes 31 Oct '14

31 Oct '14

I am learning Smalltalk, and I am developing a REST service on top of Pharo 3 with Latest update #30859. I have installed the latest SeaSide I have done a Manual Installation of the most recent Configuration of SeaSide. And I have installed the latest SeaSide30Addons. I would like to ask a few questions: 1) Why do I see this error in SeaSide, and how do I fix it? I have the latest SeaSide running on latest Pharo 3 with Seaside-REST http://localhost:8080/ Error: you are forbidden to access "/" 2) I have a Seaside REST object that is not responding to the URL request below. http://localhost:8080/weight/kg?lb=10 I have the following class/instance configuration. Am I missing something else? WARestfulHandler subclass: #WeightRestHandler its class initialize method contains: WAAdmin register: self at: self 'weight'. And it has an instance method "weight" with following annotation: <get> <produces: 'text/json'> <path: '/{toUnit}?{fromUnit}={aNumber}'> Rubens

3 2

JQAutocomplete and #onAjaxStart:
by Mariano Martinez Peck 30 Oct '14

30 Oct '14

Hi guys, My app has a some code (thanks Esteban Lorenzano for sharing it with me) to show a little "Loading..." banner... That is: renderAjaxLoadingDivOn: html html div style: 'display:none'; class: 'loading'; script: (html jQuery this onAjaxStart: (html jQuery this show); onAjaxStop: (html jQuery this hide)); with: 'Loading...' Now...it works well for some explicit parts where I use ajax. However, it doesn't work for the JQAutocomplete. It my case, the callback to the autocomplete can take some seconds. It seems #onAjaxStart: is NOT intercepting what the autocomplete os doing. Could it be because autocomplete is doing a getJson actually? The key code of the autocomplete is: search: aSearchBlock labels: aLabelsBlock callback: aCallbackBlock "A one argument block aSearchBlock that will be evaluated with the term the user currently typed. The block is expected to answer a collection of objects. aLabelsBlock should answer a string label to be displayed for each object. aCallbackBlock is evaluated with the selected object and an ajax script to be performed." | term mapping | mapping := IdentityDictionary new. "assigments to temps don't work in GS 2.4' http://code.google.com/p/glassdb/issues/detail?id=221" term := WAValueHolder new. self source: ((self jQuery getJson callback: [ :value | term contents: value ] value: (JSStream on: 'request.term'); text: [ :stream | stream json: ((aSearchBlock value: term contents) asArray collect: [ :object | GRSmallDictionary new at: 'label' put: (aLabelsBlock value: object); at: 'index' put: (mapping at: object ifAbsentPut: [ mapping size + 1 ]); yourself ]) ]; onSuccess: 'response(arguments[0])'; dataType: 'jsonp') asFunction: #('request' 'response')). self onSelect: ((self jQuery ajax callback: [ :value | term contents: value greaseInteger ] value: (JSStream on: 'ui.item.index'); script: [ :script | mapping keysAndValuesDo: [ :object :value | value = term contents ifTrue: [ aCallbackBlock value: object value: script ] ] ]) asFunction: #('event' 'ui')) Any help would be very appreciated. Thanks, -- Mariano http://marianopeck.wordpress.com

3 6

Worker images with nginx and URL hash for sticky sessions
by Torsten Bergmann 25 Oct '14

25 Oct '14

Hi, in nginx one can use for load balancing: upstream seaside { ip_hash; server 127.0.0.1:8080; server 127.0.0.1:8081; ... } This is using the IP Hash method for balancing (http://nginx.com/products/application-load-balancing). Any experience how to configure the more generic Hash method (based on user-defined key such as the URL) with nginx? Similar to what is described for Apache: http://book.seaside.st/book/advanced/deployment/deployment-apache/mod-proxy… but for nginx? Thx T.

5 4

WAFileMetadataLibrary>>#deployFiles ignores directories
by Udo Schneider 23 Oct '14

23 Oct '14

All, Up to now I served some assets from within my image. To increase loading speed I decided to serve them using nginx. I thought that MyLib class>>#deployFiles would write the files to disk - and it does. Although all files in the same dir (same name as the class). So the directory structure is lost. This also means that paths created by MyLib / dirfilenameCss results in MyLib\filename.css and not in MyLib\dir\filename.css Is this the intended behaviour? Best Regards, Udo

1 0

Setup Pier environment
by dtrussardi＠tiscali.it 22 Oct '14

22 Oct '14

Ciao, i need to test the Pier into Pharo. Yesterday i work to load the Pier environment into Pharo2.0. I found some error relative the ConfigurationOfPier3AddOns ( see relative mail ). Now this problems are resolved but the Pier Admin interface work with some problem. I think to reload all Pier environment into a new Pharo 2.0 #20628 image with the command: Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPier3AddOns'; load. ConfigurationOfPier3AddOns load. But the system erase the error : MessageNotUnderstood: SmallInteger>>isEmpty resolveToLoadableSpecs: required map: packageMap | reqd allReqd map newReqd spec | reqd := required copy. allReqd := Set new. map := self packages map. ***** 632756487 ***** [ reqd isEmpty ] whileFalse: [ newReqd := Set new. reqd do: [:req | (self resolveToLoadableSpec: req forMap: map packages: packageMap) do: [:loadableSpec | newReqd addAll: loadableSpec requires. newReqd addAll: loadableSpec includes ]]. allReqd addAll: reqd. newReqd removeAllFoundIn: allReqd. reqd := newReqd ]. packageMap keys do: [:pkgName | (spec := (packageMap at: pkgName) resolveToLoadableSpec) == nil ifTrue: [ packageMap removeKey: pkgName ] ifFalse: [ packageMap at: pkgName put: (packageMap at: pkgName) resolveToLoadableSpec ]] SmallInteger(Object)>>doesNotUnderstand: #isEmpty MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: MetacelloMCVersionSpec>>resolveToLoadableSpecs: MetacelloMCVersionSpec>>expandToLoadableSpecNames: in Block: [:cache | ... MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: in Block: [:dict | ... MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:at:doing: MetacelloMCVersionSpec>>expandToLoadableSpecNames: MetacelloMCVersion>>expandToLoadableSpecNames: MetacelloMCProjectSpec>>relativeCurrentVersion in Block: [vrsn expandToLoadableSpecNames: (loadList := self...etc... BlockClosure>>on:do: MetacelloMCProjectSpec>>relativeCurrentVersion MetacelloProjectReferenceSpec>>relativeCurrentVersion MetacelloMCVersionSpec>>isPartiallyCurrentAgainst: in Block: [:prj | ... MetacelloProjectReferenceSpec>>projectDo:packageDo:groupDo: MetacelloMCVersionSpec>>specsNamed:projectDo:packageDo:groupDo: in Block: [:name | | pkgSpec | (pkgSpec := map... Array(SequenceableCollection)>>do: MetacelloMCVersionSpec>>specsNamed:projectDo:packageDo:groupDo: MetacelloMCVersionSpec>>isPartiallyCurrentAgainst: MetacelloMCProject(MetacelloProject)>>currentVersionAgainst: in Block: [:version | ... Array(SequenceableCollection)>>do: MetacelloMCProject(MetacelloProject)>>currentVersionAgainst: in Block: [:cache | ... MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: in Block: [:dict | ... MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: ------------------------------------------------------------------- Now i wonder that is the best solution to obtain a Pharo Pier environment that works. It's best follow the creation of new Pharo image as in this e-mail, ( it's best load Seaside - Magritte - Pier separately ? ) or manage the error as write in my last email Re: [Seaside] ConfigurationOfPier3AddOns load error Thanks for any considerations, Dario

2 7

ConfigurationOfPier3AddOns load error
by dtrussardi＠tiscali.it 21 Oct '14

21 Oct '14

Ciao, for testing the Pier admin image widget functionality ( see relative entry ) i load into Pharo 2.0 image the packages: Seaside3 3.1.3.1 Magritte3 3.1.5 Magritte3Addons 3.1.3 Pier3 3.1.1 When i do the coomand to load: Pier3Addons 3.1.1 the system erase the eror: MetacelloProjectSpecLoadError: No version found for #'1.0.1' of ConfigurationOfNAFileUpload the relative stack is: MetacelloMCProjectSpec>>loadVersion: MetacelloMCProjectSpec>>load MetacelloProjectReferenceSpec>>loadUsing:gofer: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [:pkg | pkg loadUsing: self gofer: gofer] OrderedCollection>>do: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: in Block: [super linearLoadPackageSpecs: packageSpecs reposi...etc... BlockClosure>>ensure: MetacelloLoaderPolicy>>pushLoadDirective:during: MetacelloLoaderPolicy>>pushLinearLoadDirectivesDuring:for: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>load MetacelloMCVersionSpecLoader>>load MetacelloMCVersion>>executeLoadFromArray: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [:dict | ^ self executeLoadFromArray: anArray] MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [self versionSpec loader: newLoader.... BlockClosure>>ensure: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [[self versionSpec loader: newLoader.... MetacelloPharoPlatform>>do:displaying: in Block: [aBlock value] BlockClosure>>ensure: RPackageSet class>>withCacheDo: MetacelloPharoPlatform>>do:displaying: in Block: [:bar | ... BlockClosure>>cull: Job>>run in Block: [result := block cull: self] BlockClosure>>on:do: Job>>run in Block: [self prepareForRunning.... BlockClosure>>ensure: ---------------------------------------------------- The ConfigurationOfNAFileUpload loaded by the system include: version101: spec <version: '1.0.1' imports: #('1.0-baseline')> spec for: #common do: [ spec blessing: #release. spec project: 'Seaside' with: #'release3.1'. spec package: 'NAFileUpload-Base' with: 'NAFileUpload-Base-NPaulDeBruicker.13'. spec package: 'NAFileUpload-Component' with: 'NAFileUpload-Component-NickAger.49'. spec package: 'NAFileUpload-Example' with: 'NAFileUpload-Example-NickAger.3'. spec package: 'NAFileUpload-Nginx-Component' with: 'NAFileUpload-Nginx-Component-NickAger.1'. spec package: 'NAFileUpload-Nginx-Example' with: 'NAFileUpload-Nginx-Example-NickAger.1' ] Everything seems ok, but don't work. Thanks for any considerations, Dario

3 6

Re: ConfigurationOfPier3AddOns load error
by Stephan Eggermont 21 Oct '14

21 Oct '14

I've updated the configurations. In addition there was a typo in a package name. It loads in the Pier3Addons 3.0 image with release3.1 from ci Stephan

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside October 2014