The best way to get those braces in Geany on an N810 is to click 'NEW' and choose C++ source file. Then it gives you a basic template with open and close braces for the main function. Then you copy and paste. It's annoying...but...cheaper than a bluetooth keyboard.

My problem is that I can't get xterm to stay open after compiling and running a hello world thing. It say compiled correctly, then launches xterm, but it disappears right away.

Any Ideas?

grinn, i use a bluetooth keyboard on my 810 to do most hacking, otherwise i do c&p coding (moving prewritten code blocks around and small tweaks).

i'm not sure about using a full IDE on the device, but I use pygtkeditor for actually manipulating the files and leave a console window open for make/run cycles.

when I'm at home, i use winscp to access the files stored on my nokia from my windows machine and edit using komodo edit.
again, I have an ssh console window open for building and output.

gcc and tools are on the device, all compilation is done natively.

lcuk,

I know a little java and am teaching myself basic c++. All I want out of this thing is the ability to write, compile and run very baisc C++ code on the 'go'.

I just tried pygtkeditor with a c++ hello world and it launched xterm properly but didn't know what to do with the code.

Any suggestions?

Thanks.

launch xterm outside of pygtkeditor, and switch between them - pygtkeditor is geared towards building python apps and the build button tries to do just that..

click save, alt tab, up arrow, return

You can tweak /usr/share/X11/xkb/symbols/nokia_vndr/rx-44 , one can even have another set of symbols usable with shift+fn (fourth column in the file, by default same as third one). It is a bit tricky to press but quite possible, one needs to press shift first, then fn and hold them both. Possible with left thumb. Also chr can be tweaked to be alt or anything else. So you can map braces to anything you like.

BTW, did you know there are gcc options to reduce memory consumption of the compiler? I thought gcc is bloated and huge C/C++ sources require lot of memory but looks like it is simply bad tuning. I had problem with compiling VICE emulator source directly on the device even with 192MB of swap enabled and someone on Pandora forum told me about gcc options --param ggc-min-expand=x --param ggc-min-heapsize=x and it made huge difference. With --param ggc-min-expand=0 --param ggc-min-heapsize=16384 VICE compiled fine without using lot of swap.

I don't want to start wiki page just with this info so it goes here, this thread is related.