seaside September 2005

seaside@lists.squeakfoundation.org

48 participants
38 discussions

Re: [Seaside] Template support in Seaside 2.5
by Adnan Zaman 07 Feb '06

07 Feb '06

Hi Alain, Your fix works so thanks for that. However, I see that my html text was not "rendered" as you would expect to see in a browser. All I saw was the same html text that I wanted to be rendered. Not sure if this has anything to do with your another email in which you asked about rendering problem in 2.5. - Adnan >>Date: Tue, 21 Jun 2005 22:42:30 +0200 >>From: Alain Fischer <alain.fischer(a)bluewin.ch> >>Subject: Re: [Seaside] Template support in Seaside 2.5 >>To: "The Squeak Enterprise Aubergines Server - general discussion." >> <seaside(a)lists.squeakfoundation.org> >>Message-ID: <daafe26dd5ae1e8b1e8f16ded82f3fdf(a)bluewin.ch> >>Content-Type: text/plain; charset=ISO-8859-1; format=flowed >> >>Hi Adnan, >> >>For the first issue, I doesn't got a dependency warning. >>Here is how I setup my image: >>- downloaded prebuild image from Avi >>(http://beta4.com/seaside2/Seaside-2.5.zip) >>- used SqueakMap Package Loader to install SmaCC Smalltalk >>Compiler-Compiler-Runtime version: 4 >>- opened a repository on the disk space containing >>SeasideTemplate-AFi.1.mcz >>- loaded this package in the image. >> >>For the second issue here is a fix: >> >>STTTemplate>>compileIn: aClass >> >> | methodNode | >> methodNode _ Compiler new >> compile: self asSmalltalkMethod >> in: aClass >> notifying: nil >> ifFail: [^ nil]. >> aClass >> addSelector: methodNode selector >> withMethod: (methodNode generate: #(0 0 0 0)). >> aClass organization >> classify: methodNode selector >> under: 'generated'. >> "aClass compileProgrammatically: self asSmalltalkMethod classified: >>'generated'" >> "| node method | >> node := Compiler new >> compile: self asSmalltalkMethod >> in: aClass >> notifying: nil >> ifFail: [self error: 'Syntax Error']. >> method := node generate: #(0 0 0 0). >> aClass addSelector: node selector withMethod: method." >> >> >>and it should work. >> >>If you try to run STTTest in Test Runner, you will notice: >>'13 run, 12 passes, 0 expected failures, 0 failures, 1 errors, 0 >>unexpected passes' >> >> >>Alain __________________________________ Yahoo! Mail Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail

4 4

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

[ANN] the Bicephale project
by Michal 12 Oct '05

12 Oct '05

Hi all - I would like to announce the first version of the Bicephale project: <http://software.auf.net/bicephale/Bicephale3-mist.1.mcz> The goal of Bicephale is to change Seaside to make it handle elegantly the display of static, long-lived objects. As it stands, Seaside is very powerful at handling sessions - sequences of pages that represent a dynamic operation and for whom bookmarkability and long-term persistence is not an issue. Seaside is however somewhat clunky at displaying simple, unchanging pages with stable and bookmarkable urls. Since most applications with sessions also need such stable pages to display the objects they are editing, Seaside suffers from this even on its home turf. To take an example, if you view a blog entry with Smallblog - the Seaside blog application - you get a different url every time you view the entry. This creates several problems: (i) such pages cannot be easily bookmarked although they should be (Smallblog resorts to a workaround for this); (ii) they cannot be indexed although one would want them to; (iii) such pages 'expire' after a while, and clicking on a link after expiration has unexpected effects, confusing the user. Almost every Seaside application suffers from this, whether it is a store, a ticketing application or an academic article repository. There are currently workarounds for these issues, but Bicephale aims at solving the problem at its root, in an elegant and principled way. It does that by introducing static, long-lived callbacks (following up on these two February 2005 posts on the Seaside list by Avi and myself: <http://lists.squeakfoundation.org/pipermail/seaside/2005-February/004400.ht…> <http://lists.squeakfoundation.org/pipermail/seaside/2005-February/004436.ht…> ) These lasting callbacks are rendered by a new type of components (WAStaticComponent) that live outside of sessions but within the application. Apart from having stable urls, these components behave just like session components: i. they use standard Seaside rendering methods - e.g. they render with the usual #renderContentOn: and link to another object with 'html anchor: anObject text: aString'. ii. they can #call: traditional dynamic components (WAComponent) and receive an #answer: from them. A static component can for instance include a (stable) link to edit the object currently displayed. That link will trigger a standard seaside login dialogue and based on the answer, it initiates a traditional Seaside editing session. iii. the handling of urls is largely transparent to the developper. Much of Seaside's appeal is the ability to concentrate on the logic of the application and have the framework automatically handle the details of the underlying http transaction, including the urls used. This is the same with static components. A Bicephale application (WABicephale) has therefore two root components: the usual session root component and the new root static component (hence the Bicephale name). By default the application renders the static component, and sessions are used only when a #call: is issued. This first version implements all of the above, but in a preliminary and experimental way. This means that it is now almost trivial to display static object with automatically generated fixed urls and have them call/answer dynamic components. At the same time, I am still experimenting with various implementations, and looking for the right abstractions -- particularly in the handling of urls/component composition. Since almost every design decision is still open to drastic revision, I would appreciate feedback! Finally, there is currently no UI or documentation. I will however post a sample application, and if there is interest, I will provide some basic documentation. Michal ps. there are no modification to base Seaside classes in this package - it only adds new classes. It should hence be harmless to install it into your Seaside image, but this being an early prototype, caveat emptor.

