Studio 11 library conversion

Tue Nov 21 21:19:35 UTC 2023

Hi Andy,I agree, and that is what I do, develope at the lowest build.Moving backwards has always been an issue.What  happens to code that only exists in later builds and you downgrade the library version by changing the first byte...Whichever way you move a library backwards, when developing on a later version than your intended target, you have to make sure you do not use later features. There are similar issues, although not as saviour but performance impacting, when developing in an older version and you have to code/develope a work around for an issue fixed in a later build. Further, if not careful, those work arounds get left in place long after everyone has moved to the versions that fixed the initial problem. I guess it all comes down to the developer being careful, paying attention to the features available in their development environment and those available in the target environments, keeping and using documentation for their code. The list goes on.Not really an answer...Kind regards Phil
-------- Original message --------From: TBS <andyh at totallybrilliant.com> Date: 21/11/2023  20:10  (GMT+00:00) To: OmnisDev List - English <omnisdev-en at lists.omnis-dev.com>, Philip Tulett <philip.tulett at pdq-networks.com> Cc: philip.tulett at pdq-networks.com, Mike Matthews - Omnis <omnis at lineal.co.uk>, Kelly Burgess <kellyb at montana.com> Subject: Re: Studio 11 library conversion 

Phil

My theory has always been that if you are supporting older versions, then developing in those versions ensures your current code works ok at that base level…..

Always seems to be ok (well 99.99%) going forwards but not always with new code going backwards !

But your JSON export/import sounds like it could be a way around it - not sure what happens if you have code that is latest versions only though ??

Andy

On Nov 21, 2023, 2:25 PM -0500, Philip Tulett <philip.tulett at pdq-networks.com>, wrote:

Hi Mike,
I only use Windows, but...
could you not develop on new Studio, and then export library to json, then import library into older Omnis, sending that library to your older clients?
Obviously extra steps to take, but so would developing in a vm running an older os.

Just a thought 

Kind regards Phil 

-------- Original message --------
From: Mike Matthews - Omnis via omnisdev-en <omnisdev-en at lists.omnis-dev.com>
Date: 21/11/2023 15:56 (GMT+00:00)
To: Andy Hilton <andyh at totallybrilliant.com>
Cc: Mike Matthews - Omnis <omnis at lineal.co.uk>, OmnisDev List - English <omnisdev-en at lists.omnis-dev.com>, Kelly Burgess <kellyb at montana.com>
Subject: Re: Studio 11 library conversion

Hello Andy,

Aye, but you can’t go backwards if your dev machine is running OSX Sonoma and v10.22 build 32066 for those running older version of Studio.

Also not using:
Do $libs.$add(Path,,,,ECode,EText) Returns rLib
There is no option for conversion sadly.  I have asked for it.

Thanks

Mike

On 21 Nov 2023, at 15:14, TBS <andyh at totallybrilliant.com<mailto:andyh at totallybrilliant.com>> wrote:

Caution: This is a message which has originated from outside the organisation. Ensure the sender is trusted and the content is safe before opening links or attachments.

Never forget when opening libraries under an Omnis notation command you can always auto-convert them - so you can maintain one set of base libraries providing your code includes : Open library (Do not close others,Enable conversion by runtime,Convert without user prompts)

Andy Hilton
Totally Brilliant Software Inc
Phone (US) : (863) 409 4870

On Nov 21, 2023, 2:04 AM -0500, Mike Matthews - Omnis via omnisdev-en <omnisdev-en at lists.omnis-dev.com<mailto:omnisdev-en at lists.omnis-dev.com>>, wrote:
Hello Kelly,

So the reason for jumping the values is this:

The new build of v10.22 32066, uses one of those numbers. You have to convert your library to run this build, and it appears you can’t go back. So a bit like from v8 to v10, and it meant you had a new code.

The new build of v11 35659 has the new library format, so it had a new code as well.

So if you develop using v10, and need the new security property, and OSX Sonoma compatibility, you have to convert all of your users to the same v10.22 build 32066, or convert the libraries before use for those users. Otherwise develop two sets of libraries of course.

Hmmm...

Mike Matthews

Lineal Software Solutions
Commercial House, The Strand<x-apple-data-detectors://1/1> Barnstaple, Devon, EX31 1EU<x-apple-data-detectors://1/1>

omnis at lineal.co.uk<mailto:omnis at lineal.co.uk><mailto:mike.matthews at lineal.co.uk>

www.lineal.co.uk<http://www.lineal.co.uk><http://www.lineal.co.uk/>

www.sqlworks.co.uk<http://www.sqlworks.co.uk><http://www.sqlworks.co/>

On 9 Oct 2023, at 06:38, Kelly Burgess <kellyb at montana.com<mailto:kellyb at montana.com><mailto:kellyb at montana.com>> wrote:

Caution: This is a message which has originated from outside the organisation. Ensure the sender is trusted and the content is safe before opening links or attachments.

I hadn't seen it mentioned before, but the latest Studio 11 35659 release converts libraries from the prior Studio 11 release. It takes an odd jump, too... I've adjusted my Applescript as follows:

if byteOne = 57 then -- 0x39
set dialogMsg to file_ & " is a Studio 11.0.x library."
end if
-> if byteOne = 60 then -- 0x3C
-> set dialogMsg to file_ & " is a later Studio 11.0.x library."
-> end if

As you see, they've skipped 58 and 59. After a long, long history of just incrementing by 1, this time they added 3.

The What's New PDF explains:

"Class Locking and Library Conversion
In order to enhance the integrity and security of deployed Omnis Studio libraries, the mechanism used to lock classes in a private library has changed in Omnis Studio Revision 35659."

FYI,

Kelly
_____________________________________________________________
Manage your list subscriptions at https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.omnis-dev.com&c=E,1,0dv8kPQTVAoW7e1chD0kbjcLnbVNVBJ-CK2f5pRfI9ngFdl_95LNV2R4mnUtfoykYJ1K_OK3FmU1yHvLirQqf4ZYrblZ80Ka9_A-YZjG-frEqiQzwYChQg,,&typo=1
Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com

_____________________________________________________________
Manage your list subscriptions at https://lists.omnis-dev.com
Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com

_____________________________________________________________
Manage your list subscriptions at https://lists.omnis-dev.com
Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com