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.
After delaying for quite some time, I think I should start the project before I get bored with it. The project will be either hosted on this current domain (coolsilon.com) at least for now and will probably move to another domain if needed. The site will be either a blog aggregator or just a simple article submission site that works kinda like digg / reddit, however, to be promoted to the frontpage the submission would have to impress the opposite group.
This is the second part of the golang learning rant log. Previously on (note (code cslai)) I managed to make each line in the CSV into a hash map. So today I am going to make it into JSON Lines.
This update took me quite a bit more time than I initially expected. Anyway, I have done some refactoring work to the original code, and thought it would be nice to document the changes. Overall, most of the changes involved the refactoring of function names. I am not sure if this would stick, but I am quite satisfied for now.
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).
Previously, I started practising recursions by implementing a type check on lat (list of atoms), and ismember (whether an atom is a member of a given lat). Then in the third chapter, named “Cons the Magnificent”, more list manipulation methods are being introduced.