FEATURE_INHERITED_PARENTSCRIPTS

Moderators: Klaus, FourthWorld, heatherlaine, kevinmiller, LCMark

trevordevore
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 960
Joined: Sat Apr 08, 2006 3:06 pm
Location: Overland Park, Kansas
Contact:

Re: FEATURE_INHERITED_PARENTSCRIPTS

Post by trevordevore » Thu Aug 15, 2013 1:01 pm

I like 'the messagepath' as well. I like both.
Trevor DeVore
ScreenSteps - http://www.screensteps.com

Levure Application Framework: https://github.com/trevordevore/levure
LiveCode Resources for Developers: http://livecode.bluemangolearning.com

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 6836
Joined: Sat Apr 08, 2006 7:05 am
Location: Los Angeles
Contact:

Re: FEATURE_INHERITED_PARENTSCRIPTS

Post by FourthWorld » Thu Aug 15, 2013 3:05 pm

trevordevore wrote:I like 'the messagepath' as well.
I like it too, provided the objects are listed in top-down order (first to receive down to last).

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
Community volunteer LiveCode Community Liaison

LiveCode development, training, and consulting services: Fourth World Systems: http://FourthWorld.com
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/

trevordevore
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 960
Joined: Sat Apr 08, 2006 3:06 pm
Location: Overland Park, Kansas
Contact:

Re: FEATURE_INHERITED_PARENTSCRIPTS

Post by trevordevore » Thu Aug 15, 2013 3:16 pm

I'm for top down as well. Just implement it before Ken Ray joins the discussion ;-)
Trevor DeVore
ScreenSteps - http://www.screensteps.com

Levure Application Framework: https://github.com/trevordevore/levure
LiveCode Resources for Developers: http://livecode.bluemangolearning.com

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 6836
Joined: Sat Apr 08, 2006 7:05 am
Location: Los Angeles
Contact:

Re: FEATURE_INHERITED_PARENTSCRIPTS

Post by FourthWorld » Thu Aug 15, 2013 3:55 pm

trevordevore wrote:I'm for top down as well. Just implement it before Ken Ray joins the discussion ;-)
Is Ken a bottom-upper? Infidel!

Thanks for taking that on. It'll be very helpful.
Richard Gaskin
Community volunteer LiveCode Community Liaison

LiveCode development, training, and consulting services: Fourth World Systems: http://FourthWorld.com
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/

jacque
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 5113
Joined: Sat Apr 08, 2006 8:31 pm
Location: Minneapolis MN
Contact:

Re: FEATURE_INHERITED_PARENTSCRIPTS

Post by jacque » Thu Aug 15, 2013 7:10 pm

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

mwieder
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 2826
Joined: Mon Jan 22, 2007 7:36 am
Location: Berkeley, CA, US
Contact:

Re: FEATURE_INHERITED_PARENTSCRIPTS

Post by mwieder » Thu Aug 15, 2013 9:22 pm

I think of it as front-to-back. I don't know what that makes me.

monte
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 1561
Joined: Fri Jan 13, 2012 1:47 am
Contact:

Re: FEATURE_INHERITED_PARENTSCRIPTS

Post by monte » Fri Aug 16, 2013 12:42 am

horizon-worshiper... shun him o ye faithful ;-)
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/

LCMark
Livecode Staff Member
Livecode Staff Member
Posts: 1033
Joined: Thu Apr 11, 2013 11:27 am

Re: FEATURE_INHERITED_PARENTSCRIPTS

Post by LCMark » Mon Aug 19, 2013 11:10 am

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).

LCMark
Livecode Staff Member
Livecode Staff Member
Posts: 1033
Joined: Thu Apr 11, 2013 11:27 am

Re: FEATURE_INHERITED_PARENTSCRIPTS

Post by LCMark » Mon Aug 19, 2013 11:25 am

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...

mwieder
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 2826
Joined: Mon Jan 22, 2007 7:36 am
Location: Berkeley, CA, US
Contact:

Re: FEATURE_INHERITED_PARENTSCRIPTS

Post by mwieder » Mon Aug 19, 2013 5:24 pm

integrate 'the <something>' into the parser which (having just looked at it in more detail) is a little more involved than I had remembered...
...having just wrestled with the parser to try to integrate "substack" and "memory", I can relate to that.

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 6836
Joined: Sat Apr 08, 2006 7:05 am
Location: Los Angeles
Contact:

Re: FEATURE_INHERITED_PARENTSCRIPTS

Post by FourthWorld » Fri Aug 30, 2013 8:26 pm

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? :)
Richard Gaskin
Community volunteer LiveCode Community Liaison

LiveCode development, training, and consulting services: Fourth World Systems: http://FourthWorld.com
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/

Klaus
Posts: 11207
Joined: Sat Apr 08, 2006 8:41 am
Location: Germany
Contact:

Re: FEATURE_INHERITED_PARENTSCRIPTS

Post by Klaus » Fri Aug 30, 2013 8:36 pm

FourthWorld wrote:Will we see an "aint" operator soon? :)
:D :D :D

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 6836
Joined: Sat Apr 08, 2006 7:05 am
Location: Los Angeles
Contact:

Re: FEATURE_INHERITED_PARENTSCRIPTS

Post by FourthWorld » Fri Aug 30, 2013 8:41 pm

Klaus wrote:
FourthWorld wrote:Will we see an "aint" operator soon? :)
:D :D :D
http://quality.runrev.com/show_bug.cgi?id=3157
Richard Gaskin
Community volunteer LiveCode Community Liaison

LiveCode development, training, and consulting services: Fourth World Systems: http://FourthWorld.com
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/

monte
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 1561
Joined: Fri Jan 13, 2012 1:47 am
Contact:

Re: FEATURE_INHERITED_PARENTSCRIPTS

Post by monte » Fri Aug 30, 2013 9:05 pm

@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/

mwieder
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 2826
Joined: Mon Jan 22, 2007 7:36 am
Location: Berkeley, CA, US
Contact:

Re: FEATURE_INHERITED_PARENTSCRIPTS

Post by mwieder » Fri Aug 30, 2013 9:16 pm

v6.1.1rc4? Any idea where I can download this?

Post Reply

Return to “Engine Contributors”