I guess I never answered the original question: The editor type isn't a LCB thing. Those are a part of the IDE. Here is the path from the open source repository: .../livecode/ide/Toolset/palettes/inspector/editors/ You should also be able to find them in your local install of LC. /Applications/LiveCode/LiveCode 9.6.9 (rc 1).app/Contents/Tools/Toolset/palettes/inspector/editors/ I agree that they should be documented somewhere. Looking at the names there, most that you would use are probably fairly evident.
The LiveCode Builder Style Guide/Widget specific guidelines covers the 4 entries needed to use many of the PI editors. There is one in a widget that could be useful though "user_visible" - this property is not displayed in the PI but is available to get/set. "options" looks to be specific to the "enum" editor. The Extending Livecode Guide covers the 4 that are needed for the widget as a whole. It does look like there are a few additional ones used in widgets that are not mentioned that should be included in the docs (os, svgicon, preferredsize, userVisible, _ide). I tend to be fairly adept at reading and understanding code - even if I don't know the syntax well enough to write it. So I didn't really read the documentation to learn LCB (but referenced the syntax and style guide as needed), but read the widgets that I was working on. As such, the things you are having difficulty finding didn't really impact my efforts. I was mainly extending the widget and was just copying existing code as a model when adding things (properties and handlers). About the only thing that really tripped me up was aliased properties. You have to define the main property and then alias works. If you define the alias, then it doesn't work (TreeView widget - scroll vice vscroll). Considering all of this, I consider all of the included LCB source code as part of the documentation for LCB. I'll add some comments to your "issues" Thanks, Brian On Sat, Sep 10, 2022 at 3:49 PM Mike Kerner via use-livecode < use-livecode@lists.runrev.com> wrote: > I was about to call you out, too, Brian. > I started trying to work with LCB several years ago, kept slamming into > things that weren't documented, and decided I had better things to do with > my time. > Now I'm back at it, but I don't think it should be such a black hole, > especially when I put it down for a couple of months and then want to get > back into it. > If we want other people to take the plunge, and maybe invent cool stuff > using it, something better than what exists, now, should exist. > > On Sat, Sep 10, 2022 at 3:36 PM Brian Milby via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > Honestly the way I learned the most about LCB was working on the LC > > widgets. There is plenty of example code there but you just have to > spend > > time understanding what you are reading. > > > > Brian Milby > > br...@milby7.com > > > > > On Sep 10, 2022, at 2:01 PM, Mike Kerner via use-livecode < > > use-livecode@lists.runrev.com> wrote: > > > > > > I was trying to work on Ralph's improvements on the navBar and I kept > > > getting bitten by the thin documentation of lcb, so for my own > benefit, i > > > started a wiki and issues list to fill in the blanks > > > Please help me learn lcb by adding to both of these. > > > The wiki: https://github.com/macMikey/LCB-missing-manual/wiki > > > The issues: https://github.com/macMikey/LCB-missing-manual/issues > > > > > > > > >> On Fri, Sep 2, 2022 at 8:42 PM Mark Wieder via use-livecode < > > >> use-livecode@lists.runrev.com> wrote: > > >> > > >>> On 9/2/22 16:54, Brian Milby via use-livecode wrote: > > >>> Did a simple test with 819kb json file: > > >>> - JSON Library / LCB 5400 ms > > >>> - PhotonJSON / LCS 400 ms > > >>> - mergJSON / extension 250 ms > > >> > > >> That's impressive. Monte's external is written in C, so that's as > close > > >> to bare metal as we're gonna get. > > >> > > >> -- > > >> Mark Wieder > > >> ahsoftw...@gmail.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 > > >> > > > > > > > > > -- > > > On the first day, God created the heavens and the Earth > > > On the second day, God created the oceans. > > > On the third day, God put the animals on hold for a few hours, > > > and did a little diving. > > > And God said, "This is good." > > > _______________________________________________ > > > 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 > > > > > -- > On the first day, God created the heavens and the Earth > On the second day, God created the oceans. > On the third day, God put the animals on hold for a few hours, > and did a little diving. > And God said, "This is good." > _______________________________________________ > 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