Quote:
Originally Posted by dirgeon
Hi,
I've been trying to find info on how to actually make an update*.bin file + KUAL, with no luck. Been searching the forums and wiki but either I'm using the wrong keywords, or I missed it.
I've written a couple hacks that run just fine when copied over and manually editing /etc/lipc-daemon-events.conf. I'd like to share them the proper way, but am stumped. 
Would appreciate any pointers. Thanks! |
Your searching is probably correct.
The update*.bin file packages are normally used in two cases:
- Where the installation has to change files outside of the USB storage area (yours does) ;
- Where the installation procedure is too complex (for the common user).
You don't find much of what your looking for because KUAL uses "Button Code" that is simply copied into USB storage.
(Like copying, I.E: "side-loading", a book - nearly every user can do that.)
But your project seems to meet [1] for certain (changing a system configuration file).
So your on the correct track with this question.
But good design (tm) for the common user can be tricky.
- - - -
We need a bit of clarification before more specifics can be given:
Do you need a modified KUAL or can the standard KUAL package be used?
I will assume the above answer is "standard KUAL" package - - - -
So in this case, you are just adding a set of KUAL buttons not a specialized version of KUAL.
Next question -
Are the changes to the configuration file a "one time" thing?
I.E: When your button set is installed.
(and the changes un-done when your button set is removed?)
OR
Are the changes to the configuration file an "interactive" thing?
I.E: You have button actions that make changes at the touch of one of the buttons.
(yup - that's one question)
- - - -
In either (or both) cases - the implementation of an "end user safe" KUAL extension can become a bit tricky.
But it has been done before (although not written up, because it is a rare case).
And we (I am volunteering the other developers here
) can give you specific guidance.