On Apr 1, 2010, at 12:27, Mjumbe Poe wrote:
It would be convenient, but not actually make sense. These are just calls out to the actual C functions, which don't take search paths or anything like that, they just look in the cwd. It would appear that in the Python days, people did things like: os.path.join(os.path.dirname(__file__), "delicious%d.png" % pixels) You can use some combination of GLib.path_get_basename and GLib.build_filename and friends, but I'm not sure that we expose the script path (__file__, in python) in the case of epiphany extensions (we do in the case of the 'seed' interpreter, but maybe not the library, I'm not sure). Maybe there's another Epiphany-y way to get the path to the extensions directory?
|