and this was my Formula One Tracks & News Mini-Project:
]]>
and this was my Formula One Tracks & News Mini-Project:
]]>
]]>
"I know that the requirement for mini project 3 is to incorporate DOM methods. My question is, not why and how; but what do I need to use the DOM for?"Maybe my "Formula One Tracks & News Mini-Project" could help you to understand the usage of DOM as I have incorporated a couple of DOM methods. For example my main page Source Code contains a "Loading ..." image in the RSS News Box (see source code)
What I am doing, after the RSS news XML file is available in the request/response object, I replace this <div> tag with a new "constructed" one (that then contains the RSS News). More details also here. I "construct" the new div tag (then with the RSS News) in this createrssfeed.js file and finally replace the old with the new div tag. I hope this gives you an idea, what you can do with the DOM methods. Honestly, I love them ;) If you still have questions, just trackback ;) -Joern ]]><div id="trackslist" class="trackslist"> <p id="FLloading" style="text-align: center"><br /> <img src="images/waiting.gif" alt="Please Wait" border=0> <br /><br />Loading... Please Wait</p> </div>
Since I really finished my Mini-Project, here are the 3 major new features in my iteration 3 (in comparison to iteration 2):
Finally I fixed this with a little CSS update (I just removed the "width: 100%;" attribute from the outer div box).
And based on Andre's very good tip about the "Multiple IE's" software (Amazing!!!), I tested my Formula One Tracks & News Mini Project now in FF 2.0.0.3, IE 7, IE 6 and IE 5.5.
So, now, feel free to access my Individual Mini-Project "Formula One Tracks & News" here and test it. Your feedback is always welcome!
@Bud: I didn't post a link yet, because the project was in a "release development folder" (different versions) and I first had to move it to it's current location ... but here we go ;)
So far the update and probably the last post concerning my Mini-Project "Formula One Tracks & News"
-Joern
]]>
Now I will optimize the CSS a little bit (one little bug in IE 6) and then my mini-project is completed :-)
So far the update,
-Joern
]]>
Additionally I found these interesting Blog Posts:
"New Google Maps feature: "My Maps" (Build your own maps mashup)"
"Google has just released a new Google Maps feature called "My Maps" which will allows users to easily create a Google Maps mashup with a few clicks, right from Google Maps! You can reach My Maps by visiting http://maps.google.com then look for the new "My Maps" tab on the left side. My Maps is being launched for Google Maps in the US, UK, Canada, France, Italy, Germany, Spain, Netherlands, Japan and Australia." "My Maps has an easy to use interface that will allow you to:and some more detailed information here "Google My Maps Mania!". Just try it, it's amazing: http://maps.google.com/ It seems like that the “MyFavoritePlaces” team had the same idea ;) -Joern ]]>
- Annotate points on a Google Map with text, photos, or YouTube/Google Videos (even HTML for further customization)
- Draw lines and shapes to show routes and regions
- View maps created in My Maps on Google Earth
- Search for businesses on Google Maps and add them to My Maps"
Enjoy MapYourBuddies!
-Joern]]>
Does anybody know, why these cities in the demo account cannot be geocoded???
Ask me in the weekly progress presentation tomorrow and I will explain it ;)
Also we will demonstrate this functionality with our real Facebook account in the weekly progress presentation, tomorrow. (Where you can really see what some friends have written into their hometown location - sometimes it is just unbelievable -)
Anyway, a "problem" I faced was that the friends list is now "sorted" in that way, how the friends come back from geocoding - and this is each time different - (And not longer in the Facebook xml order). Thomas experienced this challenge already for the marker creation process. This is because - how Thomas already found out - "The showAddress function must somehow run asynchronous and independently after called"But at the end of the day, all friends are now displayed in the list. Friends with marker on the map are "clickable" and friends without appropriate hometown location are not "clickable" but are still in the list. And for iteration 3 we won't manipulate the order of the friends in the list; Maybe in iteration 5 ;) So far for now, -Joern ]]>
var friendslist = document.getElementById("friendslist"); var LoadNode = document.getElementById("FLloading"); friendslist.removeChild(LoadNode);
Like always, more in the weekly presentation ;)
-Joern
]]>
"To enable a user to logout of Facebook, POST to http://www.facebook.com/logout.php, with the parameter "confirm" set to 1."As a result of this, when we just link to this page, the log off works, but then the user sticks with the logout/login page from Facebook.com and there is no way for the user to come back to our MapYourBuddies application. And this is what we wanted to avoid. The most elegant way would obviously be, when we could have added a parameter to the logout url (like "http://www.facebook.com/logout.php?next=welcome.html") that brings the user back to a specified page. BUT that is with the current API not possible. The Workaround for the Workaround ;) Due to this limitation of the API we had to build the first workaround. We now use the "logout" link to load the "Welcome" page. With an "onclick" event for this link we open a new "pop up window" and within this window we submitted the "Facebook logout form" automatically via a JavaScript:
So far so good. But now we had the problem that we had this open "pop up window" with the logout/login page from Facebook.com. And because we do not have an influence about the Facebook page, we were not able to close this window, after the Facebook page was loaded. Therefore I build the second workaround: Instead of loading the logout/login page from Facebook.com complete into the "pop up window", we now load a frameset and display a "Good Bye" page (that also closes the window after 10 seconds) and the logout/login page from Facebook.com is loaded in an separate and HIDDEN frameset ;)<script type="text/javascript" language="JavaScript"> document.logoutform.submit(); </script>
Basically now the Facebook logout works and we have a neat "Good Bye" page that now closes the "pop up window" and displays with a JavaScript Countdown when the window will be closed automatically. But the user may close the window just by clicking the provided link at the bottom of the logout page.<frameset rows="*,0"> <frame src="logoutPage.html" name="Counter"> <frame src="facebookLogout.html" name="Formular"> </frameset>
Now, we also fixed this Challenge. And Thanks again for all your input!
On Wednesday we will present this new feature in our weekly presentation.
-Joern
]]>