FEATURE_INHERITED_PARENTSCRIPTS
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, LCMark
-
- VIP Livecode Opensource Backer
- Posts: 1005
- Joined: Sat Apr 08, 2006 3:06 pm
- Location: Overland Park, Kansas
- Contact:
Re: FEATURE_INHERITED_PARENTSCRIPTS
I like 'the messagepath' as well. I like both.
Trevor DeVore
ScreenSteps - https://www.screensteps.com
LiveCode Repos - https://github.com/search?q=user%3Atrevordevore+topic:livecode
LiveCode Builder Repos - https://github.com/search?q=user%3Atrevordevore+topic:livecode-builder
ScreenSteps - https://www.screensteps.com
LiveCode Repos - https://github.com/search?q=user%3Atrevordevore+topic:livecode
LiveCode Builder Repos - https://github.com/search?q=user%3Atrevordevore+topic:livecode-builder
-
- VIP Livecode Opensource Backer
- Posts: 9842
- Joined: Sat Apr 08, 2006 7:05 am
- Location: Los Angeles
- Contact:
Re: FEATURE_INHERITED_PARENTSCRIPTS
I like it too, provided the objects are listed in top-down order (first to receive down to last).trevordevore wrote:I like 'the messagepath' as well.
There's a religious war in the xTalk world about how the message path should be represented, with some preferring that representations follow the natural top-down reading order, and others preferring we follow Goodman's mistake in using an inverted diagram for a bottom-up listing. You can tell which side of the fence I'm on.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
-
- VIP Livecode Opensource Backer
- Posts: 1005
- Joined: Sat Apr 08, 2006 3:06 pm
- Location: Overland Park, Kansas
- Contact:
Re: FEATURE_INHERITED_PARENTSCRIPTS
I'm for top down as well. Just implement it before Ken Ray joins the discussion
Trevor DeVore
ScreenSteps - https://www.screensteps.com
LiveCode Repos - https://github.com/search?q=user%3Atrevordevore+topic:livecode
LiveCode Builder Repos - https://github.com/search?q=user%3Atrevordevore+topic:livecode-builder
ScreenSteps - https://www.screensteps.com
LiveCode Repos - https://github.com/search?q=user%3Atrevordevore+topic:livecode
LiveCode Builder Repos - https://github.com/search?q=user%3Atrevordevore+topic:livecode-builder
-
- VIP Livecode Opensource Backer
- Posts: 9842
- Joined: Sat Apr 08, 2006 7:05 am
- Location: Los Angeles
- Contact:
Re: FEATURE_INHERITED_PARENTSCRIPTS
Is Ken a bottom-upper? Infidel!trevordevore wrote:I'm for top down as well. Just implement it before Ken Ray joins the discussion
Thanks for taking that on. It'll be very helpful.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
-
- VIP Livecode Opensource Backer
- Posts: 7237
- Joined: Sat Apr 08, 2006 8:31 pm
- Location: Minneapolis MN
- Contact:
Re: FEATURE_INHERITED_PARENTSCRIPTS
Jerry Daniels called it "sky worshippers" and "earth worshippers" which I thought was amusingly accurate.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
-
- VIP Livecode Opensource Backer
- Posts: 3581
- Joined: Mon Jan 22, 2007 7:36 am
- Location: Berkeley, CA, US
- Contact:
Re: FEATURE_INHERITED_PARENTSCRIPTS
I think of it as front-to-back. I don't know what that makes me.
PowerDebug http://powerdebug.ahsoftware.net
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev
Re: FEATURE_INHERITED_PARENTSCRIPTS
horizon-worshiper... shun him o ye faithful
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/
Re: FEATURE_INHERITED_PARENTSCRIPTS
From an implementation sense, front to back (or should that be top to bottom) makes sense - since that's the order the engine processes the message path when actually delivering messages... Also, due to the way the object hierarchy is represented, it is more efficeint to traverse front to back, less so back to front. (I shall avoid getting into any religious war on the matter - I suspect which view is appropriate depends on the context in which you are trying to explain it).
Re: FEATURE_INHERITED_PARENTSCRIPTS
Going back to the subject of inherited behaviors - in particular 'this me'. We're going to go with 'this me' being experimental in 6.1.1 - with a view to finalizing the syntax in the next major release. This allows a modicum more discussion about it as well as more time to try and integrate 'the <something>' into the parser which (having just looked at it in more detail) is a little more involved than I had remembered...
-
- VIP Livecode Opensource Backer
- Posts: 3581
- Joined: Mon Jan 22, 2007 7:36 am
- Location: Berkeley, CA, US
- Contact:
Re: FEATURE_INHERITED_PARENTSCRIPTS
...having just wrestled with the parser to try to integrate "substack" and "memory", I can relate to that.integrate 'the <something>' into the parser which (having just looked at it in more detail) is a little more involved than I had remembered...
PowerDebug http://powerdebug.ahsoftware.net
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev
-
- VIP Livecode Opensource Backer
- Posts: 9842
- Joined: Sat Apr 08, 2006 7:05 am
- Location: Los Angeles
- Contact:
Re: FEATURE_INHERITED_PARENTSCRIPTS
I just saw the release notes for v6.1.1rc4 - how did "this me" wind up in an actual engine build? There were so many clearer alternatives presented here that I'd thought "this me" was bought up only for humor, no?
Will we see an "aint" operator soon?
Will we see an "aint" operator soon?
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
Re: FEATURE_INHERITED_PARENTSCRIPTS
FourthWorld wrote:Will we see an "aint" operator soon?
-
- VIP Livecode Opensource Backer
- Posts: 9842
- Joined: Sat Apr 08, 2006 7:05 am
- Location: Los Angeles
- Contact:
Re: FEATURE_INHERITED_PARENTSCRIPTS
http://quality.runrev.com/show_bug.cgi?id=3157Klaus wrote:FourthWorld wrote:Will we see an "aint" operator soon?
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
Re: FEATURE_INHERITED_PARENTSCRIPTS
@FourthWorld I believe it was left as is for this release until the syntax is decided upon
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/
-
- VIP Livecode Opensource Backer
- Posts: 3581
- Joined: Mon Jan 22, 2007 7:36 am
- Location: Berkeley, CA, US
- Contact:
Re: FEATURE_INHERITED_PARENTSCRIPTS
v6.1.1rc4? Any idea where I can download this?
PowerDebug http://powerdebug.ahsoftware.net
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev