Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Quick start for developers

For developers here is a quick tutorial on how to set OpenSyllabus project into Eclipse

Installation Guide

Eclipse Configuration

Code Structure

Let's have a look at the OpenSyllabus code structure.

To keep it simple, in our developpement we created two separate projects (we mean Eclipse/Maven projects) : One project for the client part where you will find al the GWT source code and one project for the backend part where stands the Sakai's tool code.

Thus, the developer can code and debug all in Java by working depending to his needs in the backend project or in the client project.

Code Structure

Frontend project

Backend project

GWT code

Sakai's tool code

client

  • One project for the backend part

OpenSyllabus backend is organized as a classical Sakai's tool following a File Structure based on classic Sakai's tool directories, such as : API, Implementation and Tool directory.

    • API
    • Impl
    • Tool

But in the Tool directory there is something new : the compiled GWT content (all the generated GWT stuff : pure JavaScript and HTML).

There are also RPCServlets and RPCInterfaces for Remote Procedure Call exchanges.

  • No labels