Rockbox.org home
release
dev builds
extras
themes manual
wiki
device status forums
mailing lists
IRC bugs
patches
dev guide



Rockbox mail archive

Subject: Re: Viewing Files With Plugins UPDATED
From: Henrik Backe (backe_at_swipnet.se)
Date: 2004-01-13


"Henrik Backe" <backe_at_swipnet.se> wrote in message > > 2. Extension config
file ".rockbox/view.config". A config file lists
> > extensions and what plugin (file name) that should be ran to view
> that
> > particular file. This file is _not_ scanned at boot, but will be
read
> > and cached at first use. We could possibly have an option to parse
it
> > automaticly at boot.
>
> cached where?
> If it's cached in a separate file I can't see any performance benefits
> at startup. My thinking is to read view.config at startup if it exist,
> but also, make sure that no view.config is needed in a standard
> setup (3. takes care of that)
>

I get the cache concept now, so disregard my reply please.
I'm having a slow start after christmas.

> > View Supported
> >
> > The concept of "view supported" files changes somewhat. Internally
> supported
> > formats are of course present, but extensions in the "view.config" are
> > only supported once the file has been read and and so are extensions
> that
> > have been "verified to work". That means we've played one successfully
> and
> > thus there was a plugin for it in the proper dir.
>
> I disagree slightly. This means that plugin supported files hardly ever
will
> be showed as supported. My thinking as that if an plugin exist for an
> extensions

Now that I understand your cache concept I agree.

.../Henrik



Page was last modified "Jan 10 2012" The Rockbox Crew
aaa