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.
Should have done this earlier, I was just being lazy to go through all the steps to publish it properly. So here it is, the full source is published to bitbucket. Feel free to fork the project if you are interested. I have not attach a licence to it but it will most probably be BSD licence. I have also uploaded the latest 0.0.2 release to bitbucket and would update the download link posted previously soon.
This post is purely based on my own speculation as there’s no experiment on real-life data to actually back the arguments. I am currently trying to document down a plan for my experiment(s) on recommender system (this reminds me that I have not release the Flickr data collection tool :/) and my supervisor advised to write a paragraph or two on some of the key things. Since he is not going to read it, so I might as well just post it here as a note.
A friend of mine recently posted a screenshot containing a code snippet for a fairly straight forward problem. So after reading the solution I suddenly had the itch to propose another solution that I initially thought would be better (SPOILER: Turns out it isn’t). Then mysteriously I stuck myself to my seat and started coding an alternative solution to it instead of playing Diablo 3 just now.
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).
Another half a day spent on figuring out how to package my daemon properly, fortunately with help from friends over at #harmattan IRC channel as well as cckwes, I finally get the deb package generated properly. So just a quick reminder on what my daemon does, it is just a quick hack that toggles the ‘allow background connections’ on and off depending which kind of data network a user is connected to. Apparently I am not the only one who are looking for this, as a feature request was filed long long time ago.