[
https://issues.apache.org/jira/browse/OFBIZ-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540113
]
skipdever edited comment on OFBIZ-1383 at 11/4/07 3:43 PM:
------------------------------------------------------------
Yes, I agree, that comment was confusing, so I have deleted it. Here is a
better description of the interface:
This application runs on the users desktop. It presents the user with a fast
and easy to use interface. Like the POS application, it can be run remotely
(not recommended) and synchronized with the main Ofbiz database using Ofbiz
synchronization services.
More commonly, it is run on the same network as the main Ofbiz server and
therefore reads and updates the same database as the main Ofbiz server.
It is architected with a generic interface between the GUI code and the data.
The current implementation of this interface connects to the Ofbiz data
directly using the a GenericDelegator and LocalDispatcher, and sometimes
indirectly using the ShoppingCart and CheckOutHelper classes and associated
Order, Security, and Party services.
Because this data layer runs the entity engine, service engine, etc, it
requires a reasonably performing machine. In my testing, I would recommend a
2.4Gig Pentium class machine as a minimum.
If the data layer was re-written to use SOAP or java rpc, where the business
logic execution was offloaded to main Ofbiz server, the hardware requirement
would be completely removed as I have run Java applications like this on
machines as pathetic as a 500meg Pentium 2. This of course would eliminate one
of the two main advantages of this applications, i.e offloading some of the
workload to normally under-utilized desktop machines. But, you would still be
left with a slick and intuitive user interface that you can train users on in 5
minutes.
was (Author: skipdever):
Yes, I agree, that comment was confusing, so I have deleted it. Here is a
better description of the interface:
This application runs on the users desktop. It presents the user with a fast
and easy to use interface. Like the POS application, it can be run remotely
(not recommended) and synchronized with the main Ofbiz database using Ofbiz
synchronization services.
More commonly, it is run on the same network as the main Ofbiz server and
therefore reads and updates the same database as the main Ofbiz server.
It is architected with a generic interface between the GUI code and the data.
The current implementation of this interface connects to the Ofbiz data
directly using the a GenericDelegator and LocalDispatcher, and sometimes
indirectly using the ShoppingCart and CheckOutHelper classes and associated
Order, Security, and Party services.
Because this data layer runs the entity engine, service engine, etc, it
requires a reasonably performing machine. In my testing, I would recommend a
2.4Gig Pentium class machine as a minimum.
If the data layer was re-written to use SOAP or java rpc, where the business
logic execution was offloaded to main Ofbiz server, the hardware requirement
would be completely removed as I have run Java applications like this on
machines as pathetic as a 500meg Pentium 2. This of course would eliminate one
of the two main advantages of this applications, i.e offloading some of the
workload to normally under-utilized desktop machines. But, you would still be
left with a slick and intuitive user interface.
> Standalone Java Application for Sales Order Entry
> -------------------------------------------------
>
> Key: OFBIZ-1383
> URL: https://issues.apache.org/jira/browse/OFBIZ-1383
> Project: OFBiz
> Issue Type: New Feature
> Components: order
> Reporter: Skip Dever
> Attachments: fssoe.ZIP, startfs.bat
>
>
> This issue makes available a new desktop application that allows sales order
> entry. It is similar in concept to the pos module.
> The difference is that it essentially duplicates the functionality
> Order-Order Entry screen. It is useful if you have backoffice sales people
> taking lots of orders.
> It is architecturally different from the POS in that it is designed to have
> an interface to the Ofbiz engine in whatever manner you want. My intent was
> to produce both direct and java-rpc connections, but only the direct
> connection is done. See the com.fs.data.DataConnection and com.fs.data.
> OfbizDataConnection classes for more details.
> This runs, but is not finished. I have been pulled off to finish the AR and
> Purchasing work, and I expect that to take a month or two. So, I am offering
> this advanced look in case there are others who can use it or would like to
> contribute.
> Note that I do not expect this to be part of the Ofbiz distribution because
> the code formatting does not follow the Ofbiz guidelines. However, I have no
> intention of changing the formatting. I have over a million lines of java
> code using this formatting and I do not intend to change at this point.
> To install this, unzip the attached file in your specialpurpose directory and
> follow the minimal installation instructions in the docs subdirectory.
> The basics are reprinted here:
> Copy specialpurpose\fs\configfiles/fssoe-containers.xml to
> framework\base\config.
> Copy specialpurpose\fs\/configfiles/fssoe.properties to
> framework\base\build\classes\start\org\ofbiz\base\start
> Add:
> <load-component component-location="${ofbiz.home}/specialpurpose/fs"/>
> To specialpurpose/component-load.xml
> Run ant with no arguments in the Ofbiz root directory
> You can then run the application with:
> java -Xms256M -Xmx512M -Duser.language=en -jar ofbiz.jar fssoe
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
