FAQ

Table of Contents

  1. RAPPTOR
  1. RAPPTOR Components
  1. RAPPTOR Features
  1. Get the Source Code
    1. Release Notes
  1. How To
    1. Create a Basic Application
    1. Creating a Domain
    1. Create a Theme
    1. Writing PageParts
    1. Gluing
  1. Media
  1. News
  1. Contact
  1. FAQ

Why is this software called RAPPTOR?

'RAPPTOR' is a play on the word 'Velociraptor'. RAPPTOR is designed to promote a target-oriented development style, making it the ultimate Rapid Application Development Framework.

Does RAPPTOR come with documentation?

Sorry, not yet. Maybe early-September 2007 or so.

With which web servers does RAPPTOR currently run?

Apache+mod_mono, IIS, the mono XSP2 Webserver and as stand alone.

Can I use RAPPTOR for my commercial applications?

Yes, see the [License license] (LGPL) for details.

Does RAPPTOR support SOAP or Microsoft WCF Web Services?

You can implement this by writing a driver.

Which security model does RAPPTOR use?

At the moment we're using a group-based security model consisting of pre-defined permissions. Each user is assigned a group, although being a member of multiple groups can be configured. A users group membership is then stored as triples. Role based security should be possible in the near future.

Is RAPPTOR professionally supported?

Yes. If you use RAPPTOR for commercial projects you can get expert support from the development team at thdata as well as general consulting on how to implement your solution.

How is RAPPTOR configured?

we are implementing a complete GUI which will allow a developer to configure an application completely, without having to configure a bunch of files by hand. However, some localisation must take place and that will require configuration of some .manifest files.

Does RAPPTOR work today?

Yes, but ... see the release notes.

Does RAPPTOR support Ajax?

RAPPTOR supports partial page rendering by an own Ajax logic. In case of a JavaScript?-enabled client, code is automatically hooked into the client ‘PageLoad’ event that will generate modified HTTP requests, which will trigger the specific server responses. RAPPTOR encodes state in proprietary element IDs. These IDs will also indicate whether the client supports Javascript and thus Ajax. On a Postback these IDs will automatically trigger certain server events so that a partial page refresh request is detected and processed accordingly if applicable. If on the other hand the user agent does not support JavaScript? just nothing will happen and the full page is transferred on a Postback. Currently this functionality will not integrate with popular Ajax frameworks without extra work. But you can turn off the RAPPTOR Ajax feature and do what you want by writing your own low level JavaScript? code to handle the HTTP communication.

Remark: This feature is not included in the current build, please see the project roadmap.