[The Geek]

Hey Mak,

I don't really know of any other way to explain it than how I have done . I think we are like passing ships with my explanation and my understanding of what you are wanting to do (I still have no clue what you are trying to do!). Let me try to sum up the way the Extraction regexp works another way.

Most of the time, the URL contains the information that is needed to embed without any additional work. For instance a URL may look like this:

www.yoururl.com/video=123456

And on that page, will be an 'Embed this video' box which will contain HTML that looks like:

<embed src="video" param="123456">

So the replace code in AME looks like:

<embed src="video" param="$p1">

So when AME looks at the URL, it pulls out the 123456 and puts it in the $p1 placeholder and Wham! You have your embedded video.

Where the extraction tool comes into place is when the URL looks like

www.yoururl.com/video=123456

But the Embedding HTML on the page looks like:

<embed src="video" param="abcdefg">

In this instance, there is no correlation between the URL and the embedding code so for the embedding to work, AME must go to www.yoururl.com/video=123456 and do a search for that parameter.

So if the definition includes an Embedding Regexp, AME knows to download the page the first time it is saved and run the Embed Regexp on the source code to lift the abcdefg out. That way, AME will then have all the information it needs to display the embedded media.

You cannot use the Embedding Regexp for anything other than putting parameters in the Replacement code as it wasn't designed to do anything else but what it is currently doing. Saying that, I can put a couple more hooks in so that if you wanted to extract additional information from the destination page at save then you could, however I still am at a loss as to what you are trying to achieve.