// First post here, hope it fits as it’s more a question then an already finished script.
I’m a thankful user of the “AppDrawer”-script (create an appdrawer anywhere) and in it’s spirit, I’d like to also have a drawer for contacts and one for music/video.
The question is mostly for the music/video part as in does LLx scripting have access to the filesystem?
Basically, my music is stored like this:
/base/music/artist/(year) albumname
In /artist/ there’s an artist.png and in /(year) albumname/ there’s a cover.png and an .m3u-playlist
So what I would like to have is a page showing all artists as pictures. Long pressing it should queue all playlists alphabetically (thus by year) while short pressing should spawn a list of albums with cover. Again, longpressing should queue the album and shortpressing should spawn the list of files.
Would all of that currently be possible?
]]>
D5 Creation
< ![CDATA[
As far as I know you can’t read the filesystem by script.
]]>
< ![CDATA[
Ah, that’s too bad. Do you know who’s limiting it, Android itself not allowing it or LLX not implementing it? root’s available if that would make it possible.
]]>
< ![CDATA[
I don’t know if it would require a permission, but it’s definitely not implemented in LLX ATM
]]>
< ![CDATA[
Well, Pierre Hébert, maybe you could shed some light on this?
]]>
< ![CDATA[
This is more a conservative approach: remember, this app is a launcher 😉
At the moment LL has already the permission to access the external storage (for the backup and templates) but full access to this filesystem area is somewhat dangerous.
That does not mean that it won’t be implemented one day, given the fact that some excessive APIs are already available today, lol !
]]>
< ![CDATA[
For a launcher, your xterm has come pretty far already 😉
I could think of quite a few useful (in my book) ways to use direct access to the filesystem, especially combined with root, but of course it’s yours to decide, so start already jk
]]>
< ![CDATA[
Too far maybe ?
No doubt that access to the filesystem would find a lot of use case. But not so easy to select the right API. I don’t know yet whether it could be a direct Java File and *Stream or if it should be a simplified APIs with few classes and method. First would allow access to much more than files, while the second would be obviously way easier to use.
]]>
< ![CDATA[
I just hope root wont ever be required to take advantage because that wouldnt be fair.
]]>
< ![CDATA[
No root, nor internet permission.
This is a line that won’t be crossed.
]]>
< ![CDATA[
Looking at how LL is doing now I’d say so far you’ve always chosen power/flexibility over ease of use. In my book, that’s what makes it interesting (I’m tinkering with my FVWM config for 10+ years now and I’m still not done ;)). I mean, you started the scripting, afaik there’s not a single competitor on that level, so why stop?
If you’re afraid of the complexity for new users, just hide it behind a beginner mode, but as you already layed a pretty solid foundation, there’s no reason to stop there. Could also maybe pack it into a payed extension, I’d gladly pay some bucks for that stuff and if it helps to keep you motivated, all the better. But for now, sleepy time :p
]]>
< ![CDATA[
+1 for pack as an extension (not paid one…), I also had this idea
]]>