The only things you have to edit in the elementData.xml are those two lines to get Alice to read them properly.

As I said, not easily. Is this a challenge? I'm presuming it is. The way I would do it though wouldn't have involved entering the .a2w , but you have given advice and I am going to attempt to follow it now.

I could create a script, but the way you said would cause too much ambiguity, with a high possibility of overlapping names.

Thanks for your info. But, for me, this is way to complicated. I'm pretty sure that the students will have enough on their plate just creating the "worlds". It would seem to me that since Alice is supposed to teach programming, that it would allow methods or objects created to be easily incorporated into a world.
Much like any programming language would allow this.

you can import a method by putting it into an object then saving that object.

That's essentially what my method does. I remembered how X had come up with a similar idea of just renaming an a2w to an a2c and importing. But that had many complications which made it both impractical and much harder in this scenario.

All my method does is completely convert a world to an object, then you can do what TauTrumpsPi said (do you have a nickname on the forums, something like TTP?).

Sorry, I have a habit of over-complicating things that aren't actually that hard when you try them. Maybe I will make a script, but not a clean, bug free one, just a quick thing.

Well, I've made a script that should work, but I'm getting an error from within the jython modules. It seems the ziplib.py module has bugs and has not been built to call the Java code properly in part of it, so I will need to make a workaround.