Rockbox mail archive
Subject: Re: Scripting language
From: sophana (jobarjo78_at_yahoo.fr)
>> Yeah, a scripting language inside rockbox! I like the idea.
>> Maybe there exist some freeware language which is light enough to go
>> inside rockbox?
>> The lightness might be the problem, don't you think?
> I discussed this with a friend at length last night, he mentioned a
> basic interpreter was built in 1K of C in a competition at ioccc a few
> years back, that leaves 31K for a cute plugin interface, or you could
> include it in the core, as you prefer.
Is it open sourced? I would be glad to have a look at it. Maybe
sourceforge has some related projects ?
> Either way I have some snazzy ideas for it, unless one of the Rockbox
> guys beats me to it. The dilemma is that to create a full event
> driven interface (when a song starts <x>; when a menu displays (y),
> when the machine boots <z>) would require hooks all over the core code
> - and that bit is out of my hands now :(
The scripting language should be in the rockbox core as a simple library
call. (for the autostart it would be better...)
But appart from the autostart what other applications can we imagine?
Plugins could be written directly in the script language? That would be
cool don't you think? If you give access to the directory and files
structure and the id3, we can imagine lots of applications. Maybe
replace the actual wps and tree routines?
For the events, we should rely on existing event queues (queue_wait()),
especialy the button queue. The script should run in a thread like any
other sequential program...
Page was last modified "Jan 10 2012" The Rockbox Crew