TheNextWeb reports Twitter no longer displays what client a tweet was posted with on web.
Twitter has removed the ability for users to determine exactly what client was used to post a message to its service from the web client. This was previously removed from its official iPhone client and that change has been removed from the web version as well.
Twitter is likely attempting to reduce the exposure of third party applications. Applications such as gladlyCast and Seesmic are affected.
(Autoscaling Google Maps with multiple markers.)
I just want this tutorial to be focused on autoscaling so I’m not writing how to display the markers like the screenshot above. There’re many articles and demos covering that subject much better than I can. If you just like to see the full set of codes, just scroll to the bottom of the article.
1. Creating the Google Maps object
First, we’ll need to create the Google Maps object which initialize Google Maps on your webpage. I have a div element with the id “panel_maps” which I intend to use for this tutorial. This would initialize Google Maps as an object but I haven’t specify the centering and zooming parameters yet:
2. The minimum and maximum of latitude and longitude
I’m skipping this step to get the min and max of the latitude and longitude since the method is largely dependent on how you iterate through your data structure. I will use the following values for the minimum and maximum:
var lat_min = 1.3049337;
var lat_max = 1.3053515;
var lng_min = 103.2103116;
var lng_max = 103.8400188;[/code]
Continue reading How to autozoom and autocenter in Google Maps
Google announces that Google Wave is to be no more, amongst reasons cited are that it hasn’t gain the traction Google has hoped for. This is hardly surprising for me, Google Wave is just too complex for most. It tries to be everything and failed to stand out.
(It’s time to wave goodbye.)
Update on Google Wave
Wave has not seen the user adoption we would have liked. We don’t plan to continue developing Wave as a standalone product, but we will maintain the site at least through the end of the year and extend the technology for use in other Google projects. The central parts of the code, as well as the protocols that have driven many of Wave’s innovations, like drag-and-drop and character-by-character live typing, are already available as open source, so customers and partners can continue the innovation we began. In addition, we will work on tools so that users can easily “liberate” their content from Wave.
Wave has taught us a lot, and we are proud of the team for the ways in which they have pushed the boundaries of computer science. We are excited about what they will develop next as we continue to create innovations with the potential to advance technology and the wider web. (Source: Google Blog)
RIP. And thank goodness I didn’t explore the Google Wave API much.
Google Analytics API has been launched as a public beta.
Attention Developers: Google Analytics API Launched!
A Google Analytics API has long been one of our most widely anticipated features. Today we’re pleased to announce that the Google Analytics Data Export API beta is now publicly available to all Analytics users!
What’s so exciting about an API? The API will allow developers to extend Google Analytics in new and creative ways that benefit developers, organizations and end users. Large organizations and agencies now have a standardized platform for integrating Analytics data with their own business data. Developers can integrate Google Analytics into their existing products and create standalone applications that they sell. Users could see snapshots of their Analytics data in developer created dashboards and gadgets. Individuals and business owners will have opportunities to access their Google Analytics information in a variety of new ways. (Source: Google Analytics Blog)
Here’s the documentation.
And so… Windows 7 is the name for the new version of Windows, the successor of Windows Vista. The thing is… It actually is Windows 6.1 if you check system properties and this has been confirmed by the Windows Team Blog. I don’t think it’s that great an idea honestly. I prefer the marketing version number to coincide with the development version number.
we decided to ship the Windows 7 code as Windows 6.1
Windows 2000 code was 5.0 and then we shipped Windows XP as 5.1, even though it was a major release we didn’t’ want to change code version numbers to maximize application compatibility.
That brings us to Windows Vista, which is 6.0. So we see Windows 7 as our next logical significant release and 7th in the family of Windows releases.
We learned a lot about using 5.1 for XP and how that helped developers with version checking for API compatibility. We also had the lesson reinforced when we applied the version number in the Windows Vista code as Windows 6.0– that changing basic version numbers can cause application compatibility issues.
So we decided to ship the Windows 7 code as Windows 6.1 – which is what you will see in the actual version of the product in cmd.exe or computer properties.
There’s been some fodder about whether using 6.1 in the code is an indicator of the relevance of Windows 7. It is not. (Source: Windows Team Blog)
In the case, I think it would be better to just call Windows 6.1 Windows 7. I think it’s clearer for developers who are going to start using the Windows platform.
Ahh, my eyes:
(Google App Engine and the color purple.)
This is what happens when you make a mistake in the helloworld demo. You get purple as a punishment. App Engine’s pretty cool, my only complaint is: Why can’t I quit the dev appserver with CTRL+C?!
It’s annoying and I have to re-navigate through if I want to restart the server. The solution is, well you don’t. As in, you don’t restart the server at all.