Notes on codes, projects and everything
Generally, library holds a wide variety of reading materials and providing ample space for quiet study. A full range of services is provided in a library, such as loan, reservation, inter-library loan, reference, online resource, document delivery, photocopying, audiovisual and microform materials.
Initially, the library transactions are handled manually by the library staff. The references are stored using the filing system. This tradition method has raised many inconveniences to the library staff.
Hence, you are required to do some research on the problems that faced by the conventional library management system, and then develop a computerized library system by using the ASP.NET.
A master page is used to set up a consistent look and feel to the website. However, since it is not being discussed in class, therefore we had got to learn that ourselves. We implemented a simple master page to the website and separate the layout and data presenting element using a stylesheet file. The tool used to develop the assignment is Visual Web Developer 2005 Express Edition.
Following included are the screenshots for some main functions.
This is basically a small incremental update to my script published here. For some reason, the previous version of the script didn’t really work, so this release should fix the problem. Besides fixing the problem where the daemon did not actually launched at start up, I have added a settings applet for this script as well.
After comparing my own implementation of MVC with CodeIgniter’s, now I’m comparing Kohana’s and Zend’s. I have just shifted from CodeIgniter to Kohana recently in work and is currently learning on how to use Zend Framework to build my web-app. As everybody knows, Zend Framework is more like a collection of library classes than a framework a la Ruby on Rails, using MVC in Zend Framework would require one to begin from bootstrapping stage. However, in Kohana, just like other frameworks, bootstrapping is done by the framework itself so the developer will get an installation that almost just works (after a little bit of configuration).
In the previous post, I re-implemented Annoy in 2D with some linear algebra maths. Then I spent some time going through some tutorial on vectors, and expanded the script to handle data in 3D and more. So instead of finding gradient, the perpendicular line in the middle of two points, I construct a plane, and find the distance between it and points to construct the tree.
It is very much expected that there will be endless stream of new (and often times better) tools introduced to solve the same set of problems. While I am slowly resuming my programming work, and in the process of reviving my very much dead postgrad project, I found some alternative to the tools I had used in the past. I suppose I shall just jot them down here so that there’s a reference for later use.
After reading through the documentation, I find that the role based ACL and work flow can be more tightly integrated. Therefore I made all the transaction into many FSMs and my work flow component now consists of one work flow library and one work flow management model. As I am going a more normalized design (I use denormalized design in work as it deals with a lot of documents, however for a small project like mine, a denormalized design should do well).