2.) To fit a nice source code editor in 160x128 pixels is not easy. Also the default font is for technical reasons 8x8, so there is not much space on screen for text (if I use the standard gfx system). To create a good editor is also quite a lot of work.
3.) I thought about it! Especially because you can do almost everything using PEEK and POKE, it would be a good fit for Assembly. But here are my reasons against it:
- It would NOT be faster than BASIC, because LowRes NX has a virtual limit of CPU cycles and the BASIC commands are already counted without any interpretation overhead. So BASIC in LowRes NX is as fast as Assembly would be.
- It would require a lot of new documentation. I would probably create a custom, simplified Assembly, to be consistent with the rest of the system. But then I would need to write documentation.
- I don't think we would get new users because of Assembly. Maybe a few, but it's probably not worth the effort.
Hi. Sorry, at the moment the iOS app is not available anywhere, because I didn't pay Apple. I will do it eventually. You can still check the Win or Mac versions.
Hi. I'm not planning exporters, but I have a simple HTML template, which you can use: embed.zip
I like to keep LowRes NX as an own platform, not as a tool to create games for other platforms. The user should know about the existence of LowRes NX and about its limitations.
Not directly, it's quite low-level. Please check the documentation chapters "Memory Access" (COPY command) and "Hardware Reference" (about character data).
The call will look somehow like this, but you'll have to adjust the parameters:
Hi. LowRes NX has a limited video RAM for 256 characters. This is what you can show on screen at the same time. BUT: You can store several character sets in one cartridge/program and copy them dynamically to VRAM. So different scenes in a game can use different character sets. You can even combine them, e.g. 128 fix characters for the whole game and 128 for the current level.
