-
Notifications
You must be signed in to change notification settings - Fork 71
Seaside Load Groups and Packages
Seaside is composed of several parts, often mapping to a separate code package or a Metacello group, so you can load only the parts you need when working on your own Seaside application project. Obviously, the configuration specifies all required dependencies, so that when you want to load the 'JQuery' group, the 'Javascript' group will automatically be loaded as well.
The default load group (i.e. when you do not specify any specific groups to load) loads the most common parts you will need when building a web application. This is perfect when you start out with Seaside. However, at some point in time, you will want to load additional groups or leave out the parts you do not use in your own project.
Here is a complete list of Metacello groups you can use, with a small description of the contents. If you want to know more, check out the Metacello config in the BaselineOfSeaside3
class.
- Core: This is the core of Seaside you will need in all cases.
- JSON: Serialize Smalltalk objects to JSON, deserialize JSON to Smalltalk objects and produce JSON responses in general using a JSON parser and Seaside JSON canvas.
- REST: Create a REST API service (See https://github.com/SeasideSt/Seaside/wiki/Seaside-REST)
- Email: Support for sending emails
- Javascript: Support for generating Javascript code
- JQuery: Binding for generating jQuery scripts (http://www.jquery.org)
- JQueryUI: Binding for jQuery-UI components (https://jqueryui.com/)
- Scriptaculous: Binding for Scriptaculous (https://script.aculo.us/) and prototypejs (http://prototypejs.org/)
- RSS: Support for building RSS feeds
- Security: Extensions to activate specific security features
- Seaside-InternetExplorer: Support for Internet Explorer-specific features
- Comet: Polling-based updates (See http://book.seaside.st/book/web-20/comet)
-
Filesystem: Support for
WAFilelibrary
functionality on disk instead of via the image (i.e.WAExternalFileLibrary
) - Seaside-ExternalFileUpload: Support for large file uploads, off-loaded to Nginx (http://jbrichau.github.io/blog/large-file-upload-in-seaside)
- Gettext: i18n solution for Seaside apps (https://www.gnu.org/software/gettext/)
- Development: Development tools
- Slime: Lint rules
All the web server adaptors are also contained in separate groups. You need at least one adaptor to serve your Seaside application.
- Zinc: Default (and recommended) in Pharo (http://zn.stfx.eu/zn/index.html)
- WebClient: Squeak only. (http://ss3.gemstone.com/ss/WebClient.html)
- Swazoo: http://www.squeaksource.com/@nRFs5PD_3rsW_l2b/z59e7NTB
- Kom
- FastCGI (Gemstone only)
Changelogs
- (newer changelogs, see https://github.com/SeasideSt/Seaside/releases)
- 3.4.0
- 3.3.0
- 3.2.4
- 3.2.2
- 3.2.1
- 3.2.0
- 3.1.3
- 3.1.2
- 3.1.1
- 3.1.0
- 3.0.11
- 3.0.9
- 3.0.8
- 3.0.7
- 3.0.6
- 3.0.5
- 3.0.4
- 3.0.3
- 3.0.2
- 2.8
- 2.7
- Past Releases
Development
Documentation
- Configuration and Preferences
- Embedding Subcomponents
- Maintaining State
- Generating HTML
- CSS and Javascript
- Debugging Seaside Applications
- Links, Forms and Callbacks
- Development Tools
- Call and Answer
- Naming URLs
- Security Features
- Securing Seaside Applications
- Seaside-REST
- Add-On Libraries
- Persistence
- Gettext
- FileLibrary
- The Render Tree
- PDF Generation
- Long-Term Issues
- Ajaxification
- Web Components
- Big Issues
Sprints