Projects

QiPki

QiPki is an effort to create Java developper tools to build cryptography into applications and heading towards building a suite of packaged cryptography services. Development tries to follow principles learned from DDD, DCI, ReST and more using the Qi4j engine and framework.

Naked Objects PHP

Naked Objects is the idea that a domain object should be able to generate its own GUI interface and its own data persistence layer based on introspection of its own data members and methods. There are two main concerns here: One is to make it easier for developers to create applications. ... [More] The other is to make things easier for users by having more consistent UI elements, and by allowing them to manipulate them as they see fit. The pure Naked Objects concept as implemented has limitations. You can't directly control the UI so that limits how much you can do without changing the framework itself. It also potentially puts to much onto the user to arrange his objects efficiently. The goal for my version (and maybe a name change is in order) is get as much advantage as possible witho [Less]

blueBill

Source code is licensed through the Apache Software License 2.0, graphics under the Creative Commons BY-NC-ND 3.0 License.

nsdci

The nsdci AOLserver module includes a number of utility APIs, data structures, and network transports created initially during the creation of the AOL Digital City Web site. We hope others will find it as useful as we have over the years. Sub-modules include: cache, ncf, neval, np, nproxy, nrate, nsob, nt, nv, page and proxy.

magic-drafting-application

What does it do?During a standard Magic draft a calling judge has to keep track of time, the number of cards called and the direction of the draft. All those things can be confusing sometimes and this applications helps judges by automatizing the whole project. How to use?Either use online ... [More] version, either download it in advance. If you choose to download it in advance, please come back here once in a while to check for new version releases. If you know how to use feeds, you can take the feed of updates and add it to your RSS/Atom reader. Credits and involvementI am Denis Sokolov (homepage) and I created this application myself. Want to help? There are many ways you can help: Spread the word Report bugs, request features, discuss Help to write texts both here and in the application Translate the application Help code the application [Less]

waxphp

Evolved from the WISP PHP Framework Core (development now discontinued and moved to this project) - it is designed as a rapid prototyping PHP framework that does not require all the hassles of a traditional PHP MVC framework. Wax involves no command-line interaction and uses a control library to ... [More] build websites. Wax is made possible through the Rensselaer Center for Open Source Software and through the generosity of Mr. Sean O'Sullivan. DCI: Data Context InteractionThe new DCI paradigm is at the heart of the Wax framework. DCI is the programming model that is the successor to MVC. To learn more about it, you can read an article written by the creators (Trygve Reenskaug and Jim Coplien) at http://www.artima.com/articles/dci_vision.html. If you'd like to read even more about it, here's a 74 page paper on it: http://folk.uio.no/trygver/2009/commonsense.pdf DCI allows the framework to work in ways far different than a traditional web framework. The idea is that all application functionality/logic is coded in Role classes. Controllers call Role methods as necessary depending on the context of the call. The application still follows an MVC architecture, but the logic is in the Roles instead of the models and controllers (which are mostly just for connecting the different roles). This leads to a very flexible runtime network and exciting possibilities for many different aspects of web development. HistoryIn 2005, I was doing several development jobs for my high school. Across all of the applications there were several common tasks that I wanted to expedite. At the time I wasn't really aware of any PHP frameworks. As I continued working on projects, I began building a library of scripts, PHP objects, and stylesheets that I could use across all of my applications. It was this original library that sparked the very beginning of the Wax framework. CGLCGL, or Common Graphics Library as I called it, was a folder that contained all of the files that I used across my applications, including several scripts, stylesheets, and PHP objects, including an Active Directory interaction class and several custom functions. CGL 2CGL2 was an extension of CGL which included a few custom classes that I created that could be extended to create simple PHP controls that could be reused - like a Image Thumbnailing class and a MenuBar class. CGL2 was overall not very scalable, and was therefore not developed too much further. PADTo solve the problem of authenticating across all of these systems we created a very very simple system dubbed Pseudo Active Directory. The name didn't really describe the function, although it did provide a decent single sign-on solution for the school. Performance was terrible though, and it didn't work very well in a production environment. CompactISThe Compact Information System was developed to solve the problems with PAD. It used a vast library of interfaces and classes to provide an extensible single sign-on and access control list solution. The system itself worked quite well, except it was developed mostly by one of my colleagues, who unfortunately left very little documentation on the project. In addition, the project utilized cutting-edge PHP features that would not be widely portable across different versions. WISP PHP FrameworkAfter a little more looking into web standards and technologies, I decided to bundle all of the previous projects I had worked on into a single PHP framework, entitled WISP: Websites with Integrated Scripts and PHP. The project was promising but had a pretty messy codebase due to the several design changes encountered during development. Wax PHP FrameworkUpon cleaning up the WISP code, I realized that the framework I had was considerably different than the original ideas I had. As a result, I renamed the framework to Wax (which portrays the application style: Build Apps with Wax Blocks). The framework is designed to be highly extensible and useable without the hassles and bloat of a standard MVC framework. This project, once mature, will allow even more rapid prototyping than projects like CakePHP, Symfony, CodeIgniter, etc. [Less]

dcimenditto

drum corps international<3