processing category
category: general [glöplog]
Quote:
im also strong advocate for future directx/ogl and shader technology distinction in the categories.
what the HELL
icon for whatever shit platform appears next! :>
oh, didnt turn transparency on :P
gargaj: i'd like to know what runs on ps3.0 and what doesnt. its just not compatible with current database scheme of things.
it also has nothing to do with the prod type or platform - ps3.0 is not a type or platform, neither was mmx, hw accel, windows xp or ds lite. msdos/gus was also a very misguided step considering that.
implement tags? :)
which is a good reason to consider it for v2.
i'd also very much like to know what runs ati only for example.
and yes, it will be a hassle to sort things out, but since we're re-writting things we should defnitly define an architecture that considers these distinctions imho.
i'd also very much like to know what runs ati only for example.
and yes, it will be a hassle to sort things out, but since we're re-writting things we should defnitly define an architecture that considers these distinctions imho.
tags could be a nice solution yes. crowd sourcing ftw
tags will happen in v2
finally \o/
my 2c one cup!!
one cup of STFU!
Maali: cool 4k gfx icon!
(i don't really like the current one :( )
(i don't really like the current one :( )
The current one would be a nice candidate for the "gay deathstar" category :)
Do processing demos need a framework installing or anything? or would they run on a plain java install? I guess that's the key to it for me. I couldn't care less what tool it was made in for the categories.
ps: I think dx/ogl as categories is a bad idea, as it doesn't really make a lot of difference to anyone but the coder (on windows at least.. and it's irrelevant elsewhere).
Shader version is a better idea, but you'd have to be careful with it - somebody with a ps2 card would want to search for ps1/2 demos to watch, not only ps2. Then you have the opengl/dx shader model versions - on pc, everything goes by the dx version, on mac it's opengl, do you have them separate or are they pretty comparable? And what happens with stuff that gets ported? I can see it getting messy :)
ps: I think dx/ogl as categories is a bad idea, as it doesn't really make a lot of difference to anyone but the coder (on windows at least.. and it's irrelevant elsewhere).
Shader version is a better idea, but you'd have to be careful with it - somebody with a ps2 card would want to search for ps1/2 demos to watch, not only ps2. Then you have the opengl/dx shader model versions - on pc, everything goes by the dx version, on mac it's opengl, do you have them separate or are they pretty comparable? And what happens with stuff that gets ported? I can see it getting messy :)
psonice, you need the Processing libraries but I imagine people are distributing them with their productions, and there is no FMOD category...
I thought it was decided that all the specific platforms infos should be put into nfos and certainly not into an extra note field displayed under the screenshot ?
Also ps: will you add the 1979 year ?
Also ps: will you add the 1979 year ?
Quote:
maybe we can have a "tools used" box for prods?
This is interesting... uhm.... maybe something like this?
Platform: PC, Amiga, PSP, C64...
OS: Win32, MacOS, Linux, Browser...
Language: Asm, C, C++, Java, Processing, Actionscript...
A bit tricky, but it may work?
In a way this fixes the problem of my demo being in the category of Java. People may not know that my demo have a Win32, MacOS and Linux executable to run it, and if they are looking for demo to run on their Win32 OS my demo won't appear because it's on the "Java" category.
Oh, by the way, just so you know, there is Processing for Javascript and also for Actionscript.
I think processing means roughly the same as pc and amiga.. A sub-scene, in the sense that the shared technology *or* conventions creates some unique trends inside it.
I like the idea Trace. Somehow it's nice to get something accurate instead flooding the wild section. Imo category could be rethought, just, the main platforms shouldn't be lost inside a lot of "sub-scenes"
(and ok to add 'processing' :])
the idea of a number of minimum requirements to be chosen does somewhat appeal to me. if you can actually specify "ps3.0 required", "needs such and such a version of dx sdk", "opengl + nvidia only", "windows vista" and so on - it might be helpful for those who cant read info files before downloading and commenting. (or those who fail to put such pertinent information in info files in the first place.)
personally though, i think if it runs in exe form, save the language, tools and "how it was done" for the info file. if you want to make demos in LOGO instead of c++ and you're heavily limited because of it, thats your problem. :) and the idea of having "werkzeug" as a platform sounds like thumb-down bait for those who are bitter at being unable to do something better with their current efforts than what can be done in a 5 year old demotool. :)
personally though, i think if it runs in exe form, save the language, tools and "how it was done" for the info file. if you want to make demos in LOGO instead of c++ and you're heavily limited because of it, thats your problem. :) and the idea of having "werkzeug" as a platform sounds like thumb-down bait for those who are bitter at being unable to do something better with their current efforts than what can be done in a 5 year old demotool. :)
http://www.openprocessing.org/
I've gotten into processing over the last few weeks (making live sound-reactive stuff for a music concert), it's delightful to re-implement things in this in a day that took a week to code and ages to tune in c++ as a wmp dll. It's super-easy for anyone, regardless of programming XP to get started, seriously as easy as LOGO, but with an easy path up to hardcore stuff like opengl support through jOGL the power is there, and they're doing shaders in it now.
Anyway openprocessing is already a heavily populated place for this type of collection. No need to have it here.
I've gotten into processing over the last few weeks (making live sound-reactive stuff for a music concert), it's delightful to re-implement things in this in a day that took a week to code and ages to tune in c++ as a wmp dll. It's super-easy for anyone, regardless of programming XP to get started, seriously as easy as LOGO, but with an easy path up to hardcore stuff like opengl support through jOGL the power is there, and they're doing shaders in it now.
Anyway openprocessing is already a heavily populated place for this type of collection. No need to have it here.
It makes no sense to have a Processing category. It's a framework using java. Those prods should be submitted in the Java category.
