Originally posted by pal666
View Post
Announcement
Collapse
No announcement yet.
Cairo Proposed To Become Part Of ISO C++
Collapse
X
-
-
Originally posted by BlackStar View PostThere is. It's called SDL. No need to burden the standard library with that.
if sdl was of any good for task at hand, iso c++ ppl would be in touch with sdl ppl to standardize it's api, not with cairo ppl
bottom line: stop posting bullshit
Leave a comment:
-
Originally posted by BlackStar View PostI
Human-machine interfaces like mice, keyboards, touchscreens, microphones, cameras? C++ offers nothing of the sort, you must be looking at a different language entirely.
Leave a comment:
-
Originally posted by BlackStar View PostNot only is this a terrible reason, java.awt is also the perfect example why adding a UI library to the standard library sucks. It's slow, it's ugly and it produces terrible UIs that no user would ever want to touch with a ten foot pole.
Leave a comment:
-
Originally posted by Vim_User View PostAnd now show me the mass of webservers actually using that hardware. It is as simple as this: There is a use for unaccelerated graphics functions and therefore it is plain wrong to assume that people that produce libraries for this use are fools.
Leave a comment:
-
Originally posted by BlackStar View PostGive me *one* good reason why a UI library should be part of the standard library specification for C++.
so you could teach students c++ using some ui
now you can as along as you ui is implemented via iostreams, which is too 1970s
btw, cairo is not ui, it's graphics. nobody thinks about standardising gtk(yet)
Leave a comment:
-
Originally posted by curaga View PostBecause win32 sucks, that's why.
Leave a comment:
-
Originally posted by LightBit View PostBecause, POSIX already is IEEE standard and win32 is controlled and used only by Microsoft.
posix is standard for unix, not for generic operating system
c++ does not care who controls what, it is intended to be used by everyone
Leave a comment:
Leave a comment: