Interfacedefinition for Car-PC Module
first i want to say that i really like the idea of frodocom (as far as i understood it :)).
IMHO i think if more developers will use this network and make modules for it, everybody will be able to "design" its own softwarecollection for his carPC like zorro shows in his graphic.
So everybody could choose if he wants a player based on winamp or on mediaplayer and so on.
but the mainproblem is, that we first had to arrange about a general interface description for each module??? or am i wrong?
lets say u have a module which handles the skin, also u had a module which plays music, one for video and one for gps. where does each module know what to do or maybe the skin-module know, what command should be send to what module???
so my idea is to have a definition for each module-type to be interfaced and which type this module is. F.e.:
Functions: PLAY; STOP; PAUSE; NEXT; PREV; FASTFWD; FASTRWND; SHUFFLE; REPEAT1; REPEATALL; .....
Properties: CUR_SONG_TITLE; CUR_SONG_GENRE; CUR_SONG_ARTIST; CUR_SONG_LENGTH; CUR_SONG_POS; REPEAT1; REPEATALL; SHUFFLE; ALBUMART; ....
Funcions: MAINMUTE; MAINVOLUP; MAINVOLDOWN; LINEINMUTE; LINEINUP; LINEINDOWN; MICMUTE; MICUP; MICDOWN; PRESETNEXT; PRESETPREV; ...
Properties: MAINVOLLEVEL; MAINMUTE; LINELEVEL; LINEMUTE; CURPRESET_NAME;...
i hope u understand what i mean???
please tell me if i'm totally wrong, but i think if we had such a definition, it will be much easier to the developers to write a module for frodocomm??