Thanks for the response Christopher!

1)  Get the menu completely written down.  Figure out how best to enter in
these items.
---This is done already, I'm working with the Pizza Shop owner to get the
menu setup.

2)  Figure out how you are going to do credit card payment.  Through the pos
or cc box?
---We'll register the sale as CC but use the external CC reader to process
the sale

3)  Is delivery involved?  What is the process flow of having drivers? -
orders, payment, etc.
---I believe I'm going to a client address field, and add it to the store
receipt and print that for the cook and delivery.

4)  What hardware makes sense for you to use?  Touchscreen?  Card swiper?
 Receipt printer?
---The owner is more than willing to purchase the entire getup.  I'm going
to find some full terminal solutions that are JPOS hardware compatible (from
what I read, ofbiz is compatible with JPOS hardware correct?)

I'm lead to another question through all of this.  After quickly learning
how to modify the POS XUI screen, I'm very happy!  Although, Jacques
mentioned something that DemoRetail.xml isn't used with strictly seed data,
and that you need to use your "webapps" to create some sort of DB export to
xml for a "new - non demo" DemoRetail.xml equivalent.  I try not to pester
dev's too much with things I can learn though reading, but I have NO clue
how to do this, and can't find any literature.
While I'm on that subject, In the /pos/config/screens/default/menu  I notice
that the variable <Button name="{SKU, another button screen call, or
something else}>  I realize this is the "bridge" that the POS XUI uses to
connect to the actual products.  I've seen articles that the "Button name="
is related to the catalog and categories.  Although I can't find out WHERE
to find my product's ID"
To clarify.  I have a pizza.  A large plain pizza.  It's set in my catalog
under the pizza category.  Where can I go to find out what the "Button name"
of that item actually is in my DB?

This will get my snowball rolling down hill I think.  After which, hopefully
I'll gain a bit of speed on my own! ;)

Thanks!
On Feb 7, 2008 11:11 AM, Christopher L <[EMAIL PROTECTED]> wrote:

