antime, for all of you that are interested, please stop over at
the LCB Missing Manual repo on github (
https://github.com/macMikey/LCB-missing-manual). The wiki is an attempt to
build a real LCB manual. The issues are for all of the things that get you
stuck, so please post. That will help the
On 17/09/2022 08:54, Jacques Clavel via use-livecode wrote:
point 6. maybe potential for future performance gains :
- But today LCB is surprisingly less efficient (/3) than LCS (???)
Yes, at first glance it is surprising; typed variables etc. *should*
make it possible to be more efficient. An
point 6. maybe potential for future performance gains :
- But today LCB is surprisingly less efficient (/3) than LCS (???)
JC
Le sam. 17 sept. 2022 à 01:35, Alex Tweedly via use-livecode <
use-livecode@lists.runrev.com> a écrit :
>
> On 15/09/2022 16:37, Ralph DiMola via use-livecode wrote:
> >
On 15/09/2022 16:37, Ralph DiMola via use-livecode wrote:
Docs aside... I still think that widgets and lcb is one of best additions to
LC. Community collaboration like this will make for better documentation and
more new/improved widgets. A robust library of widgets can only help LC to
penetrat
By the way, we updated it, again, this morning, because, we're like little
kids now that we're starting to crack the code on this thing. It's nothing
too exciting, today, but it's better than it was, yesterday, including
fixing the copyright header - which was my error.
Here's what happened on the
Sorry, I confused things by using the word "outdated". I wasn't
referring to the date in the copyright statement, but to the fact that
it says "Livecode is free software [... GPL]", and "this file is part
of Livecode", and implications that may have on the license situation
for the widget and
Legally the only date that matters is the date of creation. Almost everyone
adds the current date as well, and I keep trying to talk my clients out of
it but they won't listen. Then I have to keep updating the copyright
string, knowing it doesn't matter, but if I don't the app looks old and
uns
On 15/09/2022 15:44, Mike Kerner via use-livecode wrote:
What's NavRAD? It's a better version of LiveCode's NavBar widget.
Why "RAD"? Cos Ralph A DiMola said so, since he added the first two nifty
updates to it:
I see the code has an outdated copyright statement, which would (I
think) current
Docs aside... I still think that widgets and lcb is one of best additions to
LC. Community collaboration like this will make for better documentation and
more new/improved widgets. A robust library of widgets can only help LC to
penetrate the market. If only we had these when I started...
Shout ou
ber 15, 2022 10:45 AM
To: How to use LiveCode
Cc: Mike Kerner
Subject: Re: NAVRAD was: lcb missing manual
What's NavRAD? It's a better version of LiveCode's NavBar widget.
Why "RAD"? Cos Ralph A DiMola said so, since he added the first two nifty
updates to it:
* an autoHil
What's NavRAD? It's a better version of LiveCode's NavBar widget.
Why "RAD"? Cos Ralph A DiMola said so, since he added the first two nifty
updates to it:
* an autoHilite boolean, so you can intercept clicks before the selected
icon changes instead of after, and
* icon zoom
Now it's also got margin
ime 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
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.
> >
ues 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
tps://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 M
y/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
l Message-
> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On
> Behalf
> Of Mike Kerner via use-livecode
> Sent: Saturday, September 10, 2022 12:03 PM
> To: How to use LiveCode
> Cc: Mike Kerner
> Subject: Re: NAVRAD was: lcb missing manual
>
> Update:
[mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Mike Kerner via use-livecode
Sent: Saturday, September 10, 2022 12:03 PM
To: How to use LiveCode
Cc: Mike Kerner
Subject: Re: NAVRAD was: lcb missing manual
Update:
* Put it on github because I'm starting to tweak it, too (on the dev
Update:
* Put it on github because I'm starting to tweak it, too (on the develop
branch - Ralph's original version is on the Deploy branch)
* Made several properties invisible in the Properties Inspector
* on to the next item on the list
On Fri, Sep 9, 2022 at 4:54 PM Mike Kerner
wrote:
> Thanks
Thanks for the help, guys.
What about this list for a next-up wishlist?:
* I think some of the properties in the PI are extraneous: "selected item
name", "pre Hilited item", "pre hilited name", so remove them from the PI
* Add borders/margins or offsets, because on mobile, there is furniture,
espec
via use-livecode
Sent: Friday, September 09, 2022 1:47 PM
To: How to use LiveCode
Cc: Matthias Rebbe
Subject: Re: NAVRAD was: lcb missing manual
If you would extract the .lce file, then you could copy the extracted folder to
the extension folder.
Von meinem iPhone gesendet
> Am 09.09.2022 um
runrev.com] On
>> Behalf Of Brian Milby via use-livecode
>> Sent: Friday, September 09, 2022 9:54 AM
>> To: How to use LiveCode
>> Cc: Brian Milby
>> Subject: Re: NAVRAD was: lcb missing manual
>>
>> You have to use the IDE to install widgets.
>> T
: Friday, September 09, 2022 9:54 AM
To: How to use LiveCode
Cc: Brian Milby
Subject: Re: NAVRAD was: lcb missing manual
You have to use the IDE to install widgets.
Tools… Extension Manager… + (icon, top right)
Brian Milby
br...@milby7.com
> On Sep 9, 2022, at 9:40 AM, Mike Kerner via use-l
rev.com] On
> Behalf Of Brian Milby via use-livecode
> Sent: Friday, September 09, 2022 9:54 AM
> To: How to use LiveCode
> Cc: Brian Milby
> Subject: Re: NAVRAD was: lcb missing manual
>
> You have to use the IDE to install widgets.
> Tools… Extension Manager… + (icon, to
ginal Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of
Brian Milby via use-livecode
Sent: Friday, September 09, 2022 9:54 AM
To: How to use LiveCode
Cc: Brian Milby
Subject: Re: NAVRAD was: lcb missing manual
You have to use the IDE to install widgets.
Too
t;> file. So many unknowns. I am trying to find a way to resize it to the card
>>> width with a user setting for height percent of card width. But the docs
>>> are so scant and confusing I feel the giant headache coming on again.
>>>>
>>>>
>>>> Ralph Di
th a user setting for height percent of card width. But the docs
>> are so scant and confusing I feel the giant headache coming on again.
>> >
>> >
>> > Ralph DiMola
>> > IT Director
>> > Evergreen Information Services
>> > rdim...@evergree
gt; -Original Message-
> > From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On
> Behalf Of Mike Kerner via use-livecode
> > Sent: Tuesday, September 06, 2022 3:00 PM
> > To: How to use LiveCode
> > Cc: Mike Kerner
> > Subject: Re: NAVRAD was:
de-boun...@lists.runrev.com] On Behalf
> Of Mike Kerner via use-livecode
> Sent: Tuesday, September 06, 2022 3:00 PM
> To: How to use LiveCode
> Cc: Mike Kerner
> Subject: Re: NAVRAD was: lcb missing manual
>
> Ralph,
> got the source, somewhere? i'd like
use LiveCode
Cc: Mike Kerner
Subject: Re: NAVRAD was: lcb missing manual
Ralph,
got the source, somewhere? i'd like to learn from it.
testing to begin...now.
On Thu, Sep 1, 2022 at 1:32 PM Ralph DiMola via use-livecode <
use-livecode@lists.runrev.com> wrote:
> I took a major st
Ralph,
got the source, somewhere? i'd like to learn from it.
testing to begin...now.
On Thu, Sep 1, 2022 at 1:32 PM Ralph DiMola via use-livecode <
use-livecode@lists.runrev.com> wrote:
> I took a major stab at LCB and created a new widget based on the navbar
> widget. I have made 2 changes to th
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
Did a simple test with 819kb json file:
- JSON Library / LCB 5400 ms
- PhotonJSON / LCS 400 ms
- mergJSON / extension 250 ms
Brian Milby
br...@milby7.com
> On Sep 2, 2022, at 4:27 PM, Brian Milby wrote:
>
> Look no further than comparing the JSON library written in LCB and LCS
> (PhotonJSON).
Look no further than comparing the JSON library written in LCB and LCS
(PhotonJSON). I’m thinking that the LCS is probably faster. Probably worth a
shot to actually test in more detail. I tried to import the smartcrumbs output
with the external, LCB and LCS and only the LCS even was successfu
On 9/2/22 10:43, Jacques Clavel via use-livecode wrote:
You can write exactly the same functions, commands in LCB than in LCS
Um, no.
There are quite a few pain points trying to determine the differences in
what is supported and what is different.
--
Mark Wieder
ahsoftw...@gmail.com
As a typed language, LCB should be more efficient than LCS.
Writing programs in LCB is more difficult and time consuming (bogs...) than
using higher level language (LCS)
You can write exactly the same functions, commands in LCB than in LCS
JC
Le ven. 2 sept. 2022 à 17:13, Mike Kerner via use-livec
I wonder why the polygrid is so much faster than the datagrid at rendering,
then, in the demo
On Fri, Sep 2, 2022 at 10:54 AM Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Or slower than both? As I understand it, LCB has the capability to call C
> externals which themselv
Or slower than both? As I understand it, LCB has the capability to call C
externals which themselves would be faster than anything, but on it's own it is
slower than both.
Bob S
On Sep 2, 2022, at 01:00 , Geoff Canyon via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
On Thu, Sep
On Thu, Sep 1, 2022 at 10:08 AM Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Its much faster than C but slower than Script.
Should that be "much slower than C but faster than Script"?
In which case, what happened to the "faster than script" part?
I took a major stab at LCB and created a new widget based on the navbar widget.
I have made 2 changes to the navbar and call it navrad. It does not modify the
stock navbar. With almost no docs it was a challenge. There were so many
unknowns I got a few giant headaches. It adds 4 new
properties(
Geoff Canyon wrote:
> I've put off LCB because I don't much bother with widgets.
> I suppose I could update Navigator, but it already works well,
> so ¯\_(ツ)_/¯
>
> So if it isn't faster, dare I say it, why would I?
Foreign Function Interface, and certain custom control needs.
In short, the lan
Sneidar
Subject: Re: lcb missing manual
Also, when it comes to performance, developers should ask not only is it
faster, but would anyone notice the difference? I used to say, "A computer only
needs to be fast enough." Some will ask, "Fast enough for what?" To which I
reply,
Also, when it comes to performance, developers should ask not only is it
faster, but would anyone notice the difference? I used to say, "A computer only
needs to be fast enough." Some will ask, "Fast enough for what?" To which I
reply, "Now you are asking the right question."
Bob S
On Aug 31,
I don't know why you would.
Libraries that aren't trying to get into system-level API's don't need to
be there.
On Thu, Sep 1, 2022 at 12:56 AM Geoff Canyon via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Agreed -- I've put off LCB because I don't much bother with widgets. I
> suppose
Agreed -- I've put off LCB because I don't much bother with widgets. I
suppose I could update Navigator, but it already works well, so ¯\_(ツ)_/¯
So if it isn't faster, dare I say it, why would I?
gc
On Wed, Aug 31, 2022 at 5:54 AM Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wro
The subject of the dictionary has long been one of contention. One that I
have often spoken up and been shouted down about (nb, I'm not making
accusations or flames :) ). But I also understand the great amount of
resources this would take to produce decent, up to date guides and
indices of all the
It would be interesting if lcb was slower, since it's supposed to be
lower-level.
The demo that Steven did, demonstrating the speed of populating a polyGrid
(lcb widget) vs. a dataGrid (lcs group) was that it was much, much faster.
On Tue, Aug 30, 2022 at 5:58 PM Brian Milby via use-livecode <
use
LCB has been slower than LCS, but the advantage is that you can easily link to
much faster compiler code. I’m not sure if that has changed any… I could pull
out some code from a while back where we were doing some speed tests.
Sent from my iPhone
> On Aug 30, 2022, at 5:31 PM, Geoff Canyon via
Is there a page that discusses the pros of LCB? I looked and didn’t find it.
I’m thinking of a simple list (I’m making this up because I didn’t find the
page)
— N times faster execution than LCS
— interface with code libraries using simple hooks
— bundle code and graphics together into widge
On 8/28/22 11:06, Mike Kerner wrote:
the lcb documentation, especially in the api widget is ungreat.
the good news is that as long as there is an oss repo version of LC, you
can hunt for some of the information that is missing. AND, at least for
now, you can still find much of it in the LC appl
the lcb documentation, especially in the api widget is ungreat.
the good news is that as long as there is an oss repo version of LC, you
can hunt for some of the information that is missing. AND, at least for
now, you can still find much of it in the LC application
example: as i was hunting, i foun
On 8/28/22 09:58, Mike Kerner via use-livecode wrote:
things for lcb that are supposedly documented, but i can't find:
* editor types (e.g. com.livecode.pi.number)
* other metadata definitions for properties, widgets, etc.)
...things that we use in LCS but aren't available in LCB:
colornames
sw
It would be good were there full documentation for LCB, and, preferably
with some sort of thematic search so, unlike the LiveCode dictionary one
did not have to flounder around so much working out what to search for.
On Sun, 28 Aug 2022, 18:00 Mike Kerner via use-livecode, <
use-livecode@lists.run
things for lcb that are supposedly documented, but i can't find:
* editor types (e.g. com.livecode.pi.number)
* other metadata definitions for properties, widgets, etc.)
--
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
54 matches
Mail list logo
