Edinburgh Aug 2-4, 2016

[-hh]

> > Hermann H. wrote
> > I use to look at the top of the current bugs list when I 
> > report one. I have several more to report but stopped for 
> > a while: 
> > The list is simply too long. They will even have problems 
> > to solve the bugs for the current 8.0-dp and to solve the 
> > main problems of LC 6/7 to get (essentially) rid of that 
> > versions. [So any further bug report that goes from LC8 
> > back to LC6 will slow down the 'avantgarde development’.]
> Monte G. wrote.  
> LiveCode is a very large and complex system. Bugs are always
> going to exist in it. The ones that definitely won’t get fixed
> are those that are never reported though! Considering you’ve
> just had one of your bugs fixed (17013) within 6 days of
> reporting (including the weekend) I’m really not sure why you
> are overly concerned about posting bug reports.
> Cheers Monte 

I didn't and I can't complain about resolving bugs reported by
me as they are currently mainly to HTML5.
[And 17013 is one that takes place when going to the limits of
LC 7/8. This wasn't really important. They probably used it to
detect actual memory (leak-)problems.]
But one can see from handling bugs, how much 'nasty' work they
are doing (you will know already now better in detail than I
do) and have on their to-do-list.

It is not important for me to solve some HTML5 problems others
find important. I know HTML5 and can do that "directly" what I
need. It's the fun with LC, to push it in that direction.
It's a good path: For example even leading Mozilla-dev people
(Firefox) already know and acknowledge, that LC is the first
scripting-IDE that compiles (using emscripten for rendering)
directly into HTML5.

******* And your answer to the proposal of an actual *******
******* externals-SDK is really the empty set?  :-(  *******

But I shouldn't waste the time of a LC dev-team member ...

Hermann