Issues related to cross branch browsing

Hi,

I'm using cross branch browsing by using below code.

[html]

vpath = '/default/main/linde/gce/gce_intranet/WORKAREA/default/gce_hr';
ceiling = '/default/main/linde/gce/gce_intranet/WORKAREA/default/gce_hr/images';

...........................

window.open('/iw-cc/command/iw.formspub.browse_for_link?vpath='+vpath+'&ceiling='+ceiling+'&show_thumbnail=true&hier_callback=eval(callback_81=function(path){opener.parent.getScriptFrame().doBrowseCallBack("'+itemName+'",path)})','Browse','scrollbars=yes,width=600,height=500');

...........................

..............................

[/html]

But there's some issues with this... this will enable us to browse through workarea '/default/main/linde/gce/gce_intranet/WORKAREA/default/gce_hr'.. if we wish to browse some file from any other workarea (e.g: /default/main/linde/gce/gce_internet/WORKAREA/default/gce_internet) from the same browse window then how to do this?

Thanks & Regards,
Nitesh Ambuj

Find more posts tagged with

Comments

Ambuj

Any help on this please?

footer_only_last_page.rptdesign

Ambuj

I raised a case with Interwoven and I got to know that they do not support multi branch browsing capability..

I was directed to below link..

http://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=52258

Cheers,
Ambuj Smiley Happy

Migrateduser

I've implemented this but you're basically looking at custom development for this. It should be simple enough if you don't mind reverse engineering but you can write a wrapper and within it, use IW's in-workarea file browser and either write your own or use some incantation of IW's workarea/branch browser when the user navigates above that level.

Dave

rwinterpacht

Dave,
Do you care to share more specifics on how you went about this?

Migrateduser

Gladly.

It's been a while since I did this but if you look at the OOTB browser interface that Interwoven provides and look at its URL, query string, links and any hidden form variables, you'll get a good sense of how their browser works. If you do this for the super-workarea browser and the sub-workarea browser (they work pretty much the same) and if you nest these browsers within a frame that will basically control these and allow for communication back to the calling form, you have yourself an all-around browser.

So, a (possibly "the") super-workarea browser is at:

http:///iw-cc/command/iw.ccpro.area_browse_single?ceiling=VAR&hier_callback=(any URL-encoded JS function)&vpath=VAR

... and the sub-workarea browser is at:

http://192.168.1.102/iw-cc/command/iw.teamsite.browse_for_dir?ceiling=VAR&hier%5fcallback=(JS function as above)&vpath=VAR

I'm sure there are better terms than "super-workarea" and "sub-workarea" but it's Friday and that's what I thought of Smiley Happy

Dave

moonkhanna

good one Dave!