The API has changed (has become more strict). Apps have to adhere to the
new specifications, or the Google Play Store won't allow them to be
downloaded to "Android Wear" compatible watches. It works with my watch
because it isn't recognized as a true Android Wear device, but instead as a
tablet.
Roger Eller wrote:
> On Mon, Mar 16, 2015 at 10:56 AM, Richard Gaskin wrote:
>
>> Roger Eller wrote:
>>
>> > Does it have to use the LC 7 engine? Why not use what fits, LC 6?
>>
>> There is no build of the v6 engine that runs on wearables.
>>
> Ummm... http://livecode1001.blogspot.com/search?q=
On Mon, Mar 16, 2015 at 10:56 AM, Richard Gaskin wrote:
> Roger Eller wrote:
>
> > Does it have to use the LC 7 engine? Why not use what fits, LC 6?
>
> There is no build of the v6 engine that runs on wearables.
>
>
Ummm... http://livecode1001.blogspot.com/search?q=Android+Wear
Just luck I gue
Roger Eller wrote:
> Does it have to use the LC 7 engine? Why not use what fits, LC 6?
There is no build of the v6 engine that runs on wearables.
What "fits" is more than size.
Fixes are backported to v6.7 as a courtesy to those who haven't yet
migrated their work to the current engine, but
I have built an app that uses accelerometer from LC7 to Google Glass, and it
worked ok. That doesn’t mean that watch specific features (e.g., heart rate)
will work without new functions in LiveCode.
> On Mar 16, 2015, at 8:03 AM, Roger Eller wrote:
>
> Does it have to use the LC 7 engine? Wh
Does it have to use the LC 7 engine? Why not use what fits, LC 6? Like I
said, my early watch accepts LC apps built with 6, but a modern Android
Wear watch has a more strict definition of what is allowed. OTOH, if
Raspberry Pi handles LC 7, a smart watch should - based on hardware specs
alone.
O
Looks like that will be much simpler to implement because it's a full app
that's installed on the watch. Still I think there will be issues with app size
because of the size of the LC 7 engine.
On 16 Mar 2015, at 12:07 pm, Roger Eller wrote:
> If it's not feasible for WatchKit, then how about
If it's not feasible for WatchKit, then how about the Android Wear API?
On Mar 15, 2015 8:08 PM, "Monte Goulding"
wrote:
>
> On 16 Mar 2015, at 9:10 am, Roger Eller
> wrote:
>
> > I look forward to hearing from Runtime Revolution on their plans of
> support
> > for these new devices.
>
> I hadn
On 16 Mar 2015, at 9:10 am, Roger Eller wrote:
> I look forward to hearing from Runtime Revolution on their plans of support
> for these new devices.
I hadn't looked at it until you're post prompted me... It doesn't look like it
would be all that easy for LiveCode to support WatchKit as only U
I haven't looked at WatchKit yet, but I have looked into LC apps for smart
watches running AndroidWear OS. Previously, a lite Android 4.4w (KitKat
for wearables) existed, until the official API was announced in January,
2015.
https://developer.android.com/wear
I look forward to hearing from Runt
10 matches
Mail list logo
