seaside-dev November 2008

seaside-dev@lists.squeakfoundation.org

14 participants
123 discussions

Re: [Seaside-dev] basicNew
by Avi Bryant 07 Jan '09

07 Jan '09

On Mon, Sep 29, 2008 at 12:43 PM, Randal L. Schwartz <merlyn(a)stonehenge.com> wrote: > Avi> Change super to self in this method, and (given the rest of the code > Avi> in my example) you would have infinite recursion. > > I didn't see that you had a local initialize. If you had, then > *it* should have been the one to have super initialize, since the local > initialize is superceding it by extension. And what would the rest of that method look like? What would the other methods look like? This is a fairly intricate convention and it doesn't make sense to look at an individual piece of it in isolation. If you're arguing that the local initialize should call its super method, can you also show what the rest of this (tiny) example would look like so I can understand the entire control flow you're proposing? Avi

6 14

renderloop dependency on component
by Julian Fitzell 01 Dec '08

01 Dec '08

Seaside-RenderLoop-jok.25.mcz from Seaside 2.9 by John O'Keefe <john_okeefe(a)instantiations.com> update dependencies -- Seaside-Component required John, what was causing the dependency? The intention, I think, is that RenderLoop will only depend on WAPainter (or possibly on some extra protocol) rather than on WAComponent. Julian

2 2

Issue 165 in seaside: consider WAPainter refactoring
by codesite-noreply＠google.com 29 Nov '08

29 Nov '08

Updates: Status: Fixed Comment #4 on issue 165 by jfitzell: consider WAPainter refactoring http://code.google.com/p/seaside/issues/detail?id=165 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 218 in seaside: WADispatcherEditor doing a #call: in #initialRequest:
by codesite-noreply＠google.com 28 Nov '08

28 Nov '08

Updates: Status: Fixed Owner: renggli Comment #1 on issue 218 by renggli: WADispatcherEditor doing a #call: in #initialRequest: http://code.google.com/p/seaside/issues/detail?id=218 This is fixed in: Name: Seaside-Development-lr.47 Author: lr Time: 28 November 2008, 4:45:04 pm UUID: d9653cf2-e77b-402a-841b-b3647f72e770 Ancestors: Seaside-Development-lr.46 - fixes Issue 218: WADispatcherEditor doing a #call: in #initialRequest: Additional improvements are in: Name: Seaside-Development-lr.48 Author: lr Time: 28 November 2008, 4:54:24 pm UUID: 575a119d-7fda-4398-97b7-5802df1b75a9 Ancestors: Seaside-Development-lr.47 - use #show: instead of #call: in the configuration editor, as nowhere a blocking behavior is required - this makes the configuration editor work in VA and uses much less memory -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 247 in seaside: WAValidationDecoration>>#validate does not work on all platforms
by codesite-noreply＠google.com 28 Nov '08

28 Nov '08

Comment #2 on issue 247 by WeybridgeWay: WAValidationDecoration>>#validate does not work on all platforms http://code.google.com/p/seaside/issues/detail?id=247 I've investigated exception handling in some depth to implement it in GemStone and I don't recall any rules about returning from a handler. It should just be a block like any other Smalltalk block. Good practice, however, is to explicitly return/resume at the end. I would, therefore, consider the following if you wanted to avoid an explicit method return (^) in the handler: validate: anObject ^[ validationBlock value: anObject. message contents: nil. true ] on: self exceptionClass do: [ :exception | message contents: exception messageText. exception return: false ]. James Foster -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 219 in seaside: Why does WADecorationTask override #updateStates: ?
by codesite-noreply＠google.com 28 Nov '08

28 Nov '08

Updates: Status: Fixed Owner: renggli Comment #1 on issue 219 by renggli: Why does WADecorationTask override #updateStates: ? http://code.google.com/p/seaside/issues/detail?id=219 Name: Seaside-Tests-Functional-lr.31 Author: lr Time: 28 November 2008, 4:41:15 pm UUID: 00cda7be-dda4-44b4-b6d3-047e2b9673d9 Ancestors: Seaside-Tests-Functional-pmm.30 - fixes Issue 219: Why does WADecorationTask override #updateStates: ? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 247 in seaside: WAValidationDecoration>>#validate does not work on all platforms
by codesite-noreply＠google.com 28 Nov '08

28 Nov '08

Comment #1 on issue 247 by philippe.marschall: WAValidationDecoration>>#validate does not work on all platforms http://code.google.com/p/seaside/issues/detail?id=247 Aren't there some general rules that you shouldn't to a return from an exception handler? what about: validate: anObject | valid | valid := true [ validationBlock value: anObject. message contents: nil. ] on: self exceptionClass do: [ :exception | message contents: exception messageText. valid := false ]. ^ valid Do we need a lint rule for this? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 241 in seaside: WANumberPrinter>>#digitsOf:base: uses a Float as an Array index
by codesite-noreply＠google.com 28 Nov '08

28 Nov '08

Comment #2 on issue 241 by renggli: WANumberPrinter>>#digitsOf:base: uses a Float as an Array index http://code.google.com/p/seaside/issues/detail?id=241 I think it is better to do that conversion in #digitsOf:base:, at the place where it is also creating an absolute value. I posted a fix and additional tests: Name: Seaside-Platform-lr.20 Author: lr Time: 28 November 2008, 3:44:11 pm UUID: 4d4bd2c8-a6d8-4494-8e3e-6eee35fd710b Ancestors: Seaside-Platform-lr.19 - fixes Issue 241: WANumberPrinter>>#digitsOf:base: uses a Float as an Array index Name: Seaside-Tests-Platform-lr.17 Author: lr Time: 28 November 2008, 3:48:07 pm UUID: 8eac5550-c99c-4450-87f2-15fe96cc47e7 Ancestors: Seaside-Tests-Platform-pmm.16 - tests Issue 241: WANumberPrinter>>#digitsOf:base: uses a Float as an Array index -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 247 in seaside: WAValidationDecoration>>#validate does not work on all platforms
by codesite-noreply＠google.com 28 Nov '08

28 Nov '08

Status: Accepted Owner: ---- Labels: Type-Defect Priority-Medium New issue 247 by renggli: WAValidationDecoration>>#validate does not work on all platforms http://code.google.com/p/seaside/issues/detail?id=247 Some Smalltalk platforms seem to continue evaluating the receiving block of #on:do: after processing the exception handler of a notification. Adding a return to the end of the exception handler solves this issue: validate: anObject [ validationBlock value: anObject. message contents: nil. ^ true ] on: self exceptionClass do: [ :exception | message contents: exception messageText. ^ false " <-- add this" ]. ^ false -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 241 in seaside: WANumberPrinter>>#digitsOf:base: uses a Float as an Array index
by codesite-noreply＠google.com 28 Nov '08

28 Nov '08

Updates: Status: Started Owner: wembley.instantiations Comment #1 on issue 241 by wembley.instantiations: WANumberPrinter>>#digitsOf:base: uses a Float as an Array index http://code.google.com/p/seaside/issues/detail?id=241 Updating senders of digitsOf:base: -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev November 2008