I’m of the mind that it’s probably better to start out with engines/frameworks to get your footing before you move on to lower-level stuff. Then again, I’m not very far either (and sort of stalled for a few reasons).

Godot might be a good avenue with GDextension (GDnative for 3.X), particularly with C/C++. Nim bindings exist (and this is my language of choice) but if you like C/C++ it will certainly have a lot less friction and with those you probably can get far with just the official docs. For C++, you could probably edit the engine itself especially for older versions.

Raylib is another option (and you will likely do a lot more boilerplate stuff) for pretty much any language. And again, with C/C++ it will likely be even more straightforward.

EDIT: Sorry, I see that you know about Raylib already. To say it more directly, I am saying it is likely better to find quick projects that you want to make on the device you’re already coding on (likely a computer) rather than trying to immediately support a specific device or dream projects. Though other low-cost devices (single-board-computers, microcontrollers) if you can get them (at/below MSRP) might be an easier way to fill that niche as well.

hey, sorry I’m late. Well, yeah, maybe it’s convenient to start with something else, even though I have the truth C and above all C + + I like it, it’s good for me, so what it takes more is to find graphic bookstores that help me in my goals, raylib I’m interested, I know it, but I don’t know or use it, honestly. And well, maybe I can agree with maybe it would be convenient to do quick projects, but what quick projects? What can I do? I have no idea

How far along are you with data structures and algorithms?

That’ll really define the path you need to take, especially if you’re learning a low-level programming language along the way

If I know where you stand, I can give you some pointers

i have read only 84 pages of a programming manual, I know I have made very slow progress, but nothing, I am a perishable. I’m also trying to keep learning the language.

I’'ve only ever used sdl 2 and 3, but I’ve encountered 1.2 code in the wild. APIs are going to be different, but big picture stuff is mostly similar. If you learn how to use one version, it shouldn’t be too difficult to switch.

well… i guess it would be nice to look for sdl2 tutorials and see how i adapt to sdl1.2

Best I can do is just point to source code written by an old colleague and friend of mine from back in the day: https://sourceforge.net/p/qbubblemp/code/HEAD/tree/

I wrote system apps and UI frameworks and it’s 25 years ago so I don’t want to pretend to remember too much :D

okay, thank you so much, i’ll take a look at it and see if i can do anything with it, if the answer is yes, i’ll show you what i get.

Harvard’s CS50 (Introduction to computer science) is available for free on edx.org. It starts with Scratch and goes on to C the second week. Excellent lectures by David Malan and lots of weekly exercises you can do and submit for review that will give you a solid foundation to build on.

thank you very much, i’ll take a look.

What, you want to join the development? It’s the same. I hope to get my nex browser soon jajaja.

Take a look at https://www.codedex.io/cpp it’s a great gamified way you can run through fundamentals that ramp up to more complex scenarios and bridge the gap to where you want to be

thank you very much, i’ll take a look at it later.

For pointers in particular, this seems like a good starting point: https://sites.cs.ucsb.edu/~mikec/cs16/misc/ptrtut12/pointers.htm

As for compiling for old C/C++ versions, fortunately most compilers can be set to restrict what standard they will compile for. So you could turn the compiler all the way back to something like C99 and it should work, although you’ll have to avoid using modern syntax.

That said, with regards to compiling for an old platform, be advised that complete and functional toolchains will be harder to come across. They may not even work anymore, if they haven’t been upkept. That’s another complexity that you may have to deal with, and it will no doubt be aggravating, than working with a modern platform but limiting yourself to only older C/C++ standards and graphics libraries.

Basically, the starting effort is quite high for developing for older targets. Be certain that this is the direction you want to start with.

I’ll take a look later.

As for the compiler… well, someone has already passed me tools to program in symbian, and they seem to work well, there are more people in symbian than it seems at first. Not too many people, though.

You should start with C before going into C++. This is because C is the simplest possible language that exposes you to pointers and memory management. That’s the most important foundational skill you need in low level languages like this.

You could learn memory management using C++, but there are a lot of distractions, and the modern features designed to make memory management easier may make it harder/confusing for someone starting at the beginning.

My advice: follow a modern tutorial for C and SDL (on your PC, not that N95), and use it to make a simple game or UI with SDL’s drawing API. Actually aim to finish something (even if it sucks) and you’ll learn a lot.

thank you very much for the advice. The book I use to learn teaches C and C + + at the same time. See what I can do with the pointers.

So, modern sdl doesn’t change much of sdl 1.2? Because if that’s the case I’m trying to use some sdl 2 tutorial, by proximity, I think there’s more of this in my language.

hey, yeah, I’m sorry about that. I’m a fan of obsolete devices, how do you think I get to Symbian in the first place?

I’m aware of how different c + + of c + + symbian is, which I try in most cases only to resort to “apps.”

Do you have any advice from that time? I mean, how do you not do this structure that usually leads to crasheos, or use this graphic library, that I know.