Random "work in progress" shots
category: general [glöplog]
I think he was saying that the C64 IS A BREAD BIN.
@kb_: open source it!
Yeah, well... kinda working
Some Forever 2015 C64 musical shit in progress.
noby: better than deepchord!
continuing adventures in software rendering, 2015 edition.
inspired by c++14, werkzeug operators, and python (generators) -- I started over.
here's some workstages, while trying different ways to implement the operator chaining.
inspired by c++14, werkzeug operators, and python (generators) -- I started over.
here's some workstages, while trying different ways to implement the operator chaining.
anix,
?
Code:
class object
{
const object& op1(params)
{
// do something with instance
return *this;
}
const object& op2(params)
{
// do something with instance
return *this;
}
}
auto o = Object();
o.op1(params).op2(params);
?
Ah sorry, returned references probably shouldn't be const.
I considered *this chaining, and I could revisit it, but the way I implemented the operators, it may not work as you wrote.
each operator is a class with (thread-local) storage for state, implements begin()/next() style iteration, and expects the input operator to have the same interface. everything is lazy evaluated, with the exception of things like Center() which has to perform all of the chained operators on the root aabbox to compute its offsets.
I'm pretty happy with one-operator-per-line since it's easy to edit, or disable an operator with comments. (of course, *this-chains could still do that)
Connecting one source operator to multiple inputs would be trivial also.
The first screenshot used object composition, which makes a nested mess -- that was out right away :)
each operator is a class with (thread-local) storage for state, implements begin()/next() style iteration, and expects the input operator to have the same interface. everything is lazy evaluated, with the exception of things like Center() which has to perform all of the chained operators on the root aabbox to compute its offsets.
I'm pretty happy with one-operator-per-line since it's easy to edit, or disable an operator with comments. (of course, *this-chains could still do that)
Connecting one source operator to multiple inputs would be trivial also.
The first screenshot used object composition, which makes a nested mess -- that was out right away :)
1993 authentic.
barti: <3
Under Construction here we come!
Barti: cool.
i wonder why 90's design are not so prominent in demos anymore. thats much cooler than todays demo-standards :P
i wonder why 90's design are not so prominent in demos anymore. thats much cooler than todays demo-standards :P
xmass!!
Yeah Yeah numtek :D
here are xmas balls:
visy: watteh frak! looks fantastic :D
mu6k: I love your ascii-rendering stuff :) really great!
Does this count?