It so happens that I’m digitising Roald Dahl’s first book, written when he was
still a Flight Lieutenant in the Royal Air Force, and I came across this.
Forgive any lack of political correctness - it was a very long time ago:
> “I've just found a nest of widgets,” he said, and looked around in
there isn't any reason why bug bounties have to all go to the mothership.
you're (for lack of a better word) kickstarting a bug fix. it's a bounty.
it should go to the person who delivers the fix, the bounty hunter.
___
use-livecode mailing list
Not only that.
I don't think the SE "get definition(s)" from *.livecodescript, stacks. Unless
perhaps they are open.
I just submitted a PR to fix a "get definition" bug. Currently if the
handler you're looking for is in quotes the menu item will be dimmed.
On 2019-10-07 15:41, Trevor DeVore via use-livecode wrote:
With LiveCode 9.5 one can deploy 32-bit or 64bit Windows applications.
While LiveCode Builder has an `architecture` function that can be used
to
detect 64-bit, LiveCode Script does not. Does anybody have a function
for
determine
On 10/7/19 6:26 AM, Sannyasin Brahmanathaswami via use-livecode wrote:
Not only that.
I don't think the SE "get definition(s)" from *.livecodescript, stacks. Unless
perhaps they are open.
I'm probably misunderstanding something here, but it sounds like you
want to search for definitions in
With LiveCode 9.5 one can deploy 32-bit or 64bit Windows applications.
While LiveCode Builder has an `architecture` function that can be used to
detect 64-bit, LiveCode Script does not. Does anybody have a function for
determine 64-bit vs. 32-bit architecture in LCS?
--
Trevor DeVore
ScreenSteps
On 10/7/19 8:38 AM, J. Landman Gay via use-livecode wrote:
That's been my experience too, script-only stacks aren't searched when
looking for handler definitions.
Hmmm... I don't have that problem. Do you have an example of one that
doesn't work?
--
Mark Wieder
ahsoftw...@gmail.com
I have a theory that the solution to a problem cannot be simpler than the
problem itself. If it is, then the problem wasn't as complex as first imagined.
The issue with developing with multiple dissimilar platforms is that the
interface is SOOO different between desktop and mobile, that a
Because Apple is no longer going to accept apps that are nothing more than a
web portal.
> On Oct 5, 2019, at 05:47 , R.H. via use-livecode
> wrote:
>
> Let us face the fact that today's browsers are capable of almost
> everything you want to do with a rich application. Why should I develop
Ok.
Bob S
> On Oct 4, 2019, at 16:20 , Brian Milby via use-livecode
> wrote:
>
> Yes, any bug fixes in 9.0.5 will be (or have been) merged into the 9.5 branch.
>
> Thanks,
> Brian
> On Oct 4, 2019, 4:01 PM -0400, JJS via use-livecode
> , wrote:
>> I understand, but these will be merged
Hi all,
Read about new developments in LiveCode open source and the open source
community in today's edition of the "This Week in LiveCode" newsletter!
Read issue #197 here: http://bit.ly/2OvkIsr
This is a weekly newsletter about LiveCode, focussing on what's been
going on in and around
On Mon, Oct 7, 2019 at 9:47 AM Mark Waddingham via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 2019-10-07 15:41, Trevor DeVore via use-livecode wrote:
> > With LiveCode 9.5 one can deploy 32-bit or 64bit Windows applications.
> > While LiveCode Builder has an `architecture` function
On Mon, Oct 7, 2019 at 9:47 AM Mark Waddingham via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 2019-10-07 15:41, Trevor DeVore via use-livecode wrote:
> > With LiveCode 9.5 one can deploy 32-bit or 64bit Windows applications.
> > While LiveCode Builder has an `architecture` function
That's been my experience too, script-only stacks aren't searched when
looking for handler definitions.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On October 7, 2019 8:28:39 AM Sannyasin Brahmanathaswami via use-livecode
wrote:
Cripes . . . this is turning out to be a right can of worms . . . and,
obviously, there is an awful lot of reluctance
to sponsor/donate for bug fixes. Let me attempt to summarise so far:
1. people feel that the company responsible for producing some software
should bear full
responsibility
Interesting life. Check out the wiki.
Bob S
> On Oct 7, 2019, at 04:33 , Graham Samuel via use-livecode
> wrote:
>
> It so happens that I’m digitising Roald Dahl’s first book, written when he
> was still a Flight Lieutenant in the Royal Air Force, and I came across this.
> Forgive any
thx Dsc!
Op 6-10-2019 om 22:22 schreef dsc--- via use-livecode:
I tend to use a lot of whitespace in layout and keep label fields and text
buttons long.
And, since I am often the LiveCode programmer's programmer, building libraries
& LCB extensions and such, I sometimes just throw controls
On 10/7/19 7:57 AM, Mike Kerner via use-livecode wrote:
there isn't any reason why bug bounties have to all go to the mothership.
you're (for lack of a better word) kickstarting a bug fix. it's a bounty.
it should go to the person who delivers the fix, the bounty hunter.
Um, no. You'd be
Huh? I'm suggesting that this be taken the direction of a bounty.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
Interesting, but these are professional developers, right? Not common end
users. I'm just taken aback by the notion that no one would ever develop
software again if they had to fix all the bugs themselves.
Bob S
> On Oct 7, 2019, at 15:56 , Richard Gaskin via use-livecode
> wrote:
>
> Bob
by the way scroll a bit down, you'll read: 53% of the website visitors
will click away if it does not load within 3 seconds.
Think again about the html5 export...too slow to load.
Then you are better off writing a html page yourself and add html5 stuff
in it, mucho faster
Op 7-10-2019 om
> On Oct 7, 2019, at 13:42 , Richmond via use-livecode
> wrote:
>
> 1. people feel that the company responsible for producing some software
> should bear full
> responsibility for fixing bugs.
>
> Mind you, if that were the case I don't think there would be anyone
> developing any
Bob Sneidar wrote:
> What other software company shares the burden of bug fixing with
> it's clientele?
Bug bounties are pretty common.
https://www.guru99.com/bug-bounty-programs.html
https://gadgets.ndtv.com/internet/features/bug-bounty-hunters-and-the-companies-that-pay-them-820636
Home is fine unless you are going to be using it in a business environment. If
you aren't or never will be joining a domain, if you are not going to be
sharing files (except with other Windows 10 Home computers) then 10 Home should
be fine.
Bob S
> On Oct 6, 2019, at 09:21 , Martin Koob via
, while on the other hand you can put something extra on your
website and it can be installable as a webapp on your mobile, so that it
becomes faster than ever to load.
https://developers.google.com/web/progressive-web-apps
Op 7-10-2019 om 18:18 schreef Bob Sneidar via use-livecode:
> On Oct 5, 2019, at 16:10 , Mark Wieder via use-livecode
> wrote:
>
> Happily most of the efforts I've helped fund on Kickstarter have reached
> conclusions (the Deathstar never got completely funded).
So they say...
___
use-livecode mailing
In my working life as an ict-engineer it was most of the times Microsoft
related, so starting with Visual Basic 6/SQL Server decades ago and ending up
with .NET/C# nowadays not to mention the SharePoint (365) and BizTalk
implementations... But I must say I have only worked for companies who
Thanks for sharing your tips Peter.
Appreciate it, and will test some.
Regards!
Op 7-10-2019 om 01:31 schreef Peter Bogdanoff via use-livecode:
I work on text-heavy e-book-like, multi-language applications where layout is
important.
I use fields instead of buttons as it is much easier to
I don't have a current example, it happened when I was working on Swami's
project which is almost entirely script-only stacks. I had to use BBEdit to
search folders to find a handler definition.
He could probably provide an example though.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
Terry Judd wrote:
> These seem to be bounties for finding critical (mostly security-
> related) bugs rather than fixing them - hard to see large tech
> companies outsourcing their security fixes.
Yes, probably not the best examples. I could dig up others, but
sometimes I feel like there would
On 8/10/19, 11:02 am, "use-livecode on behalf of Mark Wieder via use-livecode"
wrote:
Back in the old days LC/RR had a voting system on bugzilla. You had five
votes you could allocate to bug reports, and this gave an indication of
how many people were affected by a given bug.
I think the politicking was a big factor in killing the voting system. I
remember many times when people would post to the list, urging others to
cast a vote for an issue so it would rise to the top. Those voters may
never have seen the bug but it sounded important and they had a vote or two
When I was working on the project, all the scripts were put in use when the
app launched and they were all listed in the in-use pane in the message
box. It was a huge list, too. I wonder if that matters.
BR would know more about how it's working now.
--
Jacqueline Landman Gay |
Bob Sneidar wrote:
>> On Oct 7, 2019, at 15:56 , Richard Gaskin wrote:
>>
>> Bug bounties are pretty common.
>
> Interesting, but these are professional developers, right? Not common
> end users.
LiveCode is a developer tool. We use it to make software for end-users.
A lot of discussion around
On 10/7/19 4:31 PM, Terry Judd via use-livecode wrote:
These seem to be bounties for finding critical (mostly security-related) bugs
rather than fixing them - hard to see large tech companies outsourcing their
security fixes.
You'd have to separate proprietary from FOSS products here. One of
On 10/7/19 9:28 AM, J. Landman Gay via use-livecode wrote:
I don't have a current example, it happened when I was working on
Swami's project which is almost entirely script-only stacks. I had to
use BBEdit to search folders to find a handler definition.
So you're editing a script in the SE
These seem to be bounties for finding critical (mostly security-related) bugs
rather than fixing them - hard to see large tech companies outsourcing their
security fixes.
We already have an established system for reporting bugs, and LC are actively
attending to fixing some/most of them. The
Terry Judd wrote:
> I'd totally forgotten about the Bugzilla voting system. I liked that
> approach as well and agree that bringing it back could help both us
> and LC to prioritise fixes.
Voting is one of those things that has a certain ring of rightness about
it (who doesn't love
38 matches
Mail list logo
