oricOpenLibrary by [raxiss]

[iss]

Hello, @all!

My oricOpenLibrary is available at github. Included are:

• lib-basic - Executes BASIC and SEDORIC commands from C code.
• lib-sedoric - Sedoric compatible load and save functions. (obsolette by lib-basic)
• lib-ijk-egoist - IJK-egoist / IJK-joystick sample code.
• lib-ttf - Library and tools for TTF rendering and use in Oric.

I hope you will found it useful.
As always feedback is highly appreciated!

[iss]

Some pics from the last added lib-ttf:

[ibisum]

Very nice work, thanks so much for sharing! This is a cheeky bit of code:

Code: Select all

#define basic(str)  {_basic_s=((char*)(str)),_basic();}

Why the , instead of a ;? .. Does this instruct CC65 to place the retval from _basic() into basic_r? If so, int-er-esting ..

EDIT: okay, I've read the rest of the library code, and I think it is very interesting where you are going with this .. I'm counting the days down until we have a text editor for the Oric, finally, worth using ..

EDIT2: okay, you get even more points from me for the presence and purpose of the .lua files in this archive .. BTW, load81-oric?

[jbperin]

Thank you very much Iss for sharing this library with the community.

That is undoubtedly a very valuable library for modern development on Oric. The code is neat, very readable. Very nice work !
And there are many things to learn from this code.

There are at least two things that I've allways wanted to understand and that I can better explore thank to this library:
- file loading/saving with sedoric .. (this lib seems to make things so simple .. from C or from BASIC).
- the IJK interface .. (very interesting example .. good starter for dummies C programmers).

Just to make sure I did understand what I read.
Are data defined here the result of assembling the driver in ijk-driver.s?
I like this way to make some assembly routines available from the BASIC

The TTF font rendering looks very cool. And that seems to be a very convenient and stylized way to display dynamically defined text on a hires screen. I wonder how it would behave if it is used over a previously loaded B&W image.

PS: I noticed that your data block definition in ijk-btest.txt ends with the french word FIN. Funny to see a french word here

Congratulation and thank you

[xahmol]

Thanks. Again. The TTF addition is very interesting.

And without the other parts my Oric Screen Editor and Ludo would not have been possible, at least not in their present form.

[iss]

Guys, thank for the kind words - this is really motivating .

...

All headers may look bit unusual and wired but the reason for this is to be compatible with cc65 and osdk - the idea is to be used static variables for passing params and compiler independent return of result. (A:X vs. X:A).

Are data defined here the result of assembling the driver in ijk-driver.s?

Yes, it's the same asm source compiled and converted to DATA.

About 'FIN' - yes, I use it frequently and mainly in asm sources. I don't remember which assembler was but it gives an error when I used 'end' as label (obviously it was treated as reserved word ).

[iss]

I've just updated my oricOpenLibrary with new item:

• lib-romident - library for ROM identification using known crc32.

I hope someone will find it useful.

[ibisum]

I hope someone will find it useful.

For sure! LOCI support already, very nice!

Sure is looking like a lot of huge things are happening for Oric these days ..