| |
Frantic
Registered: Mar 2003
Posts: 1661 |
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....
|
| |
Frantic
Registered: Mar 2003
Posts: 1661 |
Yes.. sorry for the inconvenience. It will be up again shortly. The data is backed up, as Moloch says, in several places even.
...but, Moloch: Did you see my emails? |
| |
Skate
Registered: Jul 2003
Posts: 506 |
seems to be up again. now you can read all the tutorials there and take the first place in the top demos list with your hyper super duper ultimate mega demo project. ;) |
| |
Frantic
Registered: Mar 2003
Posts: 1661 |
Yep, it is now up again and the wiki system is also upgraded to the latest version. Enjoy! |
| |
McKrackeN
Registered: Feb 2011
Posts: 20 |
Great!! I'm glad to read that! :D |
| |
Moloch
Registered: Jan 2002
Posts: 2972 |
Quoting FranticMoloch: Did you see my emails?
I got one email, is there more? I'll check again today and see if anything else is there.
You can always send a message here, I'm here two or three times a day.
|
| |
Mace
Registered: May 2002
Posts: 1799 |
The more I browse through Codebase, the more I miss proper explanations of the principle behind routines.
Having some commented, or, god forbid, raw sources is nice, but it is so freakin' time consuming to plough through them to understand what happens.
May I invite people to write small descriptions of their routines?
Example for, say, a DYCP in hires bitmap:
- FONT: 64 char font, 75x pixels per char
- DATA: 256 bytes of sine data in $00 - $2b range
- TEXT: plain screencode text, end code = @ ($00)
- TABX: table of screen addresses based on X-axis
- TABY: table of screen addresses based on X-axis and sine offset (DATA)
Get a letter from TEXT, fetch corresponding char from FONT and plot in memory calculated from TABX en TABY.
{source here}
|
| |
bepp
Registered: Jun 2010
Posts: 268 |
What Mace said! |
| |
Oswald
Registered: Apr 2002
Posts: 5127 |
yep. I dont like that kind of sourcedumping in there either. |
| |
Six
Registered: Apr 2002
Posts: 322 |
Sometimes understanding the theory behind something is far more important than having the code. I'd love to see a section explaining the math and timing behind different effects. |
| |
Count Zero
Registered: Jan 2003
Posts: 2012 |
Special sections? Have such explanations right with the routines, I'd say. It's a wiki so - contribute! :)
Of course pasting source into a page is much easier than explaining it but thats community work as well, no?
|
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 - Next |
