CPCWiki forum

General Category => Programming => Topic started by: GUNHED on 21:45, 01 December 20

Title: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 21:45, 01 December 20
Today we start the FutureOS Programming Contest

Prices:
1. 200 Euros
2. 100 Euro
3. LambdaSpeak FS (not yet available - the final chapter)4. 50 Euros

Maybe additional prices will be donated.

Submission date: 1.12.2021 (one year to go)

How can you participate? Well, just program something. Examples:
- Game
- Application
- anything else, as long as it runs with FutureOS

Informations you can get at www.FutureOS.de (http://www.futureos.de) or right here (post or PM)  :) :) :)

How will the winners be determined?
- We let all the CPC users decide


Any questions? Anything else?
Right here please.
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 18:28, 02 December 20
The first participant is Slartibartfast. He is coding a game.


Everybody else is welcome to join the contest. Of course you can even 'join' at the last day of the contest, in case you don't want to have pressure on yourself too much.


Good luck and much fun to everybody!
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: zhulien on 06:48, 04 December 20
I wonder if someone would create a BASIC shell for futureos?  and a CP/M shell?
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: funkheld on 11:38, 04 December 20

fotureos currently only works with asm.


cannot be handled as easily by a normal programmer as we are. therefore futureos is not for us if we want to program something.


greeting
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: Sid_ on 12:15, 04 December 20
You can code in c language also.
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: funkheld on 19:44, 04 December 20
then show me a demo in c for futureos and with which c compiler?   8) 

and then start the demo program in futureos

where are the lib and include for futureos in the c compiler?


greeting
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: AMSDOS on 01:11, 05 December 20
Quote from: funkheld on 19:44, 04 December 20
then show me a demo in c for futureos and with which c compiler?   8) 



I wrote 2 (Star Scroller & Bouncing Ball) using Small-C with the FIOLIB in 2013:


https://www.cpcwiki.eu/forum/programming/futureos-corner/msg66182/#msg66182 (https://www.cpcwiki.eu/forum/programming/futureos-corner/msg66182/#msg66182)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: funkheld on 16:01, 05 December 20
hello thanks.


which one  :  Small-C ?
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 13:42, 06 December 20
Quote from: zhulien on 06:48, 04 December 20
I wonder if someone would create a BASIC shell for futureos?  and a CP/M shell?
Indeed a simple kind of BASIC would be a cool idea and probable a doable entry.


Quote from: funkheld on 11:38, 04 December 20fotureos currently only works with asm.cannot be handled as easily by a normal programmer as we are. therefore futureos is not for us if we want to program something.


Quite in contrast, to code something for it in ASM is more simple then anywhere else. Some reasons:
- You can use the complete RAM from 0 to &A000 (up to &B800 if needed)
- You can use all RST vectors for you own program
- You can use the &0038 Interrupt vector and the &0066 vector the way you want
- You can use all registers, of course the second register set too.

To have OS functions be split in four different ROMs may be a new concept, but in reality it's simple. Just switch the ROM on and call the OS function. Done.
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 13:49, 06 December 20
Quote from: AMSDOS on 01:11, 05 December 20

I wrote 2 (Star Scroller & Bouncing Ball) using Small-C with the FIOLIB in 2013:


https://www.cpcwiki.eu/forum/programming/futureos-corner/msg66182/#msg66182 (https://www.cpcwiki.eu/forum/programming/futureos-corner/msg66182/#msg66182)


Thanks for mentioning that.  :) :) :)  Maybe FIOLIB need an update for SDCC or something like that. That would actually be a great project too.


Of course I'm here to help everybody with all entries / projects.  :)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 19:29, 07 December 20
In addition there probably will be a hardware price too. An new expansion, I'll let you know when time is right. :)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 15:50, 11 December 20
We have only one entry up to now. Even the smallest additional entry will win!  :) :) :)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 14:02, 10 January 21
Dear coders...

If you plan to do something for the CPC / Plus then just adapt it for FutureOS and contribute to this nice contest. Your gain: You will win a price. Our gain: Your great work.

Of course I will always provide support for anything just in case the 500 KB of documentation are not too well written (which is sometime the case for somebodies own projects, even an OS).

:) :) :)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: m_dr_m on 02:16, 18 January 21
Great initiative! Not sure about the prices though :)  I don't think potentially interested CPCists are drawn to money.
Maybe some rare goodies would be appreciated? E.g. A Symbiface 2.5 or a balloon from KlassenTrefen.


