A little demonstration of the mobile application.
Link to the final presentation
Links to all the the services and applications that have been build during the project.
KuantoKusta: http://kuantokusta-api.appspot.com
Register: http://uallet-users.appspot.com/
Payment (Stable): http://uallet-cs.meligaletiko.tk
Payment Client Tester: http://uallet-cs-client.meligaletiko.tk/
Composer: http://uallet-service-composer.appspot.c
Mobile: http://dl.dropbox.com/u/6625529/test.mob
Test Machine: http://uallet-machine.meligaletiko.tk
A aplicação mobile do projecto UAllet foi realizada. Encontra-se um vídeo da mesma no link:
http://videos.ua.sapo.pt/VblFwyUGtwSN9
ASP machine created.
URL: http://uallet-machine.meligaletiko.tk/
The test machine it's almost deployed and its needs an API to create QR Codes.
So i do a search on the internet for QR Code API's for ASP.NET and found a few but most of them are for commercial use.
I found a helper for a QR Code REST API. It creates the qrcode using its servers and returns receives it using REST.
To use the helper i use NuGet on Visual Studio to include it on the project.
Website: http://www.esponce.com/
ASP.NET Documentation: http://qrcodeapi.codeplex.com/wikipage?t
When using Payment Service in other services some problems appear because the king of WSDL style that i'm using.
I decide to search for the problem and get more information.
The payment service has been deployed last night with improvements.
I allows you to create new suppliers and add machines to the suppliers, as well modified methods to provide this new fields when requesting a new payment.
A bug that prevents different suppliers to have the same bill ID has been fixed.
Two more methods to provide queries to the service will be added.
Stable address: http://uallet-cs.meligaletiko.tk
Client to test the service: http://uallet-cs-client.meligaletiko.tk
Right now i'm improving the payment service. More work on performance has been made.
The payment service supports now, payments that comes from any entity. It was suppose to work but a bug was founded on the database. Now its corrected.
A lot of research was made on Propel framework to improve performance and stability when working with database tables.
A few background improvements made, like the developement of exceptions to return specific errors about problems that occur during the execution.
More two methods developed to support suppliers and his machines addition.
Expected to be finished tomorrow morning and starting work on machines website. This one will be developed in ASP.NET.
All functions with persistence.
Client with test functions in deployment. A few table will be created on web service home page to shows the database data.
. Encoded vs Literal on WSD...
. Payment Service release c...
. Current work on Payment S...
. New functions with persis...