Browser staff client / merge prep
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
See action items:
http://
Code is here:
If you install this code as-is, it will not build the browser client. Some stuff will get installed, because it's in the web dir, but it won't function. The purpose of this bug is to see if the browser client can safely be installed w/o affecting existing code, so I won't go into detail about fetching dependencies and building the browser client here. I'll open a different LP for documenting and improving the build process.
For testing, the main things to look at are the bits of Evergreen proper that changed to support the browser client.
* I added a few permacrud sections to fm_IDL.xml. Changes are all used in the browser client, so they have received some amount of testing, but extra eyes won't hurt.
* Holds placement in the XUL client (via embedded browser)
* Bookbag actions in the XUL client (via embedded browser)
* Copy barcode detail link in record copy grid (via embedded browser)
Regarding the merge, it's a giant pile (349) of practically non-documented commits. Fine-grained squashing would take too long, so we can either commit as-is, with a nice big merge commit message, or squash it all down to a handful of gigantor commits.
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Based on conversations in IRC, I'm going to do some heavy squashing. Will report back soon.