The visual text-diff project would be very sweet to resurrect.
Also, a little shell with file-search facilities would make my day. To dig into the archives.
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 20:58, 18 January 21
Well, price #4 is a special blue LambdaSpeak FS (they are not available yet, but in testing phase).

Somehow it's amazing how much participants they got in spain - for money prices.

Right here I wished we would have more participants than prices.
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: roudoudou on 09:12, 20 January 21

is there a "good to know" manual or "don't do that!" manual in order to make a clean coding?
i opened an API manual and i understand there is system values in the screen area?  :o

Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 17:15, 20 January 21
Quote from: roudoudou on 09:12, 20 January 21
is there a "good to know" manual or "don't do that!" manual in order to make a clean coding?
i opened an API manual and i understand there is system values in the screen area?  :o
Well, not it's in the ROM area, your API entries are in the area of &FF00 to &FFFF (upper page). This area is equal in all FutureOS ROMs.

In the download section of www.futureos.de (http://www.futureos.de) there is the manual, the API manual and OS functions explanation for all four OS ROMs. Also you have a "how to start" guide and examples.

Please feel free to ask for coding examples right here. I'll support of course.  :) :) :)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 19:01, 20 January 21
Well, what are the advantages of FutureOS

- You're free in using the machines hardware. For example all RETs are yours, the 2nd register set can be used fully anytime. Free selection of interrupt mode and. Ints and NMIs are yours too.
- Free RAM from 0 to &A000 and as long a you don't load/save files you can use RAM up to &B800 too.
- Memory management for 16 KB blocks between &4000 and &8000
- Very quick OS functions
- Support of many hardware expansions.

So, it's ideal for games, demos and bigger applications.
Hope that some people are interested, because this is made for you all.  :) :) :)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 16:08, 19 February 21
Just an idea: For the LambdaSpeak there is a nice software library. It would be pretty to see somebody doing something for the FutureOS programming contest and the LFS.
If you're interested, let me know, I will provide the hardware (LambdaSpeak FS).
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 02:12, 26 February 21
One idea for the programming contest for FutureOS.


It would be nice to see an application which is capable to download OS updates from the internet.
I would help to burn the new ROMs.
You would write something to download the ROMs - using the M4 card or the SF3.
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 13:55, 11 March 21
Just a reminder, let's be creative and participate here.

Support is provided in many ways.

Corona time = programming time!  :) :) :)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: SRS on 22:03, 15 March 21
About SDCC and FutureOS, GUNHED knows my troubles :)
I hereby give y'all my try of a helloworld in C/SDCC with source, comp.bat , *.dsk and no idea why i can't get it to compute under FOS :)

C-CODE

//Helloworld FOS

#define RAMCHAR #0xB847 //located in first 64 KB RAM
#define TERM_2 #0xD48C     //located in ROM A (Textausgabe)
#define KLICK #0xFE9A     //located in ROM D (Rücksprung in den Desktop)
#define ROM_D #0xFF12     //located in all ROMs



void init_FOS()
{
__asm

    ld bc,(#0xFF01)
    out (c),c
    ld bc,#0x7F82
    out (c),c
    ld (RAMCHAR),bc
__endasm;
}

void exit()
{
__asm
    ld hl,KLICK
    call ROM_D
__endasm;
}


void prints(char *text) __z88dk_fastcall
{
__asm
   call TERM_2
__endasm;
}


void main()
{
    char* test = "\x1E\x15\x1aHallo FOS-WELT vom SDCC!";
   
    init_FOS();
    prints(test);
    exit();
}


Assembly from SDCC:
Spoiler: ShowHide
   
;--------------------------------------------------------
; File Created by SDCC : free open source ANSI-C Compiler
; Version 4.0.0 #11528 (MINGW64)
;--------------------------------------------------------
    .module helloworld
    .optsdcc -mz80
   
;--------------------------------------------------------
; Public variables in this module
;--------------------------------------------------------
    .globl _main
    .globl _prints
    .globl _exit
    .globl _init_FOS
;--------------------------------------------------------
; special function registers
;--------------------------------------------------------
;--------------------------------------------------------
; ram data
;--------------------------------------------------------
    .area _DATA
;--------------------------------------------------------
; ram data
;--------------------------------------------------------
    .area _INITIALIZED
;--------------------------------------------------------
; absolute external ram data
;--------------------------------------------------------
    .area _DABS (ABS)
;--------------------------------------------------------
; global & static initialisations
;--------------------------------------------------------
    .area _HOME
    .area _GSINIT
    .area _GSFINAL
    .area _GSINIT
;--------------------------------------------------------
; Home
;--------------------------------------------------------
    .area _HOME
    .area _HOME
;--------------------------------------------------------
; code
;--------------------------------------------------------
    .area _CODE
;helloworld.c:10: void init_FOS()
;    ---------------------------------
; Function init_FOS
; ---------------------------------
_init_FOS::
;helloworld.c:19: __endasm;
    ld    bc,(#0xFF01)
    out    (c),c
    ld    bc,#0x7F82
    out    (c),c
    ld    (#0xB847),bc
;helloworld.c:20: }
    ret
;helloworld.c:22: void exit()
;    ---------------------------------
; Function exit
; ---------------------------------
_exit::
;helloworld.c:27: __endasm;
    ld    hl,#0xFE9A
    call    #0xFF12
;helloworld.c:28: }
    ret
;helloworld.c:31: void prints(char *text) __z88dk_fastcall
;    ---------------------------------
; Function prints
; ---------------------------------
_prints::
;helloworld.c:35: __endasm;
    call    #0xD48C
;helloworld.c:36: }
    ret
