Showing posts with label module. Show all posts
Showing posts with label module. Show all posts

Tuesday, January 06, 2009

The Rubicon Panel - Control Panel

    The Rubicon  Panel is a custom developed control panel for use with the redesigned Mangalam College of Engg site. A number of features have been improvised and implemented into the panel. Shown below are the screen shots of the important features of the panel.


    This is the Rich text editor for managing the news, events and even the static contents for the site. All the data arse stored in the database. Even a person without  any knowledge with web designing can easily add or edit contents with much ease.



    This is the Add new staff member to the database form, part of the staff management module. 



    The Gallery management module has been a powerful module that has been researched and implemented for this project. New album can be created very easily and thumbnails are generated automatically for each uploaded image.



    The uploaded document manager makes it easy to upload documents to the site. It also provides the feature to get the link for each file , so that it may be added to a news or event item easily.

    That covers the important features provided by the panel ....

   

Thursday, May 15, 2008

Audio Steganography Application with Source Code

Ok, as i had promised earlier, here is the working part of the Audio Steganography Application done in Java. The Source code is also included in this package. As there is very little time, i cant explain the complete working here soon. So if there are any doubts, im happy to explain that portion...

So heres the link for download :

http://www.mediafire.com/download.php?m4ktmdhdnnj 


Hope this is useful. Also included are complete documentation and the source code in Java.


Edit :


The above link is no longer available.


Please refer to the following links :
http://midhunhk.blogspot.com/2011/10/audiosteganography-info.html
and
http://midhunhk.blogspot.com/2011/08/faq-regarding-audiosteganography-app.html

Sunday, January 13, 2008

Module Header - New Proposal

   Ok, heres a new addition / proposal for the satndardization 
of the module structure for software projects. Its just an 
addition to the previous one.

* Name of the module [Application Domain / Type]

ie;
[Application Domain] is the addition to the Name of a module and specifies which might suggest where the module is implemented and how it can be classified. This might be useful if the software development group has multiple application domains, like us. Its more or less like keywords..

eg:

* ClientScroller [hta / script]

* AlbumGallery [web / php / script / db]

* XmlReadList [app / flash / xml]

Wednesday, January 09, 2008

Software Module Header Structure

    After much research, i found a quite standard way of writing headers for software projects. It is used in almost every professional development environment. These are just some specifications, individuals or firms may have their own changes according to their requirements.

   The need for such a standardisation is that once a module is written and debugged, the author or other software developers may understand cleanly what is going on and would help in debugging for the entire application, modification without sideeffects and ofcourse as a strong supporter of the "Open Source" movement, code sharing.

Module Header Format ($ revisoon 2)
--------------------------------------------
* Name of Module
* Synopsis of Module
* Date of creation
* Author's Name
* [Modification History]
* [Different Functions supported with in / out params]
* [Global Variables accessed or modified by it]

--End--

eg : say the module header of a new program that i created might have the following header

--Start--
* ClientScroller
* script that Scrolls the client area up and down
* Decemebr 2007
* Midhun Harikumar (Centrum inc Software Solutions)

$ Version 0.32

--End--

    Another important specification is regarding the use of global variables. While using Object Oriented Programming, i guess there would be minimum amount of 
global variables lying around. The specification is to name the global variables 
with a leading small case g and underscore.

eg :
int g_nDestFileCount;

    This way we can easily figure out where the global variables are used and might help
debugging a lot easier.