LinkPress
A del.icio.us linkblog plugin for WordPress
(should work for any RDF file though)
README
Download (.tar.gz file, 13K)
pramodsite-1.0
The set of Perl scripts that I use for this website.
README
Download (Source. .tar.gz file. 100K)
You need the following Perl modules to run the scripts:
XML-XPATH(.tar.gz file 40K)
XML-RSS(.tar.gz file 40K)
Date Manip(.tar.gz file 140K)
ri
A simple text editor for the Linux platform, using ncurses. Developed during 5th semester.
README
Download (Source. tar.gz file. 36KB)
Epaint
A graphics editor for the MS-DOS platform, using the Turbo C Graphics Library. Developed during 6th semester.
README
Download (Source. Zip file. 51KB)
I could give you ideas on how to go about the VTU syllabus in my own words, but why reinvent the wheel?
Here are links to some good stuff for VTU students:
Deepak's VTU Lab Programs and Projects
VTUCodes - Lots of VTU projects and lab programs
Kalyan Varma's Projects FAQ
Good Graphics Editors
5 good graphics editors I have seen, all developed as part of VTU syllabus. 3 of them are very similar, and one of them is distributed binary only.
(I've included mine too in this zipfile)
Download (Source. Zip file. 384KB)
Also check out Manu Bharadwaj's CUBISM. Extremely good.
Some suggestions:
If you are really interested in doing a good graphics editor, consider these:
1. Use assembly if and where required. Sometimes, graphics.h and dos.h are not powerful enough
2. Try to get 256-color mode working in DOS. Explore the graphics.h functions related to setting the Graphics driver and color modes. (the initgraph() function is a good place to start). Especially learn about Palettes (setpalette()). I remember that you can download a .BGI file from Borland that gives 256-color mode on DOS.
Learn about Mode X.
3. Try to support some simple standard image format..link pnm or ppm. Even BMP is doable.
Good Text Editors
9 of the best text editors I've come across, all developed as part of VTU syllabus. I referred to them a lot while writing my own.
(I've included mine too in this tarball)
Download (Source. tar.gz file. 364KB)
Simple Text Editors
6 editors strictly conforming to the VTU syllabus. No jazzy features and simple to understand. (I haven't tested them properly..so I can't guarantee anything. But they should compile and work ok)
Download (Source. tar.gz file. 64KB)
Ncurses Text Editor HOWTO
An excellent tutorial for all those who are just starting off on their own.
Download (.tar.gz file. 12KB)
Ncurses Programming HOWTO
An introduction to Ncurses Programming, with examples.
Download (.tar.gz file. 64KB)
ned - Text Editor of the future
This page has information about this editor, along with links to many documents explaining the concept and implementation of text editors. The Craft of Text Editing seemed particularly good.
Along with these, my suggestions:
* There's a C++ wrapper for ncurses generally available by default, on all Linux systems (/usr/include/ncurses/cursesapp.h). Take a look at it. This could substantially reduce the complexity of the API.
* Explore the following directories thoroughly: /usr/share/doc/ncurses-x.x, /usr/share/doc/ncurses-devel-x.x, /usr/share/doc/ncurses-c++-devel-x.x. They contain authentic and authoritative information on various aspects of the library, and also many example programs. And don't forget the actual header file itself (/usr/include/curses.h).
* Almost everyone surely uses the accompanying Panel library (man panel). But apart from this, ncurses also contains the Menu library (man menu) and the Forms library (man form). Even these are installed by default. These can make your programming job much easier. Do check them out.(The editor "gyte" in directory "yash" of the above collection uses these)
* There's also a Dialog library (dialog.h) which is based on ncurses. Creating dialog boxes using this library is a breeze. See "man dialog" and play around a little, you'll only realize. Unfortunately, the C/C++ API for this package is not installed by default (on Red Hat systems, at least). But you can easily get it from the net. The only reason I didn't use it in my editor was that I was too scared that it might not be accepted in the exam! Anyway, there's a lot of design knowledge to be gained by simply looking at the output and header files of the Dialog library!!
* Learn make, gdb and vi. An hour spent on these can save you many in the future!
* Another neat idea: try "rpm -ql ncurses-devel | less" and explore the output files!
* When you get down to the actual coding, man ncurses is the best resource!
* Google like mad, on _everything_ editor-related. There's much more great material out there.
* Discuss with knowledgeable people. Nothing can beat this.
* Don't waste money on Ncurses Programming books. Or Linux programming books. Use the Net. You can get a copy of a good C/C++ book instead. I always used the C++ Primer.
This kind of approach to projects will do you a lot of good in the long term. It's these skills that you carry from one project to another, and not the specific knowledge of any API.