@cavemann
no problem i was just saying :)

about the first draft, it's the first post of this thread. free for everyone to see and comment. i'll wait and see if there's suggestions (i hope there will be) before sending bounty to p2ppl.

toolsdaemon isn't opensource afaik.. but porting it shouldn't be necessary.. as tooldaemon just exploit OS functionalities (that are missing on aros) .

once such functionality will be present (it's called "appmenu" i take it then?) they could be accessed in very different ways... for example: through 3rd party programs or scripts or through a tool bundled with aros (as OS component..pref)

problem now is that the OS itself doesn't support it..

@freeeaks, sorry I should read more carefully.

I don't think the name is as important as listing the specific requirements needed to complete the bounty. It seems to me that there are two parts to the bounty.

The first part is getting the system menu in AROS to the same level as the Classic Amiga. I don't know if this is simple or difficult, but it would set the stage so programs that use the Amiga system menu can also work on AROS.

The second part would be to port toolsdaemon (if open source) or another tool, which I suppose would be simple once the first part of the bounty is complete.

Before you send the bounty requirements to Power2People, I suggest that you put the first draft of the bounty in this thread. Then everyone can take a look and make suggestions. Someone that knows the technical details might have some good tips.

Thanks for your efforts. I hope someone will pick up this bounty soon.

@cavemann

i said before i knew toolsdaemon was just another mean of adding menus, but there are others. these tools are just exploiting a functionality of the OS. (ex: current os4 use a simple arexx script to allow adding menus)
toolsdaemon was just mentioned as reference.

so maybe this draft should be reworked you think ?
how should we call it ?
appmenu v1 bounty ?

i have no idea how to phrase such bounty..
how would you do it ?
all i know is: no custom menu = too bad
but i agree that i miss menubar clock and screenswitcher too..

It is not just about Toolsdaemon. It should be possible for all sorts of applets to have a home on the menu bar. Launchers, clocks, screen switchers, all could pop up with a right click.

It's a part of the Amiga Os that I would like to see sooner rather than later. I would be happy to donate to help get AppMenu working.

Quote:

of course, menu customisation is a personal thing you are right.

glad to see some talk about multiuser , btw :)

It does not "might be" a better choice, it should be the right choice from start. The S: drawer is meant for scripts and should be user-unaware. envarc: is the place for system settings.

Unluckily AmigaOS/AROS are single user environments, but some efforts have already been done to support at least a minimum of multi-user behavior. They move and archive the contents of envarc: when a different user logins, and this enchanced menu thing is something that every user should keep on his own.

@paolone
good idea envarc: might be better suited for storing user settings than s: eventualy. i'll add it to the draft.

@freeeaks

why using S: to store user customized menu? wouldn't envarc: fit this need?

@ncafferkey
only workbench.

btw, toolsdaemon wasn't the only way to add custom menu on amiga.
i think current amigos (os4) does it through arexx.
it's just another mean to add new menu to launch programs.

my workbench menu was usualy like this:

normal menus:
workbench
window
icons

then my added menus:

inet (containing launcher for amirc, amiftp, ibrowse, etc..)
sound (songplayer, eagle player, amigaamp ..)
grafx (arteffect, imagefx ..)
sys (edit startup-sequence, edit user-startup, comodities ...)

you can create a lot of launcher without cluttering the desktop..
works well with or without sticky menu option..
only affect wb menu..it just add the possibility to add more items to the existing menu, thats'all.

Workbench 3.1 AppMenu functionality needs to be completed for AROS so Apps can dynamically add and remove their own menu items from the Workbench replacement app's screen (background window).

Beyond that, gets into questions of who created the publicscreen and what should the "background window" have for menu-items, and what should individual app windows have for menu-items when their window is active.