I got it through the Apple validation process and up onto test flight for testing. From there we can easily launch to beta testers (and eventually to the App Store once we’ve got the bugs worked out). Good news is that the basic functionality is working. Messages view is very cool. A few crashes, but I can work through those. The bad news is that the layout is now messed up. Very badly messed up. It seems that the new iOS layout stuff is getting in the way and our automatic re-arrangements aren’t working (or at least we were previously locked to a simple compatible view). It is likely to take some time to get this better, but the simulator works well (as does storyboard), so I am working on it… Regards, Mark.
On 30 Jan 2019, at 8:51 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
I’m trying to get an adhoc release out first.
But quite a few changes in App Store side, related to iOS 11+ and asset catalogs. Working on it. Maybe tonight…
A general App Store release will have to come later. That has to go through the stricter App Store approval process.
Regards, Mark.
On 30 Jan 2019, at 7:42 PM, Geir Øyvind Vælidalo <geir@validalo.net <mailto:geir@validalo.net>> wrote:
This is a major step up :-D How long before we can see it in AppStore? Do you have an idea?
Geir
Sendt fra min iPhone
30. jan. 2019 kl. 03:01 skrev Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>>:
All done. Now to get it past the Apple gatekeepers…
<PastedGraphic-1.tiff>
Mark
On 29 Jan 2019, at 7:40 PM, Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>> wrote:
Good grief, that was painful. Almost as many classes and files in this chat messaging framework as in the whole rest of the project combined.
After hours and nights of struggling, I’ve finally got a working messaging UI up in the iOS App (both iPhone and iPad).
Now, to implement the actual message content…
<PastedGraphic-2.tiff>
Regards, Mark.
P.S. At least it looks better than Android 😜
On 16 Jan 2019, at 4:46 PM, Geir Øyvind Vælidalo <geir@validalo.net <mailto:geir@validalo.net>> wrote:
Great work, Mark!!! I tried to fix the warnings myself, but it felt like walking through knee deep mud :-D Apple sure isn’t afraid to change their API. It’s probably for the best, but it is quite overwhelming for people like us who isn’t working with these things on a daily basis. Hope you get the messaging tab working! Good luck 🍀
Geir
Sendt fra min iPhone
16. jan. 2019 kl. 09:32 skrev Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>>:
I played around with it some, and managed to get the number of warnings down from 550+ to below 100 :-) The bad news is, of course, 80/20 rule that the last 20% are gonna be by far the hardest. But these are warnings, so we may get away with them for some time. Mostly deprecated function interfaces that are still working (but maybe dropped at some point in the future). Some date back to IOS 6, so a little scary...
I also took the opportunity to fix a couple of niggling issues that have been annoying me. Tidied up the storyboard layouts, fixed a crash on lock/unlock for cars not supporting the function. etc. I’ve committed what I have done so far.
I’ve also started working on a messaging tab (just like the android app). Adding the tab was relatively easy (despite changes in storyboard), but the ‘drop in framework libraries for chat bubbles’ all seem incredibly convoluted. Not 'drop in' at all. I was expecting something to draw the screen for me, and simply give me a method to call to add a chat text message. But, no; these libraries want me to do all the drawing myself. Literally copy-and-paste half a dozen classes from example code, then try to remove dependencies on yet more third party libraries. Good grief… So much more complex than I had hoped, but I am working on it.
Regards, Mark.
> On 11 Jan 2019, at 4:12 PM, Geir Øyvind Vælidalo <geir@validalo.net <mailto:geir@validalo.net>> wrote: > > Hi Mark, > > I totally know what you mean. The changes from Xcode 9.4 to 10 are major. I had to change the build system to «legacy build system» to get the OVMS APP to compile. Unfortunately that is a temporary solution. > > I wish I was more fluent in Xcode... > > Geir > >> 11. jan. 2019 kl. 03:01 skrev Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>>: >> >> Geir, >> >> I haven’t had time to do anything on the iOS App at all. I did try to get it running on the latest xcode, but many (hundreds of) error messages and a real PITA. Just too much on my plate at the moment to work on it. >> >> There are a bunch of drop-in iOS framework libraries for chat bubble style messaging. I think the UI would be easy. >> >> Regards, Mark. >> >>> On 11 Jan 2019, at 4:48 AM, Geir Øyvind Vælidalo <geir@validalo.net <mailto:geir@validalo.net>> wrote: >>> >>> Mark, >>> >>> Did you get anywhere with the message-function on iOS-App? Would it be possible to send commands like «stat» and then see the result in the App? >>> >>> Geir >>> >>>> 3. jan. 2018 kl. 13:32 skrev Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>>: >>>> >>>> Geir, >>>> >>>> I’m looking after the iOS version. I can build and release for Apple devices, and post updates to iTunes Store. >>>> >>>> I have some changes made to enlarge some fields, and I want to add a ‘messages’ function similar to the Android version (to be able to issue commands to both v2 and v3 boxes). Other than that, I don’t have anything outstanding on the iOS version - it seems to support the v3 metrics just fine as is. >>>> >>>> If anybody else has any changes to iOS version, please make a pull request on the GitHub and I’ll merge in. >>>> >>>> Regards, Mark >>>> _______________________________________________ >>>> OvmsDev mailing list >>>> OvmsDev@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> >>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev> >>> >>> _______________________________________________ >>> OvmsDev mailing list >>> OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> >>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev> >> >> _______________________________________________ >> OvmsDev mailing list >> OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> >> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev> > > _______________________________________________ > OvmsDev mailing list > OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> > http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev