On 06/04/12 16:03, Krinkle wrote:
> Blame me for loving front-end technology, but maybe one of these ideas
> are useful to you:
No blame, I welcome your insights, Krinkle :)
> * Not WLM specific internally, please (instead it could come with a
> number of modes, possibly extendable with plugins)
I'd prefer not to hardcode anything WLM-specific, but maybe there's a
killer feature hard to do without it. Maybe I can get all WLM-specific
things in a module, and have the application linkable with a different one.
I've added a note about it at the application page.
> * Perhaps not a desktop application at all (nothing more mobile and
> future proof than the web[1]). Something like a MediaWiki extension or a
> standalone web application. Or extend / improve UploadWizard.
I don't find UploadWizard comprehensible enough to extend it :)
We could have a web application which stored the image preferences at
localStorage (not as good as an actual file, but could work), but I
don't think we could load the submtited filenames from a previous run
(nor would be too safe for a spec to allow that). It might be possible
in Firefox by requesting higher privileges.
> * If none of these, perhaps you can be persuaded to go for a hybrid,
> look at Adobe AIR. With AIR you can use HTML/CSS/JS but not deal with
> traditional web browsers. Instead it runs as a native application, also
> very flexible and cross-OS. And no cross-browser issues since the only
> engine it'd run on is that of AIR (uses WebKit). With AIR it still has
> most desktop application possibilities such as caching files locally,
> updating the application periodically, storing preferences, accessing
> the file system, details I/O and up/download uploading/progress
> meters etc.
Isn't that based on Flash? Had you proposed Prism... Still, the overhead
of these approaches seems too big.
Also, Adobe Air seem to have discontinued their Linux support, and
reliance on that propietary system doesn't seem like a good idea.