Development Plan

[AMIGASYSTEM]

@deadwood

Discussing with ALB42 on AmiTube we have found that on AROS ABIv1, then AROS 68k and AROS ABIv11 there is a problem on the texts obtained after a search with AmiTube, in practice the texts are corrupted, to fix them you have to enlarge the GUI.

I specify that on AROS x86 ABIv0 everything works perfectly and there is no corruption on the text!

I attach a link to the discussion where ALB42 has attached a video that shows the artifacts on the text, while I attach a video on AROS One x86 where there is no corruption, the text is perfect.

http://eab.abime.net/showthread.php?t=109252&page=2

[deadwood]

Thanks, bug report created: https://github.com/deadw00d/AROS/issues/61

[deadwood]

Hi,

As indicated earlier, I made plans for next milestones - you can find them below. They are listed in an order I plan working on them.

1) Release new version of AxRuntime based on recently releases ABIv11
2) Migrate ABIv0 from GCC 4.2.4 to GCC 6.3.0. This will provide better tooling for 3rd party developers.
3) Release new version of ABIv0 refreshed to common codebase from around 2019-03-01 (Today we are on 2018-04-15)

Some time has passed since I decided on these milestones and I figured out an update is in order.

Over last weeks I've been focused on working on point 1) and doing some extended testing with @magorium and @muibase. I'm pleased to report that all experiments that I had planned in are now finished with success and I'm moving to phase of clean up and preparation for release. If all goes well the new release of AxRuntime should be available by end of this month. This means starting from April I will turn my focus on ABIv0 and having it catch up with features of mainline development.

[AMIGASYSTEM]

Ok thanks deadwood, I will wait for April to update and distribute the new version of AROS One x86

[Amiwell]

ok deadwood thank you

[AMIGASYSTEM]

@deadwood

Why on Wanderer is it not possible to rename a volume?

To change a volume name you have to do it from the Shell with the command relabel or from HDToolbox!

[deadwood]

I don't know, probably a missing feature.

[AMIGASYSTEM]

Yes it is a problem of Wander, but also of Scalos, as you can see from the screenshot the two systems give a different error.
No problem for Magellan, but this is normal since Magellan completely replaces "the Workbench".

[deadwood]

Hi,

As indicated earlier, I made plans for next milestones - you can find them below. They are listed in an order I plan working on them.

1) Release new version of AxRuntime based on recently releases ABIv11 - DONE
2) Migrate ABIv0 from GCC 4.2.4 to GCC 6.3.0. This will provide better tooling for 3rd party developers.
3) Release new version of ABIv0 refreshed to common codebase from around 2019-03-01 (Today we are on 2018-04-15)

Hi,

Today a new release of AxRuntime has been made. With this, I will take a few days off and then move to ABIv0 topics, starting with upgrade of GCC.

[AMIGASYSTEM]

Thank you for your work !

[Amiwell]

thank you deadwood

[deadwood]

Hi,

As indicated earlier, I made plans for next milestones - you can find them below. They are listed in an order I plan working on them.

1) Release new version of AxRuntime based on recently releases ABIv11 - DONE
2) Migrate ABIv0 from GCC 4.2.4 to GCC 6.3.0. This will provide better tooling for 3rd party developers. - DONE
3) Release new version of ABIv0 refreshed to common codebase from around 2019-03-01 (Today we are on 2018-04-15)

Hi All,

Migration is now done and release made. See this thread: https://ae.amigalife.org/index.php?topic=909.msg10802#msg10802

[deadwood]

Hi,

Being 2/3 done on my January list, I wanted to give you a bit more info on two concrete things I'm planning and a bit longer-term horizon.

Concrete planned items:
1) Release new version of ABIv0 refreshed to common codebase from around 2019-03-01 (Today we are on 2018-04-23)
2) Port Scalos to AxRuntime so that it can become Linux desktop manager

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.

It's a lot of work. If you are interested in helping out in any of these topics or just writing code for AROS, please let me know!

[Amiwell]

yes Deadwood I understand as soon as it will be released I will try Axruntime with the new scalos desktop is interesting as evolution, I don't know if I will be able to create a distribution but I will try

[AMIGASYSTEM]

Hi,

2) Port Scalos to AxRuntime so that it can become Linux desktop manager

If there have been no new updates on Scalos, i would say that compared to Wandere at less speed and less compatibility, if on the other hand there have been updates that improve Scalos, then there will also be AROS One Scalos x86 version.

Thank you epr the much work you do for the community