If you're wondering why I've been quiet, it's because I'm at Eclipse Summit Europe 2007 in Germany demoing and talking about the AJAX Toolkit Framework. While I'm here, though, I've seen some interesting technology I wanted to share.
qooxdoo is a very cool looking AJAX toolkit that's actually been around quite a while. Right now it's more geared toward building an application from the ground up. The widgets look amazing! Check out the demo. Incidentally, the RAP project is using qooxdoo to render RCP applications in the browser.
When I first heard about Jazz, I thought it was yet another bug system. Boy was I wrong. This is a very cool tool set that helps people collaboratively build software. It's being used by the Jazz team to build Jazz. You should take a look.
That's all for now. Next up is a week at home and then off to Ajax Experience. See you there!
Hey Google, Yahoo! and 30 Boxes (and others).
PLEASE create places where I can simply POST vCards or iCals or microformats or JSON or something else to your services to add contacts and calendar entries. I'm not a web app, so I can't get an API key. And I shouldn't have to maintain login state when the browser is doing it for me. All I want is an easy way to add stuff to a logged in users account. Is that too much to ask?
With Yahoo! calendars and contact, as well as Google Calendar, I have to resort to undocumented URL syntax. Google Contacts I can't do anything. 30 Boxes requires that the ics file be physically located on a server, although they have a URL syntax that kind of works.
It doesn't even have to be a POST. If you could come up with some straightforward URL syntax, that would be great. Trying to figure out the stuff you guys have put together so far is incredibly painful.
So please. Help a guy out.
Cross-posted from the Enterprise2.0 blog
Call on Sept 19th was about useful Extensions for the Enterprise. A larger portion of the meeting, however focused on the apparent dwindling interest in Enterprise Firefox within the larger community.
Is the Enterprise simply not ready to bring Firefox in-house? Or, are the majority of institutional adopters simply happy with a consumer product floating about?
Perhaps one of the problems is that we still talk about Firefox as a Web Browser as opposed to a "Productivity Platform" for the Desktop.
Firefox is a Productivity Platform
All the features that make Firefox a consumer favorite deal with productivity. Tabs, keywords, search bars, extensions, dictionaries, etc help us be effective and productive in our work and home lives. When consumer says "better usability", enterprise says "better productivity".
Mike Kaply spoke about adoption at IBM. Developers are finding ways to enhance the end-user experience by writing custom extensions for Firefox. Whether the extensions glue several applications together or simply automate the tedious process of filling out web-forms, end result is a boost to productivity.
If Firefox is the gateway or glue between what's on the Desktop and what's on the network, potential for productivity-boosting application is something to ponder.
Mike and I are going to take lead on a few initiatives to help raise awareness on the Enterprise Firefox front:
- 10 Steps to adopting Firefox in the Enterprise -
Now that we've begun to pool experiences, we should be able to bake out a definitive guide of sorts for things to consider when bringing Firefox into an enterprise environment
- Good Ol' Conference -
We will begin looking at opportunities to present at some Conferences
- Blogging - check...
- Code Day and Training -
The learning curve for any kind of Mozilla-related development is rather high. Perhaps training targeting institutions and enterprises (like an Enterprise track) will help developers scale this wall.
- Enterprise Firefox Incubator -
Talk has alway been cheap. As we address settings management, security, tools etc we will kick off projects within the Enterprise Working Group.
Enterprise Working Group Incubator
On my end, I'm going to kick off some projects for the Incubator. Specifically there has been interest in:
- Mission Control - how to get up and running, what the back-end implementation can look like and benefits over GPO
- Customized Reporter Extension - so that you can redirect Broken Website reports to a repository on your intranet
- Managed Security Zones for Firefox - how to configure and lock capabilitiy.policy settings in Firefox, how to create a "trusted" zone and fully leverage Web2.0 technologies within your trusted intranet.
As always, if any of these topics or projects are of interest to you, please visit the wiki, participate in the calls or simply leave a comment on this here Blog.
What's exciting is that we final got all through all the legal hurdles so you can now download one package that contains the entire environment, with stuff that isn't relevant to ATF removed. So just download the M4 milestone from here, unzip it and you can try it out. If you want to see how it works, you can check out the demos, but note that we are in the process of updating those to the new version.
I'll be at AJAXWorld next week talking about this project so feel free to look me up. I'll definitely be at the ATF presentation on Monday at 5:40 and I'll probably be hanging around IBM booth on the Expo Floor at other times. If you want to set up a time to meet with me about something specific while I'm out there, feel free to contact me.
The website iDOO added support for hCards and created an Operator user script to integrate with iDOO. The even plugged Operator in their announcement. Nice work!
You can get more information here.
So it's only been a month or two, and participants on the Firefox Enterprise Working Group calls have dwindled. So I'm putting out this plea:
If you are at all interested in Firefox in the Enterprise, please either post to the Firefox Enterprise Wiki (participants section), participate in the call or reply to this post with your thoughts.
If we are ahead of the curve here and need to slow down or if phone calls are the wrong communication medium, we want to fund that out. We also need to know is if this is something that is important to a lot of folks or if it's only important to a handful of people.
So please, let us know what you think we should do next.
Here's the info about the next call:
We’re planning our fourth call for Wednesday, September 19th at 10:00am Pacific, 1:00pm Eastern, 17:00 UTC. Here’s the meeting details:
- 650-903-0800 or 650-215-1282 x91 Conf# 280 (US/INTL)
- 1-800-707-2533 (pin 369) Conf# 280 (US)
- IRC - irc.mozilla.org - #ewg
The theme is "Extensions." We're going to talk about how folks are using extensions in their organizations.
Other upcoming calls include Deployment and Microsoft Group Policy vs. Mission Control.
I'll be away for a few days, and since I'm not famous enough to have a guest blogger, feel free to watch these podcasts of what I'll be doing.
Disney Cruise Line Podcasts
I'm going to hold off on an EWG meeting this week. Our next one is scheduled for Sept 19. The topic will be Extensions, since the last meeting didn't happen (Sorry about that).
We're already starting to see things kind of drop off. I'd REALLY like to try to make sure that doesn't happen. So if you have any interest in Firefox in the enterprise, please plan to attend the meeting on Sept 19. And please feel free to read/update information on the Enterprise wiki.
In my Enterprise series, I mentioned an extension from IBM called Koala that could be used to automate business processes.
This extension has now been made available via alphaWorks Services as CoScripter.
From the web page:
CoScripter is a system for capturing, sharing, and automating tasks on the Web. CoScripter scripts contain human-readable instructions for completing Web-based processes, such as changing your mailing address or searching for real estate. If the CoScripter plug-in for Firefox is installed, CoScripter can step through scripts with you, showing you how to perform the task, step by step. CoScripter can also run scripts automatically, eliminating repetitive or mundane tasks for the user.
There's a more detailed post about it at Luis Suarez's blog.
Go check it out. It's pretty cool.
Operator 0.8 is now available from addons.mozilla.org.
One of the first things you'll notice is that I changed the default view to be data formats instead of actions. I did this because I found this is what most people did anyway. If you disagree, you can go to Operator Options and switch back to options.
You'll also notice that if you did any customizations, you lost them. Unfortunately I did some preference rewriting this time around and the migration was getting to be painful. It shouldn't happen again.
Some of the new features in Operator 0.8 include:
- RDFa support (courtesy of Elias Torres)
- eRDF support (courtesy of Keith Alexander)
- New user interface elements, including an icon on the location bar as well as a sidebar
- New preferences including auto-hiding the toolbar
- The address microformats has been split out so that actions can be more granular
- Actions can now be associated with multiple types of data, so the Google Maps action, for instance, works with Addresses and Locations
- Much better support for frames and iframes
- Support for non HTML documents
- When debugging microformats, Operator connects to Brian Suda's X2V behind the scenes so you can compare results
- Lots of bug fixes
I had to break user script compatibility with this release. Most user scripts have already been updated and can be found on the user script page. I also changed the location of user scripts, so old user scripts won't conflict.
Finally, I've created a page specifically to talk about Operator. If I've missed anything, please let me know. And feel free to visit my weblog and take my poll about how you interact with Operator.
Special note to users of the 0.8 betas - you'll need to go Options and delete "RDFa" and re add it as "RDF" to get RDF functionality back.