seaside-dev August 2011

seaside-dev@lists.squeakfoundation.org

10 participants
10 discussions

Configurations, again…
by Philippe Marschall 03 Sep '11

03 Sep '11

Hi I'm once again banging my head against the wall that is our configuration system. First, I have an attribute #trackingStrategy in WARegistryConfiguration that defines as the only option a query field strategy. I have the same attribute again in WAApplicationConfiguration having many more options like cookie based. However in the configuration editor only the options from WARegistryConfiguration show up. Is this supposed to work? To me the code is incomprehensible and undebuggable. Second, what I want is an instance from a list of classes. This doesn't really seem to be supported. I could just #collect: #new but then I have to implement #= to only compare the class names. Any suggestions? Third, WAUserConfigurationEditorVisitor >> #visitListAttribute: always sends #beOptional. I don't want to have the option to select nil. Looking at the other configurations #serverProtocol in WARequestHandlingConfiguration seems to be the only one for which nil makes sense. Wouldn't it be better to make the list not optional and if you want to allow nil you have to include it in the options explicitly? Fourth, I really believe our configuration system is way too complex and slow as a result (which matters because creating a URL as to look up #serverPath and friends). As a first simplification step, does a configuration really need multiple parents? Couldn't we get away with just one? Cheers Philippe

4 6

Invitation to connect on LinkedIn
by Avi Shefi 30 Aug '11

30 Aug '11

Seaside, I'd like to add you to my professional network on LinkedIn. - Avi Avi Shefi CTO at Heartland - Salepoint Israel Confirm that you know Avi Shefi: https://www.linkedin.com/e/ngq8wc-grzdlswj-6h/isd/4033139034/Jq9fniiZ/ -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/ngq8wc-grzdlswj-6h/vFToWuoJwK3hUwvKXHUwERSl8KcIal… (c) 2011 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.

1 0

Where is Seaside-Tests-Canvas-pmm.55?
by Philippe Marschall 17 Aug '11

17 Aug '11

Hi I think Seaside-Tests-Canvas-pmm.55 is the version of Seaside-Tests-Canvas that should be used in Seaside 3.0 currently. However what's currently in is Seaside-Tests-Canvas-jok.55 and Seaside-Tests-Core-pmm.246 which produces dirty versions because only half the fixes for Issue 671 are in. Does anybody know what happened? Did SqueakSource yet again lose versions? Cheers Philippe

5 7

[ANN] Dynatree as part of jquery widget box
by Torsten Bergmann 16 Aug '11

16 Aug '11

I've wrapped the dynatree as a jquery widget for seaside as part of the jquerywidgetbox project. This widget represents a tree, see: http://wwwendt.de/tech/dynatree/doc/samples.html Load latest version of ConfigurationOfJQueryWidgetBox and then JQWidgetBox-Dynatree-Dev-tbn.3 JQWidgetBox-Dynatree-Core-tbn.3 evaluate JQWidgetExample initialize and point your browser to http://localhost:8080/jquery-widgets/dynatree for a simple demo. It's working but not yet complete. I will later also update the config so it gets loaded with the project. Have fun T. -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone

1 0

GRPlatfom>>deleteFile:ifAbsent:ifFail:
by Philippe Marschall 16 Aug '11

16 Aug '11

Where is that used? Philippe

2 3

MAConditionError opens a debugger
by Romain Verduci 12 Aug '11

12 Aug '11

Hi, I have a problem with my seaside application using MAConditionError. It's suppose to display a message error and in my case it opens a debugger. Code with MAConditionError : MAConditionError description: self description signal: 'Invalid name or password.'. I don't understand why it does this. To simplify the explanations and reproduce the bug, you can: - download my image on: http://demo.ovh.com/fr/466c8bec0e28467ab3d473647833e0e8/ - copy the service/ dir on your root dir (/) - run the image - go to localhost:8080/sh - try to login with a fake name And then the MAConditionError opens a debugger when there is an error in login. Thanks Romain

1 0

About 3.0.6
by Philippe Marschall 08 Aug '11

08 Aug '11

Hi Again we have a nice collection of fixes [1]. Also it seems that John has been active so that hints to a release there. What's peoples feeling about doing a 3.0.6? [1] http://code.google.com/p/seaside/wiki/Seaside306Changelog Cheers Philippe

3 3

Re: [Pharo-project] Web app security
by Dale Henrichs 06 Aug '11

06 Aug '11

Laurent, I think that the best defense is the limited access/rights unix account, perhaps even a separate unix user per account (to provide isolation between accounts) ... I think this is what VMware does in in its Cloud Foundry ... to be completely safe you'd have to turn off the ability to read and write files and turn off socket access (this is what javascript in the browser does), but going this far severely limits what you can do in the image ... I would think that you could screw things down pretty tight just using unix permissions .... Dale ----- Original Message ----- | From: "laurent laffont" <laurent.laffont(a)gmail.com> | To: "Seaside - developer list" <seaside-dev(a)lists.squeakfoundation.org>, "An open mailing list to discuss any topics | related to an open-source Smalltalk" <pharo-project(a)lists.gforge.inria.fr> | Sent: Saturday, August 6, 2011 3:06:38 AM | Subject: [Pharo-project] Web app security | | Hi, | | | with a public SmallHarbour (public fork of SeasideHosting - | smallharbour.org ) people can upload images that do bad things: | change filesystem, run commands, .... | | | Actually, what are the ways of securing a server so people can't do | bad things ? | | | I'm thinking of: | - run the vm/image within a low right unix account | - remove dangerous plugins (OSProcess, ?) | | | Can we easily chroot ? | | | what are known solutions ? | | | Laurent.

1 0

Seaside 3.1 open
by Philippe Marschall 03 Aug '11

03 Aug '11

Hi As announced I copied the session tracking branch and the current versions of the rest to the 3.1 repository (currently only the Metacello configurations are missing). The I removed all the deprecated methods. Among others this includes: - WACurrentSession - #displayString - prototype deployment libraries The only ones still standing are where methods are deprecated in the JavaScript libraries rather than in our wrappers (SUInPlaceEditor, PTElment, JQueryClass >> #browser). Then I fixed an amazing number of tests that were still sending deprecated messages. I also did a short check on the functional tests. I still expect there to be some senders left, especially in the JavaScript area. It seems that all our wiki pages are gone. Can somebody confirm this? Is anybody aware of a Google code outage? [1] http://www.squeaksource.com/Seaside31 Cheers PHilippe

3 4

session tracking branch ready for merging
by Philippe Marschall 01 Aug '11

01 Aug '11

Hi The branch that removes how a session/handler should be tracked from registry/application into a dedicated class is ready for a merge [1]. Since it breaks #useCookie and I had to remove some deprecated methods on application the consensus seems to be that this should mark the beginning of 3.1. If everybody agrees I'll copy the versions and the current ones from the 3.0 repository to the 3.1 repository and remove all the deprecated methods. [1] http://www.squeaksource.com/SeasideWip Cheers Philippe

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev August 2011