Re: File - read from EOF

[Jan Schenkel via use-livecode]

On Sun, 5/28/17, JB via use-livecode  wrote:
>
> Subject: File - read from EOF
> To: "How to use LiveCode" 
> Cc: "JB" 
> Date: Sunday, May 28, 2017, 2:23 AM
> 
> I want to read a file as binary of any
> size but as crazy as it sounds I want
> to read in sections form the EOF and
> stop at the beginning of the file
> instead
> reading from the start to EOF.
> 
> I have no problems opening, reading
> and
> closing files or reading in sections.
> 
> Does anyone know the easiest way
> to determine when I reach the start
> of the file similar to using EOF to
> stop reading at the end of the file?
> 
> JB
> 

Hi JB,

You could always read the file straight into a variable and then check the 
number of bytes.
But if it's a very large file then you could run out of memory space (at least 
until we get a 64-bit engine on Windows)

>From your description, it sounds like you don't need the entire content and 
>want to cruise around the file on disk to extract bits.
In that case, you can quickly determine the file size using the 'detailed 
files' functionality.
I wrote a utility function for that a long time ago; here it is:

--

function qrtUtil_FileSize pFilePath
   local tFolderPath, tFileName
   set the itemDelimiter to slash
   put item 1 to -2 of pFilePath into tFolderPath
   put item -1 of pFilePath into tFileName
   local tDefaultFolder, tDetailedFiles
   put the defaultFolder into tDefaultFolder
   set the defaultFolder to tFolderPath
   put the detailed files into tDetailedFiles
   set the defaultFolder to tDefaultFolder
   filter tDetailedFiles with (tFileName & ",*")
   set the itemDelimiter to comma
   return item 2 of tDetailedFiles
end qrtUtil_FileSize

--

HTH,

Jan Schenkel.

=
Quartam Reports & PDF Library for LiveCode
www.quartam.com

= 
"As we grow older, we grow both wiser and more foolish at the same time."  (La 
Rochefoucauld)

___
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: Will LiveCode run an x86 android device?

[Jan Schenkel via use-livecode]

On Sat, 4/29/17, Richard Gaskin via use-livecode 
 wrote:
>
> [snip]
> 
> I had thought one of the reasons Android uses the Dalvik and ART
> VMs is because they're VMs, separating the APIs from processor architectures.
> 
> If so, then the LC engine for Android is bytecode rather than machine 
> code, and as such should run on either processor architecture, no?
> 

Hi Richard et al,

Actually, LiveCode was not rewritten in Java, nor compiled to Dalvik/ART 
bytecode.
The engine for Android is largely written in the same C++ as for the other 
platforms.
And then compiled to native ARM instructions for the specific Android variant 
of Linux.

Most Android apps are written in Java, and occasionally tap into native code 
via the Android Native Development Kit (NDK).
Android NDK is the platform-specific implementation of the Java Native 
Interface (JNI).
Android has multiple Application Binary Interfaces (ABIs) to support various 
architectures.

ARM Android apps that don't need access to native code can run 'as is' on x86 
Android devices.
Those that do need native code, will have to compile separate builds (and may 
bundle them into a single 'fat' APK).
Or they have to rely on the ARM-on-x86 emulation feature named Houdini.

So LiveCode is a bit of an outsider, as the apps it produces spend little time 
in the Dalvik/ART virtual machine.
All scripts run in the native portion, and events are funneled from the VM into 
native code to be handled there.

All this to say: if we want native x86 Android apps, then the LiveCode team 
will have to crank up the compilers again...

Jan Schenkel.

=
Quartam Reports & PDF Library for LiveCode
www.quartam.com
=
"As we grow older, we grow both wiser and more foolish at the same time."  (La 
Rochefoucauld)

___
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: Quartam reports blank page on Sierra Macosx

[Jan Schenkel via use-livecode]

Hi Josep,

I'm always happy to help, but if you post on the forum on Saturday afternoon, 
then you might not get an answer by Sunday afternoon...
Can you provide a little more background infoàrmation, because I can't quite 
follow what problem you are encountering.
Some screenshots or perhaps a screen recording would definitely help me to 
understand the issue.

Let's continue this over on http://forums.quartam.com so the good folks on the 
use-livecode list can concentrate on the LiveCode bits :-)

Cheers,

Jan Schenkel.

=
Quartam Reports & PDF Library for LiveCode
www.quartam.com

=
"As we grow older, we grow both wiser and more foolish at the same time."  (La 
Rochefoucauld)


On Sat, 2/4/17, Josep Maria Yepes Montardit via use-livecode 
 wrote:

 Subject: Quartam reports blank page on Sierra Macosx
 To: use-livecode@lists.runrev.com
 Cc: "Josep Maria Yepes Montardit" 
 Date: Saturday, February 4, 2017, 6:37 AM
 
 Hi,
 
 I need help with Quartam Reports. Since Sierra MacOSX when
 you print preview any report a blank page left on desktop
 making unusable these zone until close the app.
 Since now was impossible contact with Quartam support.
 Any idea if Quartam still exist or is supported?
 Alternatives?
 
 Salut,
 Josep M
 
 
 ___
 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