Re: Musings on Architect, MVC, Nested Behaviors

2018-12-30 Thread Andre Alves Garzia via use-livecode
Be aware that YAML is tricky to parse, there are better formats such as TOML which are much easier and tend to be less error prone. It is very easy to get some indentation wrong in YAML and move something up or down a level. TOML is IMHO a better format for such stuff.   YAML: http://yaml.org

Refactoring is your friend / moving from 6.x to 9.x

2018-12-30 Thread Malte Pfaff-Brill via use-livecode
Hi list, I finally found the time to test / move one of my old projects from the 6.x (started in 3.x) to the 9.x engine. At first I was very very disappointed about performance. The stack was somewhat between acceptable and snappy in the 6.x engine series, rather unusable on 8 and on 9. This

Re: Refactoring is your friend / moving from 6.x to 9.x

2018-12-30 Thread Mark Wieder via use-livecode
On 12/30/18 1:25 PM, Malte Pfaff-Brill via use-livecode wrote: Hi Kaveh, Thanks for the kind words. :-) Regarding lock screen, here is one simple example: on mouseUp lock screen subhandler unlock screen answer the lockscreen end mouseUp on subhandler

Re: Refactoring is your friend / moving from 6.x to 9.x

2018-12-30 Thread Andre Alves Garzia via use-livecode
Malte, So happy that you're back here my friend. I too spent some time away. So, refactoring and constantly trying to erase mistakes of my past coding self are a constant here. I wish we had better refactoring tools so that we could rename a handler and all code that called that handler was

Re: Refactoring is your friend / moving from 6.x to 9.x

2018-12-30 Thread Malte Pfaff-Brill via use-livecode
Hi Kaveh, Thanks for the kind words. :-) Regarding lock screen, here is one simple example: on mouseUp lock screen subhandler unlock screen answer the lockscreen end mouseUp on subhandler lock screen — other stuff may follow, but do not unlock

Re: Refactoring is your friend / moving from 6.x to 9.x

2018-12-30 Thread Kaveh Bazargan via use-livecode
I don't think LiveCode without Malte is really LiveCode, so glad you are back. :-) Could you pls elaborate on the lock screen strategy? You said we should not nest, and you also said that screen will not immediately be unlocked after a handler. I was under the impression that multiple locks were

Re: Refactoring is your friend / moving from 6.x to 9.x

2018-12-30 Thread Tom Glod via use-livecode
a very interesting thread ...lots to learn. I refactored a project from 7 to 9 and definitely had a couple of "how did this code ever work?" moments, meaning i found the most recent versions of the engine to be more strict with syntax. As far as performance comparisons I don't have a lot to

Re: Refactoring is your friend / moving from 6.x to 9.x

2018-12-30 Thread Geoff Canyon via use-livecode
In 6.7.3 on a Mac, this results in true for me. Checked in 5.0, also resulted in true. On Sun, Dec 30, 2018 at 1:26 PM Malte Pfaff-Brill via use-livecode < use-livecode@lists.runrev.com> wrote: > > Regarding lock screen, here is one simple example: > > on mouseUp > lock screen >

Re: Refactoring is your friend / moving from 6.x to 9.x

2018-12-30 Thread Malte Pfaff-Brill via use-livecode
Hey Mark, At least it is behaviour that changed between engine releases. :-) Thinking of a counter here is a good way to describe the behaviour, however, it is not what is written in the dictionary. "unlock screen Sets the lockScreen property to false, updating the screen and displaying any

Re: Refactoring is your friend / moving from 6.x to 9.x

2018-12-30 Thread Mark Wieder via use-livecode
On 12/30/18 1:55 PM, Malte Pfaff-Brill via use-livecode wrote: Hey Mark, At least it is behaviour that changed between engine releases. :-) Thinking of a counter here is a good way to describe the behaviour, however, it is not what is written in the dictionary. Yes, it is definitely a change

RE: Refactoring is your friend / moving from 6.x to 9.x

2018-12-30 Thread Ralph DiMola via use-livecode
Task: Add ellipses if text does not fit visible field width. V4, v5 and v6 I put the data into the field and then looped thru the lines. If text was too wide I chopped off 1/2 of the overflow chars(rough guess) and then iterated what was left using the formattedwidth as the last chars were