Development Plan

[AMIGASYSTEM]

The native 32-bit AROS (ABIv0) will continue being maintained by me as described in the "long term horizon" section.

Thank you deadwood for the confirmation, otherwise there would be no point in carrying on AROS One, thanks to you AROS One has grown notevlly, work much aprreciated by many users.

[Amiwell]

The native 32-bit AROS (ABIv0) will continue being maintained by me as described in the "long term horizon" section.

I don't plan on working on 64-bit native version. I know in the past Kalamatee worked a lot on 64-bit native version. Neil also seems interested in it.

Yes when abiv0 will be aligned to abiv11 there will be the possibility to use some Hollywood plugins I plan to collaborate for some software thanks deadwood

[deadwood]

Hi all,

With availability of beta of Intuition (window manager), I now consider the POC phase complete. This means I will start moving to second objective - a refreshed release of ABIv0. I will inform you separately what will be the target freshness of common codebase to which we well be upgrading.

1) Proof of concept of Scalos providing a Linux desktop environment [DONE]
2) Release new version of ABIv0 refreshed to newer common codebase [IN PROGRESS]
3) Enable most functionalities of Scalos under Linux

The long term horizon remains unchanged:

"On a longer horizon, there will be a lot of work related to ABIv0 and AxRuntime. I want to update ABIv0 to be based on latest ABIv11 source code. This will be an enabler to having a version of AxRuntime that is capable of running ABIv0 32-bit programs on top of Linux.

Once all these things are in place, we will have a Linux-native desktop (Scalos) and ability to run AROS ABIv0 programs (32-bit), AROS ABIv11 programs (64-bit) and AxRuntime-recompiled programs (64-bit). This way existing Distros could be re-created using Linux as a base without loosing existing functionality for users, enabling a gradual migration from 32-bit to 64-bit."

[AMIGASYSTEM]

Thanks deadwood, you are doing a great and great job, I am looking forward to the ABIv0 upgrade.

Regarding the Linux base, as already mentioned not being a linux expert, I would not feel comfortable, and I would not be able to offer the support to the users in case of problems with the Operating System.

[Amiwell]

@Deadwood thank you attemp new release of abiv0

[Amiwell]

Deadwood I told Andreas Falkenhahn about the new release of aros abiv0 and its hollywood plugins he replied like this

"Show me some code on how to manually initialize and deinitialize the C++17 (or better)
runtime in a project linked with -nostartfiles and loaded via LoadSeg(). C++ exception
handling must also work in that project! If that is possible on AROS, I can provide
builds of the plugins..."

Thank you in advance

[deadwood]

I'll take that into account

[Amiwell]

ok thank you

All Best Deadwood

[Amiwell]

Deadwood Alfred Faust could bring a software on AROS only that there is a problem with the interface midi devices usb you should compile the driver that is in native assembly for 68k you could do something the software is an advanced midi sequencer

alfred wrote:

If you can have a look at the 68k-camd-driver (the bridge between Poseidons camdusbmidi.class and the CAMD-System)
I attach it here.

NB.: here is the text at the top of the source to the camdusbmidi.class
/*
 *----------------------------------------------------------------------------
 *                         camdusbmidi class for poseidon
 *----------------------------------------------------------------------------
 *                   By Chris Hodges <chrisly@platon42.de>
 */

/* TODO: Somebody needs to port the assembly 68k camd driver to something that is used under AROS! */

[deadwood]

It's unlikely I will look into that.

[Amiwell]

okay thanks

[deadwood]

Hi all,

With the release of ABIv0 20201110-2 its now time to refresh development plan for next couple of months.

Previous plan:
1) Proof of concept of Scalos providing a Linux desktop environment [DONE]
2) Release new version of ABIv0 refreshed to newer common codebase [DONE]
3) Enable most functionalities of Scalos under Linux

Current plan:
1) Synchronize code bases between repositories and release new version of ABIv11
2) Release first stable version of IntuitionWM
3) Release new version of ABIv0 refreshed to newer common codebase

As you can see the work on Scalos under Linux has been pushed out of current planning. There are two reasons:
1) At this point I'm not sure myself if I'd personally use Scalos under Linux instead of native Linux desktop manager. The plan is first to start using IntuitionWM and then decide
2) There is an uptick of activity in AROS which means getting ABIv0 to the same code level as ABIv11 is becoming more urgent. Not having these code bases synchronized is going to generate more cost down the road.

The long term horizon remains unchanged, however there are notable additions:

"On a longer horizon, there will be a lot of work related to ABIv0 and AxRuntime. I want to update ABIv0 to be based on latest ABIv11 source code. This will be an enabler to:
1) develop a version of AxRuntime that is capable of running ABIv0 32-bit programs on top of Linux and
2) develop an emulator that will allow running AROS 32-bit programs under 64-bit AROS.

Once all these things are in place, we will have a Linux-native desktop (Scalos) and ability to run AROS ABIv0 programs (32-bit), AROS ABIv11 programs (64-bit) and AxRuntime-recompiled programs (64-bit). This way existing Distros could be re-created using Linux as a base without loosing existing functionality for users, enabling a gradual migration from 32-bit to 64-bit.

For people preferring native AROS we will also have ability to use ~80% of the existing software base on 64-bit AROS, which then is an enabler to transition to 64-bit base system."

[OlafS3]

@Deadwood

thanks

we all appreciate what you are doing

[AMIGASYSTEM]

Thanks Deadwood I am glad that the native mode and ABIv0, will have substantial updates

[paolone]

Once all these things are in place, we will have a Linux-native desktop (Scalos) and ability to run AROS ABIv0 programs (32-bit), AROS ABIv11 programs (64-bit) and AxRuntime-recompiled programs (64-bit). This way existing Distros could be re-created using Linux as a base without loosing existing functionality for users, enabling a gradual migration from 32-bit to 64-bit. For people preferring native AROS we will also have ability to use ~80% of the existing software base on 64-bit AROS, which then is an enabler to transition to 64-bit base system."

I like this plan, although I am not sue I'll have the skills to port Icaros to Linux.