I agree - I already was toying around with a "toolbar" type look and interface - trying to get fancy - but it will grow and expand depending on if there is data there or not - it stays open as a communication tool until the user closes it - so if the admin needs to push back 3 urls after a few minutes it simply explands the window - accomadates the URL and user can close it and the "toolbar" will shrink back.
I will be sure to share the URL when it's developed enough. Thanks! jay Joshua Miller wrote: >Actually I think the idea is that the hidden frame does nothing but look >for data and then make the OTHER large browser frame do all the work. >Cookies, sessions, etc. should be intact because all you'd be doing is >something like: parent.frame.document.location.href="#pushed_url#" so if >it was in the same site the cookies, sessions, etc would still be there >just like clicking any other link. I wouldn't see any need to popup in a >new window. If you don't want to make a site-wide hidden frame, then >just popup a small window that says "Retrieving Data" or something and >then when it finds what you're after have it change the calling page >(opener.document.location.href="#pushed_url#") to the URL in question >and then close the remote (self.close() or window.close()) and all is >good. Alternatively you could make a small data collection frame appear >when they click the "Help" button that would perform all the actions >from that point on. Make it look like a toolbar or something with a >close button so they could get rid of it when they want to. > >There are probably a hundred ways it could be done to avoid using a >hidden frame across the entire site. I wouldn't want to do that either. > >Good luck! > >Joshua Miller >Head Programmer / IT Manager >Garrison Enterprises Inc. >www.garrisonenterprises.net >[EMAIL PROTECTED] >(704) 569-9044 ext. 254 > >************************************************************************ >************* >Any views expressed in this message are those of the individual sender, >except where the sender states them to be the views of >Garrison Enterprises Inc. > >This e-mail is intended only for the individual or entity to which it is >addressed and contains information that is private and confidential. If >you are not the intended recipient you are hereby notified that any >dissemination, distribution or copying is strictly prohibited. If you >have received this e-mail in error please delete it immediately and >advise us by return e-mail to [EMAIL PROTECTED] >************************************************************************ >************* > > >-----Original Message----- >From: Jason Miller [mailto:[EMAIL PROTECTED]] >Sent: Wednesday, January 29, 2003 11:45 PM >To: CF-Talk >Subject: Re: ColdFusion and Javascript - pushing browser windows > > >Between you and Joshua - I think you gave some good ideas - not how I >intended it to work - but definately a way to make it work. > >With a little js and css - If a page comes back to this invisible frame >-I could have it resize so they can see what I am sending - while not >losing their page - The only issue I guess I will have to overcome is >how my cookies will act - I will have to set a new function to read and >get their cookie and cart info - so that anything clicked on from the >"pushed" page will be recorded properly into their cart. > >The only thing is - I definately am a bit reserved in having to >implement an invisible frame - especially site wide. Thanks though - >gave me some interesting solutions guys! jay > >Scott Weikert wrote: > > >Well this is something I hatched in my brain in about ten seconds, so it > > >may need some work. > > > >One thing you can do is set up, if you're able (i.e. no proclamations >about > >being frameless) an "invisible frame" - i.e. you do 'rows="100%,*"'. Put > > >your main content in the visible frame, and set up the second, invisible > > >frame, to be on a timed refresh. > > > >When a user can't find something, and clicks the "send a 'help!' to the > >admin" button, you store the particulars of that request in your >database. > >Tag it with some identifier for the user - i.e. some UUID that you store >in > >a cookie, IP number, whatever. > > > >Admin does his surfing, and updates the database record with the proper >link. > > > >Remember the second, invisible frame, with the page that's refreshing >from > >time to time? That page always looks in the database for a record with >the > >user's identifier, AND that has an admin-supplied solution. If it finds > >one, then it executes a JS popup that displays the info the admin >supplied, > >in whatever form. > > > >Maybe set up this page to autorefresh every minute. If it finds nothing >(no > >requests for help that have been answered), this page should execute > >super-super-fast and not be a burden on your server/bandwidth. > > > >At 05:50 PM 1/29/2003 -0800, you wrote: > > > >Okay - to clarify push - > >I think explanation of the scenario is best - > >1) User can't find a product or a piece of information on a large >website - > >2) User clicks a button and sends a request to the Administrator - ( a > >whole que or dynamic page would be setup to handle these requests and > >post multiple ones) > >3) Administrator surfs around - finds the piece of information And > >pushes it back to user. > >4) On users computer in the originating browser window - or maybe frame > >-the file loads up. IN fact thinking it would have to be frames based. > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