;helloworld.c:39: void main()
;    ---------------------------------
; Function main
; ---------------------------------
_main::
;helloworld.c:41: char* test = "\x1E\x15\x1aHallo FOS-WELT vom SDCC!";
;helloworld.c:43: init_FOS();
    call    _init_FOS
;helloworld.c:44: prints(test);
    ld    hl, #___str_0
    call    _prints
;helloworld.c:45: exit();
;helloworld.c:46: }
    jp    _exit
___str_0:
    .db 0x1e
    .db 0x15
    .db 0x1a
    .ascii "Hallo FOS-WELT vom SDCC!"
    .db 0x00
    .area _CODE
    .area _INITIALIZER
    .area _CABS (ABS)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 23:25, 15 March 21
You bank in the lower ROM ( LD BC,&7F82:OUT (C),C ). therefore the start of the program must be at &4000 or higher (ORG &4000).

Or you can use an OS function to copy the ROM character set to RAM (from &3800 to &3FFF) using OS function INRZ from ROM C.

However FIOLIB does provide a PRINT function for C (made for Small C - I got no idea if it works with SDCC).
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 17:16, 17 March 21
Also this is wrong:

    ld    bc,#0x7F82
    out    (c),c
    ld    (#0xB847),bc


Because RAM variable 'RAMCHAR EQU &B847' is a byte in size, not 16 Bit.
To load BC there will corrupt the Cursor position:

;FDC_RES EQU &B840
;RAMCHAR EQU &B847
;C_POS   EQU &B848
;AKT_ROM EQU &B84A
;AKT_RAM EQU &B84C

Somehow I'm afraid SDCC can't do it.


A simple 'Hello World' program for FutureOS look like this...

ORG &8000 ;Hello World - File HELLO.MAX

WRITE"HW.64K" ;SAVE assembled file to disc, Autostart at &8000
              ;The extension 64K tells, that the program runs in first 64K RAM

;Prints "Hello World" in the files section of the screen
;Doesn't disrupt the icon section

HELLO LD BC,(&FF01) ;BC contains &DF00 + ROM_select of FutureOS ROM A

OUT (C),C ;Switch FutureOS ROM A on between &C000 and &FFFF

LD  BC,&7F82     ;Selects MODE 2 and Lower ROM = ROM character set
OUT (C),C        ;Switch it on!
LD  (RAMCHAR),BC ;SAVE MODE and ROM configuration to OS system variable

LD   HL,TXT ;Pointer to text, that shall be shown on screen
CALL TERM_2 ;PRINT text on screen

LD   HL,KLICK ;OS call KLICK is used to return to FutureOS with intact icons
JP   ROM_D    ;Switches ON the ROM D and then jumps to HL (here to KLICK)

;Text

TXT DB &1E,21,26 ;Control Code &1E works as LOCATE, using 64 x 32 screen mode
                 ;The Y position is line 21, and the X pos. is column 26

DB "Hello World!",0 ;The string is terminated by a 0 byte (or by &1A)



;EQUates of OS variables

RAMCHAR EQU &B847 ;located in first 64 KB RAM


;EQUates of System Calls

TERM_2 EQU &D48C ;located in ROM A
KLICK  EQU &FE9A ;located in ROM D
ROM_D  EQU &FF12 ;located in all ROMs


Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 23:16, 18 April 21
Anybody else participating? Let us know.  :)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 17:02, 20 May 21
Just a reminder... Please finish your project until 1st of Dezember this year.  :) :) :)


