Re: Seeking clarification on which Android versions to build against in LC 9.5.0 (dp 1)

2019-06-04 Thread Sphere via use-livecode

According to Monte, it doesnot matter. Just hit the TEST button.
But probably you need to have downloaded the correct dependencies in 
Android Studio.

It sees against which it has to build.

But for the PAK standalone you need to decide for whcih processor you 
want to build.
the ARMv7 is the quad core as of android 4.1.2 according Mark, the ARM64 
are often octa-cores and of course 64bits.



Terry Judd via use-livecode schreef op 2019-06-04 04:53:

OK - so I'm trying out 9.5.0 (dp 1) and am loving the fact that we now
have a functional emulator (I'm using Android Studio) that we can use
to test Android apps. Thanks dev team! But, I'm not entirely clear
which processors I need to build against in order to publish the app.
I'm *not* distributing the app via a store but am instead just
allowing users (students) to download and install it directly. In the
past I just had to select to build against 'Android' but now there are
4 possible build options. I'm assuming that I can ignore both x86 ones
unless I am using the emulator, which leaves me with armv7 and arm64
(same as armv8?) to choose from. Do I need both, and if I do, how
might I go about advising our students which one they should download
and install?

Terry...

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: slow slower slowest scroll on Android

2019-05-30 Thread Sphere via use-livecode

This line: "Guess i did investigate good enough on the ARM versions."
should be: "Guess i did NOT investigate good enough on the ARM 
versions." forgot the NOT


request made: https://quality.livecode.com/show_bug.cgi?id=22118

Sphere via use-livecode schreef op 2019-05-30 19:09:

Thank you Mark , that makes it clear.

Guess i did investigate good enough on the ARM versions.


The arch index is a good idea, somtehing similair is also what i saw
inthe Google explanation on multiple APK's to have a version nr where
the position of the nr identifies what version and for what
architecture it is, like also commonly is used with serial nr's from
tv's for example.

I will create a feature request.

Thanks very much.

Best regards,

Jerry

Mark Waddingham via use-livecode schreef op 2019-05-30 18:09:

On 2019-05-30 19:54, Sphere via use-livecode wrote:

Perhaps for the older ARMv6 devices we may need 5 versions, but like
you said Google play will push the best APK option for the device. 
And

yes every APK needs to have a different/higher Version Code. And keep
in check which Version Code you used for which type of APK.


LiveCode only supports Android 4.x and above, and all devices which 
run
4.x have at the very least an ARMv7 processor - so there isn't any 
need
for a ARMv6 device build anymore (hence why it has been removed in 
9.5).



Is it possible as feature, that there can be a checkbox added, so you
can choose to have separate builds instead of one multiple build when
more then 1 build is chosen?


That would be quite a useful thing to have - perhaps a check-box which
'builds separate APKs' on the standalone settings pane. It could also
do something to derive a new versionCode (they all have to be 
different).

e.g.

APK-versionCode = S/B-specified-versionCode * 10 + arch-index

   arch-index = 0 (ARMv7), 1 (ARM64), 2 (x86), 3 (x86-64)

That would save having to specify (by hand) several different 
versionCodes

for each build.

Could you file an enhancement request for such an option, and we can 
see what

we can do.

Warmest Regards,

Mark.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: slow slower slowest scroll on Android

2019-05-30 Thread Sphere via use-livecode

Thanks,
i will go fiddling around to see if it works and else no glow :)

Regards,
Jerry

Mark Waddingham via use-livecode schreef op 2019-05-30 18:13:

On 2019-05-29 23:10, JJS via use-livecode wrote:

Wow, what a difference does it make.


*Phew*


