More Information/Training

Introduction

The Grails Portal Framework is being built to enable programmers and users to implement user personalization for Grails applications. It will have a built in ability for AJAX using the Grails UI plug-in and YahooUI plug-ins. This portal will take advantage of the DRY principle and Convention over Configuration to make it very simple to put together applications quickly. One example of this is the ability to use plug-ins to add functionality within the Grails Portal framework.

This project is in a development stage with the first development release slated for late September, 2010. The code that is checked in may not be stable at this time, and may not actually compile. If you are interested in contributing code or plugins please send an email to the project list or apply to be a contributor to the project.

Development Environment

MySQL version 5.x
Spring STS
Grails 1.3
Java 1.6.0_10

Recommended deployment Environment

This matrix will show which versions of the application has been tested with different application servers:

No verification is ready yet

Goals

Create a simple way to build a working framework for a user portal written in Grails.
Build upon some very popular features in Grails such as GORM and Groovy Server Pages.

It also provides integration with other third party plugins such as:

Apache Shiro
Grails UI
Yahoo UI
Daisy Plugin - created and available on this site

Latest News

6/24/2010 - Menu features have been added to the code base. The configuration of the menus are now driven completely out of the database.
7/29/2010 - Menu default data has been added to the bootstrap class that will populate the data automatically. Right now there are three types of menus, anonymous, admin, and user.
8/11/2010 Menu Grails based scaffolding configuration has been tested along with default data.
8/11/2010 Started to fix issues with the default scaffolding of different types of domain relationships.

Feature Plan - Version 0.1 September 2010

Domain changes

Add more comprehensive packages to the domain model to enable more of a separation of concern for the application. Separate out the different areas of domain from each other into separate packages.
Enable domain class based annotation that will affect the presentation of the data to the user when doing automatic scaffolding.

Default Scaffolding changes

Change the default scaffolding to enable the use of the Grails Portal configuration tables.
Change the default scaffolding to use the domain classes to indicate different types of scaffolding behavior.
Change the default scaffolding to use custom classes in the Grails Portal Source Tree.