5 7

newbie question: deployment and RDBMS support
by C R Zamana 01 Oct '05

01 Oct '05

Hi all! Sorry for the totally newbie questions, but I was unable to easily find them: 1) How can I deploy a web application to my customers? They need to download some kind of "runtime engine" or "plugin", or just the browser is enough? 2) What about if I need to connect to a PostgreSQL database? Thank you. Best regards.

3 2

Re: [ShoreComponents] WebTree, SVG demo and dynamic files
by Jan B. Krejčí 26 Sep '05

26 Sep '05

> From: radoslav hodnicak <rh(a)4096.sk> > > 3) a decorator allowing to preserve page scrolling coordinates between > > submits, so if you have scrolled 5 feet down to find the button you > > want to click, you will see the same page location after the response > > is loaded from server. I saw this in .NET and I like it very much. > > Do you know how is it implemented in .not? Page anchors won't scroll > vertically (at least not in IE). I'd like to have this one too so I'm > willing to implement it. sure. please have a look into enclosed HTML file. It's done this way: 1) reister onScroll handler to <body> 2) in the handler store the coordinates into hidden form fields 3) make sure they are submitted with each clickable component you need 4) put a script at the end of the page causing the scroll position is restored after the page is loaded (or use <body onLoad="..."> that's all > I will try to pick some interesting pieces from my app and add it to the > collection but really, can we pick a better name than ShoreComponents? It > hurts my fingers. Something shorter, like Seadgets or whatever... uh, well, I do not really insist on "ShoreComponents" name, but please consider what impact would that have. How about creating some voting component, expose it in the demo and count other's opinions? :) -- .:jbk:. Jan B. Krejci

11 12

Javascript stuff
by Avi Bryant 25 Sep '05

25 Sep '05

I've been doing some work on Javascript support over the last few days. It's still incomplete, but it's at a stage that other people might find interesting. The first part is an extension to the Seaside package itself, found in the latest a2 dev versions on SqueakSource. This is a new method on WASession, #addLoadScript:. Any strings you pass to that method will be collected into an onLoad() function which is appended to the bottom of the next response, and used as the onLoad handler for the body tags. In general, it's probably better to use this while rendering than to use an inline #script:, because it will execute at a more predictable time. But the especially interesting part is that it can be sent from a callback, to add a script that will be included on the subsequent render. I find that I frequently want this for things like setting the location.hash property (where the browser scrolling will jump to) following some action. The second part is a separate library that models the Prototype library (http://prototype.conio.net/) and its Script.aculo.us set of effects (http://script.aculo.us/). It's the Scriptaculous package inside the Seaside project on SqueakSource. You can poke around the demos on the script.aculou.us site to get an idea of what it does. The approach I'm taking is to have one instance per Javascript function call, that knows how to #asString itself into the appropriate Javascript source, so it can be used as a parameter for #onClick: or #script:. You can see some simple usage examples in the SUExample class. Using, for example, the "highlight" effect looks like this: "highlight this div when the user clicks on it, and fade out over 5 seconds" html div onClick: (html effect highlight duration: 5); with: 'Foo' "highlight the element with id 'bar' when the user clicks on this div" html div onClick: (html effect highlight id: 'bar') with: 'Foo' "highlight this element immediately on page load" html div script: (html effect highlight) Note that WARenderCanvas has an #effect method here which makes it convenient to create SUEffect objects, but these are *not* tag objects like WARenderCanvas>>div or WARenderCanvas>>anchor etc. I also added an #effect method on WASession which makes use of #addLoadScript:, allowing you to use effects from callbacks: someCallback self doSomethingWorthyOfHighlighting. self session effect highlight id: 'someElementOnTheNextRender'; duration: 10. There's also some AJAX support that is similar to, but a completely different implementation from, the liveRequest stuff that now lives in SeasideAsync. For example: html div id: 'toBeReplaced'; with: 'Placeholder text'. html anchor onClick: (html ajax id: 'toBeReplaced'; renderBlock: [:r | r text: 'Some new text']); text: 'Replace the placeholder text asynchronously'. There's quite a bit more stuff in those libraries (autocompleting text inputs, drag and drop, more effects), but this should be enough for people to evaluate the general strategy and give me some feedback. Cheers, Avi

2 2

How to spawn a process ?
by Dmitry Dorofeev 23 Sep '05

23 Sep '05

Hi all, I trying to spawn a process from WAComponent which should run quite long time. I do it like this: process := [dataBank do: [:e| self processData: e.]] newProcess. process resume. But i found my squeak process eating 98% of CPU and morphic non responding after a while. Have i missed something ? Thanks. -Dmitry.

2 1

seaside sites
by Martin Rubi 22 Sep '05

22 Sep '05

Hi all. Would any of you have a link to any site done with Seaside with nice charts on it ? I know a fellow who has to do a web application to show lots of charts and bar graphics and he asked me if I knew any. If there is no such site with public access, I guess a few screenshots or some other sites, even with no charts, might work as well (I know I saw charts in some Seaside tutorial, so they could be done, right ?). Thanks in advance. Martin

3 4

Seaside and HandHeld Devices
by Adnan Zaman 21 Sep '05

21 Sep '05

Is it possible to use SeaSide for developing web apps for handheld such as T-MOBILE SIDEKICK II (to be very specific here)? Any ideas are appreciated. Regards, Adnan __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

3 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 September 2005