I was just wondering, do my libs have any place at all in SDL libraries
section? I mean, they’re really so basic that everyone just does the
shit
themselves. They’re basically just OOP style bits of code for the
following:
Pixel Reading (WIP. Adding one or two new features)
Pixel Writing
Anti-Aliased Pixel Writing (WIP. Adding new features)
Line Drawing (To be revamped)
Sprite Manipulation (WIP)
Should I bother putting up a homepage for the cpp classes that I’ve made
that do this crap, or not???–
OOPMan (@OOPMan)
“He who fights with monsters should look to it that he himself
does not become a monster…When you gaze long into the abyss,
the abyss also gazes into you…” - Frederich Nietzsche
if you make a lib that helps me managing my scrolling problem, just put
it on the site
“OOPMan” <oop_man_za at yahoo.com> a ?crit dans le message
news:<39D31BBE.892680FC at yahoo.com>…
I was just wondering, do my libs have any place at all in SDL
libraries
section? I mean, they’re really so basic that everyone just does the
shit
themselves. They’re basically just OOP style bits of code for the
following:
Pixel Reading (WIP. Adding one or two new features)
Pixel Writing
Anti-Aliased Pixel Writing (WIP. Adding new features)
Line Drawing (To be revamped)
Sprite Manipulation (WIP)
Should I bother putting up a homepage for the cpp classes that I’ve
made> that do this crap, or not???
–
OOPMan (oop_man_za at yahoo.com)
“He who fights with monsters should look to it that he himself
does not become a monster…When you gaze long into the abyss,
the abyss also gazes into you…” - Frederich Nietzsche
Ha, if I can ever get some of my other stuff fininshed. I was just editing
the AAPDE just now and I reckon I screwed up a bit. I suppose
I’d better ask the question to see if you I should rewrite the whole thing
way A or way B. So, the question is:
Should I provide support for dynamically scaled AA pixels???/ Like,
when you call the func for the drawaapixel, should I make it that any
pixel of a scale higher or lower than one is caluclated on the fly using
some odd method or other? I think I should maybe not bother cause the
whole idea behind a pixel is that it’s small, even an AA on. Grrrrrrrr.
Just kinda screwed my code up. And forgot to backup. WTF, I’ll just redo
from the start.
I’ve also been having another weird related prob compiling on of my cpp
classes that leads me to believe either there’s some really big invisible
error in the file, or that g++ has gione haywire and refuses to believe
the file is in cpp (You should see the errors
julien wrote:> if you make a lib that helps me managing my scrolling problem, just put
it on the site
“OOPMan” <@OOPMan> a ?crit dans le message
news:<39D31BBE.892680FC at yahoo.com>…
I was just wondering, do my libs have any place at all in SDL
libraries
section? I mean, they’re really so basic that everyone just does the
shit
themselves. They’re basically just OOP style bits of code for the
following:
Pixel Reading (WIP. Adding one or two new features)
Pixel Writing
Anti-Aliased Pixel Writing (WIP. Adding new features)
Line Drawing (To be revamped)
Sprite Manipulation (WIP)
Should I bother putting up a homepage for the cpp classes that I’ve
made
that do this crap, or not???
–
OOPMan (@OOPMan)
“He who fights with monsters should look to it that he himself
does not become a monster…When you gaze long into the abyss,
the abyss also gazes into you…” - Frederich Nietzsche
–
OOPMan (@OOPMan)
“He who fights with monsters should look to it that he himself
does not become a monster…When you gaze long into the abyss,
the abyss also gazes into you…” - Frederich Nietzsche
