The situation

[miker1264]

Actually I just had a tought about the "views". It should be placed to the left of the blue "parent" button. Maybe a small round white button with two opposing black tringles inside. Wanderer knows which view mode is current. When the user clicks the button the view changes. I really like that idea!!

Zune (and Amiga in general) has had a very useful gadget for this kind of jobs, Cycle Menus: just add one in the interface and you would end up with a nice alternative to your windows-ish button menu. Something like this (see attachment).[size=78%] [/size]

paolone

Thanks for the idea. I did think about a cycle button but it's too big and not consistent with the glass "parent" button. I didn't intend to use a Windos-ish view menu button just that such a button is common. (That's funny though!). I was thinking of a simple glass button with an arrow like the arrow button shown in this sample. But instead of black it would be white or grey.

Although kalamatee is working on a revised Wanderer program maybe it would be good to update the current version incrementally to improve performance and add functionality. Maybe start by fixing the title and adjusting how it deals with icons and adding a green button. Why green? Well we already have a blue button and green is somewhat complimentary. A red button doesn't seem right for some reason.

Adding a button and fixing a title might be something a novice like me could handle. But then again it may end in disaster! ;-)

Yannick,
You might consider joining the Slack Channel where most of the AROS developers are. Currently there is a conversation about Scalos and the new build system. It's not that there's no ongoing development. It's just that you're listening in the wrong place. Your input and insight would be very helpful.

[Yannick]

And how do I join a Slack channel talking about Aros when there is no indication anywhere about it's existence?
And what is coming out of the discussions there?
What is communicated to the outside world? highlights from November 2016 on AROS official page => 3 years without any news?

[walkero]

That is a great discussion here. As an Amiga user for a long time, mainly of AmigaOS 4, I like the idea and the usage of Aros as well. Actually, in Aros there is a tiny contribution from my side, which is the Greek language and keyboards. I wish I could do more.

If you allow me, I would like to add my opinion on the discussion. First of all, I agree that competing Windows, MacOS and Linux is a no go for Icaros, but I like the idea of running it hosted. This is something that makes the running process even faster and great.

I believe that Aros could be a great OS for SoC ARM systems, especially because there are no equivalent Operating Systems there, especially if this could be really fast. Of course there is Debian and other Linux distribution, but I believe that Aros can beat them on speed.

Secondly, I would like to say that Aros needs more users as much as it needs more developers. Last weekend I was in Neuss of Germany at Amiga34 event. It was unfortunate that Aros was nowhere. Not a single machine was running it, not a single person talked about it. And that happens almost to every event. In a few days their is going to be Amiwest 2019. Are there going to be any presentations/updates on where Aros is and where it goes? Speak about how much active it is?

Aros needs to be communicated to people. More users will result more people talking about it, more people using it and it's software, less developers leaving it.

Thank you for your patience with my message.

[miker1264]

And how do I join a Slack channel talking about Aros when there is no indication anywhere about it's existence?
And what is coming out of the discussions there?
What is communicated to the outside world? highlights from November 2016 on AROS official page => 3 years without any news?

They will need your email address. You can send it in a message. Then someone there can invite you to join.

If you really want to know about the Scalos Dicussion the basic understanding was that it currently does not work well for 32bit and it doesn't compile for 64bit. But the sources are maintained by the original author. Much of the discussion on a daily basis deals with the current build system, the new build system that is being developed now and programs that work or don't work with AROS 64bit.

If you are interested message me here with your email address and I'll forward it to one of the maintainers of the Slack Channel. When I first heard about it my response was similar. I said "Slack What? What's that? How do I join." One of the developers from the Amiga OS4 channel invited me. But AROS is there as well.

I'll voice your concern about a needed update on Aros-Exec to see if one of the main developers will have time to give an update.


 

[Amiwell]

yes I didn't understand why to abandon abiv0 when there is no stable replacement project

[nikos]

yes I didn't understand why to abandon abiv0 when there is no stable replacement project

