Richard:
> And in this here-and-now, I don't have an opinion
> on the conversation between Jacque and Sean,
> which is why I didn't reply to them.
Jacque and Sean made good points.
As did Bob and Bernard.
Which is why I quoted them too.
All of them made great points
on Priorities, the thread
My two pesos, following these comments
Sean:
> they leave something as *basic as this
> unrepaired for EIGHTTEENYEARS !?!
Jacqueline:
> they have to make considered choices in what to address
> at any given time given the resources available to them.
Bernard:
> At least the new
Craig:
> I will indeed get an error in the message box
> if I just invoke “openStack” directly.
So Peter, make sure whether this bug is your original issue,
and not just a red herring from the debugging itself.
Either way:
> 3. But the home.livecodescript code could be more robust.
> (Always
Peter:
> I’ve just tried making a new stack that has:
> on openStack
>pass openStack
> end openStack
1. Make sure this openStack is in your first CARD's script.
> I poked into the script of the stack home.livecodescript
> and see these lines
> if the short name of the owner of the
Sean:
> a whole stream of specific bug reports
What a shame! I had just written a message warning
that many or most had already been reported!
(Some by myself. Others have been discussed here.)
My list was a RECAP for your benefit.
Re-reporting them would only waste time.
> Stop getting
Sean:
> I will post a series of reports to the quality list
> and see which ones get bumped as duplicates of others.
No, absolutely DO NOT waste LC Team time with random info.
Re-reporting bugs carelessly (after not reading) would only do harm.
Many on that list had been reported and
Sean:
> I think Curry was aiming that at me to read his previous lng
> email and see all that stuff about his well being
Line Counts in my first email below
- Re Tiemo's line # issue: 3
- Re Sean's Bug comment: 5
- Re Separate LC 9 SE Bugs: 9
- Re Me sick: 2
Wasted if you don't read
Sean:
> Have you logged these on the quality site?
> I didn’t see them when doing my research.
Me:
> Is there a separate Bug reported on this?
> It is not the same as performance issues.
> I am still a bit sick with the tail end of COVID,
> so not up to searching or reporting bugs this
Craig:
> I am on a Mac. Ever since the red dot issue was resolved
> a few versions ago I have seen none of these issues.
Not seeing and not having are two different things. :)
It may be conflating topics; note the wide range of bugs
that I just listed. Incredible variety. Off the top of my
Me:
> Separate LC 9 SE Bugs we have, or had:
"- Performance and practical script size limit.
- This one, line # updating.
- Messed up handler indentation.
- Disassociation of SE from script's object.
- SE window disappears if too many tabs.
- Excessive disk use (for HDD/antivirus)
- SE
Tiemo:
> beside the horrible IDE performance in general
> the line number doesn't gets updated when scrolling the code
> Has anybody perhaps found any tweak to get the line # working again?
Only the same tactic you mentioned:
> You have to click the mouse into the code, to get the line #
Roland:
> there are number of stacks that have the same stack name
1. Use "delete stack" to remove one from memory
before loading another. Do it carefully;
this is a powerful command! See the dictionary.
> I am not just talking about my own stacks,
> but also stacks from third parties, and
Jacqueline:
> If the third param is omitted, the script compiles okay
> but apparently aborts with no error message
> and no information when the app runs on the device.
Hey LC Team: This may be not merely a bug,
but also a "bad habit" in coding practice.
A habit that leads to multiple bugs.
I can't find the customary use-list and dev-list email,
announcing and summarizing an LC release, for 9.6.4.
(And I never find the Release Notes PDF as useful.)
Perhaps it was mentioned in another thread,
but if so, I overlooked that too.
What are the big LC 9.6.4 changes versus 9.6.3?
Ben:
> all RCs and DPs have gone, leaving only STABLE versions
Martin:
> there was a policy change by LiveCode that was announced back in May
Heather/LiveCode:
> If you think this will affect you, please do feel free
> to reply to this email, we would be very interested to hear
> why you are
Lagi:
> My Laptop is SSD and still the problems.
> I have the problems with or without defender on.
> I don't use third party antivirus anymore
That's 2 out of 4 common steps!
Have you disabled the SE "bling" options?
Bling is slang for flashy expensive trinkets,
such as Live Errors and Auto
Ben:
> It would be good to understand if this has always been an issue,
> or whether it came in with the switch to LC7, as we know
> some other Windows-specific speed issues did.
Not "it". Instead a combination:
1. LC 7 Engine Performance issues.
2. New Windows antivirus trends affecting
I hate to ask this offlist one-on-one because
it seems much more of an FAQ-type question,
where answering once could service many people,
saving both LC Ltd and ourselves lots of time.
So here it is
Now "Email Support" is listed as an Addon
in the new livecode.com Standard Pricing page.
Hi Folks,
This seems headed for trouble again if we're not careful.
We must avoid repeating the same history:
1. Added work for LC Ltd without compensation*
2. Buggy struggling main product due to #1
3. Overcomplicating things
4. Burdening those who pay with the extra expense
5. *Added work
Alex:
> I'm surprised there is no "annual payment" option
> on the standard plan. The standard plan is also the hobbyist plan
"The LiveCode standard plan is an annual subscription which starts
at $299 per deployment platform per year"
"LiveCode Starter Plan
A great way to get started with
Kevin:
> After 8 years with an open source offering we have come to
> the conclusion this is not the way forward for LiveCode.
I agree. In 2013 I was on-the-record as an OSSLC skeptic.
I urged caution, but my input was summarily brushed aside;
"we've already decided with our VIPs" was the
Ben:
> But the key thing is: for this task, LC9 is
> dramatically slower on Windows!)
> Have others seen something like this?
Generally: Yep, I've seen plenty of slowdowns.
On both Windows and Mac, depending on the task.
Specifically: I'd like to test this later;
still recovering from two
Sannyasin:
> So, in the htmltext
> set the htmltext of fld "helpField" to tNews
> in there a “link” that would take you, by example, to a stack called
> card “listen-collections” with in “listen.livecode” ??
Matthias:
> the linkClicked message should be your friend
Me:
... and a text link
(Had some downtime again this week; still under the weather.)
Here are a couple of additional math/logic lessons seen in media,
which can be applied equally well to LC code and software dev
A. Periodic Task Optimization (B-21 bomber stealth coating repair):
1. Calculate impact of various
Only 1 post this week; typing hurts.
(Downtime after a neurotoxin exposure.)
Big fan of the F-35 stealth fighter.
So naturally, the HMS Queen Elizabeth too!
Great journey this year with US and UK jets.
Also a TV show about the ship, "Supercarrier."
One episode had a good math (or code)
Ralph:
> I have to make a decision on what Mac to get.
> I don't need a laptop so a Mac mini
> is definitely a lower cost option for me.
I say go for it; no regrets here.
My purpose is LC dev/test machine,
and it will fit that role perfectly.
I already had that old Mac mini,
and the new one
Keith:
> Very good to see this thoughtful list
> of your reactions and feelings.
Glad you liked it!
I'll do a follow-up in a few weeks.
Yes, "feelings" are wonderful ...
Especially the kind measured
to the nearest millisecond.
Those are my kind.
LiveCode felt that my M1 Mac
was ms
I'm finally getting a chance to post this,
after setting up a brand new Mac mini
recently to replace my old 2012 Mac mini.
It's all about LC work, of course
Origin: Made in Malaysia.
If you need a Mac Not-Made-in-China,
and can't afford Mac Pro, this is it!
(Ethically sourcing my hardware
Don't subtract the topmargin; that's the problem.
(BTW, LC already limits the max scroll for us.
Usually we don't need to calculate it.
But if you do, the topmargin is your issue.)
Best wishes,
Curry Kenworthy
Custom Software Development
"Better Methods, Better Results"
LiveCode Training
Paul:
> In a list field, if you are scrolling a field by script control,
> the max vertical scroll to display the last line
> essentially you have to take the formattedHeight
> minus the field height and subtract out the margins and borders
Subtracting the topmargin is not needed (and gives
Paul:
> the data in the custom property look like:
> codename1
That's backwards, try this:
name1code
And with a tab stop, you may not need a custom property!
Fields can hold more content than what meets the eye.
> foldernameA
Do you really need "folder" and "code" spelled out?
Redundant
Panos:
> LiveCode 9.6.3 RC-1 comes with more than 60 changes
Thanks, I will aim to do some rc1 testing this week and next week.
Best wishes,
Curry Kenworthy
Custom Software Development
"Better Methods, Better Results"
LiveCode Training and Consulting
http://livecodeconsulting.com/
Paul:
> It appears Livecode's language has no support for Backwards searching.
These days, for a one-off backward sequential find with no hints,
I'd be tempted to use a "last item of" calculation; short and simple.
> With hints, so it shows you snippets of the matches for you to jump
> to
Here's a test stack and Word document to either Crash or Hang LC 9.6.2.
This will be the first in my "Crash or Hang" LC Bug Report series!
Two bug reports, which use the same test stack:
https://quality.livecode.com/show_bug.cgi?id=23238
https://quality.livecode.com/show_bug.cgi?id=23239
Paul:
> if word 7 of X = the layer of fld "Address" then
Sean:
> If word 7 of X = the number of fld “Address” then
I prefer this:
if short name of field N is "Address" then
Best wishes,
Curry Kenworthy
Custom Software Development
"Better Methods, Better Results"
LiveCode Training and
Paul:
> Is there an debugger feature or tip or trick anyone has
> that can do the equivalent of set a break point when a property
> is changed and let me see the executionContexts
> to tell what the heck is changing it!
Add a setprop with either a breakpoint and/or the executionContexts?
Jacque wrote:
> It's either the Flying Spaghetti Monster or fullscreenmode. ;)
For Dawkins so loved the things of this world
Might be good to steer away from such, and back to LC. :)
Richard:
> I'm still wondering why we're still scripting scroll regions at all.
...
> I'm also wondering
Paul:
> I created a slider with a label on the left and right in a group.
> The slider is set to min 0, max 2, inc 1 and it's script is:
> on scrollbarDrag pNewPosition
> [...]
I like this UI approach! Your script could be shorter.
A 4-liner or 5-liner would be ideal; just eliminate the
Jacqueline:
> Just a data point: yesterday I downloaded 9.6.2 stable directly
> from the download page and got about 500 kb/second. It took a
> very long time to get the file.
Yes! That's my typical experience. (Except lower than 500 kb.)
LC download usually takes forever, and sometimes fails
JeeJeeStudio:
> And wow got me a massive 30KB/sec download
> while my download speedtest is 74.87Mbps...
> That's the speed back in 1996...
That happens to me a lot. Like the T3 cyborg using dial-up in the past.
But I'm happy to report an LC 9.6.2 download at 5 MB/sec!
From East Coast
Richard:
> Because if it's just the stack name conflict thang,
> I'd rather we solve that at the root by being done
> with that IDE-imposed limitation
Yes, good idea. I would be happy if LC either:
1. Solves it at the root, per RG suggestion.
2. Fixes what they already have, in the IDE.
David:
> I set out to learn some Livecode, but instead learned about Zalgo.
Patience, dear chap! :)
Indeed you learned a relevant fact about Zalgo, and also Hindi, to
demonstrate the answer to your first assumption and first question:
> Would I be right in thinking if codepoint count > the
David:
> Would I be right in thinking if codepoint count > the number of chars
> in a text string, then it probably contains invisible characters?
Negative; there are other possibilities. Including
Paul:
> There are characters that consist of more than one codepoint -
> composite
Jacqueline:
> I routinely run 3 versions of LC simultaneously
> with different stacks and projects in each.
> I've left them all running for weeks at a time without any issues
That's pretty scary; your habits are much like mine! That's how I work.
I have two LCs minimized today, and each has
Matthias:
> I just wrote about my observations and asked for a recipe.
...
> If you felt that as "doubt" then i am really sorry.
No worries! I also apologize if I've misread your message.
It's probably a "Good Thing" anyway that we've had some exchange,
because it brings more attention to
Scott:
> Paypal account or not, if Matthias is a bot we need to
> figure out how to spawn more instances.
That's no problem; we can hack into the server and "borrow" the Matthias
source code. But I don't know what kind of hardware he requires. ;)
(Again, for any who did not understand the
Matthias:
> Believe me i am real. I purchased every library
> you've created in the past, so i must be real.
Not necessarily! You could be a "bot" with a Paypal account.
But I am not prejudiced; human or not, you're a valued customer. :)
And so hopefully you see, and understand, what I'm
Matthias:
> I did not had any hang/freeze.
Hi Matthias,
Good for you! Perhaps you work with fewer projects, or fewer LC areas.
Anyway, you and I are obviously not doing the exact same work, right?
So count your blessings. Every hang does have a trigger and a cause.
No trigger = no hang.
Panos:
> What Tiemo described sounded like this issue
> https://quality.livecode.com/show_bug.cgi?id=22896
> - so if this is the
> case, this bug is very specific to Big Sur,
> and it is fixed in LC 9.6.2 RC-1+.
Hi Panos,
I'm not disputing that you recently addressed a specific Hang.
But you
Panos:
> If I remember correctly, this happened on Big Sur only,
> and it is fixed in LC 9.6.2 rc-X
No way.
Hangs have become a defining feature of the LC experience.
They are quite common on both Mac and PC in various situations.
I'm not disputing that you fixed "something" recently.
Tiemo:
> Only a hard close via task manager
> is the only option to quit the engine
That has become a defining feature of the LC experience.
Hangs are quite common on both Mac and PC in various situations.
> Is it something about my stack what makes
> the engine hang, or do you also
>
Mark:
> Sorry to hear of all your crashes and hangs Curry.
Thanks! The crashes and hangs are only the icing on the cake; 90% of the
calories are normal bugs, glitches, and poor quality of feature support.
But I actually love bug-hunting, and finding a crash or hang is like a
trophy
(Full disclosure: Testing a "Cheerful Rant" format to see whether
employing some humor is more effective when letting off steam, and
hopefully even slipping a bit of common sense past politically-correct
radars under the cover of attempted wit. We'll see how this fares,
compared to the
Andre:
> I like verbose code that is full of comments.
Ah yes, comments are good! But comments do not make code verbose.
Terse code can be heavily commented, and vice versa.
Commenting is not closely related to my issue, nor perhaps to yours.
Me:
> But there's an even bigger danger than the
Me:
>> The biggest code is the most repetitive and least modular!
Jacqueline:
> Not always, but often. I try to aim for the smallest code base,
> so I think the contest should be to solve a complex problem
> with the least amount of code.
Yes, but not brevity for its own sake! Rather for
Andre:
> Often in LiveCode (and most programming languages to be honest)
> we go coding for a long while and then realise that our code
> need extensive refactoring. We may have repeated a pattern over
> and over again and discovered that we need to change every
> instance of them, or
Charles:
> Please do not ban anyone.
Somehow that struck me as a pure and beautiful sentiment!
Short and simple. It grew on me during the list silence today.
We can be punitive, or else help each other as we imperfectly stumble.
I'd hate to see the entire list hurt for the sake of a
Jacqueline:
> It's not a bug, it was intentionally introduced to allow a couple
> of features, like retaining script local variables after a build.
> Given the amount of extra scripting to work around it for existing
> stacks, I think it may have introduced more problems than it tried
> to
Sean:
> if there is a way of replacing using cr
> in the find/replace panel of the script editor.
So what you are REALLY asking is whether nested style arrays and chained
behaviors can be used with tsNet and DataGrid in a git-compatible
environment to create an IDE within an IDE, via a
Me:
> Best solution: SDD.
*SSD
Best wishes,
Curry Kenworthy
Custom Software Development
"Better Methods, Better Results"
LiveCode Training and Consulting
http://livecodeconsulting.com/
___
use-livecode mailing list
use-livecode@lists.runrev.com
Tiemo:
> working with LC 9.6 on a fast win 10 machine
> the responsiveness of the IDE on every mouseclick
> or other action is almost not acceptable slow.
The biggest issue was not Windows per se, but rather disk access:
LC IDE's casual repetitive disk usage + modern antivirus + HDD.
Best
Bob:
> MS Office copy operations are notoriously problematic.
> Microsoft maintains their own clipboard format, so that when
> switching to another product the clipboard must be translated.
> Other apps may do the same.
> The translation does not always go to plan.
Eh ... I think this is a
Sean:
> char 1 of rawclipboarddata["CF_BITMAP"] crashes it
That's simply standing on principle, which I find admirable!
After all, give us a char and we'll likely take ... an image. :)
But on the tech side, not surprising; char 1 of (the data).
--
Paul:
> I would consider this a serious
Sean:
> put the keys of the rawclipboarddata
Yes, I have a little clipboard browser stack for that.
There are regular, full, and raw keys. Joy awaits
> or any other CF_, it crashes out of LC altogether
I had that joyful experience earlier today, with my test stack.
You gotta love it,
LC Bugathon continues
Recently I ran into this bug, which Trevor already reported:
"Unable to paste images copied from Microsoft Word on Windows"
https://quality.livecode.com/show_bug.cgi?id=21906
Copying an image directly (not inline with text) fails.
The clipboarddata contains nulls,
Inline sort param variables:
If anyone files this bug report/feature request, let me know!
I will sign on
Best wishes,
Curry Kenworthy
Custom Software Development
"Better Methods, Better Results"
LiveCode Training and Consulting
http://livecodeconsulting.com/
Paul:
> apparently neither the sort direction (ascending|descending)
> nor the sort type (international|text|datetime|numeric|binary)
> can be variable!
> I see this a a bug or perhaps a failure to fully
> robust impliment the sort container command?
> Does any one else see this as a bug?
Me, recently:
> I don't have any big headaches, thank God!
That's true; it's rare that I get stuck. I'm workaround-musclebound. :)
But I do understand why people get headaches and get stuck.
Hope I didn't sound aloof from the problems; just busy working around.
It's not just features; it's
e.beugelaar at me.com:
> https://www.b4x.com if u dont want headaches.
Thanks for the tip - looks pretty neat. I like the website.
Before going all-in with LiveCode, I did a lot with VB-style code.
HOWEVER, I don't have any big headaches, thank God!
Nor do I feel any need to try another IDE.
JeeJeeStudio:
> I like Livecode a lot, but it has it's limitations,
> lot of bugs are not solved.
True. Would be more accurate with "yet" added; solving bugs is ongoing!
We could also say that many bugs HAVE been solved. Moderate progress.
(I know, having been on the front lines of the
Jacque:
> I did a test before answering and the message was sent to the card
> of my otherwise blank stack, after dismissing the IDE dialog.
Same here!
Bob:
> there have been at least 2 versions that were unstable that crash
> to desktops were not uncommon, and after losing so much data, I
Richard:
> they still offer a business card size with rounded corners -
> I'm taking it as a challenge to bring the card content
> down to just the essentials. ;)
> https://www.avery.com/products/cards/88220
Thanks for that link - good idea! Mini cards look great.
I doubt my own hands can
Mark:
> I agree with others that this isn't a Good Idea,
> and a cleaning routine in preOpenStack would do the trick nicely.
Amen, Brother Mark! Good Idea to avoid Bad Habits.
(Agreed, except a small but crucial difference in details)
As Tore said:
> execute the necessary routines as part
Tore:
> I do not do any clean up at closing time. Instead I execute
> the necessary routines as part of a preOpenStack handler.
> I then do not have to consider which way the stack was closed.
Yes! Like you, for cleanup I also avoid that how-closed consideration.
Much easier to have a simpler
Bob:
> I am trying to clean up my stack (i.e. clear the fields),
> then save it when I close it
This is a good topic for LiveCode learners; I'm chiming in
I often do something similar - but with an important difference:
I perform cleanup when I save. I do NOT force an auto save.
(More on
Paul:
>> ... but why?
Richard:
> 1. Because we can. It's fun to figure stuff out.
Yes, it is! :)
> 2. Print-and-Play tabletop games.
This special printer paper looks way too fun:
https://www.avery.com/products/cards/4785
(Discontinued already? Que lastima!
This thread is giving me
Paul:
> I'm sure this could all be worked out as far as
> how to do the layout and printing directly from LiveCode... but why?
Good question! Might be a good reason, but not much point in guessing.
The bigger question is: what was the true original problem?
Brian:
> The problem is, printing
jbv:
> if myvar = trunc(myvar) then
Different approach: I prefer "mod" for loop breakouts/pitstops.
Very clean way to determine action for certain loop iterations!
Useful for fractional values too, in LC versions thus far.
> set numberformat to "#.000"
You can easily set the
David:
> My impression is that a LiveCode field scrolls less smoothly
> than a comparable field in some other programs
Fair impression. :)
> 25,000 words into a word wrapped scrolling field
Performance does degrade as text size increases.
(Exponentially, after a certain point.)
> Does
Me:
>> Try tsNetUploadFile - fewer steps!
Bruce:
> Thanks, much appreciated.
No problem. That's why I love, and preach, KISS!
(My father taught me "Keep It Simple (Stupid)" at an early age.
Probably around 7 years old. Military aircraft electrician.
They popularized this phrase - and they
Bruce:
> tsNetUploadSync
> binary files are corrupted
Try tsNetUploadFile - fewer steps!
Best wishes,
Curry Kenworthy
Custom Software Development
"Better Methods, Better Results"
LiveCode Training and Consulting
http://livecodeconsulting.com/
Andrew:
> I can’t add a breakpoint because the Remote Debugger
> will take focus from the standalone
Behold the power of the log file:
Logs DOMINATE standalone debugging for all but the simplest issues.
They don't affect focus, either.
(Remote Debugger is cool, but like most things, has big
Brian:
> I’d like to print decks of cards, front and back
This post has become a master puzzle of its own!
Enough detail to elicit solutions, yet still open-ended.
Each answer makes its own assumptions, and solves a different problem.
But I like it. So OK, I'll join. Here goes
My own
Bob:
> Why am I still seeing this?
Why are you continuing this topic? And quoting the entire text?
I consider the topic closed, and the horse just about beaten to death.
Dead yet? Yeah...probably. Just about.
I didn't start this, or even continue it - I received a series of
unprovoked
Stephen:
> forgive me that last post was supposed to be for Curry only
Stephen, I want to thank you for providing verification of the kind of
hate speech/harrassment you were sending offline.
And for the record, I didn't attack you - I mentioned the FBI's lack of
action when commenting on
Andrew:
> You can click in the field and the blinking I-bar is inserted,
> but typing on the keyboard does nothing.
I love field topics!
Win/Mac differences can really hit you, even on a stack that you thought
was well-tested. Because only well-tested on one platform.
This glitch sounds
Richard:
> For those of you who haven't seen Ralf's recent work
> on the revIgniter site [...]
It's been on the edge of my radar, but never had a chance to use it yet.
Thanks for the testimonial and reminder! Hope to try it later this year.
Rick:
> Why are you still using PHP when LC is
Jerry:
> Please keep it offlist.
Sorry, guy. Any implication that I'm bringing brand-new stuff onlist is
inaccurate; sharing an offlist definition of what was meant by "team" -
which was used right here online.
> Ce fromage pue !
Je ne sais pas. Je n'ai jamais goûté de fromage français.
Stephen:
> Curry's gaslight and personal attack
Sorry guy, not true. Simply holding your post up to logic.
You are political, so maybe you see politics everywhere.
As I wrote to you offlist, in reply to your hateful and cursing rant:
"Look again at my post. Notice the timeframe of the scams
Stephen:
> Putting down the FBI won’t help anything and makes me think you
> might be partial to the dark forces and fake news. We get enough
> of the hate through other sources and it is unwelcome here.
Ah Stephen, it's good to see that you've moved on from your previous
practice of
Matthias:
> So in my case it was not scam but just a rude person.
Plenty of those around. Including what comes around.
Manipulative people usually follow 2 tactics.
Either buttering up for a favor, or being rude to apply pressure.
Sometimes both; they will abruptly switch if one fails.
In
Paul:
> I find myself wishing each custom
> property has a comment field.
DIY approach with another cp:
cProperty = cp itself
iProperty = info
Best wishes,
Curry Kenworthy
Custom Software Development
"Better Methods, Better Results"
LiveCode Training and Consulting
Always remember who is the computer, and who is the coder!
The computer may need to perform a loop under the hood, but that doesn't
mean you need to use the "repeat" keyword.
It's often cleaner/faster when you don't. For those who value concise
code and good performance in LiveCode, avoid
JeeJeeStudio:
> One could ask him/her-self the question if it is still ethical to
> buy a reall Mac? Seeing the child-labor in their factories in China
> is still present.
I'm glad you went there! Thank you. I do ask myself, and the answer is
clear. Whether it's a Mac, or any other product.
Me:
> I'm planning to get an M1 Mac this year
Naturally, right after I post this, Apple makes headlines (again) for
doing something arbitrary and rather dim.
So an ethical and professional disclaimer:
I don't support self-contradictory and illogical policy,
any more than
Paul:
> we have several customer who have said
> they are upgrading to M1 laptops
Yes; important to support! I'm looking in that direction too. It'll be
popular, plus it's what I can afford. Many people in the same boat.
(Backstory: Apple's biz model forces Apple to force us to spend on
Ben:
> What is the best way to structure a library these days?
Flashback to an interesting conversation, when LiveCode Ltd (or RunRev
Ltd) asked me, "what is a library?"
Not kidding; real question. It's like Newton Ltd asking you, "what is
gravity?"
That opened my eyes to how libraries
... to my friend and colleague Josh. Amazing coder (godlike skills),
generous with his knowledge, and highly available. Thanks Josh. Enjoy
your day, you earned it! ;)
Also,
LiveCoders: holiday greetings. May you give and receive the best gifts
this year. (Not the virulent dirty gift that
Bob:
> The promise of creating standalones and encrypted stacks
> containing code sounds promising, but there are caveats.
Just like anything else - you have to learn the ropes. First time at any
task can present some challenges. For those in the habit of encrypting
stacks, it comes more
Mark:
> It's actually OSX where CEF usage was
> dropped, not Windows.
Yep, it actually feels great to be a Windows-first LiveCoder.
Ironically, things "just work." In fact I'm doing a Windows app right
now, using - guess what - the Browser widget. Works a treat.
It's hard to overstate how
101 - 200 of 393 matches
Mail list logo
