does anyone know what compiler would compile the notepad program in the sourcecode section. It seems badly writen so I thought if I could see it in action it would be easier to figure out how it works, or if it doesn't work how a text editor should work.
You know? For a brief moment I had the idea of rewriting it using modern standards. Luckily, a quick look at it put me back into my senses. My lack of God, it would be quicker and generally better to start from scratch.
garob: If you want to see text editor code, you could take a look at finished a product, like pico. I'd suggest Notepad++, but I think it's too complex if you just want to see a simple text editor.
yeah i also tried to compile it and didn't work, the developer's email may also be dead. the read me did not mention what compiler it uses to build the project and did not include the executable in the package. i think the sourcecode section needs update.
However, the source code for Pico is closely linked to the source code of Pine; therefore you cannot download Pico on its own - you have to donwload the source of the complete newsreader to install the little editor. Worse: Although Pine is freely available you should know this:
Pine and Pico are not "OpenSource"
Pico is dead - long live Nano
Yes, you cannot just download the source for Pico and install on its own. However, many users would like to use this kind of editor and simply copy it everywhere for personal use.
is confusing. How can you look at the sourcecode if it is not open source? Sorry if this is a dumb question.
is open source now as well.... ok I take that back, I just read the disclaimer.
1) The metapad code has been released under the GNU
General Public License. This fact directly impacts
what you can and cannot do with the source code. See
the file COPYING-LICENSE.txt (included in this
distribution) which will explain things in detail.
2) This source code in its current state is uncommented,
unmodular, and generally not very understandable
for anyone that is not deeply familiar with it. All
of the code is contained in one 8000 line file. Of
course this is not the best way to write software
that others may read (which was not a concern when
I originally wrote it).
3) I no longer consider myself a win32 programming
expert by any means. If you are confused by anything
you find here please contact your local C/win32 guru.