On Wed, 2010-03-24 at 15:15 +0100, Nicolas Chuche wrote:
> > But, maybe, in those cases dbus-scripts is the wrong tool
> > and it would be better to create a custom daemon to do whatever is required.
>
> I really like the idea of dbus-scripts to handle all my dbus scripts.
> I don't like the idea
Hello,
> reinventing the wheel could be hard and dangerous so I was thinking
> about something like yaml. On the plus side, it's easy to parse with
> libraries. On the minus side, you need to have the library on n900.
I've coded some kind of POC. It's not finished (my C is a bit
rusted...) and ju
> I did not add arrays because I did not see the need for it, but since you
> need it, there is no problem to add this. What format do you think might be
> useful for passing an array of bytes as a parameter to a script?
If I'm the only one to need that no need to rush :)
Perhaps a dumb yaml dump
> I tend to favour either using a filespec (a file which dbus-scripts deletes
> after the script has run) or using base64 (because there are probably
> convenient libraries in many scripting languages).
good ideas. I think I'd rather the filespec.
> Of course, this doesn't allow for more complex
On Wednesday 24 March 2010 11:22:34 Matan Ziv-Av wrote:
> I did not add arrays because I did not see the need for it, but since
> you need it, there is no problem to add this. What format do you think
> might be useful for passing an array of bytes as a parameter to a
> script?
I tend to favour ei
On Tue, 23 Mar 2010, Nicolas Chuche wrote:
Ok, found why in dbus-scripts.c. It's not yet implemented :) :
#if 0
[...]
case DBUS_TYPE_ARRAY:
{
int current_type;
DBusMessageIter
Ok, found why in dbus-scripts.c. It's not yet implemented :) :
#if 0
[...]
case DBUS_TYPE_ARRAY:
{
int current_type;
DBusMessageIter subiter;
dbus
