Defining Pet Features and Essentials

[Ender Nafi Elekcioglu]

Richard:
> Does Livecode not need a revamped url library 

It does indeed, on the Roap Map under "Queued". 

I don’t know how I missed that; I’ve checked again and yes, it’s right there and it’s excellent news :)


Richard:
> modern limits for object sizes 

Current object sizes go up to about 32' - how big do you need them?

The problem is the limits of group objects, here.
40’ images or graphics are useless most of the time, I know. 
But groups are must-have for scrolling, both on mobile and on desktop.
Think a video news app for iPhone 5 like Vimeo
or Twitter app for Mac desktop.
Let’s assume each thumb is 300px high.
Then the developer would have been limited to ~100 videos.
It’s not much.
I did a quick test and it took 8 fast scrolling flick to get the 100th video in Vimeo for iOS.
Considering a Twitter-like news reader app; it’s really a tight limit.


Richard:
> an engine with enough horsepower for the year 2014 not for 2002? 

Always a fan of performance boosts, but to move that forward let's look 
at the areas of greatest interest: what would you like to see faster, 
text manipulation, math, object rendering, or something else?
- What tasks would we like to see performance gains with first? 

You’re right, Richard, another notion which should be defined correctly.
"Which one should be faster” is a good question, indeed.


Richard:

- What would a syntax for threading look like? 

Once, we discussed this issue with Bernd.
He said that he wouldn’t want to go through all the hassle of managing threads.
It’s not an easy task, not implementing rather using the already implemented multithread feature.



Regards,

~ Ender