In case you need couple days more, let us know, and the deadline can be extended for some days.  :)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 21:09, 07 December 21
The contest was closed on Dezember 1st. The only participant was TFM himself with his Multi-Tasker Caruh.
(Actually he didn't but it sounds better than to just say: Nobody participated).

Quote from: GUNHED on 21:45, 01 December 20
Prices:
1. 200 Euros
2. 100 Euro
3. LambdaSpeak FS (not yet available - the final chapter)4. 50 Euros

All that could have been yours with a single line of code writing "Hello World" on the screen  :laugh: :P
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: tjohnson on 23:14, 07 December 21
It's a shame nobody entered the competition :(
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 23:54, 07 December 21
Well, maybe a small game is coming up during the next months... At least it got started.  :)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: Cwiiis on 01:16, 08 December 21
Shame, I didn't realise this was on or I would've entered something :) Next year, maybe?
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: TotO on 10:35, 08 December 21
Perhaps we can draw some conclusions:
- Developers do not do this kind of contest for money
- They can't participate in all competitions and their own projects
- Finally, Future OS was never really popular, isn't it?

Also, if this competition was made to boost the use of Future OS, it has above all shown that despite its undeniable technical qualities, it is not a new wallpaper or an update of the icons that will make it sexy to use. It accuses a graphical interface whose concept is 30 years old and it had a serious concurent in name of SymbOS since.
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 18:30, 08 December 21
True this. But an interface is not bad, because it's 30 years old (or 33 to be precise  :laugh: ).
It you have any suggestions how to make things more interesting. please let me know.  :)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: norecess464 on 20:25, 08 December 21
Sorry, I'm going to be off-topic a little bit.

I think both FutureOS and SymbOS are amazing projects. In both cases, the internal specs are wonderful, and it's obvious it's made by people that know really well their machine.
But, and this is my opinion, I keep thinking that an user interface with icons and such is asking too much for our Amstrad machines. I believe that the use of a mouse cursor as main input device is counter-productive. Yes, you probably have keyboard shortcuts -- I can also drive Microsoft Windows from the keyboard, but will I do that for real ? nope.
I would love to see something simpler, based on CP/M-like commands. On top of it, if you want to bring some interactivity with the user and that a commands-only workflow is not enough, then you could think about a very primitive text-based toolkit (Discology workflow in mind, with the menu system etc). There are amazing command-line interfaces on Linux that would make a great job on the Amstrad (Midnight Commander, Tilde, cmus, etc.).

I'm not saying YOU should do that. I'm not saying that I have the best solution either. Stay true with your project and your direction :) I'm just sharing my opinion, as a point of thinking and the expectations I get for an OS add-on/replacement for the Amstrad.
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: menegator on 20:44, 08 December 21
Both FutureOS and SymbOS are examples of what a talented and devoted programmer can accomplish on an almost 40 years old hardware. That been said, though SymbOS is prettier and carries a huge WOW factor, SymbOS with its "dated" interface is IMHO more near to the 8bit spirit in the context that is a "dated" interface to a dated -without quotes- machine.

The problem is that the shell itself negates the need to use the API because unless I am mistaken you can execute anything or almost anything. "Serious" games talk to the hardware directly and for the rest the ever present if suppressed by the FutureOS firmware can handle the rest.

Just me 0.02€
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 17:06, 09 December 21
Quote from: norecess on 20:25, 08 December 21
I would love to see something simpler, based on CP/M-like commands. On top of it, if you want to bring some interactivity with the user and that a commands-only workflow is not enough, then you could think about a very primitive text-based toolkit (Discology workflow in mind, with the menu system etc). There are amazing command-line interfaces on Linux that would make a great job on the Amstrad (Midnight Commander, Tilde, cmus, etc.).
Thanks a lot for your comment!  :) :) :)  I will have a good thought about it and put that on my 'To Do' List. Also thanks for mentioning examples, that's always a great help. Surely I find some youtube vids about it.  :) :) :)

Quote from: menegator on 20:44, 08 December 21
... though SymbOS is prettier and carries a huge WOW factor, SymbOS with its "dated" interface is IMHO more near to the 8bit spirit in the context that is a "dated" interface to a dated -without quotes- machine.
SymbOS of course has that 'WoW' factor. That's true for sure. For FutureOS I did choose MODE 2, because it does allow to display a full directory (64 filenames) at once. The trade-off is the monochrome screen though. If you know a way to make the appearance of FutureOS more pretty let me know please.

