pouët.net

Some of you might have already seen it when visiting the website, but:

The sizecoding.org website has been updated to include information for the following architectures and platforms:

- 6502: Atari XE/XL , Atari Lynx, Atari 2600, Commodore 64
- Z80: Spectrum, Amstrad CPC
- M68K: Atari ST, Amiga

I've setup some pages with some basic information that i learned on my own ventures on these platforms (Mostly Spectrum and a bit of Atari XE and ST) and will hopefully expand a bit more on this in the future as well as having Spkr (Atari ST) and Fready (Atari XE) help out a bit on the Atari side.

However, if you have anything you'd like to contribute for any of these platforms or even platforms not mentioned here. Please feel free to add it to the website. The website is set up as a wiki, so you can just create an account and start editing and adding information.

I think sizecoding.org is a great source of information and i think contributors like Hellmood and Kuemmel/exoticorn (ARM/RISCOS) have done a great job in adding valuable information. Lets now grow the website to cover all popular demoscene platforms!

I'd add one on linux and one on GBA (and maybe gamecube too), but, still no https? :<

https doesn't seem to work. http://www.sizecoding.org/wiki/Main_Page is the correct URL.

Thanks @porocyon , appreciated! Let me know if you need any help setting up the pages

Thanks for the support guys =)
I just pinged Trixter for the https issue
Might take a while, might not ;)

awesome!

@porocyon i quickly setup an ARM / GBA page as well as a link to Linux based work on the main page of the website to help you to get started ;-)

Someone should remove the .git folder from the web server...just saying.

^ this

I have done some 4k on Amstrad CPC / Z80.
On my experience the key point is to think about the final size AFTER compression and not the size of the code produce by the assembler.

It means that we have to produce stuffs that compresse very well and it modifies some way of doing things: for example, instead of producing a small assembled code that generates effect code at the beginning of the demo it is better to produce a huge unroll code straight before the assembling that does nothing at the beginning of the effet.
To reorder function has sometimes an impact as well as writting slower code that looks like more other parts

hi @krusty,

in my experience approaches for 256b, 1k and 4k can differ a lot. If there is anything you could add in the now still empty CPC section that might get people started getting something on screen or out of the speaker , or which tools to use. it would be greatly appreciated.

I was thinking about adding something to the Speccy/Z80 section and was going to mention exactly the same thing about writing code for the compressor. The last Speccy 4k I released was something like 20-30k after decompression. But then I saw that you're targeting 256 bytes or smaller... I'll have a think if there's anything useful that I can add there

It's "256 bytes or smaller" for DOS. Equally elegant and/or awesome tiny intros might a bit bigger on other platforms by design. Don't hesitate anyway to contribute your knowledge to make the entrance for non(your-platform)ers more easy =)

The .git thingie apparently posed no danger but was removed nevertheless ;)

evilpaul: if you still want to contribute that 4k knowledge somewhere, in4k could also use some ZX Spectrum knowledge :)

superogue: I appreciate the help, but, my comment was more of a "I don't want to sign up for an account over unencrypted HTTP". You can get certificates for free nowdays, so, why isn't there HTTPS?

@porocyon: there will be in a few days =)

@evilpaul - just add a section compression (like e.g. the RISCOS/ARM section has) and feel free to contribute any knowledge you have.... a simple but small y*32+x offset calculation routine (to hl or de) is also very welcome.

Ok.. I added a few bits to the ZX Spectrum part of the wiki. Hope they are useful to someone.

If I think of anything else I'll add it later. It could probably do with more links to small intros with documented source code if anyone has some