On 08/10/15 12:14, Ali Lloyd wrote:
So that this does not get lost in the Project Browser / App Browser thread,
I've split it off into a separate topic:
On Wed, Oct 7, 2015 at 8:04 PM Richmond <richmondmathew...@gmail.com> wrote:
While I'm on a roll, I could also point out that I cannot see any
obvious advantages in the complete
remake of the Preference Palette in LiveCode 8.
There may not be many immediately obvious advantages to the new property
inspector, but there are two extraordinarily significant related ones:
1) Widget properties would not work with the old inspector. You would
perhaps have to create individual stacks for each widget and have its card
copied to the inspector. This is really not practical or viable in the long
term.
The new inspector just requires a few lines of metadata in the widget file
specifying what type of editor to use for a given property. Everything else
happens automatically.
2) The new inspector is *really* flexible for the classic objects. Have a
look at this fix for bug 16118 (no way to change a scrollbar's tooltip in
the property inspector):
https://github.com/livecode/livecode-ide/pull/562/files
We'd like to make it as good and useful as possible. If the worst you can
say is you can't see any advantages, then I think the non-obvious ones
above make it well worth it ;-) Otherwise it would be great to hear
constructive criticism and suggestions for improvement.
Ali
_______________________________________________
While your points #1 and #2 are true, I'm sure, that does not explain
why the RunRev team decided
their had to be a complete overhaul in what the thing looked like . . .
Richmond.
_______________________________________________
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/listinfo/use-livecode