Quote from: menegator on 20:44, 08 December 21
The problem is that the shell itself negates the need to use the API because unless I am mistaken you can execute anything or almost anything. "Serious" games talk to the hardware directly and for the rest the ever present if suppressed by the FutureOS firmware can handle the rest.
Well, I'm not sure to understand... FutureOS is designed to be a great environment for games (which means, the game doesn't need to kick it out like we know from Firmware). The advantages are that a game can use up to 62 KB of RAM from the first 64 KB. Only 2 KB are needed for the OS, part of that is the stack. The OS is made in a way that you can either use OS functions or use hardware directly - no problem to to both. Hope that I didn't miss the point.  :) :) :)


In general it is a project for the CPC scene. It's for you all. And I would love to see it to bring fun into your live and hopefully sometimes some 'serious help' too (like lots of other great persons here are doing wonderful projects for the CPC too - doesn't matter if hardware or software).  :-* :) :) :)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: menegator on 23:09, 15 December 21
Quote from: GUNHED on 17:06, 09 December 21For FutureOS I did choose MODE 2, because it does allow to display a full directory (64 filenames) at once. The trade-off is the monochrome screen though. If you know a way to make the appearance of FutureOS more pretty let me know please.
It was a typo, I meant to write FutureOS is more near to the 8bit spirit.
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 19:47, 17 December 21
Quote from: menegator on 23:09, 15 December 21
It was a typo, I meant to write FutureOS is more near to the 8bit spirit.
Thanks a lot, it's interface is out of that time. However, I'm always there to hear options and ideas. It may be taking a while, but of course I try to make it up in a way that you all like.  :) :) :)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 20:26, 25 December 21
Quote from: norecess on 20:25, 08 December 21
Sorry, I'm going to be off-topic a little bit.

I think both FutureOS and SymbOS are amazing projects. In both cases, the internal specs are wonderful, and it's obvious it's made by people that know really well their machine.
But, and this is my opinion, I keep thinking that an user interface with icons and such is asking too much for our Amstrad machines. I believe that the use of a mouse cursor as main input device is counter-productive. Yes, you probably have keyboard shortcuts -- I can also drive Microsoft Windows from the keyboard, but will I do that for real ? nope.
I would love to see something simpler, based on CP/M-like commands. On top of it, if you want to bring some interactivity with the user and that a commands-only workflow is not enough, then you could think about a very primitive text-based toolkit (Discology workflow in mind, with the menu system etc). There are amazing command-line interfaces on Linux that would make a great job on the Amstrad (Midnight Commander, Tilde, cmus, etc.).

I'm not saying YOU should do that. I'm not saying that I have the best solution either. Stay true with your project and your direction :) I'm just sharing my opinion, as a point of thinking and the expectations I get for an OS add-on/replacement for the Amstrad.


There is actually something very nice. Yes, we do have Z3Plus for the CPC. What is it? Something closer to CP/M and to Unix. The manual is pretty awesome, have a read if you like...
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 20:53, 13 January 22
But back to the original topic of this thread...


Eventually, five weeks late, but nevertheless an entry was presented!  :) :) :)
It's a MineSweeper Clone for FutureOS.  :) :) :)
The lovely game was created by Slartibartfast.  :) :) :)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 16:05, 10 February 22
The MineSweeper from Slartibartfast can now be found on my homepage (see downloads, see games there). You can use the SF2 mouse or the keyboard to control it.  :) :) :)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: Jean-Marie on 17:10, 10 February 22
Do you have some news about the sisters, by chance ?  :)


https://youtu.be/_AhSUYKX8AI
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: Prodatron on 00:06, 11 February 22
Quote from: GUNHED on 16:05, 10 February 22You can use the SF2 mouse or the keyboard to control it
Why not all of this, too?

https://www.cpcwiki.eu/index.php/FutureOS#Additional_HIDs_.28Hot_Plug_.26_Play_compatible.29

Doesn't make sense for me, if an OS is said to support >=15 HID devices, but if there is a new app, it can only use one or two.
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 13:40, 16 February 22
Quote from: Prodatron on 00:06, 11 February 22
Why not all of this, too?

https://www.cpcwiki.eu/index.php/FutureOS#Additional_HIDs_.28Hot_Plug_.26_Play_compatible.29 (https://www.cpcwiki.eu/index.php/FutureOS#Additional_HIDs_.28Hot_Plug_.26_Play_compatible.29)

