Loading AI tools
From Wikipedia, the free encyclopedia
Yeah I had your page on my wacth list from some old comment and the atlas looked interesting. I ended up copying your whole js file since I already used the preivew thing, but didnt have the instaview widget. When I try and use the atlas say at Washington Monument I just get a grey grid with firefox 1.5.0.3, I can drag the grid around though. -Ravedave 14:08, 16 May 2006 (UTC)
Hi, Dschwen -- Your atlas idea is something that I've always wanted to do on Wikipedia. Have you looked at using an existing map library like OpenLayers for this? It might help speed up your development. --Schuyler 14:45, 12 July 2006 (UTC)
Hi, Dschwen. Your atlas is great. I was wondering if I could ask you some questions about how you serve up the map data. After digging through your javascript it appears that the tiles go through sat.php script. Some of the tiles come up with a message about NASA's servers being overloaded. Does this mean that your script is actually a proxy to a nasa server that caches the tiles? I am trying to find a stable mapping server for use with desktop Java applications so I'd love to learn some of the details of your solution. You can read about the SwingLabs open source mapping component here and . Could you contact me at joshua at marinacci dot org? Thanks so much. BTW. Your photos are great.
I was wondering if you wouldn't mind looking at Wikipedia:Featured picture candidates/Zabriskie Point Panorama again. The image is in FPC limbo awaiting more imput. I have created an edit that adjusted the levels and correcting some stitching errors. Unfortunately, there is nothing I could do to increase the horizontal resolution. Anway, your imput would still be greatly valued. Thanks.--Andrew c 15:49, 3 November 2006 (UTC)
The only recent vandalism has been committed by User:Elk Salmon. Please reconsider taking out the GaWC WP:OWNership of the picture set. — Arthur Rubin | (talk) 20:22, 6 November 2006 (UTC)
I have uploaded a new version on FPC, which you might check out. It addresses the concerns voiced by the opposers. Greetings, --Janke | Talk 15:29, 8 November 2006 (UTC)
Daniel,
Just to let you know that the Featured Picture Image:Goettingen Marktplatz Oct06 Antilived.jpg is due to make an appearance as Picture of the Day on February 15, 2007. If you get a chance, you can check and improve the caption at Template:POTD/2007-02-15. howcheng {chat} 17:27, 17 January 2007 (UTC)
Hello Dschwen/Archive3, please send your real-name, your prefered login-name and the public part of your ssh-key to . We plan to create your account soon then. --DaB.
When executing the following line:
wikiminiatlas_settings = document.getElementById('wikiminiatlas_settings');
The error "Object doesn't support property or method" is raised. I know what causes this, and the solution is:
try { wikiminiatlas_settings = document.getElementById('wikiminiatlas_settings'); } catch(ok) { }
The error is caused by the fact that wikiminiatlas_settings already contains the correct object, and it is read-only. So the code tries to execute the default property set, which is not supported by HTML elements. Apparently something in the remainder of the script is necessary for correct operation, because I only get a grey rectangle, no maps. Shinobu 11:57, 13 November 2006 (UTC)
I sort of works now, but not flawlessly, I'll send you some more bug reports :-)
As for the double initialization of wikiminiatlas_settings, that's actually a historical thingy. When Microsoft implemented their first DHTML or whatever it was called back then, they thought it would be nice to be able to refer to objects using JavaScript. This was before getElementById which is recommended nowadays. They opted to export every HTML element with an id to the scripting engine, using that id as the identifier. Now everyone uses getElementById, but the old method is still available, presumably to avoid breaking compatibility with older scripts.
The way Microsofts script engine works, assignment to these exported objects is done through the default property set. This is presumably done so that the hosting application gets notified. Probably an implementation specific thing, so it may or may not work in other browsers. Note that scripting engines are not only used by the browser, but also by other applications, so that may be important. In Windows objects have had default properties since early COM days.
Note that you also cannot assign a different value to the window object. It's exported to the scripting engine in the same way, although the default property set of the window object does generate a more helpful error.
So why did it break in this case? Two reasons. First, you called the variable same as the id of the object it referred to. Second, JavaScript (or at least JScript) uses the same syntax for accessing the default property on exported objects as for assignment. If either of these were not the case, it would have worked.
Note that at least when using Firefox, wikiminiatlas_settings is also initialized with the HTML element. But because its JavaScript doesn't do default property sets, it isn't a problem (it'll be the same as assigning to a variable).
So now you probably now a lot more than you ever wanted to know about this. Shinobu 12:27, 14 November 2006 (UTC)
That's possible, although the try-catch method works just fine as long as you don't need to assign something different to wikiminiatlas_settings. Note however that when your new variable name is accidentally equal to an id, you'll run into the same problem again.
There is an easy way to solve this: declare your variable explicitely. You see, when you don't do so JavaScript first searches all objects exported by the host application, i.e. the browser in our case. If you use xxx, first the local closure will be searched for any variable called xxx. Than the closure above that, all the way up to the global scope. If no variable is found, any object with id="xxx" will be used. If that doesn't exist, then a member of window will be used, since it's the global object. It turns out that the window object creates new members if you assign to them, just like any old JavaScript object. So essentially you're not using a normal variable but a member of the window object in this case. Code sample:
<html> <body> <p id=xxx></p> <script> //var xxx; try { xxx = document.getElementById("xxx"); } catch(e) { alert("No soup for you!"); } xxx.innerHTML = "Hallo!"; </script> </body> </html>
When you open this in IE, or any other browser that uses the same JavaScript implementation, i.e. JScript, you'll see "No soup for you!", but the last line will still work. Now uncomment the first line: now xxx is a variable in the global scope, which has precedence. The alert will not be displayed and it still works.
Note that the id="xxx" object is exported as a member of the window object. However the var xxx isn't, it's just a variable in the global scope. You can check this by changing the id and query window.xxx. Note that, as said before, in Firefox id'ed elements are not part of the window object but variables in the global scope. So:
xxx = value;
in Firefox changes the value of the xxx variable, which was initialized with the paragraph element, while in IE it tries to call the property set for window.xxx, which is not defined, so it does a property get for window.xxx (just like it would do in Firefox if you would query window.xxx and a corresponding getter would be defined) and then it tries to call the default property set on that object, which is not defined. Or something like that.
When I write scripts I usually do all the work inside an object, thereby eliminating the possibility of conflicts with other scripts. Then I can use private or public variables, depending on what I need, to hold HTML elements and other stuff. Shinobu 22:13, 14 November 2006 (UTC)
It might be nice if the script somehow notifies the user if the XMLHTTP object could not be created. I have arranged it such that I have to activate it on a site-by-site-basis. I've added http://atlas.schwen.de and now everything works, but it would have been nice if the script told me what was wrong, so that I would not have needed to debug it to find out what was wrong. Shinobu 12:41, 14 November 2006 (UTC)
Hi Dschwen. I was disappointed to see your comments about Fir0002's self-nominations at FPC. Past discussions have shown that there is consensus support for self-nominations; it could be argued that we'd be diminishing the utility of FP in encouraging high-quality image contributions if we banned them.
Of course, you're perfectly entitled to a different opinion, but it strikes me as unhelpful to express it as you did here - that sort of comment could be interpreted as assuming bad faith, not to mention rude and unnecessary. There is currently no limit to the number of self-nominations a user can make; if you think that should be changed, the proper course of action would be to discuss it at the FPC talk page. Personally I can see no harm in multiple self-nominations - if they get shot down, the only loser is the nominator's ego; if they are supported, we're richer by one top-quality image and the contributor might feel encouraged to go and create some more. Conversely, personal attacks can only weaken our encyclopaedia and discourage new contributions. In future, please comment on content, not the contributor, and consider whether your actions will genuinely help improve Wikipedia. Happy editing, --YFB ¿ 03:44, 22 November 2006 (UTC)
This is to let you know the Featured Picture you uploaded and/or nominated Image:Gull ca usa.jpg is scheduled to be Picture of the day on January 18, 2007, when it will be featured on the Main Page. Congratulations! howcheng {chat} 17:17, 20 December 2006 (UTC)
I must say, well done. You've brought a much-needed sense of humour back into FPC. We already have Wikipedia:No climbing the Reichstag dressed as Spider-Man, maybe we should have Wikipedia:No climbing Tower Bridge dressed as the Queen? If you don't mind, I think I'll put that pic of her maj into the WP:Oh I say, what are you doing? Come down from there at once! Really, you're making a frightful exhibition of yourself. page. —Vanderdecken∴ ∫ξφ 10:51, 21 December 2006 (UTC)
Hi Dschwen ! I have left you a message on Meta about putting the WikiMiniAtlas for the French Wikipedia. Feel free to answer here or there. Thanks ! le Korrigan →bla 17:20, 25 August 2007 (UTC)
Seamless Wikipedia browsing. On steroids.
Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.
Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.