On Mon, 29 Aug 2005 22:45:15 +0200, Jonatan Liljedahl wrote:
> It's still possible that the user doesn't want to use 0launch at all. I
> think it's cool, but personally I prefer the control I get when an
> AppDir is an AppDir and not a wrapper to an internet based auto-download
> tool. IMHO, putting the apps in hidden cache-directories is like
> avoiding the nice concept of relocatable AppDirs, which can be moved
> around, opened and looked into, or deleted.
Of course, you can install apps locally and register them with the
injector, but assuming we're talking about the normal case of having the
injector download them for you:
- Moving: The normal reason for moving something is to organise your apps
directory neatly. You can still do that with the injector; you're just
moving the wrappers instead.
- Examining: Cached apps can still be looked into or deleted; the easiest
way is to choose 'Help' from the menu and click Up, but you can also do it
through the injector interface (menu -> Versions -> Program -> Open cached
copy). This has the advantage that you can quickly look inside not just
the application, but any libraries it uses too (eg, ROX-Lib).
- Deleting: Having opened the application, you can of course delete it.
Just make sure you delete the whole directory (named sha1=...). And, you
don't have to worry that some application you'd forgotten about needs it;
if so, it will just offer to download it again for you when required.
We probably need a cache cleaner, which suggests removing old versions of
programs that you haven't run for a long time.
> So, please make 0launch a good alternative for those who wants to use
> it, but make sure everything works consistently without it. For example,
> a button that tries to start "0launch the-uri-to-Mime-Editor" in
> rox-filer should check if 0launch is available first.
It does. It even tells you where to get it from. What else could we do?
- Try in ~/Apps. OK, but what if it's in /usr/local/apps, ~/Applications,
~/Apps/Configure (this is where mine is), etc?
- Ask the user to find it and register its location with ROX-Filer.
This isn't really any different to finding MIME-Editor and registering it
with 0launch, except that you'd have to do it with every program that runs
MIME-Editor, not just ROX-Filer.
> But sure, it's good (and actually nessecary) for some apps to find other
> apps, and 0launch solution to this is absolute URI's. But why not have
> an APPDIR_PATH? In reality, most people have their rox-apps in two tree
> structures: /usr/local/apps and ~/Apps.
Why not have 0launch search your ~/Apps directory for you? Search for an
interface XML file with 'uri=<the program you want>', and run that.
> Also, it would be cool if 0launch could just install the apps "as usual"
> in some configurable folder (like ~/Apps). Maybe the auto-update
> features and sha key checking could be inserted into the appdirs instead
> of the other way around?
How can you share downloads between users in that case?
Dr Thomas Leonard http://rox.sourceforge.net
GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1