i want to plot a graph from scratch and setpixel sucks dick. any good books to look at? msdn encylopedia is way too large.
Name:
Anonymous2007-05-02 16:19 ID:GjpvmtPk
Why the hell would you want to do it with C++?
Name:
Anonymous2007-05-02 16:26 ID:XRcdnMaL
cause im hella pimp
Name:
Anonymous2007-05-02 16:28 ID:XRcdnMaL
>>2
im looking for speed, the calculations that go into the graph are pretty long.
Name:
Anonymous2007-05-02 16:37 ID:GjpvmtPk
Just use Numpy like everyone else.
Name:
Anonymous2007-05-02 16:46 ID:KpE7iXLs
>>1
Use Python+Psyco. For graphics, use wxWidgets, I think I saw chart widgets somewhere. Or output something you can then feed GNUplot or something like that, I believe. Or do as I do, poor man's charts (AKA nigger charts):
Do it the Unix way: make the calculations in C, output it in a format suitable to feed to gnuplot, and pipe them together.
Name:
Anonymous2007-05-03 1:49 ID:lyl64VhK
>>11
is there anyway to create like a virtual pipe/console in windows or dos? im already nigger piping (creating in.txt, system("xxx.exe < in.txt > out.txt"), then reading out.txt) another .exe to do some of the calculations
still working on it. im probably going to create a bitmap then display it. the piping part im not worried about yet since it still works well without it. (i would just integrate the .exe into my program since its open source but its library is sprawling shit) my next problem is screenscraping to detect certain images.
Also, get VC++ 6 or 7 (not dot net's 2002+). Most examples on the web can't be done without its MFC, and here is where free or open source alternatives fail. For example, if you want to even make an icon, you can't with just gcc. Your resource file has to be created somewhere else, even though cygwin has a resource compiler.
Also, DevC++ has advanced little in the past 5 years: though it can help with the API, it has no MFC support. There is WxWidgets and a DevC++WxWidgets port, but I forget why I stopped using it.
Again, if you have VC++ (ugh,) go grab an old book. Avoid dot net since you won't learn Win32 the right way. I think the 2002+ compilers are removing legacy Win32 support. The free VC learnig edition or whatever is a damn DOS builder --MS decided that to code even a basic window, after literally half an hour worth of setup changes, they would discourage us via a required manual edit cycle. And still no MFC there. Windows itself is the reason why our code is not windows friendly and still uses DOS boxes, 7 years after the underlying DOS layer was removed and emulated on demand by the OS.
Name:
Anonymous2007-05-06 16:17 ID:yBSSkgic
Avoid dot net since you won't learn Win32 the right way. I think the 2002+ compilers are removing legacy Win32 support.
If the compilers are removing support... uh... just a guess: maybe you shouldn't bother learning it? You only have so many hours in a day.
>>43
Who wants MFC anyways? Win32 fails hard; MFC is blOOatware and fails even harder.
Name:
Anonymous2007-05-06 16:59 ID:PX4jl9bJ
>>44
Er, here's the problem: Microsoft doesn't know where it's going to be in 3 years. They want to force businesses into Vista and dot NET. You can go ahead and learn dot NET now, but millions of users and businesses that don't include the latest runtimes, and users of illegal Windows who never run Windows Updates, are out in the cold.
If you work in IT you'd know that every time Java and .NET APIs change, you WOULD have to go to every machine in your business and install the new runtime, because MS and SUN Microsystems sure don't automate this for you. And WOULD means that they don't, and just sit it out with their old versions, and wait till the programmers wisen up or the entire business gets a hardware/OS upgrade.
So yes, MFC is bloat, but it's 300% faster than the bare C++-on-Win32 learning curve. I hate its guts, and that's why it's going to be a long year while I learn Win32 the long way as well.
Name:
Anonymous2009-01-14 13:47
Vim
Name:
Anonymous2009-03-06 5:46
Purposes Lover of Lisp Yet what the combination of functional programming and enterprise quality would yield now but I invented This may not surprise you but I invented taking credit for your own answer to your own when make is readily available but individual makefiles ought to be kept small When you can just write cout n String occurs so I have some real.