seaside March 2005

seaside@lists.squeakfoundation.org

50 participants
64 discussions

Version 2.5b6 for VW is ready
by Bany, Michel 06 Nov '05

06 Nov '05

I just published Seaside 2.5b6 for VW on the public repository. It is based upon Seaside2.5b6-avi.8.mcz 15-Jan-2005 16:15 i.e. the very latest version of 2.5b6. This port includes all the fixes that were discussed here: - file upload - lost halo icons and missing styles Note: I also fixed Seaside 2.5b5 on the public repository. For the fun, I added the Seaside logo on some of the pages. Bundle to load : either SeasideForWebToolkit or SeasideForSwazoo. Enjoy, Michel.

3 4

Nested form tags
by Bany, Michel 04 Nov '05

04 Nov '05

I came accross some weird situation when using a component that is a composition of other components. A subcomponent may in turn be a composition of some more components. To make things even more complex, some deeply nested subcomponents may call some other component. Some of the subcomponents may contain some input html tag and as such will require to be contained in a form html tag. In such a complex construct it may be difficult to decide exactly what component should have the responsibility to generate the form tag. Also, it happened frequently to me that form tags become nested especially when a subcomponent calls another component that happens to be a dialog. Therefore I am making the following suggestion : Seaside should prevent form tags from being nested. It should discard any form tag that occurs within a previously opened form tag. With this in place, I can design a component that needs a form with a form construct knowing that if my component happens to be used inside a form, then my form construct will be discarded. Otherwise my form construct will be preserved. If my component calls a dialog component, the form generated by the dialog component will be discarded if my component happens to be used from inside a form. Michel.

6 6

Re: Seaside and GOODS
by Avi Bryant 12 Apr '05

12 Apr '05

(copying the list after an off-list discussion on strategies for using GOODS) On Thu, 17 Mar 2005 08:31:17 -0500, Daniel Salama <dsalama(a)user.net> wrote: > What I mean is that I was thinking/hoping to simply use the standard > collection classes to store my objects, but had my reservations in > terms of how I can use that data efficiently. For example, if I store a > zip code lookup "database" in a Dictionary (where the zip code is the > key), I should be able to search by the zip code. However, say I wanted > to present to the user, the list of zip codes, sorted by city name, I > thought I would have to extract the subset of data I wished to present > to the user, and then internally sort it in whichever way I wanted. > > What I understand you're suggesting, and I guess is mainly for > performance purposes, is that I use BTrees or TSTrees instead of the > Dictionary, for example. Right; the standard collection classes assume that the entire collection is resident in memory, and optimize accordingly. BTree and TSTree assume that the collection is mostly resident on some slower media (like disk or over the network) and so try to minimize how much of it needs to be loaded in for any given request. A 5-digit zip code would probably want to be stored as a SmallInteger key in a high-order BTree (IIRC, something like "BTree order: 20"). > I guess, internally, I may be thinking too much with a RDBMS mentality, > thinking that I could simply ask GOODS for a list of zip codes in the > state of Florida sorted by city name, as an example. I would expect this to look something like (self root stateAt: 'FL') cities asSortedCollection gather: [:ea | ea allZipCodes] That is, the root would have an index of states; the State object would have a list of its cities; the City would have a list of its zip codes. After the initial lookup of 'FL' it's all direct pointer references. > Then, the other problem that comes to mind is, if I have a person > object which stores a reference to a list of addresses, where each > address stores a reference to the zip code, how can this be > represented? The address object just stores a reference to the zip code object. > In my mind, I would try to apply the data normalization > rules I normally apply when designing a DB schema in an RDBMS, where > there would be a bunch of foreign keys in, at least, three different > tables (i.e. people, addresses, zip_codes). Would I or should I use a > similar concept when using GOODS? No. :) Don't look stuff up by keys except when the keys are user input (like 'FL' above, and even there, ideally they picked it from a list which in Seaside means you should have a direct reference to the object anyway). The equivalent of a foreign key column is simply a pointer reference (in an instance variable). If you need to go in the other (to-many) direction, store a collection. You'll sometimes only need one or the other, and sometimes need both - in which case you have to be careful to maintain the invariants: State>>addCity: aCity aCity setState: self. ^ cities add: aCity Generally, I recommend making the collection side of this the public interface, and the backlink private (#setState: vs. #state:) and never sent directly. Or the other way around, but be consistent about which you use. Many-to-many relations get a little more complex; I usually model this a little more "relationally", and keep a separate object that acts as the join table and keeps two dictionaries: one mapping X to sets of Y, the other mapping Y to sets of X, both always updated in sync. > I guess, in particular, is it smart to create an object for, say, zip > code 33180, then store that in a root object in GOODS where I keep all > my zip codes (the analogy of a zip_codes table) and at the same time > store it in the address that belongs to the person? Will GOODS store a > single instance of that zip code object and make references to the zip > codes root object as well as the address or addresses referencing it, > or would it store multiple copies of the same object (one in the zip > codes root, and another in, say for example, a people root)? It will only store a single instance of the zip code object. It's fine (and ideal) to have references to it from multiple places. > Since you seems to have more experience than me in this arena, if you > were to develop a "simple" CRM web-based tool using Seaside, would you > consider GOODS or would you simply use a RDBMS, keeping in mind that > normally CRM tools offer plenty of "ad-hoc" queries to analyze contact > information? There are very few situations where I will use an RDBMS by choice. Unless there's legacy data to deal with, or the client specifically requests it, I would much rather use some form of object database and something like XML-RPC for interop. So, yes, I would consider GOODS. The main reason at this point I would opt not to use GOODS for a particular project would be performance concerns - having to do everything over the network, combined with a lack of server-side querying, can be a real problem for some applications. Local-disk solutions like OmniBase have a real advantage here. I do think, however, that it would be possible to do some aggressive caching in GOODS to improve the situation - I just haven't had time to work on that yet. As for "ad-hoc" queries: you'll have to be more specific. The only way that relational databases offer ad-hoc querying is if the user types in SQL themselves. Is that what you would do? Otherwise, you're providing a structured UI for the user to enter their query, and so you know ahead of time what kinds of queries might be used and can structure your object model and your indices accordingly. Avi

5 10

Seaslides
by Romain Robbes 06 Apr '05

06 Apr '05

Hi all, Here is a link to the slides I used today to make a 1h30 lecture of Seaside to first-year students. They might be valuable to people looking for input when preparing other slides. You might notice that some figures where copypasted from Alexandre Bergel's one ;-). The plan is roughly as follows : - Web programming, classical and Seaside approach, 30 minutes. - How does Seaside work, 30 minutes. (With examples using the counter and the store along with the slides) - Step-by-step example : tic-tac-toe, 30 minutes (You might be interested in the code, or try to implement it ;-) ) Note that a tiny part of the material is specific, since it relies on the knowledge the students have of Scheme. I will do another, shorter lecture next week (1 hour) on more advanced concepts, as I had to skip forms for example to fit in the short time schedule. The slides (500K) are at : http://www.info.unicaen.fr/~rrobbes/seaslides.pdf Any feedback is of course appreciated. Cheers, Romain

5 8

Gardner updated
by Cees de Groot 05 Apr '05

05 Apr '05

Hi, I've moved Gardner over to latest Seaside. Nothing official yet (so not on SM), but it works fine for basic Wikis. Code on http://tai42.xs4all.nl/~cg/mc Janus is updated as well but I haven't tested it. I'm going to simplify the thing anyway, when that's done and www.tric.nl runs on latest Gardner I'll do an SM release. Regards, Cees

2 2

RE: [Seaside] Suggestion: WAFile subclass: #WAImage for image uploads
by Bany, Michel 04 Apr '05

04 Apr '05

Dmitry, The attachment is for VisualWorks. You may want to try to Squeakify it and see how you like it. We may not need any new rendering method after all. Michel.

3 4

Problem starting Seaside
by Daniel Salama 02 Apr '05

02 Apr '05

Hi, I'm having some problems starting Seaside in my VM. I'm on OSX running 3.7.5Beta1. I've been running this version for some time and all of the sudden I cannot run Seaside anymore. I decided to download a fresh copy of Squeak for OSX and installed Seaside using the package manager. However, when I "do" WAKom startOn: 9090 in a workspace, I get the following exception: WAKom class(Object)>>doesNotUnderstand: #unregister WAKom class>>pause WAKom class>>stop WAKom class>>startOn: UndefinedObject>>DoIt Compiler>>evaluate:in:to:notifying:ifFail:logged: ... I don't know what has changed. This is a fresh Squeak VM copy with only Seaside loaded. Everything else is standard. Please help. Thanks, Daniel

3 2

Seaside suggestions :-)
by Marco Qualizza 02 Apr '05

02 Apr '05

I'm sorry for the intrusion if this isn't the correct list for this question, but where does one suggest fixes/changes to Seaside? For example, while #a = 'a' is true in Squeak, it evaluates to false in VW, while #a = 'a' asSymbol evaluates correctly in both. (On VW the pretty printer doesn't work. ;-) ) So, the changes that I'd like to suggest are, in WAPrettyPrintedDocument>>isKnownTag: change ^ self knownTags includes: aString to ^ self knownTags includes: aString asSymbol and in WAPrettyPrintedDocument>>isKnownAttribute: change ^ self knownAttributes includes: aString asLowercase to ^ self knownAttributes includes: aString asLowercase asSymbol Thanks, Marco

2 1

Suggestion: Page generation time to be shown on toolbar in test mode
by Dmitry Dorofeev 02 Apr '05

02 Apr '05

Hi all, I think it would be useful to see page generation time shown at the bottom in the test mode. Right to the XHTML link. I think it is 5 seconds to implement, but would like to see it as a standard Seaside feature, not only my addition to it. Thanks, -Dmitry.

2 1

defaultAction:
by Bany, Michel 02 Apr '05

02 Apr '05

Avi, I am busy porting 2.5b7 to VW so that it gets ready for VW 7.3.1. There is something puzzling regarding defaultAction: Consider the following renderContentOn: html html form: [html defaultAction: ['default callback' inspect]. html text: 'Input:'. html textInputWithValue: 'Change this' callback: [: v | v ]. html break. html submitButtonWithAction: ['ok callback' inspect] text: 'OK'] After entering some data and hiting the Return key the result is different depending on the browser. With IE6, the default callback gets evaluated With Mozilla or Firefox, the ok callback is used. With this : renderContentOn: html html form: [html submitButtonWithAction: ['default callback' inspect] image: html transparent1X1Form. html text: 'Input:'. html textInputWithValue: 'Change this' callback: [: v | v ]. html break. html submitButtonWithAction: ['ok callback' inspect] text: 'OK'] Here too it depends on the browser. With Mozilla or Firefox, the default callback is evaluated With IE6, neither callback is used. This gave me the idea to reimplement defaultAction: so that it provides both techniques. defaultAction: actionBlock self inputWithType: 'hidden' named: (self callbacks registerDefaultActionCallback: actionBlock). self submitButtonWithAction: actionBlock image: self transparent1X1Form. With this new implementation, the first example (above) works as expected and equally with all three browsers. Finally, we can also re-implement this formWithDefaultAction: defaultBlock do: aBlock self form: [self defaultAction: defaultBlock. aBlock value] Michel.

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside March 2005