OpenXTalk Forums

Am I to understand that a 'Custom Control' might be another name for a LiveCode widget (as opposed to an LCB widget), or a fancy group of other controls with an over-arching group script?

LiveCode made a thing a short while ago about an upcoming thing to make widgets in LC without LCB.

Skids wrote: ↑Thu Aug 15, 2024 3:53 pm https://livecode.com/oxy_testimonial/bu ... ilder-lcb/

Its a blank page so I guess they changed their minds.

It treats the grouped controls as if there a single object (that might be in a IDE script library that's doing that special treatment, or maybe they added support to the Engine, can't be sure but a script library could do this too I'm sure).

This repository contains widgets that I have made available to the community.

tperry2x wrote: ↑Fri Aug 16, 2024 8:39 am Have a look here:
https://github.com/trevordevore/livecode-extensions

This repository contains widgets that I have made available to the community.

Trevor Devore
In fact, might be an idea to grab all these "Community Widgets" while they are still there.

If it does "disappear", you can also try here.

////////////////////////////////////////////////////////////////////////////////

// Packages are a collection of modules which share a common set of foreign
// code and resources.
//
// When a package is loaded into memory, all its modules are loaded also making
// them available in the module namespace and accessible through the module
// functions.
//
// A package loaded from a particular file, or with a particular name can only
// be loaded once - if an attempt is made to load a package from a file and that
// package has the same name as a loaded package it is an error. If an attempt
// is made to load a package by name and such a package is already loaded it just
// returns that package.
//
// Ensuring modules are usable is done lazily - either by an attempt to create
// a module instance, or by explicitly ensuring via the appropriate API.
//
// Packages can be unloaded from memory, however they are not completely removed
// until it is possible to do so - i.e. until there are no instances of any module
// within the package in use.

////////////////////////////////////////////////////////////////////////////////
// Packages are a zip archive with the following structure:
//   <root>/
//     manifest.xml
//     module.lcm
//     support/
//       <files for the IDE / store etc.>
//     modules/
//       <compiled submodule files>
//     symbols/
//       <compiled module debug info>
//     resources/
//       <shared resources>
//     code/
//       <compiled foriegn code>
//     source/
//       <original source code>
//     docs/
//       <docs tree>

Trevor's examples Widget set are very good to start from.
He also has his own Widget building tutorials on his website:

Skids wrote: ↑Sat Aug 17, 2024 7:39 am

Trevor's examples Widget set are very good to start from.
He also has his own Widget building tutorials on his website:

Thanks for the links. Trevor helped me out with my Calendar Reader extension with issues with callbacks that I was (and is) having when trying to get the user to grant permission to access the EkEventStore. I say "is" because it no longer works in the LC IDE when running under Sonoma as Apple have depreciated some commands and require new lines in two of the plist file in the IDE. These are simple to edit but then MacOS reports that the IDE is broken because of the changes made (SIP strikes!!!).

Full details and examples plus an ugly solution are all detailed here https://quality.livecode.com/show_bug.cgi?id=24054

The issues I have with LiveCodeBuilder Widgets are that when compared to a Custom Control Groups, widgets are complex to build and require that a new programming language be learnt. Yes it's like script but it is different and as has been. However they do provide a method of extending LC/Xtalk and apparently offer some technical advantages.

The real problems for me start when I use a commercial widget in a stack and then I want some help. In my example I used a date picker which was part of the summer bundle from Run Rev in a test stack written to debug my EkEventKit extension. The only indication that the widget was not free to use when I started getting reports that my test stack was not working as expected. I realise that the community has paid for locked library stacks for years but somehow it seems simpler to fall into the trap with a widget that appears in the tools palette.

Yesterday I downloaded a number of Community Widgets and along the way read some posts by HH in 2020 detailing why he was ceasing to produce widgets : I paraphrase but he felt his suggestions about LCB were being ignored and his bug reports left unresolved.

I also found a thread where LC and Python user Stam details the issues he ran into trying to build a new script widget. Simply it caused a slow down which attracted the attention of LC. However they were beaten to the solution by Bernd. See https://forums.livecode.com/viewtopic.p ... te#p225331 and an earlier post : https://forums.livecode.com/viewtopic.p ... te#p224936

I might be able to help you with your Apple EventKit wrapper, if you share it here, explain the problem with it, like what got deprecated by Apple that broke it.

Skids wrote: ↑Fri Aug 23, 2024 4:26 pm

I might be able to help you with your Apple EventKit wrapper, if you share it here, explain the problem with it, like what got deprecated by Apple that broke it.

Wildo once I return from holiday sometime next week. From memory when running on Sonoma the SIP calls require that the IDE contain a new line in the two plist files. While simple to add (its just a text file) editing the plist file then brakes the SIP of the IDE meaning it will not run: a this application is broken alert gets posted. The work around seems to be to create a new signature file (not sure if thats the correct term) and all is well.