Doesn't make sense for me, if an OS is said to support >=15 HID devices, but if there is a new app, it can only use one or two.
Right now its the majority of them being supported in the game actually.

Well, please ask the programmer, he can explain that to you. Probably he got real life things to do (like painting the basement) and still had no time to include anything else.

In FutureOS you can use the OS function R_ALM (read all mouses) to get mouse data (dela-x, delta-y. wheel and buttons). So if the 'CALL R_PS2' gets replaced by 'CALL R_ALM' all mice will be used. And of course both MultiPlay ports can be used for mice.  :)

Thanks for asking, please let me know if I can support you in any other way.  :)
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 13:49, 16 February 22
Quote from: Jean-Marie on 17:10, 10 February 22
Do you have some news about the sisters, by chance ?  :)
Thanks a lot for asking, that's just the motivation I need.  :) 
The game is actually pretty much done, but it has a bug which seldomly crashes the computer, so I have to fix this. I hope to be able to come back to Giana during this year. (The current version is on my homepage and has 10 levels).
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: eto on 16:21, 16 February 22
I've never recognised this game. Really impressive! Especially since it's using overscan.
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 18:44, 16 February 22
Thanks! The idea was to have 32 KB V-RAM with 50 fps.
Actually it's byproduct. The used engine is a 'cut down' 3D engine we wanted to use for our Role Play Game Gerelakos. But somehow real life happened and time got lost.
But since there is still some interest I hope to be able that we continue the project(s).
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: Prodatron on 22:10, 16 February 22
Quote from: GUNHED on 13:40, 16 February 22
Probably he got real life things to do (like painting the basement)
Strange answer  :-X

Quote from: GUNHED on 13:40, 16 February 22and still had no time to include anything else.In FutureOS you can use the OS function R_ALM (read all mouses) to get mouse data (dela-x, delta-y. wheel and buttons). So if the 'CALL R_PS2' gets replaced by 'CALL R_ALM' all mice will be used.
No, not really, this function is limited:

"Die OS Funktion R_ALM dient zur Abfrage der angeschlossenen proportionalen Mäuse. Es werden die PS/2 Maus des SYMBiFACE II, die USB Maus des SYMBiFACE III und die Mäuse des MultiPlay überprüft."

I was only speaking about all the other mouse pointer-like devices in your big list:

https://www.cpcwiki.eu/index.php/FutureOS#Additional_HIDs_.28Hot_Plug_.26_Play_compatible.29

-    Atari ST mouse adapter (Schneider Magazin)
-    AMX Mouse, AMX PS/2 Mouse Adapter
-    CPC-Mousepack (Reisware)
-    GEOS mouse (Commodore 64 device)
-    Imperium Solo
-    Dk'tronics Mouse Interface limited
-    Dk'tronics lightpen
-    Happy Computer Light Pen (DIY from German magazine)
-    Lindy Light Pen
-    Hegotron Grafpad II
-    Atari ST trackball adapter (Schneider Magazin)
-    Marconi trackball

Which OS calls can be used for them? They are not mentioned in your docs.
Title: Re: Official Announcement: FutureOS Programming Contest open - End: 2021.12.01
Post by: GUNHED on 18:50, 21 February 22

If this is a strange answer to you then I can explain that in detail. In contrast to you he is not a millionaire, therefore he has not 24/7 time to program on the CPC. So he does code something when he got time for it. Is that so hard to understand? More functions need more time. That's it.
You want him to use a GraphPad or a Lightpen for a Minesweeper game? Strange idea!

Your constant criticism is not helpful here and for sure not motivating people to code something for FutureOS. But maybe that's your intention.

Seriously, we're 50 years something now all together. Is this unserious bitching really needed?
I will not answer to such comments any longer.

BTW...

Quote from: Prodatron on 22:10, 16 February 22
-    AMX Mouse, AMX PS/2 Mouse Adapter
-    GEOS mouse (Commodore 64 device)
-    Imperium Solo
-    Dk'tronics Mouse Interface limited
-    Marconi trackball
Which OS calls can be used for them? They are not mentioned in your docs.
They are all supported. Just use the game and have fun! :)  Look for OS function 'H_JC'. I would wonder if you did't find it already.

Let us all come back not to serious, helpful and fun conversations please.
Back to the topic of this thread.  :)
Powered by SMFPacks Menu Editor Mod