RANT (Mild): revZIP library

[Martin Koob]

The two bugs mentioned in this thread ( the revZip on Windows and the snapshot) sound like good candidates for the Top Ten Bugs survey that LiveCode Ltd.  had run a year or so ago.   It was a success it seemed and there was talk at the of running that survey again.

Panos, Mark,
Any plans for running round 2 of the Top 10 LiveCode Bugs  survey in the near future?

Martin

Sent from my iPhone

> On Oct 11, 2022, at 4:36 PM, Pi Digital via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> Hi Paul
> 
> I got affected by that and other win revzip issues too. I ended up parsing them through a shell script and using windows built in unzipper. Of course the downfall with that is a lack of feedback on progress which, for large files like this, requires a great deal of time to process and feedback is almost a necessity. I made the shell visible just so that the customer was aware of its progress. It was ugly in terms of UIX but it got us out of a short term hole. I hope you can get a more long term solution. 
> 
> I’m sure you’re capable of building the shell script but let us know if not. 
> 
> All the best
> Sean
> 
> 
> 
>> On 11 Oct 2022, at 20:37, Paul Dupuis via use-livecode <use-livecode at lists.runrev.com> wrote:
>> 
>> We just got bit by a 4+ year old bug (See https://quality.livecode.com/show_bug.cgi?id=20859) where the revZIP library on macOS can create and read ZIP archives over 2GB, BUT the Windows library can not.
>> 
>> We distribute our desktop research application as "cross-platform" for macOS and Windows and just had a researcher on macOS build a "package" (our term for a custom ZIP archive our LiveCode app can make of the researcher's data files) over 2GB and sent to their Window colleague who can NOT open it.
>> 
>> Yes, we walked the Windows researcher through unzipping the archive with WinZIP and accessing all the data files manually, but so much for the "elegance" of our app being cross-platform due to using LiveCode.
>> 
>> Now, do we add code to check the size and prohibit macOS users from creating "packages" over 2GB so if they are sent to a Windows researcher, they can be opened OR do we just warn the Windows researcher if the archive is over 2GB that they will not be able to open it? Neither is a good option.
>> 
>> This just makes us look bad.
>> 
>> Paul Dupuis
>> Researchware
>> 
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode