| |
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....
|
| |
Frantic
Registered: Mar 2003
Posts: 1648 |
Well.. To be more precise. I think it is kinda hard to make a clear distinction between what is "demo coding" and what is "VIC coding". In theory it is simple, but in reality many of the articles are just as much about "VIC" as about "demo coding". (I am quite fine with the other categories suggested by Oswald though).
For this reason, I still think that VIC and demo coding should be on the same page. If you (anyone) disagree, please state more precisely what parts of the current VIC-and-Demo-page that should go on a "demo coding" page and what should go on a VIC page.
In any case though, Mace is of course also right when he points out that some parts of the wiki are rather messy due to too much content on one page (especially the VIC/demo-page). So... More structure is needed, yes.
I will have a look at it.
EDIT: What kind of content exactly would go on a "pure" Demo coding page? Seems to me that there aren't really much content available on "coding demos in general", apart maybe from Putermans tutorial or so. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
imho its pointless to divide "demo" and "game" coding ... many techniques are useful for both.
why not make a generic structure (without any of the "demo" and "game" cathegories) and additional portal pages for demo/game/tool/whatever related stuff ? |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
vic&demo coding seperation:
VIC:
Basics
HW tricks
Custom modes
(all the sprite stuff below this seems to be rather game related)
demo
drawing on the screen
softmodes for effects
Articles on demo effects
Various VIC related
Demo Programming Tutorials
Sourcecodes for demo parts |
| |
Mace
Registered: May 2002
Posts: 1799 |
VIC coding:
- $D011, $D016 and $D018 tricks (FLD, VSP, FLI etc.)
- sprite tricks (flexers, multiplexers and 9th sprite stuff)
- in short: anything that is based on $Dxxx register-freaking
Demo coding:
- scrollers (the 'difficulty' is not the VIC stuff)
- general displaying of video modes, static VIC stuff
- bitmap plotting
- basic (not BASIC) stuff like sinus sprites and DYCPS
- logo swing (and tech-tech, but this could be a VIC trick too)
- zoomers
- in short: mostly done in RAM, the VIC only supports.
Also, I don't think the chapter "Demo records and world firsts" belongs in the coding section. This is general background information as long as no code is attached.
[edit]Seems Oswald and I agree for the larger part :-) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
but why do things like "scrolling" or "basic sprite stuff" belong into "demo" cathegory? i like the idea with portal pages more, then it could get a proper link from both game- and demo- related pages :) |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
Quote: imho its pointless to divide "demo" and "game" coding ... many techniques are useful for both.
why not make a generic structure (without any of the "demo" and "game" cathegories) and additional portal pages for demo/game/tool/whatever related stuff ?
thats a point, but having stuff like scrolling, collision detection, sorting plexers, game map, enemy object handling, etc. in its own game section decreases the content on one screen (if it would live with the demo stuff) and makes it more managable. |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
Quote: but why do things like "scrolling" or "basic sprite stuff" belong into "demo" cathegory? i like the idea with portal pages more, then it could get a proper link from both game- and demo- related pages :)
yeah, scrolling, setting up basic screenmodes, basic sprite setup etc. should be all belong to VIC. its 2008, since 20+ years scrolling stuff and setting up koala gfx doesnt counts as demo fx. its basic knowledge. |
| |
Frantic
Registered: Mar 2003
Posts: 1648 |
@Oswald/Mace: I still find the division between VIC/Demo/Game rather arbitrary. Whether the "advanced stuff" should go into a VIC section or a Demo section is not clear to me. Also... Inevitably, stuff like "sprite code" would consist in both simple and gradually more advanced stuff.
I think... What is needed is not only a structure (list of examples on what goes where), but also clear (and short) explanations that explain to the users where to put what kind of content in a clear way.
But... Yeah... I'll have a look. I also need to upgrade the dokuwiki distribution on the server, which means I have some stuff to do with it anyway. I hope nothing will break... :) (There are backups, yes..) |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
you could also argue that crunchers/math/algorithms should belong to the demo section because demos use crunchers/math/algos etc... there's no perfect solution but some rough lines has to be drawn. |
| |
Frantic
Registered: Mar 2003
Posts: 1648 |
Yep.. I couldn't agree more. Structure is needed. (I did find the demo/vic distinction particularly blurred though). |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 - Next |
