Entries Tagged 'Development' ↓
August 8th, 2010 — Beginner, Development, Example
Since Google is stopping the development on Google Wave, there is not a lot of meaning in continue to develop apps for wave. The number of users is probably not large and there will not be a lot of new members that will join.
We at masteringwave and Figaf.com have spend the last year developing different examples of gadgets and robots to show what Wave can be used for. We had a project that was almost done, some extra futures could be applied, but the game is perfectly playable.
So I’m happy to announce Match ‘n Dash as memory game that lets you play memory against your peers. It is quite fun to use and I hope you get around to try it.
You can find the installer at this wave. I hope you get to try it.
July 7th, 2010 — Community, Development, News
A great way to make communication more ground-breaking is through creating an open-source web-based forum. And, this is why wave developers are being sought upon as a way to help create and develop more killer applications most especially for Wave.
In fact, it has already begun. The Google Wave Team aims to continue developing more powerful and better extensions for running forums in wave. And, to take it to the next level, the team aspires to incorporate tested features from forums into a robot which in effect can make Google Wave as the ultimate platform for forum-based discussions.
The objective is, improve Wave through incorporating forum which can encourage users to utilize it for other purposes instead of sticking to which is traditional.
And, according to David Crane, an external Wave developer working on the Debatewise Extension, there are three specific areas which need further developing, namely…
(a) Objective: To enable people go hand in hand around a theme of their choice and help find waves of interest. Tasks: Group waves around disciplines.
(b) Objective: To encourage and reward participation in conversations. Tasks: Stir in the levels of participation rates and privileges and the likes.
(c) Objective: To establish mechanisms so people can decide who to invoke or ignore. Tasks: List of all user messages and their classification in the community.
June 17th, 2010 — collaboration, Development, News
A new version of Google Documents is now on its transition process and a list of better features are presented to the public for a more developed data management. Here are a few to mention:
In this new addition, users are allowed to see updates from other collaborators as they do changes or editing in a specific document on a real-time basis. This feature is very helpful especially in situations when problems occur.
Higher quality imports
There is a better consistency of importing from a desktop into Google Docs. Scanning through files is no longer a hassle.
Communication through Chat
This is the most exciting part with the new version of Google Docs. As a user makes changes, he or she can communicate with other collaborators through the use of chat within the document itself.
Google documents have a ruler for setting margins, indentations, and tab stops.
These improved features above make Google Docs a lot more fun to use, however, many might be asking now if this innovation will affect Wave.
Is this going to be good for wave or will this mean that wave is no longer up for use? Or, does this mean Google Docs will gain better advantage over wave when it comes to collaboration?
Despite of these uncertainties, what’s good about this is that there are still remarkable differences between the two. One to point out is Docs doesn’t have the ability to work with robots which Wave is capable of doing.
Many might suggest that it may possibly be more interesting if Docs becomes a client of Wave. This way, collaborators can edit documents using Wave or vice versa, which really makes integration and work collaboration easier and faster.
May 25th, 2010 — Development, Enterprise
I have been a fan of using Google Wave for communication. I have started to use wave in the sandbox, but at that time, it was not ready for enterprise use. Nothing has changed until the announcements at Google IO.
- Google can be run on your domain in the Google Apps environment. I wrote on my experiences with this earlier in “Announcing New Google Wave Application Developed by Masteringwave.” I think that this is a killer feature of the Google Apps which allows more users to switch to Gmail, because they get the functionality they want.
- With the help of wave for Google Apps it is possible to sell extensions to users of Google Wave for Apps. With the Google Apps Marketplace, it is possible to sell applications that can be used on the domain. I see this as a really nice way to start the promotion and selling of products, because it leverages the authentication of users that already exists in the enterprise. I’m expecting that this so fair is the best way to start selling products for Wave, and the way Caseish will be sold.
- The groups’ functionality is going to be extended more, making it possible to tailor the groups’ experiences even better. This is something that from the Wave Fireside chat at Google IO was something that was going to be released at some point.
- There are at least three servers that can federate with GoogleWave Sandbox at the moment (SAP, Novell, and ProcessOne). I only think that SAPs Streamworks is the only one already available.
- The stability and users experience have grown. Now it is much easier to get started using Google Wave. You don’t need to be a geek anymore to start using Wave for your projects.
May 20th, 2010 — Development, Enterprise, News
Given the chance to be a participant in the event, I can say that Google I/O is really amazing wherein all developers are surprised with the new innovations when it comes to collaboration.
And, all of us are very surprised with the new API releases which were announced, namely:
“Wave This” Service
Run robots on any server
Fetch waves with Wave data APIs
Use a robot to manipulate and retrieve attachments
Other companies also presented their current innovations like:
Seeing all these announcements prove what Google I/O truly stands for…
According to Vic Gundotra, Engineering Vice-President of Google, I/O embodies the spirit of the Web, a spirit of collaboration, a spirit of inclusiveness rather than exclusiveness, and, a spirit of innovation and of openness.
I/O also stands for two most important elements of Web Culture: Innovation in the Open.
Keep posted for more updates!