Development Plan

[Amiwell]

I will worry about publishing TinyArosX , In the past I used Pascal Papara aeros but then it became obsolete, so your new project does not scare me even if I have always preferred the native version, good work Deadwood and thanks for everything, I use every day as a main system for years

[OlafS3]

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!

Thank you very much. I think there a good opportunity to create something new and interesting based on Linux, AxRuntime and Scalos as desktop. I am already looking forward to it. BTW cool that also ABI0 aros apps will run on it. So we finally really will be able to mix Linux and any aros app or component on one platform. That (together with Scalos) will certainly make some cool things possible...

[OlafS3]

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

I already test Scalos on WinHosted and it looks pretty fast. I do not know what you mean. BTW there are a lot of preferences that influence both behavior and speed. And "less compatibility" than Wanderer? I do not understand.

[Amiwell]

Work in progress.......

[OlafS3]

@salvo

you are ahead of the time 

[Amiwell]

 

long live Aros

[AMIGASYSTEM]

I already test Scalos on WinHosted and it looks pretty fast. I do not know what you mean. BTW there are a lot of preferences that influence both behavior and speed. And "less compatibility" than Wanderer? I do not understand.

To understand you have to make comparisons and test the software one by one, as soon as possible I will try again to test Scalos with the new deadwood updates, all the anomalies, incomatibilities software will be listed.

The slowness is about the delay of Icons shown in windows, a problem you also experience on Scalos 68k.

[deadwood]

Thank you all for your support and encouragement.

To address the question of Scalos. This is not based on my own experience but mostly on comments from Olaf. As far as I understand Scalos is more feature-rich than Wanderer and usability is key for this effort. I can fix simple bugs, but adding new functionality is time consuming. That is not to say that Wanderer will not be ported. It's rather that I think it makes sense to port Scalos as more usable first and focus on adding missing pieces before moving forward.

If you however disagree and think that Wanderer can be more usable, I'd like to know your arguments, examples, comparisons (please start a separate thread in such case) to arrive at best possible decision.

[deadwood]

BTW cool that also ABI0 aros apps will run on it. So we finally really will be able to mix Linux and any aros app or component on one platform.

One thing that is also interesting is that on ABIv0 you have JanusUAE, which makes m68k Intuition windows appear as AROS Intuition windows. On the other hand, AxRuntime makes AROS Intutiion windows appear as native X windows. I wonder if this will work to eventually "forward" m68k application to work "as native" Linux applications.

[OlafS3]

Thank you all for your support and encouragement.

To address the question of Scalos. This is not based on my own experience but mostly on comments from Olaf. As far as I understand Scalos is more feature-rich than Wanderer and usability is key for this effort. I can fix simple bugs, but adding new functionality is time consuming. That is not to say that Wanderer will not be ported. It's rather that I think it makes sense to port Scalos as more usable first and focus on adding missing pieces before moving forward.

If you however disagree and think that Wanderer can be more usable, I'd like to know your arguments, examples, comparisons (please start a separate thread in such case) to arrive at best possible decision.

Sorry to comment that... with all respect Amigasystem is sometimes "special" with his attitudes. He also talked against Magellan despite Magellan far more powerfull. Or against on Aros 68k mixing Aros and Amiga software. I have no problem there with different attitudes but it starts to be silly. For me personal a limited desktop system like Wanderer is no option. I want to attract people, people from current NG camp (AmigaOS or MorphOS) or even from outside. If only Wanderer is available I will wait for Scalos to do a distribution. Unfortunately for him I use Scalos currently on both X86 and 68k so if he starts to promote Wanderer I will talk against that. The funny thing for a purist like Amigasystem (Aros purist) the idea to mix different platforms is not interesting anyway. Desktop defines user experience. I think one of the main reason for Aros being a long time not taken seriously was the limited desktop (Wanderer).

