I've been examining Visual Web Gui for a while. VWG promises nice functionality with an innovative but very familiar paradigm. So I decided to test capabilities of VWG with a known domain to me as a software developer and implementor of Pragma Issue Tracker Module for Cuyahoga Framework.
Pragma Issue Tracker (PrgIT) will try to meet the following basic requirements
- Open source
- Multi database support
- Use NHibernate with Castle ActiveRecord as Model Layer
- Use VisualWebGui as View and Controller Layers
- Service based Authentication and Membership for integration with existing web applications.
- Define Projects
- Define Components for each project
- Global and project based issue type definitions
- Global and project based priority definitions
- Link users for special roles for each project and/or component
- Issue comments and attachments
- Issue change history tracking and reporting
- Issue linking
- Custom issue tagging
- Custom fields for projects and components
- Issue work logging
- Project and component versioning
- Predefined dashboard reports
- Custom reports
- Functionality exposed via web services
- Custom and programmable issue actions per project and/or component
- Fulltext indexing and fulltext search
- Access to issues with user friendly url's
You can ask that why we need another open source issue tracker software, we already have open source issue trackers developed with Asp .Net meeting the requirements stated above? We do not actually need another issue tracker, PrgIT project was established simply to test the ecosystem composed of VisualWebGui, NHibernate and ActiveRecord, this is the main motivation behind this effort.
c669e078-c6d9-489e-b07a-f89189afe5c8|0|.0