Here are all features I plan to implant into WeBasKet.
The current version is server ressources consuming because at each user action a page should be sent to the client.
It also have big latences for the user (the page should be reloaded a lot of times) and that's not so user-friendly as the desktop application BasKet...
I will then apply Ajax techniques (JavaScript interface + XMLHttpRequest seemless lite server request...) to make the interface more responsive and fast to use.
Since it's a big change in the code, I don't know if I will keep the interface for javascript disabled browsers.
As BasKet 0.5.1 and 0.5.2 will add new concepts and change how user interact with items, WeBasKet will add those new concepts (hierarchical items, item tags and styles...).
Finally, as BasKet features and concepts will be more stables and WeBasKet more mature, BasKet will allow to synchronize baskets by using the WeBasKet server, so a basket could be shared with several users, while continuing to use BasKet desktop application, or sometimes the WEB interface, etc...