[ http://issues.apache.org/jira/browse/OFBIZ-226?page=comments#action_12456220 ] Jacopo Cappellato commented on OFBIZ-226: -----------------------------------------
Ray, I've applied your last patch and I've added a comment to the code to remember that this is something that should be improved a bit; by the way for now I think that it's fine. Thanks > Demo of warehouse functionality on handheld > ------------------------------------------- > > Key: OFBIZ-226 > URL: http://issues.apache.org/jira/browse/OFBIZ-226 > Project: OFBiz (The Open for Business Project) > Issue Type: New Feature > Components: product > Reporter: Jacopo Cappellato > Assigned To: Jacopo Cappellato > Priority: Trivial > Attachments: hhfacility-reviewed.zip, hhFacility.zip, hhfacility.zip, > hhfacility_v2.zip, hhfacility_v3.zip, location_null.patch, > product_extra_inv_service.patch > > > Jira issue created in the old server by Daniel Goodwin: > Small (incomplete) sample application used a proof of concept of facility > (warehouse) functionality delivered in form factor suitable for handheld > terminals. The tests were performed on an LXE MX6 wireless barcode scanner. > Notes > - its not complete - in fact only Goods Receipt | Product Receipt actually > works but then it is only a 'proof of concept' for my bosses! > - screen layout is meant to aid use on handheld for minimum user input. There > are, therefore more screens than necessary for normal consumption, but > enables use of barcode scanner as much as possible. > - on the product receipt screen itself, the use of javascript to enable use > of <CR> to move to next field is a requirement as the scanner can then use > auto-enter barcodes to move to next field without user intervention. > - screen size is 'hardcoded' in header.ftl - would be better placed in CSS > and use <div> layouts instead of tables. > - tried to use the widgets as much as possible, though not always > satisfactory outcome and had to revert to ftl in some cases. > ** - if running on version 7009 with default seed data, you may need to setup > a PartyAcctgPreference for Company so that error message on receipt relating > to currencyUomId does not appear. > All Comments Work Log Change History > Sort Order: [navigator.ascending.order] > Comment by Daniel Goodwin [21/Mar/06 03:22 AM] > [ Permlink ] > Facility Handheld Demo (winrar format) > Use https://X.X.X.X/hhfacility/ > Comment by Jacopo Cappellato [21/Mar/06 03:32 AM] > [ Permlink ] > Thanks Daniel, > I'll have a look at this. > About the seed data requirement: since svn rev 7035, the seed data setup is > no more needed to receive products without errors. > Comment by Si Chen [14/Apr/06 08:40 AM] > [ Permlink ] > David, Jacopo, et al - > Should we put this into either a specialized/ component of its own or put it > into applications/products/ ? That way others could try it as well? > Si > Comment by Jacques Le Roux [14/Apr/06 09:26 AM] > [ Permlink ] > Interesting, > May this be used on another (cheaper) handheld (LXE MX6 costs US$3,300) ? > Jacques > Comment by David E. Jones [14/Apr/06 01:56 PM] > [ Permlink ] > Si: There was some discussion about this around the time it was submitted. > Daniel liked the idea but did not feel it was ready for this yet. As soon as > he wants to do it, we can setup a specialized directory and give him commit > privileges. > Comment by Jacopo Cappellato [16/Apr/06 03:54 AM] > [ Permlink ] > Yes, > and I've reviewed (and modified something) the code and sent it back to > Daniel with my comments. > Comment by Daniel Goodwin [17/Apr/06 12:39 PM] > [ Permlink ] > Jacopo et al > Development on this is continuing (though slow) . Should have something with > a bit more functionality with the next fortnight. On device - as long as it > supports Pocket Explorer (though I have also used Minimo (Firefox)) it should > be ok - so wireless iPAQ, etc would be fine. We use LXE as it is mainly a > warehouse scenario where the devices get dropped a lot! or hit with forklifts > as the ruggedness of the MX6 has been OK in such scenarios > Daniel > Comment by Jacques Le Roux [17/Apr/06 02:49 PM] > [ Permlink ] > Thanks Daniel for the info > Jacques > Comment by Jacopo Cappellato [20/Jun/06 03:49 AM] > [ Permlink ] > This is a reviewed version of Daniel's component; it contains some misc > improvements I did to help Daniel to start his work in the right way; in fact > I sent this file privately to him some time ago but now that it seems there > is some interest from others (Ray Barlow) I think it's better to put it into > this Jira issue. > Here is the list of the comments I did (by the way Daniel's work was indeed > very good): > * indentation: always use 4-spaces instead of tabs > * you can remove all the instances like this one: > <#if (requestAttributes.facilityId)?exists> > <#assign facilityId = requestAttributes.facilityId> > </#if> > from your ftl templates (they were only needed during the migration > fromJPublish to Screen Widget) > * the facilities.bsh is not necessary; see my code inside the action element > of the "facilities" screen def > * however, the "facilities" screen seems not used; can it be removed? > * license: is it a problem for you to use the ASL2.0 license instead of MIT > (see the file APACHE2_HEADER in the OFBiz's main folder) > * productreceipt.ftl and qtyreceipt.ftl substituted by setFocusOnField.ftl > * changed html tag <ul> to <ol> > * added style definitions to a few form definitions > * if possible, give more descriptive names to services because to make it > easier to reuse them. > * removed unused resources (entitydef.xml, entitygroup.xml etc...) and their > references from the ofbiz-component.xml file > * removed all the ftl templates that only contained the page name; the page > name is now in the screen definitions > * There are now three screen template definition: > GlobalDecorator: this is the lower level, it defines the structure of a > screen for an hh device > CommonDecorator: at the moment it's the same of the GlobalDecorator, it > represents the base layout of a page of the hh facility application > FacilityDecorator: it is based on CommonDecorator and it is the base layout > for all the hh facility screens that contain data about a specific facility > (inside its action element the record for the facility is retrieved; in the > widget element the name of the facility is shown) > All the screens of your component can now extend the CommonDecorator or the > FacilityDecorator > For example, the hierarchy is: > GlobalDecorator-->CommonDecorator-->login > GlobalDecorator-->CommonDecorator-->main > GlobalDecorator-->CommonDecorator-->FacilityDecorator-->menu > GlobalDecorator-->CommonDecorator-->FacilityDecorator-->receipt > ... > Hope this helps! > Jacopo -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
