Yes, but we have still this problem of JavaPOS. So that's why I'm going to
continue to maintain the POS.
At least it works (not the webPOS for now) and we can support the XUI version we have as we have still access to sources (I have to
check that and maybe take a copy in trunk).
That's what decided me : http://www.openbravo.com/product/pos. I can't believe
it, but I will not give up :o)
For XUI sources I have opened this Jira issue
https://issues.apache.org/jira/browse/OFBIZ-2157
Jacques
From: "Vince M. Clark" <vcl...@globalera.com>
Agreed, they could still use the web POS interface but run local instances. You would still have sync to deal with but OfBiz could
focus on a single POS UI rather than maintaining two.
----- Original Message -----
From: "Jacques Le Roux" <jacques.le.r...@les7arts.com>
To: user@ofbiz.apache.org
Sent: Friday, January 23, 2009 4:47:28 PM (GMT-0700) America/Denver
Subject: Re: Improper PULL synchronization from MCS
From: "David E Jones" <david.jo...@hotwaxmedia.com>
On Jan 23, 2009, at 3:06 PM, Jacques Le Roux wrote:
Yes, I agree. I think I will definitively put some effort on this
side (WebPos I mean). This for this reason and the others being that
XUI is no longer supported and we have issues with it.
So it's not yet sure but I'm more an more thinking that the POS
component will be legacy on day ...
I doubt the current POS will ever be "legacy" or be abandoned,
although it depends on how many choose to use it.
Typically organizations want easier deployment, so a web-based
application is great for them.
In some cases things are very "mission critical", like getting money
from customers in physical retail locations. In those cases redundancy
and minimizing single points of failure is important. If the internet
goes down or even the network in the store, they want each cash
register to be able to run independently. For all but the smallest
retailers that's a mandatory requirement.
They could use the same mechanims with WebPos isn'it (a local DB synchronized) ?
Jacques
-David
