Ray, Bilgin,

Quickly, first, no surprise I'd rather suggest to extend the POS.

De : "Ray Barlow" <[EMAIL PROTECTED]>
>Any thoughts out
> there as to whether the XUI layer could be bundled through a browser and
> us something like RPC for the server calls?

 This might turn interesting : 
http://xui.sourceforge.net/wikka/wikka.php?wakka=XUI3 see Added an HTML 
Builder. But beware I already
did some tests with XUI v 2.0.7 and we are still stuck to 2.0.6. This should 
not be to hard though and I hope to migrate to v3 one
day (not enough hours in a day, a pity ;o)

> Re orders, seems like a lot of effort to control lots of orders for a
> table. You can apply multiple payments to an order, although that is not
> specifically related to ship groups at the moment, if you choose that
> route you could easily make that association. About speed I'd be
> suspicious about the order editing code as it exists today because as it
> has evolved over time it has lost it's way little and is already ear
> marked for a rewrite (when someone has the time/effort/investment to do
> it), it pretty much recreates the order and that could be to costly for
> your environment.

Yes, speed might a problem in a restaurant I'm afraid. Though when cached, thru 
the POS it's not so slow. This makes sense, less
functionnalities, faster...

> Ray
>
>
>
> Bilgin Ibryam wrote:
> > Hi everybody,
> > sorry for the long post, but please read ahead and tell me your opinion.
> > I have to implement a web based pos system for a restaurant.
> > Before start coding i will be glad to hear your opinions and advices.
> >
> > First of all i decided to go web-based instead of using existing ofbiz POS
> > because it does not cover all my needs. In the restaurant i need:
> > 1) To enter the registered customers for order payments.

I hope to do some work around this on POS before end of year, maybe soon 
(waiting for a client).

> > 2) To edit orders.
> > 3) To do Returns.
> > 4) To visualize tables, seats, to do table reservations...
> >
> > I decided to do a new ofbiz component, with UI similar to pos (but html, not
> > swing) for easy using with touch screens, that allows order entering in a
> > fast way (similar to order manger but with possibility to enter orders in
> > lesser clicks).

Did you chose to use html because there aer already some screens and logic 
available or have you deeper reasons ?

> > Is there someone that has experience in this kind of things that can give me
> > some advice? Do you see any possible difficulties and drawbacks in doing a
> > web based pos system?

I think it's doable, at least this exists here http://www.fastmag.fr/?lang=eng. 
But it seems that this system is used mainly in
dress shop, restaurant is harder to deal with I guess. Here you can even test 
it http://www.fastmag.fr/page.ips?p=demo (just ask for
login/pwd)

> > About the implementation:
> > The other thing that i have to care are the tables and people setting there.
> > For tables i can use Fixed assets, but i cannot decide how to handle/group
> > customer orders.
> > 1) One way to go is to create a separate sales order for every person, so
> > everyone can pay only for his/her products.
> > Then i can group the orders for the table with a work effort. I need to
> > group the orders, because i need all the time to calculate the total for the
> > table, the total product list and the complete all the orders for the table
> > with one click, if needed.
> > Do you think that manipulating lots of orders could work fast enough,
> > because for example the order creation in ofbiz is heavy_weight/slower than
> > other operations?

This might be very costly in time

> > 2) The other way to go is to create only one order per table at a time and
> > to create separate ship groups for every person. This way i can assign
> > parties to ship groups, but it is NOT possible these parties to pay only for
> > their products in the ship group. Is it possible somehow? This way i have to
> > create, edit , complete only one order for all the people setting around a
> > table at moment.

Ray suggestion (multiple payments ) seems better to me

> > (In general my questions are: is it a good idea to do a web based pos and to
> > manipulate lots of orders at the same time (like one order) regarding fast
> > working needs of a pos system ?)

This is more related to the underlying code than the UI, I think. The brower 
eats a bit of CPU but less disk accesses are involved.

Looking forward for your project.

Good luck

Jacques

> > Please advise and thanks in advance.
> > Bilgin Ibryam
> >
>

Reply via email to