Turned off the nice border glow around the grid, turned border off and
set it to zero (the latter won't make difference i guess.)


You could experiment by fiddling with the properties of control
"dgBackground" of your
DataGrid group. From memory, I believe that is a graphic, which sits
behind everything
else (within the Datagrid). At the very least, you should be able to
get the border
back, if not the glow (as it would be clipped away by the datagrid's
top-level group).

Warmest Regards,

Mark.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: slow slower slowest scroll on Android

2019-05-30 Thread Sphere via use-livecode

Thank you Mark , that makes it clear.

Guess i did investigate good enough on the ARM versions.


The arch index is a good idea, somtehing similair is also what i saw 
inthe Google explanation on multiple APK's to have a version nr where 
the position of the nr identifies what version and for what architecture 
it is, like also commonly is used with serial nr's from tv's for 
example.


I will create a feature request.

Thanks very much.

Best regards,

Jerry

Mark Waddingham via use-livecode schreef op 2019-05-30 18:09:

On 2019-05-30 19:54, Sphere via use-livecode wrote:

Perhaps for the older ARMv6 devices we may need 5 versions, but like
you said Google play will push the best APK option for the device. And
yes every APK needs to have a different/higher Version Code. And keep
in check which Version Code you used for which type of APK.


LiveCode only supports Android 4.x and above, and all devices which run
4.x have at the very least an ARMv7 processor - so there isn't any need
for a ARMv6 device build anymore (hence why it has been removed in 
9.5).



Is it possible as feature, that there can be a checkbox added, so you
can choose to have separate builds instead of one multiple build when
more then 1 build is chosen?


That would be quite a useful thing to have - perhaps a check-box which
'builds separate APKs' on the standalone settings pane. It could also
do something to derive a new versionCode (they all have to be 
different).

e.g.

APK-versionCode = S/B-specified-versionCode * 10 + arch-index

   arch-index = 0 (ARMv7), 1 (ARM64), 2 (x86), 3 (x86-64)

That would save having to specify (by hand) several different 
versionCodes

for each build.

Could you file an enhancement request for such an option, and we can 
see what

we can do.

Warmest Regards,

Mark.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: slow slower slowest scroll on Android

2019-05-30 Thread Sphere via use-livecode

Thank you Ralph and Monte,


i've read some things about multiple APK's on Google dev. "Lucky" we 
don't need to use the Google signing, it's optional. We can just use the 
Java keystore.


There is also mentioned what you say Ralph in respect of the different 
cpu and other possible dependencies.


Perhaps for the older ARMv6 devices we may need 5 versions, but like you 
said Google play will push the best APK option for the device. And yes 
every APK needs to have a different/higher Version Code. And keep in 
check which Version Code you used for which type of APK.


Also when Google signing is used there is an option to have dependencies 
build, but probably that is only useful for users of Android Studio.So 
then only the parts being needed are installed, as far as i understood 
it.



Thanks Monte for confirming it, that it will push the build upon the 
target architecture.


Is it possible as feature, that there can be a checkbox added, so you 
can choose to have separate builds instead of one multiple build when 
more then 1 build is chosen?



Indeed that would be a nice addition you proposed.


Regards,

Jerry

Monte Goulding via use-livecode schreef op 2019-05-29 23:27:
On 30 May 2019, at 7:10 am, JJS via use-livecode 
 wrote:


What will it push to the phone if all 4 options are selected? does it 
check what is connected?


Yes the deploy library (Test button) uses an adb command to detect the
target device architecture and just builds that no matter what you
have selected in the standalone settings. This means you can leave
armv7 and arm64 selected for release builds and the Test button will
deploy x86 if you are targeting an x86 emulator.

Note I just created this enhancement request to add the target
architecture in parenthesis after the target name in the menu.
https://quality.livecode.com/show_bug.cgi?id=22114


Cheers

Monte
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: slow slower slowest scroll on Android

2019-05-29 Thread Sphere via use-livecode
Strange is, when i opened the stack in 950dp1 and looked at the setting 
to set static, dynamic, scrolling. Container was selected, but when you 
click on it you can only choose from the 3 previous mentioned and not 
container anymore.

Unadorned (had to translate it first...) so no nice edge around it.
Ok will test tonight.

Thanks!

Monte Goulding via use-livecode schreef op 2019-05-28 23:23:
On 29 May 2019, at 5:49 am, JJS via use-livecode 
 wrote:


The DG2's where in container mode, now i've set them in scroller.



You should not fiddle with the layerMode of the datagrid. The scripts
already set the correct groups to container and scrolling. The actual
scrolling layerMode group in the datagroup is about 3 levels in with
its parents being container. As mentioned on other posts you need to
ensure the datagrid is unadorned (no border etc). Also if you have it
placed inside a group then that group must also be set to container
layerMode and be unadorned.

Cheers

Monte
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: IDE 9.0.4 and 9.0.5rc1 getting slow again on win10?

2019-05-23 Thread Sphere via use-livecode

Hi Jerry too,

indeed, but in the previous versions too like 904 and 905.
So i don't know exact if these are the same bugs or new ones which were 
solved.


Regards,
Jerry

Jerry Jensen via use-livecode schreef op 2019-05-22 21:44:

I hear a lot of memory leaks were fixed in 9.5.
- other Jerry

On May 22, 2019, at 2:41 PM, JJS via use-livecode 
 wrote:


Hi Matthias,


i only tried a few things to test some stacks for mobile-android and 
winx64 standalone and filed a few bug reports on it.


But did not extensively work with the editor yet, because of also the 
bugs.


Will try to test some tomorrow.


Regards,

Jerry

Op 22-5-2019 om 23:15 schreef Matthias Rebbe via use-livecode:
Jerry, did you already try the LC 9.5.0 DP1  64bit Windows. In case 
you´ve missed it, LC released a DP of 9.5.0 which not just supports 
64bit Windows standalones, but also 64bit Windows IDE.


Regards,
Matthias

Matthias Rebbe

free tools for Livecoders:
https://instamaker.dermattes.de 
https://winsignhelper.dermattes.de 



Am 22.05.2019 um 22:34 schrieb JJS via use-livecode 
>:


Hi,

anyone noticing that the IDE is getting slow again in win10-x64 
after working in a few scripts?


I notice it with 9.04 and 9.05rc1 while just typing, saving 
etcetera.


I hope it's not a regression of something, because it was solved.

Maybe i have to add LC again to Windows Defender.


Regards,

Jerry


___
use-livecode mailing list
use-livecode@lists.runrev.com 
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [ANN] Release 9.5.0 DP-1

2019-05-21 Thread Sphere via use-livecode
Oopsa, dis i read this wrong? and is the barcode library available for 
Indy?

Looks like it in the releasenotes (sometimes i read to quickly)

JJS schreef op 2019-05-20 17:40:

Nice, Nice, Nice!

We can test x86 Emulator now, superfast :)

