OpenUnderwriter is delighted to announce the arrival of Google Web Toolkit (GWT) into the project.
We chose GWT to provide a richer and more interactive web UI experience for end users of the OpenUnderwriter product suite. We looked at a few other technologies for the job including JQuery, Vaadin and Yahoo-UI, but in the end GWT won through for us on its cross-browser support, flexible internationalisation, responsiveness and rich features. Plus, being Java based makes it consistent with the rest of the OpenUnderwriter project.
How can you tell how much your open source software is being used?
One of the questions that haunts many open source projects is
How much is the thing we're developing really being used? For commercial software, it's an easy question to answer, you can count the licenses. It's indirect of course - you don't know that someone who owns a license is actually using the system - but it is accurate enough for most especially as it generally relates to income!
OpenQuote still exists, but it is now a component application within OpenUnderwriter.
There has been something of a hiatus in OpenQuote 2.0 development lately, but the break has allowed us extend the scope of OpenQuote which is something we're very excited about. In fact the scope has been extended to the point where the name "OpenQuote" is now simply too restrictive. So we've renamed the whole project.
A fortnight has passed since the last release, so it was high time to get another release out with the latest set of fixes and enhancements.
The EA3 release includes two big enhancements along with a collection of smaller fixes. The two big things are the addition of support for multiple PageFlow types and a much enhanced sandpit portlet.
Well, you probably guessed it: EA2.
It's just under a month since EA1 was release and the number of changes that fell into the
that's really quite useful category had reached a critical mass. Also, naturally, being an open source project we always aim to
release early, release often.
The first early access release of OpenQuote 2.0
Finally. It's been quite a long haul to get here, but I've just published the first early access release of OpenQuote 2.0 to source forge as a packaged, downloadable binary.
We're making swift progress towards the first Early Access (EA) release of OpenQuote 2.0.
It's quite a while since I last blogged, but we're making swift progress towards the first Early Access (EA) release of OpenQuote 2.0. If the term EA doesn't mean anything to you, there is a page on the page on the wiki that explains all.
The old OpenQuote JIRA is dead. Long live the OpenQuote JIRA.
I'd been putting off migrating our old JIRA to Atlassian's OneDemand service (which I blogged about a while ago). But now it is done, and it turned out to be a lot simpler than expected.
The last of the fixes necessary to support the quotation portlet are now committed to the 2.0 branch.
It'll be nice to be doing some UI again after such a long spell in the darkness, but more on that later.
OpenQuote 2.0 will be an earless release.
As I blogged last time, up until 2.0 OpenQuote was packaged into an EAR, but issues with Liferay's support for portlets within EARs has lead us down a different road now, and it's not one I'm sorry to be travelling down.
Moving from a JBoss Portal/Alfresco platform to Liferay
I was expecting that the job of moving OpenQuote from the old JBoss Portal/Alfresco based platform to Liferay would be a pretty tough one, but so far... well... it just hasn't been.
A big thank you goes to Atlassian this week for allowing the OpenQuote project to use their OnDemand service absolutely for free!
Atlassian's JIRA and Bamboo have been a mainstay of OpenQuote project development since we outgrew the support that SourceForge offered many years ago. They are both essential and excellent products.
Migrating away from Alfresco and JBoss Portal
Alfresco and JBoss Portal have been part of OpenQuote for a long time now and both have served the project very well. But, for 2.0, the wind of change is blowing.
Opening up alternative ways for users to communicate with OpenQuote.
Opening up alternative ways for users to communicate with OpenQuote is something we've been giving some thought to lately. While 1.4 had both HTML and XForms support, the reality was pretty much that you could use any markup you wanted as long as it was HTML. In truth, that works fine for most applications, but with our growing focus on Microinsurance we need more flexibility.
One of the major changes include in OpenQuote 2.0 is the use of velocity templates to drive the product user interface.
I'm pleased, and not a little relieved, to say that the job is now done. It's been a long haul.
The advantages of implementing UI widgets as velocity templates are enormous in terms of flexibility, especially as it is implemented an intrinsic part of OpenQuote's product structure.