As an open source Java project, Keel Framework will always attract the developer crowd.
Business managers may find it even more appealing.
Who needs what Keel offers ?
Corporate/Goverment Developers:
Enterprises would love to jump into the water with open source, if it only wasn't hard to integrate, and quirky, once set up. Keel is designed to be neither.
Keel is for business, and that may be commercial, governmental, or even personal. If a task is worth doing, you need the infrastructure to get it done within a consistent and standardized set of interfaces, regardless of the codebase you use within those interfaces.
Security Nuts:
"My first three concerns are..."
- Security
- Security
- Security
We feel the same way.
Keel not only insists on solid security, but it must work with relative ease, even to the detail level of specific records. Security that is too hard to admin is often just bypassed, in favor of ease of use.
UI or database enthusiasts.
"I need to stick with my favorite [pick one]
- User Interface
- Struts
- Cocoon
- Velocity
- JavaServerFaces
- etc.
- Database
- MySQL
- Oracle
- Firebird
- etc
Now if only I could just find a package to provide me with everything else... in a clean and easy way."
Keel fits that bill.
Component Writers.
60,000+ projects on source forge, dozens on Apache, not to mention FreshMeat and the rest of the internet, there are a bunch of us out there who are stuck in a fragmented market - all for want of a bigger audience to plug into. Not to mention the burden of providing security, user interface and database infrastructure outside our area of focus.
Whether you are writing a Calendar component or any other functionality, Keel provides the interface, all you have to do is plug into it.