Too bad the Android Barcode reader is Business, on Indy would be
great. I don't have that kind of money to spend for business
unfortunately.

But thanks! great that we now can play with it.


Op 20-5-2019 om 19:29 schreef Bob Sneidar via use-livecode:
These features look really nice! I'll play with it. Out of curiosity, 
has anyone addressed the nested behaviors for datagrids issue? The 
latest 9.0.4 does not seem to implement this.


Bob S


On May 20, 2019, at 10:04 , panagiotis merakos via use-livecode 
 wrote:


Dear list members,

We are pleased to announce the release of LiveCode 9.5.0 DP-1.

Developer Preview Release
=
Warning: this is not a stable release.  Please ensure that you back 
up your

stacks before testing them.


Getting the Release
===
You can get the release at https://downloads.livecode.com/livecode/ 
or via

the automatic updater.


Release Contents

LiveCode 9.5.0 DP-1 comes with more than 80 bugfixes. Moreover, more 
than

100 bugfixes, including several memory leak fixes, that were fixed in
LiveCode 9.0.x, are now merged into LiveCode 9.5.0 DP-1.

In addition, LiveCode 9.5.0 DP-1 includes several amazing new 
features:


- Windows 64 bit IDE & deployment support
- Static linked code libraries for iOS device builds
- Real boolean constants, Infinity constant
- Math operation refactor
- New Android Architectures
- New container layer mode
- New log command and logMessage property
- Implement filter where clause
- Progress, isSecure and allowUserInteraction features added to 
browser

widget
- New returnKeyType & keyboardType field property
- Improved sort international to support lots of additional locales
- Updated SQLite lib to the latest version (v3.28.0)
- Added support for URI filenames and JSON storage/retrieval in 
SQLite DBs

- Implemented modifier key state access for LCB (e.g. “key is down”)
- Implemented clip to path for LCB
- Several enhancements to Tree View Widget
- New mobileSetKeyboardDisplay and mobileGetKeyboardDisplay handlers
- mobileSetKeyboardReturnKey on android
- PDF Widget (Business Edition)
- Android Barcode Scanner widget (Business Edition)
- Mac status menu library


Known issues


- The Browser widget's native layer is not shown in some Linux 
distros with

Cinnamon window manager.
- The use of the Browser widget is not supported on Ubuntu 18.04 64 
bit LTS

yet.

The full release notes are available from:

http://downloads.livecode.com/livecode/9_5_0/LiveCodeNotes-9_5_0_dp_1.pdf


Feedback

Please report any bugs encountered on our BugZilla at
http://quality.livecode.com/

We have a forum available for discussing LiveCode Builder at
http://forums.livecode.com/viewforum.php?f=93

Have fun!
The LiveCode Team
--
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Android needs 64 bit builds

2019-05-10 Thread Sphere via use-livecode
a minor thing probably i noticed. The 9.1.0DP1 jumped to 9.5.0DP1. Is 
this a typo? or do have to wait longer? Just asking.



Mark Wieder via use-livecode schreef op 2019-05-06 23:26:

On 5/6/19 3:44 PM, Monte Goulding via use-livecode wrote:

Ah. OK. So the problem with running on the pi isn't with building 
form arm devices, but with interacting with the pi os?


I believe it is largely an issue of getting the build configuration 
and toolchains correct for cross compiling for armv6hf. Although given 
Pi 3s are arm64 but Raspbian is still armv6hf I guess we would need a 
build for a number of archs (armv6hf, armv7, arm64) depending on what 
OS people are running.


For us there is the extra step of getting it all setup on vulcan to 
build and package etc.


Ouch. I didn't realize raspbian was still armv6hf, although it makes
sense for older hardware. That thickens the plot a bit. I'd certainly
settle for an arm64-only build of the LC engine, but shoehorning it
into an arm6hf os seems dicey.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: acceleratedRendering bugs

