https://sourceforge.net/p/ushop/wiki/Design/Recent changes to DesignenSun, 26 Feb 2012 23:12:29 -0000https://sourceforge.net/p/ushop/wiki/Design/<pre>--- v1 +++ v2 @@ -1,5 +1,10 @@ This Wiki Page captures key design considerations and limitations. +User Interface (UI) +------------------- +Currently uShop is designed to be run on a standard Windows PC using a normal screen, keyboard, mouse, barcode reader (USB or Keyboard wedge compliant) and desktop printer. +In future it may be developed to support more specialist POS hardware, but this is not in the "basic" requirement. + SDATA ----- This offers the ability to both get data out and put data directly back in to Sage 50. This is a good thing and is implemented through a webservice - which is great. </pre>JimSun, 26 Feb 2012 23:12:29 -0000https://sourceforge.net650c76b992c3ec6200534c1cc99735f7a2698e83https://sourceforge.net/p/ushop/wiki/Design/This Wiki Page captures key design considerations and limitations. SDATA ----- This offers the ability to both get data out and put data directly back in to Sage 50. This is a good thing and is implemented through a webservice - which is great. Unfortunately, not all features support both GET and PUT. It also still appears to have errors in the interface, which allow some actions (such as Invoice posting) but not others (such as Credit Note posting). Performance ------------ Performance is a real concern when starting this project. Sage 50 is still built on the original Line 50 database, which has poor performance and scalability. The decision was made that the starting point would be to use the Sage 50 data in real time to start with. This gave best data integrity and a joined up feel. It may however be required to implement some form of accelerator.JimSun, 26 Feb 2012 22:48:08 -0000https://sourceforge.netd0cac06d21fb25d9debfe5bc785aa93fb78094ce