[Python] Direct access to objects?

def sayBoo():
    Text.Text = "Boo!"

sayBoo()
[/code:3ijtereh]

We place this script under a "start of layout"-event and run the app. The text is set to "Boo!", just like it was intended.

If we now save this script as a module named "boo.py" in the appropriate folder and replace the script in the script editor with

[code:3ijtereh]
import boo

boo.sayBoo()
[/code:3ijtereh]

and run it, we get the error "global name 'Text' is not defined". Obviously, the interpreter is not aware anymore, that Text is a reference to the text object. Of course, by extending the function with a parameter textobject and in the code using this reference (textobject.Text = "Boo!") it works again.

But what to do, if there is no input possible? Is there another way to reference an object? The above was just an example, what I really would like to access from within my own module are a few attributes from System, like System.AppPath

The script editor resolves the references on the first code layer correctly, so there must be a way. Can someone point me to the right direction?

import __builtin__

def sayBoo():
    __builtin__.Text.Text = "Boo!"
[/code:jgr2l8p6]editor:
[code:jgr2l8p6]
import __builtin__
import boo

__builtin__.Text = Text
boo.sayBoo()
[/code:jgr2l8p6]

[url=http://stackoverflow.com/questions/142545/python-how-to-make-a-cross-module-variable]See here for reference[/url]

But having to pass around objects like this is [b]very[/b] ugly.

At this point I prefer using parameters:

boo.py
[code:jgr2l8p6]
def sayBoo(o):
    o.Text = "Boo!"
[/code:jgr2l8p6]

editor:
[code:jgr2l8p6]
import boo

boo.sayBoo(Text)
[/code:jgr2l8p6]

def sayBoo():
    Text.Text = "Boo!"

sayBoo()[/code:1n5z6rp3]

If you now rename the text object in Construct to "tBoo", you get the same "global name" error. As soon as you update your script to "tBoo.Text = "Boo!" it works again.

The editor seems to map words to object references on the fly. I hoped I could have access to this mapping too (because 'System' is a built in object that will never change its name it would be easy to access without being too "hacky")

def sayBoo():
    Text.Text = "Boo!"[/code:3csgmg65]
editor:
[code:3csgmg65]import boo
boo.Text = Text

boo.sayBoo()[/code:3csgmg65]

And if the Text object is renamed only one line needs to be modified in the editor from
[code:3csgmg65]boo.Text = Text[/code:3csgmg65] to [code:3csgmg65]boo.Text = tBoo[/code:3csgmg65]

def sayBoo():
    vars['Text'].Text = "Boo!"
[/code:3onb2jrp]
event
[code:3onb2jrp]
import boo
boo.vars = globals()

boo.sayBoo()
[/code:3onb2jrp]

You still have to touch the code if you rename your objects but this way you can cycle on them since globals() returns a dict

def sayBoo():
    Text = vars['Text']
    System = vars['System']
    Text.Text = "Screen is %d,%d" % (System.DisplayWidth, System.DisplayHeight)
[/code:37kwdjs9]

class Boo:
    def __init__(self, Text, System):
        self.Text = Text
        self.System = System
    def sayBoo(self):
        self.Text.Text = "Screen is %d,%d" % (self.System.DisplayWidth, self.System.DisplayHeight)
[/code:3g03cgkv]

event
[code:3g03cgkv]
from boo import Boo
cboo = Boo(Text, System)
cboo.sayBoo()
[/code:3g03cgkv]

from fancypkgname import attractivemodulename

myclass = attractivemodulename.coolclass(globals())
[/code:25apxpgq]

Always:
[code:25apxpgq]myclass.update()[/code:25apxpgq]

They should not have to alter the code everytime they use it in another project. That was the intention

import sys
sys.path.append("D:/test")
[/code:383wvjwf]

Also, a bit OT, is there a way to write Construct plugin using python?

import os
import sys
sys.path.append(os.getcwd())
[/code:1xjyesjw]
On the other hand, when thinking of later uses by other constructors, it might be better to let them just copy the package to Constructpath\Data\Python. This way, everything one might want to use can be found at a central, general place... I made no decision yet.

Writing plugins with Python? I don't think it's possible. The sdk is for use with Microsoft Visual C++/Studio, and embedding Python through C++ (although possible, [url]http://docs.python.org/c-api/[/url]) would just make it more complicated. But maybe some day one talented programmer creates a python-plugin, a precompiled plugin whose functionality is completely controlled by simple python scripts. I would walk over broken glass if that would help to motivate someone developing it