Quote:

That is unlikely, I am hoping to have some beta ready in 2017 though. Offline/POP3 would likely come in 2018.

@ Jacadcaps

Thanks for the status update.


Looking forward to the new mail client, am using YAM 2.6 (I think later versions were rather heading to a wrong direction) which works quite okay, but does not get fresher. No urgend need though.

Quote:

...and that means MorphOS 3.10 will be out in 2017, yay (albeit without new e-mail client, boo)!

Quote:

Or that the 1st beta of jaca's mail client is deemed unfit for inclusion into the ISO....

Sorry this project has been on a hiatus for so long. I've finally started working on the Task list component. You can expect a 1st working beta within 2 months. Work on Scout and Iris will be done in parallel.

ScoutNG isn't just about reimplementing the old Scout...

Quote:

- Killing a non working or unecessary task
- Ability not only to show missing components, but to hunt them on Aminet,MorphOS depots etc.

I am all in for helping bounty with 10-20 euros. I would give more if goal can be extended to portable AROS/OS 3.x+Vamp functions/OS4 ports so we have a bit standardizet "scout" for all, until system will be able to display better error messages about missing components.

Edit: I see it done. Are extended feats and cross Amiga systems a viable goal?

[ Edited by vox 23.08.2018 - 12:59 ]

The reason is to use non public structures of Morphos in closed source application. This can't be made public/open source/portable. Other OSes also don't have obj-c frameworks.

[ Edited by zukow 23.08.2018 - 13:19 ]

This is a MorphOS bounty - the frameworks and data I am using are MorphOS-specific. An AROS version could likely be done since the system structures are all in opensource anyway. Scout NG is written in Objective-C which by all means could be ported to other platforms, but this is out of the scope of this bounty - and a bounty like that would require two additional zeros.

Quote:
It is a task manager. A task manager without the possibility to kill a task does not make sense. I expect all the functionality from Scout to be in ScoutNG because they are very helpful. So I am sure killing a task is also part of ScoutNG. I am happy to see it in a few months because I want to get rid of this broken NList MCC stuff.

Quote:
A task manager shows running programs. If a program misses a component it cannot run. So how can this no running "task" be listed in a task manager? Only for the short second or less when it tries to start and then it will be gone again from the list.
Even if: it would not be the objective of a task manager at all to point to which files you shall download. Tools like Snoopium are exactly there to show which components are missing. And then you can go to Aminet and search for them.

Quote:
Thinking of so many other platforms only makes the program blown and complicated. More than we need it. I think it will be good to have a small and specialized program instead. And no other platform can benefit from the MOS structures. So it will be useless there. What you ask for is already there. It is caleld Scout.

Quote:
You can't kill a task completely on an OS without resource-tracking. You can suspend a task and even remove it, but there will be always rests. Memory, ports, interrupts, io-handles, screens and many more will stay in the memory. You could do it by hand but that's like finding a needle in a haystack, for a complete remove.

Quote:
The old Scout also does not completely remove a task. You need to salute with three fingers for a task to be killed :)

jacadcaps
Look's nice!

Preview of the exec library monitoring facilities.

ScoutNG binary

Quote:

Better to reboot when you're ready than be forced to when you're not.

A few more words about this: it took a while to get to this point, but the internals are pretty flexible thanks to that. This is how Scout is able to show a controlling task of a msg port easily or safely update the data of a Task, etc. At this stage the Exec module still isn’t complete - I want to add detail views for Message Ports and Semaphores and list a few more Exec lists. The Message Ports and Semaphores will be reused for Intuition and other modules later on.

Just for fun scout.info

@ jacadcaps

Interesting as far as it goes so far. Any idea when you'll be nearer to having a full release available - end of 2018?

Is this still an active project?

Yes. Even committed to the repo yesterday. Been looking into making the tasklist more optimal in terms of CPU use since that's a component I'm also using on a different project called KoProfiler.

I am generally overloaded by Iris, WebKit and MorphOS 3.12 related work so that hurts progress on all/other fronts. I'll try to release a new beta soon(ish). The aim now is to finish the Exec module.

You're a champion!

Excellent news !

Such news is great to hear about, particularly as you've already said you're pretty much 'saturated' with workload at the present time.

Doing some more work on this now...

Thanks for everything you are doing for MorphOS, as I imagine your workload is immense at the moment, if not always.

Sorry this is taking so long. You'll find an updated binary here.

Requires 3.12!