Remember, any core device or pattern can be changed by defining the Id in the patch file and then overriding the value.
I don't think that any of our definitions should live in the patchfile. Wurfl kept desktops in the patchfile because it did a poor job of detecting them. That's not the case for us which is why we expanded the core definitions to bots and other device classes. Patching should only be required to add functionality. If we are missing functionality... we should consider fixing it in the core definitions. So I'm for keeping all device and pattern definitions in the core files. <div>-------- Original message --------</div><div>From: Werner Keil <[email protected]> </div><div>Date:09/10/2014 6:27 AM (GMT-05:00) </div><div>To: [email protected] </div><div>Subject: Re: Data </div><div> </div>It would be great to allow adjustment in the "Patch" file by moving a device definition like "desktopDevice" there. Whether it's named "desktopDevice" or "patchDesktop..." or similar does not really matter. It seems not show-stopper for 1.0.1, as long as the W3C compliant builder signatures work now, I would not insist on changing it now, but we may want to clean that up in the next release. Werner On Wed, Sep 10, 2014 at 1:35 AM, eberhard speer jr. <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > RIM - BlackBird...got it, no change required. Easy. > > And iOS and iPhone OS ? similar case ? > > esjr > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (MingW32) > > iQEcBAEBAgAGBQJUD465AAoJEOxywXcFLKYcgFEH/0SFzkl3h8WefhOZWM7tIAIj > SawluAF1iBugkaP+G62zafK2h7OS0ihjRnic/+lcvxIxzlUkDQnt1yy2OZqDeIhm > jS7tM0VAfkykHcvgB1yolRxUSRtAT/rGdAeUnIzojqqR7C4+FUXE2anVvwFEcGqz > 27UAX/vRkq3Pq89ZBLcu7CTMJEsbzMFxQvL9Uelf4JWyWSeKemlV2Bc/KKa8j9Uc > s2ucwS2KFY5tFYK1QllhUEhQEOgVNKxi8K8DLoc+KI00b5w3HMBif46ZJ/Yw4vpC > b1duhGZToVcbku7EgbhcjjDYxtSiO5ROzhm6iT2zvgWo93ZXWm0yHpbDYhZs47E= > =d7Ls > -----END PGP SIGNATURE----- >
