| Summary | fix boneyard demo application |
| Queue | Horde Base |
| Queue Version | Git master |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | birnbacs (at) gmail (dot) com |
| Created | 2017-10-10 (614 days ago) |
| Due | |
| Updated | 2017-10-10 (614 days ago) |
| Assigned | |
| Resolved | 2017-10-10 (614 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Rejected
Skeleton eventually, but at the moment this is Ralf's pet.
Type ⇒ Enhancement
State ⇒ New
Priority ⇒ 1. Low
Summary ⇒ fix boneyard demo application
Queue ⇒ Horde Base
Milestone ⇒
Patch ⇒ No
an empty application to start from. Documentation on how to do the
extension is pretty old (2015) and rather targets the usage of a
development environment than the additional code. Apparently the extra
code must still be pulled (manually?) from git afterwards.
Functionality seems to be restricted to optical fading between
different views. No explanation of essential concepts like the view
stack (?) or the JS library used. Static view is not comparable to
dynamic view.
If boneyard continues to be advertised as Ajax starter application it
would be nice to have some basic data exchange functionality between
the client side and the server side. Also, some support for the
difficult task of debugging Ajax applications would be greatly
appreciated. Something like a text output console and hints to firebug
and the like, maybe?
Big thanks to Ralf Lang and the rest of you guys for the good work!