It was a mistake. The whole situation got kind of out of control. Deadwood backported commits to abi v.0 but some did not like that. Some ment that slowed down development of abi v.1 and wanted it abonded. It finaly  kind of happend but as you say Salvo. It should at least be a stable brach to replace it. Abi v.1 is still not a stable branch. If to reach its goal it must be broken again. Maybe many times. All software need to be recompiled. Its a mess.

Lack of plan and leadership always been a problem. To me the project seams dead.
It is only a few software devs. that release some stuff from time to time.

Miker1264: What is it about ScaleOS. It was nice 20 years ago. I don't get it.

[deadwood]

yes I didn't understand why to abandon abiv0 when there is no stable replacement project

It was a mistake. The whole situation got kind of out of control. Deadwood backported commits to abi v.0 but some did not like that. Some ment that slowed down development of abi v.1 and wanted it abonded. It finaly  kind of happend but as you say Salvo. It should at least be a stable brach to replace it. Abi v.1 is still not a stable branch. If to reach its goal it must be broken again. Maybe many times. All software need to be recompiled. Its a mess.

FYI, since June I'm hosting a copy of AROS repository where ABI will not longer be broken and AROS itself expected to be stable. The supported build is linux hosted x86_64.

The repository is located here: https://github.com/deadw00d/AROS

If there are people interested in working on stable version that will not get their software broken every couple of months, this is the version to use.

Best regards,
Krzysztof

[Amiwell]

yes I realized that the problem was abiv1, paolone maybe wants to update the abiv0 branch, I don't know, hopefully, at least in the meantime a stable branch will exist

[Amiwell]

thank you deadwood

[wawa]

@salvo
actually im not in a position to comment on this, but from my private pov abi v0 is "feature complete" and can be used "as is" completely fine. its also fine when people are fixing it up or contributing to it, if they wish, and they do. personally, i was involved with v1 from the start since m68k is my main area of interest.

abi v1 has received a lot of updates in all areas, mainly for contemporary x64 and arm targets, but also m68k as legacy. these updates have been as far possible ported to v0 as well, mainly by deadwood. but its this is imho a bit of problematic, because even if it drags abi v0 along a while longer it also postpones the development and transition to abi v1.

[nikos]

yes I didn't understand why to abandon abiv0 when there is no stable replacement project

It was a mistake. The whole situation got kind of out of control. Deadwood backported commits to abi v.0 but some did not like that. Some ment that slowed down development of abi v.1 and wanted it abonded. It finaly  kind of happend but as you say Salvo. It should at least be a stable brach to replace it. Abi v.1 is still not a stable branch. If to reach its goal it must be broken again. Maybe many times. All software need to be recompiled. Its a mess.

FYI, since June I'm hosting a copy of AROS repository where ABI will not longer be broken and AROS itself expected to be stable. The supported build is linux hosted x86_64.

The repository is located here: https://github.com/deadw00d/AROS

If there are people interested in working on stable version that will not get their software broken every couple of months, this is the version to use.

Best regards,
Krzysztof

That is great Deadwood.
AROS64, Linux hosted is for sure a platform that can live.
I like the idea of having Linux with security, modern web-browser and run AROS for some games and apps.
Is there a version to try out that is compiled?
I don't feel comfortable compiling AROS64 myself.

[Amiwell]

@wawa

I understand in the end maybe maybe there is not as much enthusiasm as the previous years, it will go on as you can and we will wait as we have always done, meanwhile 32-bit icaros is functional despite there are no more updates in the subsystem, but we are in a transition phase, so we'll see when the first 64-bit icaros will be ready with all that is there (at least the software, I'm not talking about games)

[Amiwell]

@deadwood the alternative branch is different from the one found sourceforge which dates back to May 2019

[wawa]

FYI, since June I'm hosting a copy of AROS repository where ABI will not longer be broken and AROS itself expected to be stable. The supported build is linux hosted x86_64.

but why x64 then? all aros software out there except the binaries in ports in contribs is 32bit i386. i dont think it will work with x64? this is just another split/fork from abi v0 just without advantages abi v1 might introduce.

[wawa]

Lack of plan and leadership always been a problem.

okay, are you ready to subdue to a mighty leader right away?