(2014-10-01, 08:54)Willem55 Wrote: Thanks for the link... which holds this link at the bottom http://wiki.xbmc.org/index.php?title=HOW...on_Android
That begins with:........... Normally, you only need to use an external player if your Android device doesn't have a version of XBMC that works with hardware video decoding.
So it's just configuring XML and no code change involved...
Nice.... now why all the fuss of modding the build in player what is the catch here?
Because quite frankly the XBMC experience when using external players suck!
External players are not integrated into XBMC at all, so when using them you really notice when it launcher an external player and it break the XBMC experience.
It is a not a small compromise but a huge sacrifice and a major annoyance, it is just a dirty workaround for temporary short term use only, not a permanent solution.
Users that have poor experience with external player can give XBMC a bad reputation, and bad reputation, which will be bad for the project as less people will use XBMC which in turn mean less developers!
Also remember and understand that as long as there is a workaround then less developers will be motivated to work on a proper solution.
So it would therefore also be bad idea to try to improve the experience with external player in XBMC as it would only indirect serve to make it a worse product in the long term.
To summarize, just say no to external players! And just say no to duct tape programmers and say no to duct tape solutions!
As the saying goes; duct tape programmers are sacrificing tomorrow's productivity, today!
What is Apple made their first iPad the duct tape programer way?
Old related joke:
https://www.cs.cmu.edu/~mihaib/humor/told.jokes
Quote:How can I disable the modem whirring when a client dials in to OSR5? My computer is rack-mounted and will be placed in Telehouse so it should attract as little attebtion as possible to avoid being used as a coffee stand/pen holder.
Preferred Solution: Read the modem manual, find the codes to turn off the speaker and set them in the modem's NVRAM.
Alternate Solution: Rip all of the pages out of the manual and wrap them around the modem.
Hardware Solution: Open the modem with a screwdriver or can opener. Cut one wire going to the loudspeaker. Reassemble modem with remaining screws or duct tape (whichever is more convenient).
Software Solution: RTFM the printed manual and select several pages of technobabble to sacrifice. Rip out these pages and shove into the modem speaker. Wrap with duct tape.
Hacker Solution: Find ice pick. Stab speaker until dead. Note: This may void your warranty.
MSDOS/Windows Solution: It's a feature, not a bug. The noise is there for your own good. We know what's good for you. This feature will be fixed in the next release.
Kid's Solution: Position modem with speaker facing upward. Pour pancake syrup into speaker. This will greatly reduce the high frequency response of the speaker thus attenuating the sound.
Programmers Solution: Download the complete Rockwell command set from the modem manufacturer's site and use the bit mapped register functions to disable the speaker. Be sure that the warranty is still active as one mistake may also disable the modem.
Fast Solution: Take two needles, two clip leads and a 12volt battery. Observe that the leads of the speaker coil are visible through the grill where they are glued to the cone. Puncture these points with the needles and apply 12volts. The speaker coil will fuse open.
