seaside June 2005

seaside@lists.squeakfoundation.org

60 participants
76 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

dynamic selection - liveCallback question
by Bany, Michel 12 Jul '05

12 Jul '05

> the thing to remember about live stuff is that the update must send new content > for an element that can be found using getElementById() in javascript. Did anybody try to update more than one element ? html attributes at: 'style' put: 'width: auto'. html selectFromList: FilterOperator availableOperators selected: operator callback: [:v |] labels: [:ea | ea opCode] liveCallback: [:item :h | operator := item. self renderValuesOn: h. self renderStatusMessageOn: h. self renderAsNameOn: h] where the three renders in the callback correspond to three different ids.

8 12

Seaside
by Günther Schmidt 05 Jul '05

05 Jul '05

Hi, I wonder if I could get any of the great old ones interested in doing a Seaside port to Dolphin? Please? Günther

7 12

Re: [Seaside] odds and ends
by Jon Paynter 30 Jun '05

30 Jun '05

Actually seaside does have a "library of widgets" one just has to spend the time to dig them out of the code. For this, examples go a LONG way. For my own development efforts, the examples packaged with 2.5 were helpful, but I found the really basic controls got overlooked -- listboxes, buttons, edit fields, etc. Basicly all the rendering methods in WAHtmlRenderer should have examples. Yes some of them would be trivial -- but then we could come back and say we have (pulling a # out of the air) 75 widgets with seaside. And be able to back it up with examples. ---------- Original Message ---------------------------------- From: stephane ducasse <stephane.ducasse(a)free.fr> Reply-To: "The Squeak Enterprise Aubergines Server - general discussion."<seaside(a)lists.squeakfoundation.org> Date: Thu, 30 Jun 2005 10:22:16 +0200 >Excellent news. >Because the reaction of this guy from MS visiting us is key: what are >the widgets you have? >made me think a lot and he was right the ease of building is important > > >Stef > >On 30 juin 05, at 9:39, Pavel Krivanek wrote: > >>> I think that what is really cruelly missing is a good library of >>> pluggable components. >>> The community should consider that: this is REALLY important. >>> >> >> I'm preparing little one right now (ftp://comtalk.net/pub/ >> seaside.png). I >> hope I will make first public release very soon. >> >> -- Pavel >> >> _______________________________________________ >> Seaside mailing list >> Seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/listinfo/seaside >> >> > >_______________________________________________ >Seaside mailing list >Seaside(a)lists.squeakfoundation.org >http://lists.squeakfoundation.org/listinfo/seaside > ________________________________________________________________ Sent via the WebMail system at mail.yans.net

1 0

RE: [Seaside] odds and ends
by Ramon Leon 30 Jun '05

30 Jun '05

> What's the answer to "Why do we want to use JavaScript for that?" ? > Sure, you can make your web app look more like a desktop app. > But is that desirable? I certainly don't want people to come > to *expect* e.g. > drag&drop on webpages. > > rado I do, and I'd bet many others do to. Web apps don't get the credit they deserve because they're thought of too much as web pages and too little as real applications. Why shouldn't a web app be more like Photoshop and let you doc stuff where you like? Why shouldn't web forms be laid out by the developer at run time with drag and drop while in design mode? It's trivial to use JavaScript and the DOM to generate the necessary CSS to store a pages layout, why should CSS be written by hand when it isn't necessary? I hate the name Ajax, but the techniques have been used for years and still aren't used enough. Seaside isn't for making web pages... other frameworks do that much better, seaside is for web applications, and it does that better than the rest, IMHO, and "full" Ajax support should be built in as soon as possible.

4 4

Microsoft "seaside" (a.k.a. C/SIDE)
by Yanni Chiu 30 Jun '05

30 Jun '05

Here's a tidbit I just came across, which may cause confusion at some point. "Essential to Microsoft Navision is its graphical integrated development environment, C/SIDE (Client/Server Integrated Development Environment). Designed for the client/server architecture, C/SIDE (pronounced seaside) is built around a high-performance, customizable relational database management system (RDBMS)."

1 0

To many liveActions on a page
by William E Harford 30 Jun '05

30 Jun '05

It appears that when I have more than 20 or so live actions on a page seaside will expire session. Is this a known limitation ? Is there a work around? Am I doing something wrong ? The below is inside a loop that creates a table. When a user clicks on the name of a patient they are shown exam information in a div below. html anchorWithAction: [] liveAction:[:h | self showPatient: (row at: 'ionumber'). self renderPatientOn: h. h script: 'resizeContents();removeHightlight();'. h script: ' document.getElementById(''patientRow',(row at: 'ionumber') asString,''').className = ''active'';'. ] fixTemps text: (row at: 'lastname') . This application works well as a traditional, non-AJAX application but I am trying to AJAXize it almost to an extreme in order to get some idea of what can and can not be piratically done. -- William E Harford <seaside(a)harford.org>

3 5

liveAction using existing method
by William E Harford 30 Jun '05

30 Jun '05

Hi all, Ok I stumped. I spent a couple hours trying to figure this out and I figure you all will be able to answer this question with out much difficulty. I have a div on my page that is drawn using ... html divNamed: 'patientContainer' with: [ self renderPatientOn: html. ]. When a user clicks on a link somewhere else on the page I would like that div to be updated using the renderPatientOn method. My thought was that I would create a new instance of WAHtmlRender and pass that to renderPatientOn but an instance var of WAHtmlRender (document) is left undefined. html anchorWithAction: [] liveAction:[:h | self showPatient: (row at: 'ionumber') . fh _ WAHtmlRenderer new. self renderPatientOn: fh. h divNamed:'patientContainer' with:fh. ] text: (row at: 'lastname') . I also simply tried using the WAHtmlRender object that is passed to liveAction ... html anchorWithAction: [] liveAction:[:h | self showPatient: (row at: 'ionumber') . self renderPatientOn: fh. h divNamed:'patientContainer' with:fh. ] text: (row at: 'lastname') . When doing it that way liveAction insisted on changing a child div of patientContainer and I figured that usage was incorrect. At this point I am starting to think I am over complicating this problem. I have portions of my page that are rendered via a method that takes WAHtmlRender as an argument. I would like to update those divs (using liveAction) using the same method. Thanks Will William E Harford <seaside(a)harford.org>

6 13

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside June 2005