Just a note to acknowledge all the submissions I've had (both personal and to the list) on the Android App. Thanks for your help testing this. I'm not individually acknowledging each feedback message, to keep the volume of messages on the list reasonable. I am collecting all the feedback. Most of the points made so far are very quick and easy to fix. Mostly just cosmetic. I hope to get another update, with these fixes made, over the weekend. So far, it looks like the App works just fine, and I don't think we need many more betas. I may just try to make the arrangements to get it into the Play store directly. Regards, Mark.
Von: ovmsdev-bounces@lists.teslaclub.hk [mailto:ovmsdev-bounces@lists.teslaclub.hk] Im Auftrag von Mark Webb-Johnson Gesendet: Montag, 21. Januar 2013 14:58 An: OVMS Developers Betreff: [Ovmsdev] Android App
I'm glad to be able to (finally) announce that the new Android App is finally ready for public beta. We're calling it v3.1.1.
The source code is all in github (for the brave), and there is an APK that can be side-loaded on Android devices, via this link:
http://www.openvehicles.com/downloads/OVMS.3.1.1.beta.apk
Functionality wise, it is pretty much on a par with the iOS App. All the core functions are there and, most importantly, the virtual car layer is complete and up-to-date. We've got HOMELINK support (yay!) as well as all the new function and parameter settings. It does have the artwork for the Volts and Amperas, but no Twizy yet (sorry, that slipped through the cracks, but we'll get it in the next build). The App should support any 2.3+ Android phone, and should scale its displays to pretty much any resolution out there. Tablet support is implemented by making them look like big phones.
There are a few things still incomplete (as previously pointed out at the start of this project):
No social group support on the map No cellular usage Some recent artwork missing (this is easy, and will come in the next beta release)
These will come, but weren't considered essential for this first release. The most important is to get the Android App up to the same level of functionality as the iOS App, so that they can both be brought forward.
I think if you want to install this, you first need to uninstall the Play store version. You will probably have to re-setup your vehicle as well. If you have problems with the beta, you can always uninstall it, and roll-back to the Play store version.
Please send feedback back to this list.
Regards, Mark.
Is there any good reason why the app size is 12MB? ________________________________ From: Mark Webb-Johnson <mark@webb-johnson.net> To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Sent: Friday, January 25, 2013 8:51 AM Subject: Re: [Ovmsdev] Android App Just a note to acknowledge all the submissions I've had (both personal and to the list) on the Android App. Thanks for your help testing this. I'm not individually acknowledging each feedback message, to keep the volume of messages on the list reasonable. I am collecting all the feedback. Most of the points made so far are very quick and easy to fix. Mostly just cosmetic. I hope to get another update, with these fixes made, over the weekend. So far, it looks like the App works just fine, and I don't think we need many more betas. I may just try to make the arrangements to get it into the Play store directly. Regards, Mark. Von: ovmsdev-bounces@lists.teslaclub.hk [mailto:ovmsdev-bounces@lists.teslaclub.hk] Im Auftrag von Mark Webb-Johnson
Gesendet: Montag, 21. Januar 2013 14:58 An: OVMS Developers Betreff: [Ovmsdev] Android App I'm glad to be able to (finally) announce that the new Android App is finally ready for public beta. We're calling it v3.1.1. The source code is all in github (for the brave), and there is an APK that can be side-loaded on Android devices, via this link: http://www.openvehicles.com/downloads/OVMS.3.1.1.beta.apk Functionality wise, it is pretty much on a par with the iOS App. All the core functions are there and, most importantly, the virtual car layer is complete and up-to-date. We've got HOMELINK support (yay!) as well as all the new function and parameter settings. It does have the artwork for the Volts and Amperas, but no Twizy yet (sorry, that slipped through the cracks, but we'll get it in the next build). The App should support any 2.3+ Android phone, and should scale its displays to pretty much any resolution out there. Tablet support is implemented by making them look like big phones. There are a few things still incomplete (as previously pointed out at the start of this project): * No social group support on the map * No cellular usage * Some recent artwork missing (this is easy, and will come in the next beta release) These will come, but weren't considered essential for this first release. The most important is to get the Android App up to the same level of functionality as the iOS App, so that they can both be brought forward. I think if you want to install this, you first need to uninstall the Play store version. You will probably have to re-setup your vehicle as well. If you have problems with the beta, you can always uninstall it, and roll-back to the Play store version. Please send feedback back to this list. Regards, Mark.
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Nikolay, Here are the contents: 8.0K AndroidManifest.xml 116K META-INF 1.3M classes.dex 13M res 100K resources.arsc The App is 1.3MB, and the resources 13MB. Of that, 11MB are the graphics for the cars. I am working on a framework where we don't have to deliver those with the Apps (iOS and Android), but downloaded them from the web after installation. That will also allow us to upload new car graphics without having to change the apps. Regards, Mark. On 25 Jan, 2013, at 5:41 PM, Nikolay Shishkov <nshishkov@yahoo.com> wrote:
Is there any good reason why the app size is 12MB?
From: Mark Webb-Johnson <mark@webb-johnson.net> To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Sent: Friday, January 25, 2013 8:51 AM Subject: Re: [Ovmsdev] Android App
Just a note to acknowledge all the submissions I've had (both personal and to the list) on the Android App. Thanks for your help testing this.
I'm not individually acknowledging each feedback message, to keep the volume of messages on the list reasonable.
I am collecting all the feedback. Most of the points made so far are very quick and easy to fix. Mostly just cosmetic. I hope to get another update, with these fixes made, over the weekend.
So far, it looks like the App works just fine, and I don't think we need many more betas. I may just try to make the arrangements to get it into the Play store directly.
Regards, Mark.
Von: ovmsdev-bounces@lists.teslaclub.hk [mailto:ovmsdev-bounces@lists.teslaclub.hk] Im Auftrag von Mark Webb-Johnson Gesendet: Montag, 21. Januar 2013 14:58 An: OVMS Developers Betreff: [Ovmsdev] Android App
I'm glad to be able to (finally) announce that the new Android App is finally ready for public beta. We're calling it v3.1.1.
The source code is all in github (for the brave), and there is an APK that can be side-loaded on Android devices, via this link:
http://www.openvehicles.com/downloads/OVMS.3.1.1.beta.apk
Functionality wise, it is pretty much on a par with the iOS App. All the core functions are there and, most importantly, the virtual car layer is complete and up-to-date. We've got HOMELINK support (yay!) as well as all the new function and parameter settings. It does have the artwork for the Volts and Amperas, but no Twizy yet (sorry, that slipped through the cracks, but we'll get it in the next build). The App should support any 2.3+ Android phone, and should scale its displays to pretty much any resolution out there. Tablet support is implemented by making them look like big phones.
There are a few things still incomplete (as previously pointed out at the start of this project):
No social group support on the map No cellular usage Some recent artwork missing (this is easy, and will come in the next beta release)
These will come, but weren't considered essential for this first release. The most important is to get the Android App up to the same level of functionality as the iOS App, so that they can both be brought forward.
I think if you want to install this, you first need to uninstall the Play store version. You will probably have to re-setup your vehicle as well. If you have problems with the beta, you can always uninstall it, and roll-back to the Play store version.
Please send feedback back to this list.
Regards, Mark.
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Thanks - I was wondering why the car images were so sharp... now I know. ________________________________ From: Mark Webb-Johnson <mark@webb-johnson.net> To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Sent: Friday, January 25, 2013 10:48 AM Subject: Re: [Ovmsdev] Android App Nikolay, Here are the contents: 8.0KAndroidManifest.xml
116KMETA-INF 1.3Mclasses.dex 13Mres 100Kresources.arsc
The App is 1.3MB, and the resources 13MB. Of that, 11MB are the graphics for the cars. I am working on a framework where we don't have to deliver those with the Apps (iOS and Android), but downloaded them from the web after installation. That will also allow us to upload new car graphics without having to change the apps. Regards, Mark. On 25 Jan, 2013, at 5:41 PM, Nikolay Shishkov <nshishkov@yahoo.com> wrote: Is there any good reason why the app size is 12MB?
________________________________ From: Mark Webb-Johnson <mark@webb-johnson.net> To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Sent: Friday, January 25, 2013 8:51 AM Subject: Re: [Ovmsdev] Android App
Just a note to acknowledge all the submissions I've had (both personal and to the list) on the Android App. Thanks for your help testing this.
I'm not individually acknowledging each feedback message, to keep the volume of messages on the list reasonable.
I am collecting all the feedback. Most of the points made so far are very quick and easy to fix. Mostly just cosmetic. I hope to get another update, with these fixes made, over the weekend.
So far, it looks like the App works just fine, and I don't think we need many more betas. I may just try to make the arrangements to get it into the Play store directly.
Regards, Mark.
Von: ovmsdev-bounces@lists.teslaclub.hk [mailto:ovmsdev-bounces@lists.teslaclub.hk] Im Auftrag von Mark Webb-Johnson
Gesendet: Montag, 21. Januar 2013 14:58 An: OVMS Developers Betreff: [Ovmsdev] Android App I'm glad to be able to (finally) announce that the new Android App is finally ready for public beta. We're calling it v3.1.1. The source code is all in github (for the brave), and there is an APK that can be side-loaded on Android devices, via this link: http://www.openvehicles.com/downloads/OVMS.3.1.1.beta.apk Functionality wise, it is pretty much on a par with the iOS App. All the core functions are there and, most importantly, the virtual car layer is complete and up-to-date. We've got HOMELINK support (yay!) as well as all the new function and parameter settings. It does have the artwork for the Volts and Amperas, but no Twizy yet (sorry, that slipped through the cracks, but we'll get it in the next build). The App should support any 2.3+ Android phone, and should scale its displays to pretty much any resolution out there. Tablet support is implemented by making them look like big phones. There are a few things still incomplete (as previously pointed out at the start of this project): * No social group support on the map * No cellular usage * Some recent artwork missing (this is easy, and will come in the next beta release) These will come, but weren't considered essential for this first release. The most important is to get the Android App up to the same level of functionality as the iOS App, so that they can both be brought forward. I think if you want to install this, you first need to uninstall the Play store version. You will probably have to re-setup your vehicle as well. If you have problems with the beta, you can always uninstall it, and roll-back to the Play store version. Please send feedback back to this list. Regards, Mark.
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
A feature which would be nice is for owners to add their own JPG image for his or her own car. Could be a nice personalisation touch... Sent from my iPhone On 25 Jan 2013, at 10:13, Nikolay Shishkov <nshishkov@yahoo.com> wrote:
Thanks - I was wondering why the car images were so sharp... now I know.
From: Mark Webb-Johnson <mark@webb-johnson.net> To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Sent: Friday, January 25, 2013 10:48 AM Subject: Re: [Ovmsdev] Android App
Nikolay,
Here are the contents:
8.0K AndroidManifest.xml 116K META-INF 1.3M classes.dex 13M res 100K resources.arsc
The App is 1.3MB, and the resources 13MB.
Of that, 11MB are the graphics for the cars.
I am working on a framework where we don't have to deliver those with the Apps (iOS and Android), but downloaded them from the web after installation. That will also allow us to upload new car graphics without having to change the apps.
Regards, Mark.
On 25 Jan, 2013, at 5:41 PM, Nikolay Shishkov <nshishkov@yahoo.com> wrote:
Is there any good reason why the app size is 12MB?
From: Mark Webb-Johnson <mark@webb-johnson.net> To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Sent: Friday, January 25, 2013 8:51 AM Subject: Re: [Ovmsdev] Android App
Just a note to acknowledge all the submissions I've had (both personal and to the list) on the Android App. Thanks for your help testing this.
I'm not individually acknowledging each feedback message, to keep the volume of messages on the list reasonable.
I am collecting all the feedback. Most of the points made so far are very quick and easy to fix. Mostly just cosmetic. I hope to get another update, with these fixes made, over the weekend.
So far, it looks like the App works just fine, and I don't think we need many more betas. I may just try to make the arrangements to get it into the Play store directly.
Regards, Mark.
Von: ovmsdev-bounces@lists.teslaclub.hk [mailto:ovmsdev-bounces@lists.teslaclub.hk] Im Auftrag von Mark Webb-Johnson Gesendet: Montag, 21. Januar 2013 14:58 An: OVMS Developers Betreff: [Ovmsdev] Android App
I'm glad to be able to (finally) announce that the new Android App is finally ready for public beta. We're calling it v3.1.1.
The source code is all in github (for the brave), and there is an APK that can be side-loaded on Android devices, via this link:
http://www.openvehicles.com/downloads/OVMS.3.1.1.beta.apk
Functionality wise, it is pretty much on a par with the iOS App. All the core functions are there and, most importantly, the virtual car layer is complete and up-to-date. We've got HOMELINK support (yay!) as well as all the new function and parameter settings. It does have the artwork for the Volts and Amperas, but no Twizy yet (sorry, that slipped through the cracks, but we'll get it in the next build). The App should support any 2.3+ Android phone, and should scale its displays to pretty much any resolution out there. Tablet support is implemented by making them look like big phones.
There are a few things still incomplete (as previously pointed out at the start of this project):
No social group support on the map No cellular usage Some recent artwork missing (this is easy, and will come in the next beta release)
These will come, but weren't considered essential for this first release. The most important is to get the Android App up to the same level of functionality as the iOS App, so that they can both be brought forward.
I think if you want to install this, you first need to uninstall the Play store version. You will probably have to re-setup your vehicle as well. If you have problems with the beta, you can always uninstall it, and roll-back to the Play store version.
Please send feedback back to this list.
Regards, Mark.
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
We've had this request a few times, and it would be great to do. I've been wondering if there is a generic way to do this, but not being in any way proficient with photoshop, I'm not sure if it is possible. Can we somehow have a base layer of the solid bits of the car, then an overlay layer colour mask. Then, somehow apply a colour slider to the colour mask layer to generate the different colour variations of the car? That way, we would only need 1 image for each car (ok, two images: a base layer and a colour layer), but could generate any colour we want in the App itself (including custom colours) just with a colour-wheel (as well as provide stock colour choices). Rather than the current approach of just an image filename, this would become a base vehicle type and RGB colour selection. Any photoshop experts know how to do this? That wouldn't solve the problem of custom car artwork, which we would still have to allow for, but would (a) dramatically reduce the number of images for each car required, and (b) allow for custom colour variations. Regards, Mark. On 25 Jan, 2013, at 6:33 PM, Nikki Gordon-Bloomfield <nikki@littlecollie.com> wrote:
A feature which would be nice is for owners to add their own JPG image for his or her own car. Could be a nice personalisation touch...
Sent from my iPhone
On 25 Jan 2013, at 10:13, Nikolay Shishkov <nshishkov@yahoo.com> wrote:
Thanks - I was wondering why the car images were so sharp... now I know.
From: Mark Webb-Johnson <mark@webb-johnson.net> To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Sent: Friday, January 25, 2013 10:48 AM Subject: Re: [Ovmsdev] Android App
Nikolay,
Here are the contents:
8.0K AndroidManifest.xml 116K META-INF 1.3M classes.dex 13M res 100K resources.arsc
The App is 1.3MB, and the resources 13MB.
Of that, 11MB are the graphics for the cars.
I am working on a framework where we don't have to deliver those with the Apps (iOS and Android), but downloaded them from the web after installation. That will also allow us to upload new car graphics without having to change the apps.
Regards, Mark.
On 25 Jan, 2013, at 5:41 PM, Nikolay Shishkov <nshishkov@yahoo.com> wrote:
Is there any good reason why the app size is 12MB?
From: Mark Webb-Johnson <mark@webb-johnson.net> To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Sent: Friday, January 25, 2013 8:51 AM Subject: Re: [Ovmsdev] Android App
Just a note to acknowledge all the submissions I've had (both personal and to the list) on the Android App. Thanks for your help testing this.
I'm not individually acknowledging each feedback message, to keep the volume of messages on the list reasonable.
I am collecting all the feedback. Most of the points made so far are very quick and easy to fix. Mostly just cosmetic. I hope to get another update, with these fixes made, over the weekend.
So far, it looks like the App works just fine, and I don't think we need many more betas. I may just try to make the arrangements to get it into the Play store directly.
Regards, Mark.
Von: ovmsdev-bounces@lists.teslaclub.hk [mailto:ovmsdev-bounces@lists.teslaclub.hk] Im Auftrag von Mark Webb-Johnson Gesendet: Montag, 21. Januar 2013 14:58 An: OVMS Developers Betreff: [Ovmsdev] Android App
I'm glad to be able to (finally) announce that the new Android App is finally ready for public beta. We're calling it v3.1.1.
The source code is all in github (for the brave), and there is an APK that can be side-loaded on Android devices, via this link:
http://www.openvehicles.com/downloads/OVMS.3.1.1.beta.apk
Functionality wise, it is pretty much on a par with the iOS App. All the core functions are there and, most importantly, the virtual car layer is complete and up-to-date. We've got HOMELINK support (yay!) as well as all the new function and parameter settings. It does have the artwork for the Volts and Amperas, but no Twizy yet (sorry, that slipped through the cracks, but we'll get it in the next build). The App should support any 2.3+ Android phone, and should scale its displays to pretty much any resolution out there. Tablet support is implemented by making them look like big phones.
There are a few things still incomplete (as previously pointed out at the start of this project):
No social group support on the map No cellular usage Some recent artwork missing (this is easy, and will come in the next beta release)
These will come, but weren't considered essential for this first release. The most important is to get the Android App up to the same level of functionality as the iOS App, so that they can both be brought forward.
I think if you want to install this, you first need to uninstall the Play store version. You will probably have to re-setup your vehicle as well. If you have problems with the beta, you can always uninstall it, and roll-back to the Play store version.
Please send feedback back to this list.
Regards, Mark.
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
I've spent some time trying this tonight. I took the basic twizy image, magic wand selected the paint colour part of the vehicle, then cut and paste that as a new layer. I then converted the paint colour layer to grayscale. Next, using the colorise filter, applied to the grayscale paint layer, I tried colouring it with a colour wheel. It worked beautifully. I could generate all the possible colours, and the paint highlights and shadows looked really good. I'll now see if I can do this programatically in iOS. If I can, we can dramatically reduce the amount of artwork required for each vehicle. Just a couple of base image layers and a 4-byte ARGB code for each standard vehicle (plus a colour wheel for users to choose their own custom colour). Proof of concept - some colour suggestions for Renault: Base grayscale layer: + = Colorised: Regards, Mark. On 25 Jan, 2013, at 8:13 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
We've had this request a few times, and it would be great to do.
I've been wondering if there is a generic way to do this, but not being in any way proficient with photoshop, I'm not sure if it is possible. Can we somehow have a base layer of the solid bits of the car, then an overlay layer colour mask. Then, somehow apply a colour slider to the colour mask layer to generate the different colour variations of the car? That way, we would only need 1 image for each car (ok, two images: a base layer and a colour layer), but could generate any colour we want in the App itself (including custom colours) just with a colour-wheel (as well as provide stock colour choices). Rather than the current approach of just an image filename, this would become a base vehicle type and RGB colour selection. Any photoshop experts know how to do this?
That wouldn't solve the problem of custom car artwork, which we would still have to allow for, but would (a) dramatically reduce the number of images for each car required, and (b) allow for custom colour variations.
Regards, Mark.
On 25 Jan, 2013, at 6:33 PM, Nikki Gordon-Bloomfield <nikki@littlecollie.com> wrote:
A feature which would be nice is for owners to add their own JPG image for his or her own car. Could be a nice personalisation touch...
Sent from my iPhone
On 25 Jan 2013, at 10:13, Nikolay Shishkov <nshishkov@yahoo.com> wrote:
Thanks - I was wondering why the car images were so sharp... now I know.
From: Mark Webb-Johnson <mark@webb-johnson.net> To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Sent: Friday, January 25, 2013 10:48 AM Subject: Re: [Ovmsdev] Android App
Nikolay,
Here are the contents:
8.0K AndroidManifest.xml 116K META-INF 1.3M classes.dex 13M res 100K resources.arsc
The App is 1.3MB, and the resources 13MB.
Of that, 11MB are the graphics for the cars.
I am working on a framework where we don't have to deliver those with the Apps (iOS and Android), but downloaded them from the web after installation. That will also allow us to upload new car graphics without having to change the apps.
Regards, Mark.
On 25 Jan, 2013, at 5:41 PM, Nikolay Shishkov <nshishkov@yahoo.com> wrote:
Is there any good reason why the app size is 12MB?
Neat! In the interests of accuracy, you'd technically have to change the colour of the seat cushions too -- but I suspect no-one (certainly me) wouldn't mind if what you suggest below is the best solution ;) *grins* Nikki. P.S. Twizy is due next week (or the week after) so we will have another test Twizy. Happy to try both beta firmware and iOS apps :) On 6 Feb 2013, at 14:30, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
I've spent some time trying this tonight.
I took the basic twizy image, magic wand selected the paint colour part of the vehicle, then cut and paste that as a new layer. I then converted the paint colour layer to grayscale.
Next, using the colorise filter, applied to the grayscale paint layer, I tried colouring it with a colour wheel. It worked beautifully. I could generate all the possible colours, and the paint highlights and shadows looked really good.
I'll now see if I can do this programatically in iOS. If I can, we can dramatically reduce the amount of artwork required for each vehicle. Just a couple of base image layers and a 4-byte ARGB code for each standard vehicle (plus a colour wheel for users to choose their own custom colour).
Proof of concept - some colour suggestions for Renault:
Base grayscale layer:
<PastedGraphic-8.tiff> + <PastedGraphic-9.tiff> = <PastedGraphic-10.tiff>
Colorised:
<PastedGraphic-11.tiff><PastedGraphic-12.tiff><PastedGraphic-13.tiff><PastedGraphic-14.tiff>
Regards, Mark.
On 25 Jan, 2013, at 8:13 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
We've had this request a few times, and it would be great to do.
I've been wondering if there is a generic way to do this, but not being in any way proficient with photoshop, I'm not sure if it is possible. Can we somehow have a base layer of the solid bits of the car, then an overlay layer colour mask. Then, somehow apply a colour slider to the colour mask layer to generate the different colour variations of the car? That way, we would only need 1 image for each car (ok, two images: a base layer and a colour layer), but could generate any colour we want in the App itself (including custom colours) just with a colour-wheel (as well as provide stock colour choices). Rather than the current approach of just an image filename, this would become a base vehicle type and RGB colour selection. Any photoshop experts know how to do this?
That wouldn't solve the problem of custom car artwork, which we would still have to allow for, but would (a) dramatically reduce the number of images for each car required, and (b) allow for custom colour variations.
Regards, Mark.
On 25 Jan, 2013, at 6:33 PM, Nikki Gordon-Bloomfield <nikki@littlecollie.com> wrote:
A feature which would be nice is for owners to add their own JPG image for his or her own car. Could be a nice personalisation touch...
Sent from my iPhone
On 25 Jan 2013, at 10:13, Nikolay Shishkov <nshishkov@yahoo.com> wrote:
Thanks - I was wondering why the car images were so sharp... now I know.
From: Mark Webb-Johnson <mark@webb-johnson.net> To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Sent: Friday, January 25, 2013 10:48 AM Subject: Re: [Ovmsdev] Android App
Nikolay,
Here are the contents:
8.0K AndroidManifest.xml 116K META-INF 1.3M classes.dex 13M res 100K resources.arsc
The App is 1.3MB, and the resources 13MB.
Of that, 11MB are the graphics for the cars.
I am working on a framework where we don't have to deliver those with the Apps (iOS and Android), but downloaded them from the web after installation. That will also allow us to upload new car graphics without having to change the apps.
Regards, Mark.
On 25 Jan, 2013, at 5:41 PM, Nikolay Shishkov <nshishkov@yahoo.com> wrote:
Is there any good reason why the app size is 12MB?
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Mark, I'm tempted to forward your color experiments to the german Twizy forum... :-) Try adding a 1-2 bit feathering on the magic wand selection for the colour mask, that should eliminate the remaining border. Regards, Michael Am 06.02.2013 15:30, schrieb Mark Webb-Johnson:
I've spent some time trying this tonight.
I took the basic twizy image, magic wand selected the paint colour part of the vehicle, then cut and paste that as a new layer. I then converted the paint colour layer to grayscale.
Next, using the colorise filter, applied to the grayscale paint layer, I tried colouring it with a colour wheel. It worked beautifully. I could generate all the possible colours, and the paint highlights and shadows looked really good.
I'll now see if I can do this programatically in iOS. If I can, we can dramatically reduce the amount of artwork required for each vehicle. Just a couple of base image layers and a 4-byte ARGB code for each standard vehicle (plus a colour wheel for users to choose their own custom colour).
Proof of concept - some colour suggestions for Renault:
Base grayscale layer:
+ =
Colorised:
Regards, Mark.
On 25 Jan, 2013, at 8:13 PM, Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>> wrote:
We've had this request a few times, and it would be great to do.
I've been wondering if there is a generic way to do this, but not being in any way proficient with photoshop, I'm not sure if it is possible. Can we somehow have a base layer of the solid bits of the car, then an overlay layer colour mask. Then, somehow apply a colour slider to the colour mask layer to generate the different colour variations of the car? That way, we would only need 1 image for each car (ok, two images: a base layer and a colour layer), but could generate any colour we want in the App itself (including custom colours) just with a colour-wheel (as well as provide stock colour choices). Rather than the current approach of just an image filename, this would become a base vehicle type and RGB colour selection. Any photoshop experts know how to do this?
That wouldn't solve the problem of custom car artwork, which we would still have to allow for, but would (a) dramatically reduce the number of images for each car required, and (b) allow for custom colour variations.
Regards, Mark.
On 25 Jan, 2013, at 6:33 PM, Nikki Gordon-Bloomfield <nikki@littlecollie.com <mailto:nikki@littlecollie.com>> wrote:
A feature which would be nice is for owners to add their own JPG image for his or her own car. Could be a nice personalisation touch...
Sent from my iPhone
On 25 Jan 2013, at 10:13, Nikolay Shishkov <nshishkov@yahoo.com <mailto:nshishkov@yahoo.com>> wrote:
Thanks - I was wondering why the car images were so sharp... now I know.
------------------------------------------------------------------------ *From:* Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>> *To:* OVMS Developers <ovmsdev@lists.teslaclub.hk <mailto:ovmsdev@lists.teslaclub.hk>> *Sent:* Friday, January 25, 2013 10:48 AM *Subject:* Re: [Ovmsdev] Android App
Nikolay,
Here are the contents:
8.0KAndroidManifest.xml 116KMETA-INF 1.3Mclasses.dex 13Mres 100Kresources.arsc
The App is 1.3MB, and the resources 13MB.
Of that, 11MB are the graphics for the cars.
I am working on a framework where we don't have to deliver those with the Apps (iOS and Android), but downloaded them from the web after installation. That will also allow us to upload new car graphics without having to change the apps.
Regards, Mark.
On 25 Jan, 2013, at 5:41 PM, Nikolay Shishkov <nshishkov@yahoo.com <mailto:nshishkov@yahoo.com>> wrote:
Is there any good reason why the app size is 12MB?
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
-- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
Am 06.02.2013 23:52, schrieb Michael Balzer:
Try adding a 1-2 bit feathering on the magic wand selection for the colour mask, that should eliminate the remaining border. ...px of course :-)
-- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
participants (4)
-
Mark Webb-Johnson -
Michael Balzer -
Nikki Gordon-Bloomfield -
Nikolay Shishkov