-
Notifications
You must be signed in to change notification settings - Fork 71
CSS and Javascript
The easiest way to include CSS and Javascript in your application is to override the #style
and #script
methods, respectively, of your components. These should return static (not generated) string literals containing snippets of CSS or Javascript that will be included as external resources when the page is generated.
For more flexibility, however, you can also create a subclass of WAFileLibrary
. Put your JavaScript code in methods with a name ending with "Js" and your CSS in methods with a name ending on "Css". These are expected to consist solely a returned string literal. When configuring an application, you can add any libraries that have relevant scripts or styles, and all of the code in these libraries will be linked in to every page of the application. By default, applications include WAStandardFiles; see this class for examples.
For production we recommend using external files served through a front end web server.
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