- Deploy stable enough 5.1 to wish.flurdy.com
- Start 5.2
- Split services module into separate war
- Start Shop module
2010 plan
December 4th, 20092009 review
December 4th, 2009- 4.1β deployed to wish.flurdy.com
- 5th revision started.
- Source control moved to Mercurial.
- 5.0 tagged in May as βeta and deployed to grid.flurdy.com/wish.
- 5.1 started in May. Αlpha deployed to grid.flurdy.com/wishlist.
- New MediaWiki based wiki in December. sf.net/apps/mediawiki/wishlist/.
- New technologies introduced: Apache Wicket, JavaRebel/JRebel.
New wiki
December 4th, 2009We have moved our wiki (again).
The first wiki, wishlist.wiki.sf.net using wikispaces functionally was really good, but with a very large header section making actual content less readable.
Sourceforge discontinued this wiki and moved the wishlist wiki to a Trac based wiki, sf.net/apps/trac/wishlist/. This integrates with issue management etc. However I found it very messy.
So to have a cleaner and easier to reach wiki I have now moved the wishlist wiki to a MediaWiki based one: sf.net/apps/mediawiki/wishlist/. I hope this will be more efficient.
May 2009 update – v5.0-beta
May 21st, 2009Version 5.0 is tugging along nicely, and was today tagged with 5.0-beta-1, so it is entering bug fix mode.
Will create a downloads version of it. It is a complete rewrite so quite basic compared to v4.1.
beta-2 may be done, any RCs is unlikely.
Bring version 5.1, expecting to have a first alpha milestone during June.
wishlist 2009 plan and 2008 review
February 19th, 2009First a quick report of what happened in 2008.
- The fourth major rewrite of wishlist was started, hence version 4.x. More detail of architecture in earlier posts.
- 4.0 went to beta in august. But was never made into a release, as it was a silver bullet with many missing features. Basically you could only browse wishlist and its items.
- 4.1 went to beta at the end of September. It had much more features than 4.0. And it was quite useable. A full editing suite with access rights etc. However it was not polished enough to be released.
- 4.2 was started and milestones met, but never made it to beta. It added more usefull features and a facebook client.
So what for 2009?
- Well, the development 4.x branches has for now been stopped.
- A new 5.0 version has been started. Yes, it is the 5th rewrite. I know perpetual rewrites and never finishing. The bane of a one-man-project.
- New technologies has again been introduced. This time it is Apache Wicket, Grails and Mercurial.
- Support for multiple unconnected applications. Enabling smaller standalone wishlist applications to be developed (Grails).
- Wish-enterprise will be the name of the main application. Which will be using the same architecture as before, of multiple clients, web, mobile, facebook and web services to back end system.
- Restructuring of domain objects. Supporting tags from the start. Idea of a pool of wishes and belonging to several lists via tags, and also location, events etc.
- Try to learn from earlier problems in development model…
wish-4.0-beta-1
August 18th, 2008First beta of wish version 4.0 has been tagged!
In features it is basic compared to 3.1, as only the core add, view, edit and remove for wish lists and items has been implemented.
But is a complete rewrite, with new architecture, testing modules, admin modules, application server modules etc.
Since this is a beta, from now on no new features will be added to the 4.0 version. Some bugs and UI tweaks will be done before a release candidate will be made. A full release might not be done, as it is a featureless release, and this project is a bit perpetually beta (googleish).
With this tagged, a 4.0.x branch will be made from the tag, and the trunk will move to version 4.1 so new features can be added. (A slight cleanup of the svn structure will also be done)
For a confirmed feature plan visit the roadmap, or possible features look at the plans page.
Version 4 to trunk
July 25th, 2008After the tagging of milestone 3, the 4th version/rewrite is now mature enough to move to trunk.
Not all usability features from version 3 are implemented, but will be soon. Check roadmap.
New architectures are mentioned in previous post, but basically, split across many sub modules:
Server modules: web services, business logic, domain objects, xsd schemas, oxm marshallers.
Client ones, with a tools module to connect to servers, web reference app, facebook app, flex based app and mobile app.
Admin modules, server and client.
Testing modules, fitnesse and fixtures, soap and jmeter.
Ear moduels, for deploying a whole stack.
New(old) technologies:
Spring web servcies.
Spring security on client, reusing gold Acegi.
Spring security on server for ws-security.
JAXB marshaller for easy xml conversion, but not required as duck typing is encouraged.
Spring mvc.
Struts tiles.
Hibernate/JPA 3.
HSQLDB.
Jetty for easy development and deployment if needed.
Maven 2 for building.
Subversion for VCS ( hopefully mercurial/bazaar soon)
Version4
June 17th, 2008Guess what.
Version 3 has been released and deployed, had minor fix to it, and is nearly finished, so guess what?
Im starting version4 from scratch…
Typical one man project. constant changes and rewrites… 
~/app/branches/dev/flurdy/version4 is now the currently developed branch. When nearing stability it will move to trunk.
New features of this version is even more modularity, seperate admin applications and newer architecture, but still basically the same, i.e. seperate server and client applications, spring web services, jetty server, hibernate, hsql db, spring mvc, facebook application, flex client etc.
version 3 to trunk
November 29th, 2007Right, decided that the 3rd revision of the wishlist application is ready to go to the trunk.
So this branch
https://wishlist.svn.sourceforge.net/svnroot/wishlist/app/branches/dev/flurdy/version3
will now be available here
https://wishlist.svn.sourceforge.net/svnroot/wishlist/app/trunk
This new version has split client(web) from the application(server).
It has also been split into seperate modules. Ie.:
- jpa entity and dao module wishDate.
- wishWish for all wishlist specific logic.(and eventuall shop, gift etc).
- wishServices for web services.
- wishWeb for a reference web client.
- wishFlex for a possible flex interface.
- wishFacebook for a possible facebook application.
Of course this is all very alpha. It utilises maven, jetty, jpa/hibernate, hsql, spring-ws, acegi.
Major items still to do is:
- Security – authentication, authorisation and encryption between client and web services. Currently the web client has acegi login but that does not talk with the web services, so is not properly linked.
- Message bus. Going to integrate Mule, so maybe utilise its security options.
Also does not have all the functionality of previous versions.
Major missing items:
- Wish reservations
- Shopping link
- Wish details
Version 3
October 1st, 2007As im still the only developer on this project, it is still suffers from me testing fad techs.
Version 3 is now being developed, but earlier versions was never finished..
Now it includes spring web services, and thinking off integrating Mule between clients and back end application.
Current development branch is
http://wishlist.svn.sourceforge.net/viewvc/wishlist/app/branches/dev/flurdy/version3/