Hi,

as per my previous post, I'm building a simple web-based site for clients to view and select images. I'm using portals ... eh ... because I can't think of a better way of doing it.

Anyway ... I have come to a stumbling block. Portal pop. Is there any way to get around it with an IWP web-interface?

Grant

Try using Table view, creating Next, Previous, First and Last buttons for the header. Next and Previous move you 20 records (the IWP limit).

Hi T-Square,

thanks for the reply.

That would preclude what I do with showing a larger related image on the same layout, by running a script from the portal. (I realise that I could use a separate window ... but it's not the same).

Does your reply mean that there is no way to avoid 'portal pop' when using IWP?

Grant

Not being aware of what 'portal pop' precisely is (it's in my brain somewhere, but deeply buried), but knowing that something as ominous as 'Portal Pop' should by all rights be a particularly nasty situation that should be avoided, I made a suggestion that would avoid a portal altogether.

Why not have a View This button in the header that opens a new window with the larger image, and then close that window when you're done? Since you say you're scripting this anyway, a new window is a single line in your script.

I'm still trying to avoid that lurking Portal, with all its hissing and popping...