The default start screen has been changed. You can now start a new wave containing some prefilled content.
Templates are not something new The Shiny Wave had a post about a user contributed list of Wave templates. I’m not sure if any of the templates from the project has been reused. But some of the ideas have. The difference is that with this new addition you do not have to find a wave template and the create a new Wave based on this.
An example of this looks like this.
The idea is fantastic, it will allow you have some much better synchronized and harmonized waves. It seems like it is missing the option of adding your own templates to the list. It could be some extensions you added or something defined in your Wave for your Enterprise.
Hi Everyone! We’re presenting you a simple 5-part video tutorial showing a sample in creating a google wave gadget using flex (Flash Builder Beta as the IDE and Flex 4 as the Compiler). The application is of the same with the common flash actionscript file having a counter button that increments the result number by 1 and a reset button that resets the result number back to 0. Any of the participants that will click the buttons will be able to update the state having them with the same result on their screen. Apologies if you find the video not clear enough and so as the speaker or mispronounced some words but hopefully you’ll be able to follow and at least this will give you a head start.
The 1st part of the video is some sort of a short introduction to flex showing how to call or place given components from flex through typing the codes or dragging the component in the design view.
The 5th part is the last part of the video that shows how to publish a release build of the application/project and compile with all the files needed to get it work as a gadget in google wave.
Reminders: You always need the wave-as-client as the library of the flex application and make sure to have the wave-as-client.js placed in the same folder of the release build. In creating a gadget.xml, just make sure you’ll be able to apply an extension code to the url of your flex swf file application to avoid caching to prevent problems in updating and testing the application on the wave.
Thank you so much for the time and hopefully the video is helpful. Have a blessed and healthy day everyone!
When you are working on designing your business or a product launch, it requires the use of some of the strategic tools. It can be the SWOT, PEST or PESTEL or the BCG growth matrix. Normally work on those tools is done in a room and on a whiteboard. The whiteboard is a really great way to work and it can make people work together and create a lot of interesting content. It though has some challenges for teams that are not sitting together or are difficult to get in the same room.
With Google Wave can collaborate on creating the same result. But then you will have to use different blips for managing each cell and this can lead to some unstructed content. With the help of a gadget there can be more structure on the content. See the following video to see what the gadget is able to do.
I’m looking forward to see when the Appstore for Google Wave will be released, so it is possible to sell the gadgets and spend more time on development of the applications. At the moment the gadget is only avaible for subscribers of our newsletter. Signup to the newsletter today and get access to the gadget.
Are there any other models that you will propose we implement?
I tested quite a bit of different Google Wave gadgets in my christmas calender last month. I tried 40 different apps with a large verity in their complexity and usability. Some of them did not have any useful functions or did not work.
I really liked many of the ideas created in the gadgets and some was really useful. It was fun to see how people wanted to impress with new ideas.
The quality of the gadgets and robot was lausy. Mine included. I believe that many of to my application must be improved. But with the limited option in the robot API hinders making layouts to shine. It also provide a hindering there is a lack of way the gadget/robots can work together. If there was a better way to make the gadgets/robot work together, the layout issues could be solved.
I will say that most of the gadgets except maybe the simpler voting gadgets all require extra work before they can be used by a wider audience. The robots where you need to write commands with # or ! as the only thing in blip, I doubt that my mother will pick it up easily which is required to get non tech savvy users on board.
One key to make it possible to get the robot to function better is to pay the developers. I guess most of the developers of the robots/gadgets I have seen just tried the protocol out of see if they could make something useful. And they can. But to make them look wave-y the gadgets need to look better.
To make the gadgets/robot complete we need to be able to get some better apis and more importantly be able to charge for your apps. Currently it can be possible to charge for the usage of a robot and with some development also a gadget, but it is a pain and will require to much of the user.
I’m therefore looking forward a Wave app store is created. It will be interesting to see if it only supports one time payments or monthly payments and maybe even corporate multi seat licenses. The wave app store will mean that more developers will start with developing programs for Google Wave, making the platform more attractive.
I’m currently only letting my apps be available to my mail list subscribers. We have a new scrum gadget that just need to be published. So sign up to the newsletter and try it out.
