Seaside (software)

Seaside
Developer(s) The Seaside Team
Stable release
3.2.0[1] / May 6, 2016 (2016-05-06)
Written in Smalltalk
Operating system Cross-platform
Type Web application framework
License MIT License
Website seaside.st

Seaside is a free and open-source web application framework for developing web applications in Smalltalk.

Seaside provides a component architecture in which web pages are built as trees of individual, stateful components, each encapsulating a small portion of a page. Seaside uses continuations to model multiple independent flows between different components.[2] Seaside is a continuation-based web application framework[3] based on the ability to manipulate the execution stack of some implementations of Smalltalk.

Key features

Seaside's implementation of continuations was an initial point of interest in its first several years of existence following its 2002 release. Continuations provide a mechanism for rollback and resumption; a useful provision for the web browser environment in which "refresh" and "back" buttons may interrupt the flow of processing. Continuation servers give the developer the ability to maintain state on the server in a scalable manner.[4] The subsequent improvement of web browser implementations of JavaScript since 2002 has made the continuations aspect of Seaside less significant, by allowing the client browser to better keep track of state.

A distinctive feature of Seaside is its integrated development environment, providing access to development tools and debugging support within an application. In development-mode, unhandled errors are reported to the web page; developers can access and alter the program code and state directly from the web page, allowing bug identification and fixing process to occur within an integrated development environment.[5]

A Seaside application is a collection of interacting components. Each component stores state across page views and can "render" itself to the HTML stream. Thus, it is straightforward to write a component once and then reuse it elsewhere in an application. Seaside also supports the notion of tasks, which allow the programmer to describe the high-level logic of component interaction.

Seaside is not template-oriented, and does not offer the generation or use of HTML templates; HTML markup is generated programmatically. (The Seaside-based Pier content-management framework does offer wiki-markup syntax for templating.) Seaside uses callbacks on closures to specify actions to be taken when clicking on a link or submitting a form. The developers and users of Seaside argue that this helps enforce separation of structure (markup) from content and presentation (CSS).[6] Seaside's combination of components, callbacks, and closures can significantly reduce the semantic gap between a complex workflow and its representation in code.[7]

Seaside supports Ajax through integration with script.aculo.us and jQuery. Seaside also supports Comet-style server-push technology.[8]

Philosophy

Over the last few years, some best practices have come to be widely accepted in the web development field:

Seaside deliberately breaks all of these rules; Avi Bryant describes it as a 'heretical' framework. He argues[9] that this careful and reasoned rejection of the conventional wisdoms of web development has led to a very effective model for the development of web applications.

Ports

Although the main development of Seaside is implemented in Pharo,[10] there exist ports for other Smalltalk dialects. Michel Bany implemented ports to VisualWorks through Seaside version 2.7; Cincom supports Seaside as part of VisualWorks as of early 2008. Instantiations announced Seaside support in its VA Smalltalk version 8.0. As of February 2009 VA Smalltalk 8.0 is in beta. Esteban Maringolo maintained the 2.8 port, plus some other add-ons (such as script.aculo.us) for Dolphin Smalltalk X6.[11] Gemstone Systems implemented a port to Gemstone/S.[12] A port of 2.8 was completed for GemStone,[13] and a preliminary version of 3.0 runs on GNU Smalltalk 3.0a and later.[14]

Criticisms

Open-source projects using it

Proprietary projects using it

See also

References

This article is issued from Wikipedia - version of the 5/27/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.