- Home
- Discussion Forum
- AROS FORUMS
- Development General
- Aros default UI improvement: 2 - Better name for AHI Prefs
Aros default UI improvement: 2 - Better name for AHI Prefs
Last updated on 1 month ago
Poll: Are you in favor of renaming the preferences to something more usable and understandable for users?
Yes [6/10]60 %
No (If no please comment) [2/10]20 %
Indifferent [2/10]20 %
arosbeginnerMember
Posted 1 month agoAmigaos 3.3, in prefs "Sound"


1 user reacted to this post
olivier2222
OlafSchSenior Member
Posted 1 month agoI do not really understand what these discussions are about. There is certainly a kind of confusion with the different partly incompatible ABIs that existed in parallel. My view, as I already wrote, all distributions should use the official main branch in future for reasons I already wrote. Additional there is the discussion about changing of nightly. Of course nightlies are not perfect for end users but this is not they are for. They are test versions for developers to see if commits work and find errors. Not more not less. There should be official beginner distributions in future, perfect fitting for specific targets. Perfect fits are RPi there because of relative static hardware but I think VMs on PC could be also targets, like VMWare. That could also have standardized software and optimized icon sets. So that new users could first time see and test Aros without too many problems. Expecially configuring Aros on a PC certainly can be too much for start. And of course documentation explaining it in detail understandable even for someone without any Amiga experience.
Edited by OlafSch on 07-09-2026 05:51, 1 month ago
2 users reacted to this post
terminills, miker1264
terminillsMember
Posted 1 month ago@pixie -
That's not really your decision ... You are free to do what you want outside of the main project and support and design however you want. However it is no ones place to try and delegate what the main project does. Most of the people working on AROS are doing so in their spare time because they enjoy the project and someone coming in trying to force their views on the project is extremely counterproductive. If you want to create a theme and name every app whenever you want to name it within the license go right ahead. However aros.org is the parent to the AROS project and what happens there is not delegated by what some thread on AROSWorld determines.
I didn't knew someone expressing their opinion somehow would make it their decision, I mean, more than yours or mine for that matter. Those people working on their time can read, see if it's a good idea, or move along, no one is pressing a gun to their head.
Besides I don't understand why would someone thinks a thread on arosworld would delegate anything to aros... but at least developers can have a better understanding what their community thinks, and that would be a good thing everywhere else's... clearly, not to you.
Developers being forced on their views... please...
Anyone can have whatever opinion they want… however the project is designed a specific way and that won’t change based on a thread on a website.
My messages don’t come from a vacuum they come from other developers. Are they always the most pleasant worded no… but sometimes after giving people an example of how to achieve their goal without expecting anything from upstream and being told multiple times that’s not how things work… if we continue down the same path all it has the potential of doing is giving people false hope.
That's not really your decision ... You are free to do what you want outside of the main project and support and design however you want. However it is no ones place to try and delegate what the main project does. Most of the people working on AROS are doing so in their spare time because they enjoy the project and someone coming in trying to force their views on the project is extremely counterproductive. If you want to create a theme and name every app whenever you want to name it within the license go right ahead. However aros.org is the parent to the AROS project and what happens there is not delegated by what some thread on AROSWorld determines.
I didn't knew someone expressing their opinion somehow would make it their decision, I mean, more than yours or mine for that matter. Those people working on their time can read, see if it's a good idea, or move along, no one is pressing a gun to their head.
Besides I don't understand why would someone thinks a thread on arosworld would delegate anything to aros... but at least developers can have a better understanding what their community thinks, and that would be a good thing everywhere else's... clearly, not to you.
Developers being forced on their views... please...
arosbeginnerMember
Posted 1 month agoThanks for the clarification, I'll take it into account.
However, it wasn't my intention to tell developers what to do. My intention is to create discussion groups to propose improvements, which anyone can then read and, if they want, make a comment.
I think constructive discussion can bring value and serve as a starting point for discussions that engage the community. Many topics have emerged, including what aros is and isn't, what puts us off using it, and more.
I think these things are exciting for the community and make the system a little more ours and with more hope for the future.
However, it wasn't my intention to tell developers what to do. My intention is to create discussion groups to propose improvements, which anyone can then read and, if they want, make a comment.
I think constructive discussion can bring value and serve as a starting point for discussions that engage the community. Many topics have emerged, including what aros is and isn't, what puts us off using it, and more.
I think these things are exciting for the community and make the system a little more ours and with more hope for the future.
terminillsMember
Posted 1 month ago@arosbeginner - We're going off topic, but my opinion is that we need an AROS 1.0 or at least release versions.
Once version 1.0 is released, the official website should provide a basic distribution with a browser, shell commands (wget), and other minimal standard features automatically generated.
After that, there are the distributions.
That's not really your decision ... You are free to do what you want outside of the main project and support and design however you want. However it is no ones place to try and delegate what the main project does. Most of the people working on AROS are doing so in their spare time because they enjoy the project and someone coming in trying to force their views on the project is extremely counterproductive. If you want to create a theme and name every app whenever you want to name it within the license go right ahead. However aros.org is the parent to the AROS project and what happens there is not delegated by what some thread on AROSWorld determines.
3 users reacted to this post
Argo, deadwood, olivier2222
arosbeginnerMember
Posted 2 months agoWe're going off topic, but my opinion is that we need an AROS 1.0 or at least release versions.
Once version 1.0 is released, the official website should provide a basic distribution with a browser, shell commands (wget), and other minimal standard features automatically generated.
After that, there are the distributions.
Once version 1.0 is released, the official website should provide a basic distribution with a browser, shell commands (wget), and other minimal standard features automatically generated.
After that, there are the distributions.
2 users reacted to this post
OlafSch, miker1264
ntromansVeteran Member
Posted 2 months agoYou've got two extreames here; the nightlies are a bit too 'raw' for an inexperienced user whilst the distros are almost too complete a casual test of the sysetm (the're large and need a level of commitment in terms of downlaod time, installing an learning to use).
Neither of these are for someone who comes across AROS in an article, want to have a quick look to try it out. If it doesn't happen qucikly and easily for them, they'll probably loose interest just as fast,
So for these potential users have a streamlined distro with just the core apps (but clear information on how to progress to larger installations); quick to download to a live drive (USB/SD) and boot straight into. Launch into a brief system guide and maybe a configuration ustility to set up the look and feel right (from a menu of styles from classic through to full-flat minimalist) from first boot.
Is there any way network/wifi hardware detection could be automated as graphics hardware is? I suspect most of the questions on prefs is to do with setting those up. Of course the RPi and 68k distros have no issue here as they target specific hardware. Also have AHI set sensible defualt values when the hardware is detected.
Is it possible to make it such that a bootble USB drive could be produced simply by just copying the files to USB rather than writing an image to USB using Rufus etc., burining an iso or setting up a virtual machine, all of which woudl be a barrier to casual usage? I really like that fact for RPi you can just download the ssytem and copy staright to SD.
The PITA that is UEFI boot only machines is another barrier here; clear information prior to downloading on what machines will and will-not work would be helpful here.
Just a few musings...
Cheers,
Nigel.
Neither of these are for someone who comes across AROS in an article, want to have a quick look to try it out. If it doesn't happen qucikly and easily for them, they'll probably loose interest just as fast,
So for these potential users have a streamlined distro with just the core apps (but clear information on how to progress to larger installations); quick to download to a live drive (USB/SD) and boot straight into. Launch into a brief system guide and maybe a configuration ustility to set up the look and feel right (from a menu of styles from classic through to full-flat minimalist) from first boot.
Is there any way network/wifi hardware detection could be automated as graphics hardware is? I suspect most of the questions on prefs is to do with setting those up. Of course the RPi and 68k distros have no issue here as they target specific hardware. Also have AHI set sensible defualt values when the hardware is detected.
Is it possible to make it such that a bootble USB drive could be produced simply by just copying the files to USB rather than writing an image to USB using Rufus etc., burining an iso or setting up a virtual machine, all of which woudl be a barrier to casual usage? I really like that fact for RPi you can just download the ssytem and copy staright to SD.
The PITA that is UEFI boot only machines is another barrier here; clear information prior to downloading on what machines will and will-not work would be helpful here.
Just a few musings...
Cheers,
Nigel.
1 user reacted to this post
miker1264
terminillsMember
Posted 2 months ago@arosbeginner - Your distribution is only for 68k, but I use x64, and we're thinking of other riscv or arm users.
I'd like the official AROS website to have a single distribution, the same for all environments, with the same graphics and settings, and as a base for users.
This isn't currently the case unless you go back to the source, i.e., the development version.
Am I mistaken, and maybe there is?
The AROS Nightly should probably be considered closer to LFS than a distribution in its own right. It's the upstream base that distributions can build on, rather than something intended to provide one standardized end-user experience across every architecture.
What you could do instead is create an AROS distribution information site. Keep an updated inventory of what's included and available in the AROS Nightly builds, then provide proper reviews and package lists for each distribution.
From there, you could build a comparison grid showing each distribution against upstream AROS — which architectures it supports, what packages it includes, desktop configuration, drivers, development tools, additional software, and so on.
That would give users the "one place to see everything" you're looking for without requiring upstream AROS itself to become a distribution.
4 users reacted to this post
retrofaza, miker1264, deadwood, Telematix
OlafSchSenior Member
Posted 2 months ago@arosbeginner - Your distribution is only for 68k, but I use x64, and we're thinking of other riscv or arm users.
I'd like the official AROS website to have a single distribution, the same for all environments, with the same graphics and settings, and as a base for users.
This isn't currently the case unless you go back to the source, i.e., the development version.
Am I mistaken, and maybe there is?
indeed there is no set of base versions identical for all platforms except the development versions (nightly). But as I explained I would more advise that for every platform there is a standardized, static and tested base version or distribution created and only from time to time updated. AROS is not a static platform and it can be that the ARM Rpi 3 version and the 68k version have a problem because of a commit, that is solved again 1-2 days later. But experience should not depend if you are lucky to download at a good day.
Also as I explained as a beginner I would of course expect some basic stuff like browser that would blow up the nightly and make compilation time much longer.
So my advice define rules and collect ideas how a beginner friendly distribution could be look and what software should be in and then this could be done by people owning the hardware. There should be both 32bit and 64bit versions. On one page there should be links where to download it.
Edited by OlafSch on 03-09-2026 10:36, 2 months ago
deadwoodAROS Dev
Posted 2 months ago@arosbeginner
Make AROS Nightly the basic distribution for every user
Be aware that this is directly against project's vision.
https://aros.sourceforge.io/download.html
The nightly builds are only meant for developers and testers. The nightly builds are not configured to be easily used, are not always stable, and they are missing most of the applications essential to a regular user experience.
https://aros.sourceforge.io/documentation/faq.html#what-are-the-nightly-builds
What are the nightly builds?
AROS nightly builds are development builds produced from the current state of the AROS source tree. They are primarily intended for developers, testers, and people who want to follow and experiment with the latest developments in AROS. As such, they should be regarded as a moving development snapshot rather than a polished, end-user-oriented release
3 users reacted to this post
retrofaza, OlafSch, terminills
arosbeginnerMember
Posted 2 months agoYour distribution is only for 68k, but I use x64, and we're thinking of other riscv or arm users.
I'd like the official AROS website to have a single distribution, the same for all environments, with the same graphics and settings, and as a base for users.
This isn't currently the case unless you go back to the source, i.e., the development version.
Am I mistaken, and maybe there is?
I'd like the official AROS website to have a single distribution, the same for all environments, with the same graphics and settings, and as a base for users.
This isn't currently the case unless you go back to the source, i.e., the development version.
Am I mistaken, and maybe there is?
OlafSchSenior Member
Posted 2 months agoI am also for to have something optimized for beginner to make it a easy starting point but I am not sure if nightly are the right place. As a beginner I would for example expect a browser to be preinstalled. That are pretty big applications and a nightly is recompiled every day.
I know for example that a browser was part of contrib on 68k long ago and is removed because it made compilation very long. As far as I know this happened to all contrib packages.
Second problem, nightly are to test commits. These can lead to unforeseen effects. For example multiview on newest aros 68k nightlies had a bug I reported. That was then corrected. Assuming this would have been the version someone downloads he or she would think aros is buggy. That would not be a good idea in my view.
Nightlies are for testing and should stay that. For beginners there should be a static tested and optimized package, that includes a basic set of applications.
I am one of the aros distribution creators and work with aros already more than 10 years so I think I have a little experience there.
I know for example that a browser was part of contrib on 68k long ago and is removed because it made compilation very long. As far as I know this happened to all contrib packages.
Second problem, nightly are to test commits. These can lead to unforeseen effects. For example multiview on newest aros 68k nightlies had a bug I reported. That was then corrected. Assuming this would have been the version someone downloads he or she would think aros is buggy. That would not be a good idea in my view.
Nightlies are for testing and should stay that. For beginners there should be a static tested and optimized package, that includes a basic set of applications.
I am one of the aros distribution creators and work with aros already more than 10 years so I think I have a little experience there.
Edited by OlafSch on 03-09-2026 09:46, 2 months ago
arosbeginnerMember
Posted 2 months agoI'm a beginner user, coming from Windows. But instead of shutting down the system and deeming it useless, I'm here to constructively make suggestions for UI improvements.
I believe an open mind is needed, and as someone has already said, if all other operating systems have converged on certain UI dynamics, I believe there's a reason.
I make suggestions piece by piece, and I'd like to avoid relying on personal tastes, as stated in the AROS wiki, but instead make small, concrete improvements.
Make AROS Nightly the basic distribution for every user, while other distributions can customize and add software and options.
I'm also in favor of simplification, so for example, I'd leave fewer themes in Nightly but well-made and without gross defects. But I'll make the rest of the suggestions over time.
I'd like to achieve one small result at a time and enter a historic community with due respect.
I believe an open mind is needed, and as someone has already said, if all other operating systems have converged on certain UI dynamics, I believe there's a reason.
I make suggestions piece by piece, and I'd like to avoid relying on personal tastes, as stated in the AROS wiki, but instead make small, concrete improvements.
Make AROS Nightly the basic distribution for every user, while other distributions can customize and add software and options.
I'm also in favor of simplification, so for example, I'd leave fewer themes in Nightly but well-made and without gross defects. But I'll make the rest of the suggestions over time.
I'd like to achieve one small result at a time and enter a historic community with due respect.
2 users reacted to this post
coffeecat, aha
coffeecatMember
Posted 2 months ago@deadwood - Thanks. In those prior instances, were you trying our a nightly build from www.aros.org or a distribution (Icaros?)? Your comments on lack of uniformity and software are suggesting nighly build.
With regards to package manager - there is AADT tool in contrib package. It's a front end for downloading from AROS Archives. It's not a package manager in sense of linux etc.
I tried:
- AROS in AmigaForever
- Icaros
- AROS from Nightly
AROS One was actually the best for me (but then I figured that for dev work it's actually better to use the main line
I will check out AADT - sounds like exactly the same thing I started working on - a frontend to search and install software from AROS Archives. Which, btw, says something about me or the system: how do I know that if I am new to the platform?
deadwoodAROS Dev
Posted 2 months agoThanks. In those prior instances, were you trying our a nightly build from www.aros.org or a distribution (Icaros?)? Your comments on lack of uniformity and software are suggesting nighly build.
With regards to package manager - there is AADT tool in contrib package. It's a front end for downloading from AROS Archives. It's not a package manager in sense of linux etc.
With regards to package manager - there is AADT tool in contrib package. It's a front end for downloading from AROS Archives. It's not a package manager in sense of linux etc.
1 user reacted to this post
coffeecat
coffeecatMember
Posted 2 months ago@deadwood -@coffeecat
And the real wall is not Prefs. It's ABIv0 / ABIv11 / Icaros / AROS One / Tiny AROS / AEROS, times 32/64 bit, times x86/68k/RPi/RISC-V, with branches that aren't even binary compatible. A newcomer fails at the download page. I tried and dropped AROS 3 times before finally settling in.
Do you remember what exactly made you drop AROS each of the 3 times and what made you settle in the 4th time?
I don't remember them chronologically, but it was a mixture of:
- not understanding how I should treat AROS: as AmigaOS3.x on x86 or a modern take on the future of Amiga.
- if it's the AmigaOS3.x on PC - it lacked the software I was used to; if modern Amiga - it lacked software I'd consider using. My memory may be failing me, but at that time there was no OWB
- looks - not my alley in general, but also the fact that basically looks were/are not uniform between apps
- missing the understanding of what I can do with the system, what I can change
- where to look for the software - no starting point in the system (I actually started writing a package manager; is there already one?)
What made me come back? Ability to write software and contribute, and the recent interview with Mike from Amiga/Cloanto and AmigaBill. I still have a soft spot for the Amiga, but I don't want to just reminisce about the games I played in 1995. I loved pieces of that interview, but I have reservations about it as a whole. My personal take is that PPC is a dead end; 68k is actually more interesting, but too much preservation is going on there* despite, imho, very promising things like PiStorm. So, for me, AROS is the most approachable Amiga I can contribute to, and I feel like I am working in a relatively modern environment. E.g., having SDL3 and Rust means I can basically tell any of my colleagues to look at the platform, and there's a chance they will take it seriously, even if they have never had an Amiga
*) I have a different look at this from a hobby perspective
Edited by coffeecat on 03-09-2026 08:37, 2 months ago
OlafSchSenior Member
Posted 2 months ago"And the real wall is not Prefs. It's ABIv0 / ABIv11 / Icaros / AROS One / Tiny AROS / AEROS, times 32/64 bit, times x86/68k/RPi/RISC-V, with branches that aren't even binary compatible. A newcomer fails at the download page. I tried and dropped AROS 3 times before finally settling in."
Yes this is indeed confusing for someone not knowing about it. It is also hard to explain. There should be a WIKI page or similar only targetting end users and only with links to (active) end user aros distributions. Perhaps with short explanations about the idea behind the distribution. And Links to 32bit and 64bit if available. The nightly page should not be linked because it is only irritating and always the danger people download something not compatible like downloading 64bit nightly and 32bit contrib and then wondering it not works
Yes this is indeed confusing for someone not knowing about it. It is also hard to explain. There should be a WIKI page or similar only targetting end users and only with links to (active) end user aros distributions. Perhaps with short explanations about the idea behind the distribution. And Links to 32bit and 64bit if available. The nightly page should not be linked because it is only irritating and always the danger people download something not compatible like downloading 64bit nightly and 32bit contrib and then wondering it not works
OlafSchSenior Member
Posted 2 months agofor a beginner:
I think regarding preferences nobody likes them. On Windows people only search for preferences when they have a problem. So people have to know what and where to change to solve the problem. That are typical perhaps adapt time and date, setup of network and wireless, change screen resolution. Then if all works change background, theme, perhaps icon set. There should be some sort of beginner distribution which includes a minimal set of applications including expecially a browser, so people can start with it. This distribution should be well documented both local (PDF) and Online.
Installation should be as easy as possible and special problems depending on platform should be documented.
Different distributions normally share the preferences so this part would be valid for all platforms. For the rest every distribution needs a special documentation. But there should be a standard distribution beginners could easy start with. If somebody is getting more interested it is still possible to test other distributions too. I think one issue always disputed about Aros was there are lots of different distributions with different configurations and software but no standard environment like on MorphOS or AmigaOS.
I think regarding preferences nobody likes them. On Windows people only search for preferences when they have a problem. So people have to know what and where to change to solve the problem. That are typical perhaps adapt time and date, setup of network and wireless, change screen resolution. Then if all works change background, theme, perhaps icon set. There should be some sort of beginner distribution which includes a minimal set of applications including expecially a browser, so people can start with it. This distribution should be well documented both local (PDF) and Online.
Installation should be as easy as possible and special problems depending on platform should be documented.
Different distributions normally share the preferences so this part would be valid for all platforms. For the rest every distribution needs a special documentation. But there should be a standard distribution beginners could easy start with. If somebody is getting more interested it is still possible to test other distributions too. I think one issue always disputed about Aros was there are lots of different distributions with different configurations and software but no standard environment like on MorphOS or AmigaOS.
Edited by OlafSch on 03-09-2026 07:58, 2 months ago
deadwoodAROS Dev
Posted 2 months ago@coffeecat
And the real wall is not Prefs. It's ABIv0 / ABIv11 / Icaros / AROS One / Tiny AROS / AEROS, times 32/64 bit, times x86/68k/RPi/RISC-V, with branches that aren't even binary compatible. A newcomer fails at the download page. I tried and dropped AROS 3 times before finally settling in.
Do you remember what exactly made you drop AROS each of the 3 times and what made you settle in the 4th time?
You can view all discussion threads in this forum.
You cannot start a new discussion thread in this forum.
You cannot reply in this discussion thread.
You cannot edit the poll in this discussion thread.
You cannot vote on the poll in this discussion thread.
You cannot upload attachments in this forum.
You cannot download attachments in this forum.
You cannot start a new discussion thread in this forum.
You cannot reply in this discussion thread.
You cannot edit the poll in this discussion thread.
You cannot vote on the poll in this discussion thread.
You cannot upload attachments in this forum.
You cannot download attachments in this forum.
Moderator: Administrator, Moderators
Users who participated in discussion: amigamia, terminills, deadwood, Argo, AMIGASYSTEM, pixie, ntromans, OlafSch, arosbeginner, r-tea, x-vision, coffeecat
