Jump to: navigation, search

Difference between revisions of "Pave"

 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Overview ==
 
 
{|border="0" cellspacing="15" valign="top" style="width:100%;"
 
{|border="0" cellspacing="15" valign="top" style="width:100%;"
 
|-valign="top"  
 
|-valign="top"  
|style="width:90%;"|
+
|style="width:80%;"|
 +
__NOTOC__
 +
 
 +
 
 +
'''Pave''' framework is designed to be versatile framework for easy chaining operations. The idea behind it is that multiple standalone operations can be chained to produce more complex product. Pave is context dependent, which means that you can trigger the framework on certain artifacts(PDE project for example).
 +
 
 +
Pave framework is aimed for plugin developers to automate and produce complex patterns that the end user will can use. Patterns themselves aim to aid the end user in boring and repetitive tasks.
 +
 
 +
Pave framework is designed to be lightweight and as generic as possible, so maximum flexibility is offered to the plugin develops. Here important statement is that Pave is based on WTP Data Model Framework. Thus we get Data Model Operations that can be executed in DMF compatible in Pave.
 +
 
 +
For more information on how to embed DMF operation in Pave you can visit our tutorial section or pattern structure page.
 +
 
 +
Pave comes with three implementations of patterns.
 +
 
 +
The first one is a simple pattern for generating pattern skeleton. Sounds confusing, but it is rather simple. A pattern consists of at least one data model provider, operation and a declaration in plugin descriptor. This pattern will generate the essentials for you. This pattern is triggered on PDE project node in project explorer. CRUD pattern is Java EE based pattern for generation of Create Read Update Delete session facade for entity or a group of entities. This pattern can be triggered on JPA entity class or artifact. CRUD application is actually an extension of the CRUD Pattern (yep you can extend patterns), which will generate on top of the CRUD session bean JSF front end.
 +
 
 +
For more information on how the framework works and what more it can do visit our architecture page.
  
'''Pave''' is a framework extending Data Model Wizard Framework. It allows Eclipse developers to define patterns that later can be applied on different artifacts in a context dependent way. Pattern developers can register their functionality through extension points. Every pattern consists of a sequence of one or more operations that receive certain input and generate some result. '''Pave''' framework allows the result of one operation to be used as an input for any following ones. A pattern can contribute wizard pages to acquire user input. '''Pave''' allows its users to restrict artifacts that their patterns are applicable on. Using the framework functionality, it is easy to add logic to validate input and even override existing validators. Pattern developers can easily extend existing patterns by adding operations.
 
Using patterns, developers can generate code or even whole applications in an instance. Patterns generate error proof code. They can be very useful in educations using the technique learning by example.
 
  
  
Line 16: Line 29:
 
| list = pave-dev
 
| list = pave-dev
 
| newsgroup = eclipse.pave
 
| newsgroup = eclipse.pave
| product = Pave&component=Patterns
+
| product = Pave
 
| viewvc = org.eclipse.pave/?root=WebTools_Project
 
| viewvc = org.eclipse.pave/?root=WebTools_Project
 +
| psf = http://wiki.eclipse.org/images/0/0b/Pave.psf
 
}}
 
}}
 
|}
 
|}
  
  
 
----
 
 
== Architecture ==
 
== Architecture ==
 
+
[[Pave/Architecture]]
'''Structure of Pave framework'''
+
 
+
[[Image:PAVE_ARCH1.PNG]]
+
 
+
'''Functionality by modules'''
+
 
+
[[Image:PAVE_ARCH2.PNG]]
+
 
+
'''Pave action sequence'''
+
 
+
[[Image:PAVE_ARCH4.PNG]]
+
 
+
'''Extension Points'''
+
 
+
[[Pave/Extension_Points]]
+
 
+
'''Threading Clues'''
+
 
+
[[Pave/Threading]]
+
  
  

Latest revision as of 10:31, 27 October 2009


Pave framework is designed to be versatile framework for easy chaining operations. The idea behind it is that multiple standalone operations can be chained to produce more complex product. Pave is context dependent, which means that you can trigger the framework on certain artifacts(PDE project for example).

Pave framework is aimed for plugin developers to automate and produce complex patterns that the end user will can use. Patterns themselves aim to aid the end user in boring and repetitive tasks.

Pave framework is designed to be lightweight and as generic as possible, so maximum flexibility is offered to the plugin develops. Here important statement is that Pave is based on WTP Data Model Framework. Thus we get Data Model Operations that can be executed in DMF compatible in Pave.

For more information on how to embed DMF operation in Pave you can visit our tutorial section or pattern structure page.

Pave comes with three implementations of patterns.

The first one is a simple pattern for generating pattern skeleton. Sounds confusing, but it is rather simple. A pattern consists of at least one data model provider, operation and a declaration in plugin descriptor. This pattern will generate the essentials for you. This pattern is triggered on PDE project node in project explorer. CRUD pattern is Java EE based pattern for generation of Create Read Update Delete session facade for entity or a group of entities. This pattern can be triggered on JPA entity class or artifact. CRUD application is actually an extension of the CRUD Pattern (yep you can extend patterns), which will generate on top of the CRUD session bean JSF front end.

For more information on how the framework works and what more it can do visit our architecture page.



Egg-incubation.png
Pave Project
Website
Download
Community
Mailing ListForumsIRC
Bugzilla
Open
Help Wanted
Bug Day
Contribute
Browse SourceProject Set File


Architecture

Pave/Architecture


Tutorials

Pave/Tutorials


Implemented Patterns

Pave/Patterns

New And Noteworthy

ver. 0.5 Pave/NewAndNoteworthy