Kaleidoscope1K by Shiru
[nfo]
|
||||||||
---|---|---|---|---|---|---|---|---|
|
||||||||
|
popularity : 55% |
|||||||
alltime top: #12285 |
|
|||||||
added on the 2009-09-16 15:19:08 by Shiru |
popularity helper
comments
More Flash crap from me, this time 1K. Simple single effect with no sound, but it wasn't easy to fit it in 1K at all. Made just for fun, not for any party.
added on the 2009-09-16 15:20:46 by Shiru
Quite nice, I must say. And thanks for the source. :)
up
good.
Good enough :)
excl :)
nice, but blurry
nice one.
I don`t like that it stops for half a second when changing scroll direction.
Ok, changed if(w>40) to if(w>0), now i like it better, thanks for the source.
nice 1k.
ok
the effect is good, but it changes abruptly and breaks the hypnotic state of a watcher, ruining the experience.
ok
the blur hurts my eyes...but not bad overall
Pretty, but annoying with all the stops.
Nice one! I love kaleidoscopes. Do kids still have them?
shiny!
oks, quite generic fx.
Nice
learn to compile. just compiled it with flex sdk 3.2.0 build 3958 - target: flash player 9, filesize: 1024 bytes. this stuff doesn't use any single feature of flash player 10.
pig.
epic one.
pig.
epic one.
Yeah, unic0rn, your comment is surely epic one. You know, it is really great achievement that you recompiled the MY code probably around hundred times until you got lucky, and compiler output was 1024 bytes instead of 1025, 1026 or 1027. And of course, I didn't knew that MY code doesnt't use FP10 features. Thanks for this masterclass and new information.
actually, got 1024 bytes result after few tries, less than 10. i guess one would be able to make it smaller with some tinkering with swf file structure. after all, that's what demoscene is all about. hacking things to make something impossible possible. not about suggesting to people not knowing any technical details about flash player and related technology, that your code is a flash 10 masterpiece, just because you're too lazy to spend few minutes on compiling stuff.
sure. blame it on luck.
sure. blame it on luck.
look at my avatar, that's me atm
unic0rn, I spent much more than few minutes on compiling this. 1024 output was very unstable for me, around one time per some tens of attempts, and the switch to FP10 compile was a trick to get smaller (1020) and stable (1020 isn't smallest) result, so other people could reproduce it easily. Also, I didn't cared about FP9 support from the beginning, for me it is obsolete, not alternative. So, I suggest you to learn this: everything has the reasons. You could simply ask me why it compiled as FP10, instead of playing the guru.
i knew from the beginning why you've chosen to compile it against FP10 instead of FP9. for me it just doesn't make any sense, and demoscene is neither about (again, IMHO) making things compile perfectly on every single machine in same, predictable way, nor about requiring higher version of the platform without actually using any of it's features. if, let's say, it would be ASM code, which would be somehow smaller because of using SSE3 opcodes (bad example perhaps, but you know where i'm going with this), then it would made sense to require SSE3 support just for reducing the filesize. i'm not saying your code is bad or anything - the effect itself is pretty nice. all i'm saying is that it should be stated from the very beginning it's FP9 code, or - even better - released as FP9 intro. the small percentage of users here that will try to compile it, will know how to get 1024 bytes result, trust me.
it's all a mess, but imho the category itself should be split into 3 categories. after all, 8bit machines like amstrad have several categories, amiga as well - and this is exactly same thing. there's huge difference between pre-FP9 stuff, FP9 stuff and FP10 stuff. having or not AS3, having or not built-in 3D support, shaders and other things... it's like releasing something that would work on A500, as A1200 intro, just in case someone would like to compile it, to guarantee he'll get same result. the only thing here is that people don't really know the real capabilities of the platform, so you're not getting thumb downs for it.
as from me, thumb up for a flash prod. if it would be in separate FP10 category though, you would get a thumb down, and no real explanation would be ever required for that.
it's all a mess, but imho the category itself should be split into 3 categories. after all, 8bit machines like amstrad have several categories, amiga as well - and this is exactly same thing. there's huge difference between pre-FP9 stuff, FP9 stuff and FP10 stuff. having or not AS3, having or not built-in 3D support, shaders and other things... it's like releasing something that would work on A500, as A1200 intro, just in case someone would like to compile it, to guarantee he'll get same result. the only thing here is that people don't really know the real capabilities of the platform, so you're not getting thumb downs for it.
as from me, thumb up for a flash prod. if it would be in separate FP10 category though, you would get a thumb down, and no real explanation would be ever required for that.
get a room
thumb for the platform.
and if you guys can find a room,
So you can finally stop <fighting words>
I'll give you thumbs <linear direction> the <orifice>
and if you guys can find a room,
So you can finally stop <fighting words>
I'll give you thumbs <linear direction> the <orifice>
submit changes
if this prod is a fake, some info is false or the download link is broken,
do not post about it in the comments, it will get lost.
instead, click here !