Features from Scalos page:
100% Workbench replacement - All functions work like the original Workbench ones
Undo and Redo for most window and icon operation
64bit arithmetic - Correctly recognises harddisks over 4GB
Fully multitasking - Every window has its own task. While loading icons, any window function (e.g. Drag&Drop) is available
Icon imagetypes - All types are supported such as backfill or complement. Configurable surrounding iconborder
Icon datatype system - NewIcon datatype included. Icon support also visually highlights files which are soft-links in the file system.
Icon dragging is more stable - And far less flickery on graphics cards. Whilst dragging, icons are displayed with text and they become transparent over anything where they can be dropped! MUI-alike transparency on low colour screens. Real transparency if running at 15-bit or greater.
Cybergraphics and Picasso96 24bit color support
Window patterns - Unlimited and easily configurable via tooltypes
Optimised backgroundpatterns routine - Patterns can be tiled, centred or even scaled to fit into the windows. With the use of render.library, you get full control over the dithering and pen usage of your patterns
Live updating window scrolling - Supports middle mouse button panning too!
Drawer windows can be iconified
Menu preferences - You can enjoy fully configurable menus (includes ToolsDaemon and Parm import), including support for context-sensitive Popup menus
Application Interface (API) - Anything is possible from outside the program itself
Custom preference programs - For both palette and patterns. A pen-locker is not required any more
Nearly all Workbench preferences are used
Installation is very easy
Supports PNG icons with alpha channel and real transparency
Displays OS3.5 GlowIcons even on OS3.1 machines
Scalable icons
Thumbnail preview icons for images - Thumbnails can be permanently saved in icons
Completely confgurable, filetype-specific user-definable popup menus and tooltips
Plugin system to exchange or add features - It enhances the Workbench and makes it more configurable
Filetype plugins to display filetype-specific information. - Currently, EXIF information viewer for JPEG images is included.
Iconborders - Nice looking, Icontext variations (normal, shadowed, outlined)
Screentitle text - Shows what you want, how you want
Plugin included for 100% support of OS3.9 Workbench features
Plugin included for AREXX API compatible to OS3.9 Workbench
Online update with updater.module

[OlafS3]

BTW cool that also ABI0 aros apps will run on it. So we finally really will be able to mix Linux and any aros app or component on one platform.

One thing that is also interesting is that on ABIv0 you have JanusUAE, which makes m68k Intuition windows appear as AROS Intuition windows. On the other hand, AxRuntime makes AROS Intutiion windows appear as native X windows. I wonder if this will work to eventually "forward" m68k application to work "as native" Linux applications.

sounds cool 

[OlafS3]

Thank you all for your support and encouragement.

To address the question of Scalos. This is not based on my own experience but mostly on comments from Olaf. As far as I understand Scalos is more feature-rich than Wanderer and usability is key for this effort. I can fix simple bugs, but adding new functionality is time consuming. That is not to say that Wanderer will not be ported. It's rather that I think it makes sense to port Scalos as more usable first and focus on adding missing pieces before moving forward.

If you however disagree and think that Wanderer can be more usable, I'd like to know your arguments, examples, comparisons (please start a separate thread in such case) to arrive at best possible decision.

There is no need to add "new features". Scalos includes already tons of preferences and new features compared to 3.1 and Wanderer is functionality wise more or less on the same level. There is nothing wrong to me to have different tastes and prefer a simple and limited 3.1 level desktop but I do not think that this would attract users to it. If some bugs are identified and fixed it would be perfect. There is no need to create a new scalos version with new added features.

[AMIGASYSTEM]

OlafS3 sorry I never speak as a Fan or a Fan, I try to be as realistic as possible.

That Magelan or Scalos have a few more features does not mean they work better.

I usually look at functionality and love maximum compatibility on a system that needs to be direct and not leaning on third-party applications.

Try to configure Scalos and then compare it with a Wandere based AROS, of course the comparison should not be done with a night but with well configured AROs systems like IcarOS or my AROS One which you have probably never tried ! Try it and then maybe find out also with Wanderer you can do what you do with Magelan or Scalos but at a faster speed, in addition to using a real Amiga clone

[OlafS3]

OlafS3 sorry I never speak as a Fan or a Fan, I try to be as realistic as possible.

That Magelan or Scalos have a few more features does not mean they work better.

I usually look at functionality and love maximum compatibility on a system that needs to be direct and not leaning on third-party applications.

Try to configure Scalos and then compare it with a Wandere based AROS, of course the comparison should not be done with a night but with well configured AROs systems like IcarOS or my AROS One which you have probably never tried ! Try it and then maybe find out also with Wanderer you can do what you do with Magelan or Scalos but at a faster speed, in addition to using a real Amiga clone

Ha Ha

Icaros Desktop IS Magellan for a long time. Do your job

from icaros desktop site:
I've made some little changes to Magellan that should make us Icaros users happier. First of all, I found on DOpus 5 website a link to a newer version (a nightly build of v5.92 from 2016), which should be more polished and advanced than the one (v5.91) currently included in Icaros Desktop. I'm testing it right now without pain, so it should be good for 'production'. This was, indeed, a good time for two little changes I was thinking about for a while.

I do not care that you prefer your choice, you can do what you like to but do not try to make the other options look bad to promote your favorite. Because then I will heavily hold against it. It is of course Deadwoods decision what he supports. If it is Wanderer based on your descriptions then be it. Then I have the advantage to have more time to spend on other things  . I will not do anything based on Wanderer. It makes no sense to me. Again I currently test Scalos on Win Hosted X86. Icons are shown very fast. And even if it would be a little slower compared to wanderer, it includes tons of options to configure it how f.e. icons are shown. Wanderer has nothing to offer in comparation.

[cdimauro]

Then why don't you make a side-by-side comparison of Wanderer and Scalos, to show the pros and cons / issues of each one?


Engineers like DATA. FACTs. In order to make an evaluation.