jlehmann@wpi.WPI.EDU (Jonas A. Lehmann) (04/24/91)
Okay, there has been a LOT of talk here about how miserable demo coders are, how poor they know how to program the amiga and how un-OS-friendly their demos are. Why don't we instead try to SHOW them that it can be done rather than just talking about it. I offer to upload a DEMO (complete "real" source) coded by some kiddie programmer with all files needed for it to run (in PAL?!). We on Use/InterNet take this file, convert it to .... - Run on any Amiga - Run without killing OS or preventing Multitasking - Make it work equally well on NTSC and PAL (sound, gfx) - Convert all absolute programming to relocatable - Remove self-modifying code - Make the code look nice (commenting, style) - etc etc .. I run out of imagination :-) e then take this final version and have someone with contacts distribute it to the people who actual code like this, to show how poor they really are. It is EASY to talk, it is TOUGHER to act. Is there any interest in a test like this!? Jonas - jlehmann@wpi.wpi.edu
sschaem@starnet.uucp (Stephan Schaem) (04/24/91)
Maybe, but make the fight corectly. They look at the demo, and then do it from scrach in a day or 2! And why do you care for a demo do have good maners? Those requirment of for productivity software, I couldnt care less if a "mega ball' demo can be made resident and run on 2 'screens'... You dont have you priority strait. Stephan Schaen.
d0micke@dtek.chalmers.se (Mikael Andersson) (04/28/91)
In article <1991Apr23.193049.6097@wpi.WPI.EDU>, jlehmann@wpi.WPI.EDU (Jonas A. Lehmann) writes: |> |> Okay, there has been a LOT of talk here about how miserable demo coders are, |> how poor they know how to program the amiga and how un-OS-friendly their |> demos are. Why don't we instead try to SHOW them that it can be done rather |> than just talking about it. |> |> I offer to upload a DEMO (complete "real" source) coded by some |> kiddie programmer with all files needed for it to run (in PAL?!). |> |> We on Use/InterNet take this file, convert it to .... |> |> - Run on any Amiga |> - Run without killing OS or preventing Multitasking |> - Make it work equally well on NTSC and PAL (sound, gfx) |> - Convert all absolute programming to relocatable |> - Remove self-modifying code |> - Make the code look nice (commenting, style) |> - etc etc .. I run out of imagination :-) |> |> Jonas - jlehmann@wpi.wpi.edu Yeah! When you try to learn assembler you look at other peoples sources (assembler) and see how things are done. Well, that's how I did it anyway. And EVERY source I got my hands on was NASTY to the system... (Writing to registers directly and so on) But if someone took the time to do the things described above - send me a copy of the source and the world will have another programmer that writes system OS-friendly Amiga code. /Mikael -- * Email: d0micke@dtek.chalmers.se * Snail: * At school: Holidays: * * Mikael Andersson Mikael Andersson * The best solution to a problem is * Welandergatan 28 Murarvagen 62 * always neat, simple and wrong. * 416 56 G|teborg 902 51 Umea * -- * At school: Holidays: * * Mikael Andersson Mikael Andersson * The best solution to a problem is * Welandergatan 28 Murarv{gen 62 * always neat, simple and wrong. * 416 56 G|teborg 902 51 Ume} *
mykes@amiga0.SF-Bay.ORG (Mike Schwartz) (04/30/91)
In article <1991Apr28.151031.11475@mathrt0.math.chalmers.se> d0micke@dtek.chalmers.se (Mikael Andersson) writes: > >In article <1991Apr23.193049.6097@wpi.WPI.EDU>, jlehmann@wpi.WPI.EDU (Jonas A. Lehmann) writes: >|> >|> Okay, there has been a LOT of talk here about how miserable demo coders are, >|> how poor they know how to program the amiga and how un-OS-friendly their >|> demos are. Why don't we instead try to SHOW them that it can be done rather >|> than just talking about it. >Yeah! When you try to learn assembler you look at other peoples sources (assembler) and see >how things are done. Well, that's how I did it anyway. And EVERY source I got my hands on >was NASTY to the system... (Writing to registers directly and so on) But if someone took >the time to do the things described above - send me a copy of the source and the world will >have another programmer that writes system OS-friendly Amiga code. > >/Mikael > I just posted some assembly source to alt.sources.amiga. I hope it gets around. -- **************************************************** * I want games that look like Shadow of the Beast * * but play like Leisure Suit Larry. * ****************************************************
mykes@amiga0.SF-Bay.ORG (Mike Schwartz) (04/30/91)
In article <1991Apr28.151031.11475@mathrt0.math.chalmers.se> d0micke@dtek.chalmers.se (Mikael Andersson) writes: >Yeah! When you try to learn assembler you look at other peoples sources (assembler) and see >how things are done. Well, that's how I did it anyway. And EVERY source I got my hands on >was NASTY to the system... (Writing to registers directly and so on) But if someone took >the time to do the things described above - send me a copy of the source and the world will >have another programmer that writes system OS-friendly Amiga code. > >/Mikael > The language used makes NO difference to whether or not the hardware is accessed directly... There is an include file (1.3) called hardware/custom.h which makes it trivial for a 'C' programmer to do the same kinds of accesses to hardware. Consider the following code fragment: UWORD *b = 0xdff000; b[0x182] = 0xfff; /* set color register 0 to 0xfff */ Programmers often access the hardware directly to drive the blitter, copper, and audio hardware, even when using the operating system for everything else. -- **************************************************** * I want games that look like Shadow of the Beast * * but play like Leisure Suit Larry. * ****************************************************