seaside-dev December 2007

seaside-dev@lists.squeakfoundation.org

8 participants
8 discussions

Seaside2.8a1-tbn.537 and Seaside2.8a1-tbn.538
by Torsten Bergmann 14 Dec '07

14 Dec '07

Philippe wrote: >-1 on both <marquee> and <applet> The marquee tag support is already moved from the base seaside (see Seaside2.8a1-tbn.539.mcz) to the appropriate package at http://www.squeaksource.com/SeasideExamples For the applet tag, see http://java.sun.com/j2se/1.5.0/docs/guide/plugin/developer_guide/using_tags… "The HTML specification states that the applet tag is deprecated, and that you should use the object tag instead. However, the specification is vague about how browsers should implement the object tag to support Java applets, and browser support is currently inconsistent. Sun therefore recommends that you continue to use the applet tag as a consistent way to deploy Java applets across browsers on all platforms." So it would be good to support the applet tag in base seaside. If not we could also easily move the code to the appropriate demo package. Any comments. Bye Torsten -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

1 0

Seaside2.8a1-pmm.536
by Philippe Marschall 14 Dec '07

14 Dec '07

implements WAPackageInfo >> #register as a noop. This means instances of it or subclasses can't be registered anymore in the system. The way I understand these classes is that they are need only for exporting and would never be registered unless someone sends PackageInfo initialize. Is this correct or does this change introduce any problems for anyone? Cheers Philippe

1 0

Seaside2.8a1-tbn.537 and Seaside2.8a1-tbn.538
by Philippe Marschall 13 Dec '07

13 Dec '07

-1 on both <marquee> and <applet> Philippe

1 0

Contributing bug fixes in Seaside
by Jimmie Houchin 12 Dec '07

12 Dec '07

Hello, What is the preferred procedure for people like me who have a potential bug fix for Seaside. I am not one of the developers and do not mind having my work inspected by others before approval and being committed. However, I am happy to commit to the repository if that is preferred. I just don't want to cause problems. Though I am very cautious about anything I would commit. While playing around today, I ran into an error when playing with the Functional Seaside Test Suite and clicking on the Date and Time Selector. I clicked debug, and fixed the code. It is running fine now. I do not know if this is the best way to solve this bug or not. But it works. Any input greatly appreciated. renderSeconds | brush | brush := canvas textInput id: (self id isNil ifFalse: [self id , '-secs']); value: seconds asFloat rounded asTwoCharacterString; yourself. self addSecondsCallbackToBrush: brush. brush attributeAt: 'size' put: 2; attributeAt: 'maxlength' put: 2 The line: value: seconds asTwoCharacterString; was giving an error. I changed it to: value: seconds asFloat rounded asTwoCharacterString; Let me know how the community wants to handle things like this. Thanks. Jimmie

3 12

Seaside2.8a1-l.531
by Philippe Marschall 08 Dec '07

08 Dec '07

WTF? This is really you Lukas or a Monticello experiment of someone else? Cheers Philippe

2 2

Context Initialization was: Fwd: [Seaside] Seaside and Exupery patch
by Philippe Marschall 04 Dec '07

04 Dec '07

Hi Bryce Kampjes is working on Seaside on Exupery and suggested the following changes: Currently we have Continuation >> #initializeFromContext: aContext | valueStream context | valueStream := WriteStream on: (Array new: 20). context := aContext. [context notNil] whileTrue: [valueStream nextPut: context. 1 to: context class instSize do: [:i | valueStream nextPut: (context instVarAt: i)]. 1 to: context localSize do: [:i | valueStream nextPut: (context localAt: i)]. context := context sender]. values := valueStream contents With this change we would have Continuation >> #initializeFromContext: aContext | valueStream context | valueStream := WriteStream on: (Array new: 20). context := aContext. [context notNil] whileTrue: [context serialiseOn: valueStream. context := context sender]. values := valueStream contents and ContextPart >> #serialiseOn: aStream aStream nextPut: self. 1 to: self class instSize do: [:i | aStream nextPut: (self instVarAt: i)]. 1 to: self localSize do: [:i | aStream nextPut: (self localAt: i)]. Does anybody see any problems with this? Would ContextPart >> #serialiseOn: better be moved to Squeak*? Cheers Philippe ---------- Forwarded message ---------- From: bryce(a)kampjes.demon.co.uk <bryce(a)kampjes.demon.co.uk> Date: 03.12.2007 21:47 Subject: [Seaside] Seaside and Exupery patch To: seaside(a)lists.squeakfoundation.org Cc: exupery(a)lists.squeakfoundation.org I've placed Seaside2.8a1-wbk.523 on to the Seaside SqueakSource repository. This is a patch that moves the serialisation of contexts from Continuation into ContextPart. This is to allow Seaside to work with Exupery. Is it possible to get this merged into the development branch of Seaside? Yes, the latest development versions of Exupery will run Seaside, no, it's not yet practical. Expect bugs and don't expect a performance improvement yet. Bryce _______________________________________________ seaside mailing list seaside(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

4 3

Re: [Seaside] Seaside and Exupery patch
by Lukas Renggli 04 Dec '07

04 Dec '07

> Is it possible to get this merged into the development branch of > Seaside? Great news. We definitely want that to be merged in Seaside. The question now is how do we package these changes to keep them portable across dialects? I assume VW is using the Continuation implementation of Squeak and all other Smalltalks have their own? Correct? Lukas -- Lukas Renggli http://www.lukas-renggli.ch

1 0

Job Opening / Permanent Position / Germany / Seaside / J2EE
by Klaus D. Witzel 01 Dec '07

01 Dec '07

We are looking for a full-time developer to join our unconventional and small team of web-exclusive application developers. Our offices are located in the Dusseldorf area of Germany. Telecommuting from long distance is not an option, the ability to travel between our office locations is a must. The successfull candidate will have 2-4 years of experience with Seaside application development, Tomcat, Hibernate / other ORM, SQL and JSP, and deployment on Linux and Windows server platforms. Good command of the German language is a must, fluent English a plus. We are a network of companies who develop/license outstanding standard software for our long term cliens in the Finance Instrustry (regional banks and nationwide insurancers) and the Power Supply Industry (regional and nationwide utilities) throughout Germany, for their Change Management and Information Management. Our standard software is constantly being developed and maintained for meeting the ongoing demands of our existing and new clients, our fast turnaround time and the ability to accurately model user requirements and to employ open standards as well as industry standards are critical success factors. We expect our new team member to lead develop our new ticketing system and our new collaborative software documentation system (multimedia), both based on Seaside technology, but also to be a competent and reliable human factor in the development of our standard software. ------------------------ The position is permanent and to be filled immediately. Candidates are invited to contact, via email, together with salary and availability information and phone number (and time you're reachable): 'klaus witzel (at) cobss com' replace whitespace with dots After the initial telephone screening we expect the candidate to send us the full application (C.V. and photo, profile and references). ------------------------

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev December 2007