FAQ
Cover
This is the archive Discourse for the Processing (ALPHA) software.
Please visit the new Processing forum for current information.

   Processing 1.0 _ALPHA_
   Topics & Contributions
   Responsive Form, Games
(Moderator: REAS)
   processing flight404
« Previous topic | Next topic »

Pages: 1 2 
   Author  Topic: processing flight404  (Read 1593 times)
kevin

WWW
Re: processing flight404
« Reply #15 on: Jul 22nd, 2003, 11:36am »

On the topic of popups, it's better to use the approach described here:
 
http://youngpup.net/_ui_webapp/getFrames.asp?request=/articles/how-to-cr eate-popups.xml
 
Code:
<a href="http://google.com/" onclick="window.open(this.href, 'popupwindow', 'width=400,height=300,scrollbars,resizable'); return false;">

 
That uses a normal href, so if the person hasn't got javascript, or if it's a search engine spider then it'll fail silently which is always good.
 
arielm

WWW
Re: processing flight404
« Reply #16 on: Jul 22nd, 2003, 11:52am »

hi p,
 
i'm not following you because:
 
1) from within a flash "shell", how can you invoke <a href> as you propose?
 
2) the "persons without javascript" can't see nothing interesting on the web anyway (and flash needs javascript to speak with the browser).
 
3) the method i'm proposing (source code accessible from the before-last post) is giving the same id to all the potential windows (don't think it'll work with your method): the point is to avoid more than one content window _ with a lot of heavy stuff inside _ at a time!
 
4) it's recommended to forget a bit about jakob nielsen school of thinking (joking, joking...)
« Last Edit: Jul 22nd, 2003, 11:57am by arielm »  

Ariel Malka | www.chronotext.org
flight404

WWW Email
Re: processing flight404
« Reply #17 on: Jul 22nd, 2003, 8:12pm »

Thanks for all the assistance folks.  Ariel, regarding your example, on both IE and Safari on Mac, I get the following results.
 
1). I click the first link.
2). I refocus the page with links.
3). I click on the second link.
4). first popup closes and second does not launch unless I click the second link again.
 
This happens for any combination of clicks.  No matter which I click on, any subsequent click closes the original popup and then does nothing else.  
 
Doh.
 
I hear Casey and Ben are tightly strung so is this Javascript conversation on their Processing board going to get us banned for life?
 
 
arielm

WWW
Re: processing flight404
« Reply #18 on: Jul 22nd, 2003, 10:49pm »

argh, what i was afraid of happened: a mac-pc html singularity! (the explaination for why the average web-designer lifespan is shorther than say, java 1.4 programmers...)
 
and i don't have a mac
 
okay, i've made these 2 blind tests:
 
http://www.chronotext.org/processing/poppy404/doh_a.htm
 
http://www.chronotext.org/processing/poppy404/doh_b.htm
 
please let me know how they behave on your mac...
 
 
on Jul 22nd, 2003, 8:12pm, flight404 wrote:
I hear Casey and Ben are tightly strung so is this Javascript conversation on their Processing board going to get us banned for life

let's close our eyes for a second and think very strong about java and then, when we reopen them, all this thread could become on the subject of autonomous agents synchronization using java.swing and bagel.potato()!
 

Ariel Malka | www.chronotext.org
scrap-pile

WWW
Re: processing flight404
« Reply #19 on: Jul 22nd, 2003, 11:26pm »

In IE and Safari, on my Mac running OSX, doh_a works fine, but none of the links for doh_b are functioning...
 
arielm

WWW
Re: processing flight404
« Reply #20 on: Jul 23rd, 2003, 2:17am »

i had this born-javascripter intuition that doh_a would work, but i guess it's not a full christmas present:
 
sounds like it's working because of the relatively long delay that follows the "alert" boxes, and that's not a real-web solution...
 
i wish i had a mac to fine-tune this problem!
 
maybe the macintosh system needs a long delay between the time a window is closed and reopened?
 
in doh_b, i set a 200 milliseconds delay (over that, it won't be very user-friendly anyway), maybe that's the reason it's not working?
 
hem, well, yes i'm also starting to feel guilty to talk too much about about javascript, and this thread is afterall about acclaiming a great new website, so here is my before-last one:
 
it would be helpful if someone could check these 3 test-case pages on mac with mozilla or netscape 6.2+...
 
(just to see if it's a ie & safari issue or more like an operating-system issue)
« Last Edit: Jul 23rd, 2003, 2:19am by arielm »  

Ariel Malka | www.chronotext.org
Pages: 1 2 

« Previous topic | Next topic »