> Branden,
>
> Make sure to click on the yellow "configurable pc" in the POS.  It allows
> configurable items to be used (i.e. pizza with selectable toppings) and I
> it would imagine would easily suit your purposes.
>
> We need to get away from the "barcode centric" way that we pitch the POS.
>  Restaurants generally don't use scanners.
>
> To get a feel for what to configure, start in the pos/config and
> pos/screens.  Also check the applications/accounting/payment and
> framework/base/config/.
>
> I don't know how early you are in the process, but I'll give you random
> thoughts:
>
> 1)  Get the menu completely written down.  Figure out how best to enter in
> these items.
> 2)  Figure out how you are going to do credit card payment.  Through the
> pos or cc box?
> 3)  Is delivery involved?  What is the process flow of having drivers? -
> orders, payment, etc.
> 4)  What hardware makes sense for you to use?  Touchscreen?  Card swiper?
>  Receipt printer?
>
> Chris Lombardi
>
>
>
> > From: [EMAIL PROTECTED]
> > To: [email protected]
> > Subject: Re: POS - ProductStoreID - DemoRetail and other confusions
> > Date: Thu, 7 Feb 2008 07:12:50 +0100
> >
> > From: "Branden Strickland" <[EMAIL PROTECTED]>
> > >I was excited and typed that email too fast.. I need to proof read!
> > >
> > > Hah!  Thanks for the input!
> > > The only reason I don't see myself using the barcode is because I'm
> planning
> > > on using this application in a pizza shop that I recently got involved
> in.
> > > So unless I stick generic barcodes in a flip book or something, I'm
> not sure
> > > that's feasible.  ALTHOUGH!  If I can configure the buttons in the XUI
> of
> > > the POS to open new "windows" like the manager and promo button, then
> I'll
> > > be ok!  (You'll have to excuse me if I use the wrong terms, I'm a
> system
> > > admin (Linux based) with lots of experience, but this is the first
> time I've
> > > gotten involved in something that's still mainly in the development
> stage.
> > > It's my first time for svn and ant!
> >
> > Panels is the right way to do it un your case, I guess.
> >
> > >>>Which file ?
> > > the DemoRetail.xml file.  Which is why I was confused, as even though
> I'm
> > > using "ant  run-install-seed" It still seems to be using that file for
> > > something as a last resort it seems.
> >
> > I will  have to check, but maybe you are true since some things in there
> are mandatory for the POS to work. Also do not forget that
> > the POS as it is is mostly an UI demo... THe idea is to adapt
> DemoRetail.xml following your needs and load it in the DB thru a way
> > or another.
> >
> > > One last question... Being as you can see that I'm very interested in
> using
> > > the POS side as a start (time sheet, inventory management will be nice
> down
> > > the road, but not for now).  Where do you suggest I start reading to
> get a
> > > more indepth feel as to how to configure the POS XUI to start adapting
> it to
> > > my situation?
> > >Most of the readings are for the ecommerse end.  Although I
> > > think this could make a great in-store POS.
> >
> > There is not much documentation about the POS (I guess you have already
> read all of them). But it's pretty straitghforward to
> > adapt/setup.
> >
> > > Things like: What part of the XUI configs (which I've been looking at)
> link
> > > the button to the actual item in the one of your catalogs (or
> category?!)?
> >
> > I guess the best is (from the log KeyboardAdaptor.java:253:INFO ] Added
> [SKU.GZ-1001] to KeyboardAdaptor) to look a
> > KeyboardAdaptor.java:253. You should find your way beginning there, but
> I wonder why you need that...
> >
> > > Thanks for any help.  I'm working on this day and night, I simply
> don't have
> > > 3 years! HAH! Who needs sleep right?  Entrepreneurs don't sleep!
> >
> > Everyone sleep one day, at least after the last ;o) Philip K. Dick
> experienced some about that (beware he finished mad, but he used
> > much more than stiff drinks)
> >
> > Jacques
> >
> > > Thanks!
> > >
> > > Branden -
> > >
> > > On Feb 6, 2008 11:50 PM, Jacques Le Roux <[EMAIL PROTECTED]
> >
> > > wrote:
> > >
> > >> Branden,
> > >>
> > >> From: "Branden Strickland" <[EMAIL PROTECTED]>
> > >> > 1)  DemoRetail.xml -- Is this only for demo data?
> > >>
> > >> Yes
> > >>
> > >> >If I only use seed data,
> > >> > does the file matter at all?
> > >>
> > >> No
> > >>
> > >> >And if it does, where is it called from?
> > >>
> > >> Automaticaly by ant run-install (you should look for these words in
> all
> > >> the code if you want to understand how it works, but I guess
> > >> this shoudl not be a priority for you at this stage)
> > >>
> > >> >I've
> > >> > checked pos-container.xml and all of the xui and properties files
> within
> > >> the
> > >> > /special/pos filesystem.  When I changed the productstoreid to be
> > >> correct in
> > >> > this file, it seemed to make a difference, which confused me even
> more,
> > >>
> > >> Which file ?
> > >>
> > >> > becuase it says that files is only used for demo data in the
> > >> > ofbiz-container.xml.  A bit of light shed on this subject will help
> me
> > >> sleep
> > >> > a bit better! Thanks!
> > >>
> > >> You should provide your own data in the DB. This is a convenient way
> to
> > >> load them for demo purpose. You may have a look into
> > >> Webtools/XML Data Import
> > >>
> > >> > 2) If I load no demo data, where am I to configure how a button
> actually
> > >> > interacts with a item in my inventory?
> > >>
> > >> posmain.xml. As I answered recently in dev ML :
> > >> <<The idea behind it is that you generally don't want to have access
> to
> > >> *all* your products. Most of the time you use a barcode
> > >> scanner to get products references. It's up to you to show whatever
> > >> products you want using a combination of panel (aka categories)
> > >> and products in these panels. Actually, remember that the UI, as it
> is, is
> > >> a demo...>>
> > >>
> > >> Keep cool, OFBiz is known to have a pretty long learning curve. From
> 1 to
> > >> 4 years according to David, and I plenty agree. And even
> > >> after 3 years, I still learn...
> > >>
> > >> Jacques
> > >>
> > >>
> > >
> >
>

Reply via email to