It would help if Brian, Panos, Trevor (anybody who has got a setup ready to
compile) created an idiots guide(s) as to what compilers to install, any
land mines to cross
any tricks that they have learnt etc because what seems to happen with me ,
I start something which doesn't put food on the table
agree
On Fri, Oct 11, 2019 at 3:15 PM hh via use-livecode <
use-livecode@lists.runrev.com> wrote:
> This is a wonderful project.
>
> Should be limited to bugs that are NOT regressions.
> And instead extended by feature requests.
>
> ___
> use-livecode m
This is a wonderful project.
Should be limited to bugs that are NOT regressions.
And instead extended by feature requests.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscr
For what its worth, I think this is the way to go. A totally community run
initiative, with a bounty on bug fixes. Someone or several someones outside of
the LiveCode team would need to take responsibility for setting up a structure.
We'd love to see bugs being fixed, by members of the community
wow, i managed to mute this conversation. fail.
@paul, that's exactly why we ponied up, too, as an insurance policy. we
have been burned by numerous organizations either abandoning their software
work product or disappearing. thankfully, for most of our mission-critical
stuff, we have, own, and
I think i miss some understanding from my part. Sqlite is supported and working
ok right. So what's this with this library? Then second, Heather said that
things now in FM will flow back into lc.
Pi Digital via use-livecode schreef op 9
oktober 2019 14:53:16 CEST:
>Can you provide the full li
+1 Richard. I got onboard with what user to be Runtime Revolution (I think it
was version 2!) Where livecode is today is orders of magnitude more than it was
when it first started. There was no datagrid. No way to display tabular data
apart from a very simple table field. No arrays. Difficult an
Can you provide the full link to the SQLite feature that was funded?
Sean Cole
Pi Digital Prod Ltd
> On 9 Oct 2019, at 13:47, Richard Gaskin via use-livecode
> wrote:
>
> https://github.com/livecode/livecode
___
use-livecode mailing list
use-livecode
Lagi Pittas -
> I don't want to get into a Slanging match and I would never make it
> personal. but we were never even given a basic system to enhance -
> I Quote
>
> "Finally, remember, that this will all be open source code, built and
> included in the community edition – you will be able to t
Hi Richard,
I don't want to get into a Slanging match and I would never make it
personal.
but we were never even given a basic system to enhance - I Quote
"Finally, remember, that this will all be open source code, built and
included in the community edition – you will be able to take it, adapt
I'm less than convinced by the crowdfunding ideas that have been
mentioned so far. But there is something that is important to
understand:
1. All Kickstarter campaigns are 'all-or-nothing.' From the Kickstarter
FAQ: "No one will be charged for a pledge towards a project unless it
reaches its
Lagi Pittas wrote:
> I did absorb that - nearly 3 years ago - QED.
It's three years more recent than the old list you keep raising.
> My major itch is the crowdfunding SPECIFICALLY for Sqlite
Thank you! Specifics are the only way things can become actionable.
What needs to be done with SqLit
Now I'm a little peeved.
Richard said
"He's one of about three people who keep going back to the Kickstarter
list as some form of eternal damnation against the team, "
Forget about the kickstarter - I will say it one more time
There was crowd funding for a new Sqlite library with a timesca
Dear Richard,
I did absorb that - nearly 3 years ago - QED.
My major itch is the crowdfunding SPECIFICALLY for Sqlite , with a
manual and all that. I have gone round and round
in this, NOT as often as I should, but only when a thread gets my back up.
By the way I have 4 drafts I haven't sent (an
Pi Digital wrote:
>> On 8 Oct 2019, at 21:42, Richard Gaskin wrote:
>>
>> And here is a May 2016 update:
>>
>>
https://livecode.com/trevor-devore-interviews-kevin-mark-on-infinite-livecode/
>>
>>
>> A small number of people keep going round and round on this a large
>> number of times.
>>
>> Ho
> On 8 Oct 2019, at 21:42, Richard Gaskin via use-livecode
> wrote:
>
> And here is a May 2016 update:
>
> https://livecode.com/trevor-devore-interviews-kevin-mark-on-infinite-livecode/
>
>
> A small number of people keep going round and round on this a large number of
> times.
>
> How many
Lagi Pittas wrote:
> This is what I was talking about being treated like mushrooms - no
> communication as to what the future holds.- rough timescales
> as to when new or reassigned resources will be implemented - what
> is the intention with sqlite, 2d physics, Audio
>
> here is a 2014 upda
On 10/8/2019 12:42 PM, Richard Gaskin via use-livecode wrote:
Pi Digital wrote:
> Forgive me for saying but, except the bounty idea, wasn’t this the
> whole point of it going open source - so that the community would
> fix bugs themselves!
Personally, I try to avoid making claims about othe
Pi Digital wrote:
> Forgive me for saying but, except the bounty idea, wasn’t this the
> whole point of it going open source - so that the community would
> fix bugs themselves!
Personally, I try to avoid making claims about other people's internal
motivations. Since I'm not them, such inf
Hi All,
If I can interject here.
WHEN they have decided that they can add new resources (it used to be
people but now we are all commodities) or
reassign said resources to the LC branch rather than nearly all to the LC
for FM branch. If LCFM becomes the cash cow
then bugs will surely be fixed qui
Terry Judd wrote:
> On 8/10/19, 4:34 pm, J. Landman Gay wrote:
>
>> 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 ne
Pi Digital wrote:
> If it’s coded in LCS, how will you submit the PR considering LC do not
> accept binaries.
With very few exceptions these days, most stacks throughout the IDE were
rewritten as script-only stacks specifically to facilitate collaborative
development.
--
Richard Gaskin
Fou
Small point on LCS... most things can probably be fixed by editing behavior
scripts and not binary files. If a binary file needs to be updated, you can
write a script to transform the binary and submit it (then a core team member
can review and apply the change).
I’ll agree that feature adds t
> On 8 Oct 2019, at 14:52, Mike Kerner via use-livecode
> wrote:
>
> • insert delay while patrons enjoy the benefit of financing the fix
How does this bit work. If the PR has been submitted, how will others benefit
unless a build is released? Who would be responsible for that considering it’s
i am so not being clear about this. i hate it when no one else understands
what i'm not saying.
i am not proposing a system that is either administered by LC or where LC
is involved in the work. what i am proposing is that all of us control
this process. it's our money, right? We propose the bo
On 8.10.19 11:35, Richmond wrote:
"the severity of a bug be determined by the team"
Presumably by "the team" you mean LiveCode Central?
Somewhere in this discussion there was the idea that, perhaps, "the
team" already had so
much on their plate that both determining the severity of bugs and
"the severity of a bug be determined by the team"
Presumably by "the team" you mean LiveCode Central?
Somewhere in this discussion there was the idea that, perhaps, "the
team" already had so
much on their plate that both determining the severity of bugs and
sorting them out
were handled by pe
OK: I really need to clarify what I wrote there . . .
"if that were the case . . ."
What I meant is that, as far as I can see (pace Microsoft, Apple, et
al), software developers
release versions "into the wild" knowing that the chances of them being
100% bug-free is practically nil,
and relyi
On 10/7/19 10:13 PM, Richard Gaskin via use-livecode wrote:
> I had extensive discussion about the Bugzilla voting system with
Kevin, Mark Waddingham, and others there at LiveCode Ltd., in response
to the reactions many members of our community (including yours truly)
expressed when the voting
I feel like there are plenty of ways that a point system that avoids some of
these issues with the previous one could be implemented - fewer total votes per
person, single votes per bug only, no or reduced value votes for community
users, forced re-allocation of votes on a regular basis...
Yep,
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
to
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 democracy?),
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. S
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
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
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 pro
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
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
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
https:
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:
http://lists.runrev.com/mailman/listi
> 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 software
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 for
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 givin
> 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 list
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
use-live
On 6.10.19 2:19, Curry Kenworthy via use-livecode wrote:
Because yes, bugs are created
Indeed they are:
this is all something to do with the law of unintended consequences,
the double-effect argument and so on.
I certainly DON'T believe in people at LiveCode central deliberately
creati
William:
> where the programming effort to fix the funded bug will come from.
That's a very good que... - er, a good example of a reactionary and
blasphemous anti-bug question. I luvv buggs and perish the thought of
losing even a single precious one.
Actually we don't need to presume too mu
On 10/5/19 12:27 PM, Richmond via use-livecode wrote:
Well, well, well . . . out of the smoke a phoenix arises . . .
I am in contact "with those who know what they are doing" with a mind to
try to set up an "adopt a bug" scheme. But the real b*gger is how on
earth to
do some sort of triage on
I find this whole idea rather strange, although i understand where it is
coming from.
But, for example when i buy a car and it has bugs (in the warranty
period) it gets fixed for free.
Even if the car is out of warranty then some are called back to fix a
safety item, also for free.
If it i
Well, well, well . . . out of the smoke a phoenix arises . . .
I am in contact "with those who know what they are doing" with a mind to
try to set up an "adopt a bug" scheme. But the real b*gger is how on
earth to
do some sort of triage on outstanding bugs and find out which ones:
1. Are sorta
Folks,
The donations to fix specific bugs is a notable idea. But what comes to mind is
where the programming effort to fix the funded bug will come from. Presumably,
you are thinking it will come from mothership staff programmers. I don’t know,
but suspect the staff programmers are already busil
a bug and enjoy the protections and perks they have! They really
get to travel a lot, meet a lot of people, and be famous. They reduce
carbon and save energy when they shut down systems. And they never get
tired. So love them and promote da love - write songs, blog about bugs
in a positive way,
52 matches
Mail list logo
