| |
Frantic
Registered: Mar 2003
Posts: 1648 |
C64 Codebase
Hello!
It was a while ago now that C64 Codebase Wiki opened its doors. I would just like to encourage good coders sympathetic with this project to actually add some code there. This is important in order to keep the quality of the site. I feel that the quality is somehow fading a little with the stuff that has been added during the last 6 months, to generalize a little.
If you are a decent coder: Just think for a moment about all those sources that you have lying around on your C64 disks and PC harddrives. Codebase needs you!
http://codebase64.org/doku.php
If someone feel like donating some cool stuff, I could use that as prices in some kind of add-good-stuff-to-codebase-competition or so.
A good codebase is a good base for the future C64 scene! ;)
|
|
... 127 posts hidden. Click here to view all posts....
|
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
codebase is meant to teach people to code on the c64, and not as a dumb mass of sources. also I dont find it a good idea for newbies to use code they have no idea what it does. |
| |
LOGAN
Account closed
Registered: Aug 2003
Posts: |
I't called codebase nonetheless, not codeschool or codeideas :) |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
codebase was my idea. so just ask me & trust my answer, what it was ment to be if in doubt. |
| |
Conjuror
Registered: Aug 2004
Posts: 168 |
It would be good to have an explanation of the code that is there.
Unfortunately I have used the FLI code without understanding it and its come back to bite me.
I read it in conjunction with the explanation of FLI but didn't understand how the 4x4 chunky code was working until someone explained it to me.
|
| |
Skate
Registered: Jul 2003
Posts: 494 |
I agree with not adding too much working source codes to the codebase. This should define the difference between a new Commodore 64 coder and a new PC coder. PC coders (even many of us) use different libraries, code pieces etc. Because this is how the things became today. But we as c64 scene are proud to be a part of a different world where we know and understand (almost) everything about our hardware and code everything from scratch. If a newbie wants to be a part of it, he/she should walk the same way like we do. Otherwise nothing changes for us but they cannot have the same joy. |
| |
LOGAN
Account closed
Registered: Aug 2003
Posts: |
True, but that also means you are 15 years ahead :)
But I remember being proud when I managed to get text on the screen while playing a music. Come to think of it, I still am :)
|
| |
cadaver
Registered: Feb 2002
Posts: 1160 |
Some things you can just slap together, like music playing, loading, reading input.
But it quickly gets too application-specific to be useful. For example a sprite multiplexer usually ties into a raster interrupt system, but migrating it into a totally different interrupt system (once we move beyond simple tutorial multiplexers, which do nothing else than the sprites) would probably be so complicated that it's better to write at least the interrupt code from scratch. But what are more useful are the concepts & algorithms used. |
| |
hollowman
Registered: Dec 2001
Posts: 474 |
Quoting Skate
But we as c64 scene are proud to be a part of a different world where we know and understand (almost) everything about our hardware and code everything from scratch. If a newbie wants to be a part of it, he/she should walk the same way like we do.
The road I went was ripping every piece of usable code I could find in the computer magazines I had, and then i would try to patch that together to a demo. And after a few months I joined a group where the other coders would help out with code for setting up raster interrupts, drawing lines etc.
I enjoyed being able to actually make something which looked like a demo and as time went by I actually learned how most of the code worked and could do more stuff on my own.
But whatever, have fun up there on your high horses. |
| |
Ervin
Registered: May 2008
Posts: 14 |
I think there are some fundamental "libraries" or "routines" such as loader, cruncher, music player, etc. which IMHO are not expected to be re-created by every coder. (AFAIK there are very few coders out there whose music routine AND loader routine would be an "industry standard" at the same time, am I right?) But where is the border? If I use a piece of downloaded example code for raster stabilizing but then make my own raster trick, or I use an example 3D routine for point calculations but use my own filler - then am I a coder? :) |
| |
MagerValp
Registered: Dec 2001
Posts: 1078 |
Using other people's code is good, it's one of the best ways to learn new things. That implies sitting down and understanding it though, not just pasting it.
|
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 - Next |
