What is it?
Why use it?
AppDepot is not a content management system so web applications are not stored in AppDepot, nor written in any AppDepot specific language. It can use existing web applications (remote or local). AppDepot exchanges credential information with the application prior to the start in order to authorize the use. The exchange of credentials allows the application to determine if it should run or not. This is done via a small and simple prologue script inserted into the web application or via the AppDepot API. Alternatively AppDepot can also execute web applications without the security wrapper; which mimics portal functionality.
Who made it?
Ed Zenisek - Lead AppDepot Programmer, Developer, Designer, Marketing Consultant
Abel Sanchez - Lead AppDepot Architect, Conceptual Designer and Idea Man, Marketing Mastermind
Stephen Carr - CSS, Marketing Consultant, AppDepot Website Design
Special thanks to the following people for their help, contributions, testing and input.
- Elva Nanawa
- Dominic Munoz
- Chris Ratheal
- Philip Braker
- Joel Johnson
- Erin Kelly
- Steve Barkes
- Ahmed Abdelali
- Anderson Hall Community
- New Mexico State University
- Research IT Department
- Physical Science Laboratory of New Mexico State University
Acknowledgements
- Javascript Tree: Tobias Bender (www.phpexplorer.org)
- Javascript Tooltips: Walter Zorn (www.walterzorn.com)
- Misc Java Functions: jQuery (www.jquery.com)
- Icons: Mark James (www.famfamfam.com)
- PDF Reports: FPDF (www.fpdf.org)
- Flash Reports: Open Flash Chart (www.teethgrinder.co.uk/open-flash-chart/)
- Mailing Script: phpMailer (phpmailer.worxware.com)
- Rich Text Boxes: fckeditor (www.fckeditor.net)
- Calendar: JACS (www.garrett.nildram.co.uk/calendar/jacs.htm)
- Admin Tabs: Tabifier (www.barelyfitz.com/projects/tabber)