Forum OpenACS Development: Why is "install application" seperate from "install service"?

Only a developer would know the difference anyway. I think this adds unneeded complexity (not that much, more an annoyance) to the interface. Would a site-wide admin know where to look to install a certain package?
I'm not sure what the best UI is. But I believe the thinking has been that an admin typically only wants to choose among applications and not have to bother with service packages. The service packages will be installed by default based on the applications chosen.
Yeah. The idea is that most sane people don't want to install "notifications".

They want to install a bug-tracker, and then installing bug-tracker will cause notifications to get installed as well.

So "application" is anything that is actually usable in itself.

I'd like to move the services part out completely, or at least obscure it even more.


That makes sense for notifications, but I'm not sure it works for all other packages.  general-comments isn't required by anything (as far as I know) but it can be optionally installed and used.  So IMHO we shouldn't make it too hard for the site admin to do that.

Personally, speaking as a developer, the distinction between applications and services has always annoyed me. If I need to watch a file in a service it requires an extra page load to get there in the APM.  Maybe we could have a "developer mode" that would show all packages on one page?

Speaking of watching files...

A week or so back, I updated a dev instance to HEAD and noticed that (at least) one package was automatically watching all files. I don't recall the package, but I didn't do anything to cause this to happen. This phenomenon continued across service restarts also.

Is there a new *static* setting that was added to get this behavior?

Actually, the APM index page was changed a while ago to show all packages by default.

And yes, general-comments are required by at least lars-blogger and news, so it will get installed there.

Well, obviously I haven't installed 5.0 yet. ;)

I don't have a problem with making things easier for users, but I don't think we should frustrate budding developers, either.  That's really my point.

It seems to me a service is something that would only be used by another application, something that would never be stand-alone, and therefore something that would never be installed by a person except as a dependency.

The cronjob package doesn't fit this definition. It is a stand-alone package. It only has admin pages because it might be too dangerous to allow users to run queries of their choosing anytime they want.

However, if you can still navigate to and install a service package, then it really doesn't matter to me where cronjob shows up in the apm.

concerning the package watch, that was because of a file that I added by mistake and then discovered and removed.

During development it's quite convenient to have the packages you are working on watched all the time. The way to accomplish that is to put a statement like the following in an init file in your tcl directory:

foreach package_key $package_key_list {
    apm_watch_all_files $package_key

Thank you, Peter. That's a neat trick.