2019-03-12 Thread Sphere via use-livecode

Thanks for your reply Randy.
Nice app you made.

I noticed it is sensitve and that the DG2 group with images and text got 
even slower.
So i have to play some more to get it more smoother as it looked more 
cloggy when scrolling.
i can try the max and see if it will have some effect. I also tried it 
on BlueStacks after i saw the hint from Richmond.
That should be very fast, as we have to wait on 9.1 before we can use 
the fast x86 emulator.

But even in BlueStacks the DG is slow and cloggy.

Randy Hengst via use-livecode schreef op 2019-03-12 11:38:

My work is only with  iOS. So, no comments about Android…

But, I found while working a recent iPad app (with many moving
controls) that I needed to adjust the layerMode to dynamic and back to
static after the move.

I also increased the compositorCacheLimit as you noted… only I went up
to 256*1024*1024.
I made this adjustment in the startUp handler.

I even needed to up the compositorCacheLimit while working in the IDE.
I made that adjustment in the message box.

I didn’t make any changes relative to compositorTileSize or 
compositorType.


The app I was developing when I first started making these adjustments
is free (if that will help understand my context) ….
here is the Apple App Preview page:
https://itunes.apple.com/us/app/begotten/id1431461736?mt=8


be well,
randy
www.classroomFocusedSoftware.com


On Mar 11, 2019, at 4:13 PM, JJS via use-livecode 
 wrote:


i was playing a bit with the separate command you can use instead of 
acceleratedrendering (on Android mobile)


compositorTileSize,layerMode,compositorType,compositorCacheLimit

and noticed that setting compositorType to opengl for android causes 
the black out screen


i'm not sure yet about compositorTileSize what it does on speed

the compositorCacheLimit needs to be big like 64*1024*1024 for 64MB 
according calculation in the dictionary, if you set it small it gets 
slow updated


now i'm not sure if i need the separate commands to be set empty in 
the closecard (to prevent upshifting on other cards when using 
keyboard) or that setting the acceleratedrendering to false would be 
enough.


till now i set the accelerated rendering on and off depending if i 
need keyboard on the card



anyone else have experience with these commands?



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Colorizing line only works once?

2019-02-25 Thread Sphere via use-livecode
Solved it another way which also perfectly fits the idea by following 
this:

https://forums.livecode.com/viewtopic.php?t=13025#p62226
Thanks to Sri.


JJS via use-livecode schreef op 2019-02-24 11:46:
Just did some tests. with the test stack from the lesson and with my 
own stack


It seems there is something strange with my indexes.

I would think that if a DG is emptied and then filled again that the
index would start at 0 or 1 again.

It seems not the case and i see random numbers

so i have to figure out why this is happening


Op 23-2-2019 om 19:09 schreef JJS via use-livecode:

Hello,


i used this lesson: 
http://lessons.livecode.com/m/datagrid/l/7332-how-can-i-colorize-individual-lines-in-a-table


to colorize a few lines in my DG. When in one column the value is 1 
then the line stays black, when it is a 2 the line becomes red.


Now it just works :)...but only 1 time.


After repopulating the DG with stuff from an other category it does 
not do it although the same sequence is being done.


It only does it again when i reload the stack in the IDE.


Any idea what i can do?

Refresh index or line does not help


Thanks for any help.


Jerry


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: LC902 and LC901 Hang with Answer (was Crash)

2019-02-20 Thread Sphere via use-livecode
And i double check if i did not turn off messages, sometimes i need to 
double click it to get a good reaction. But that's separate from these 
issues.


J. Landman Gay via use-livecode schreef op 2019-02-19 22:30:

On 2/19/19 3:00 PM, JJS via use-livecode wrote:
But just yet i also had a weird issue that it would not post or 
receive, restarted LC and worked again


it's making me nuts


Me too. Sometimes I go back to an earlier version of LC for a while if
I don't need new features. There's no recipe for the problem either,
it's always something random.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: The coming of SVG

2017-11-06 Thread sphere via use-livecode
I agree with Rick and Jacque.
Something combined with SVG or vector-image is better.
Anyone working with images knows (or learns very fast) what svg's are.
Picture is to much linked to Photo (for me it is the same), if you take a 
picture the result is a photo.
I would not think for picture at all if i was looking for svg

and i disagree on the word FRAME as FRAME is part of video and movie
that would make totall confusion

a few suggestions:
Figure
Drawing
Form
Illustration
Model
Reflection
Replica
Carbon
Simulacre
Similitude
Representatio
Appearance
Semblance
Shape
Illiusion
Vision
Visualisation
Envision
Impression 

_
Sent from http://runtime-revolution.278305.n4.nabble.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode