[#14704] fix boneyard demo application
Summary fix boneyard demo application
Queue Horde Base
Queue Version Git master
Type Enhancement
State Rejected
Priority 1. Low
Requester birnbacs (at) gmail (dot) com
Created 2017-10-10 (614 days ago)
Updated 2017-10-10 (614 days ago)
Resolved 2017-10-10 (614 days ago)
Patch No

2017-10-10 09:15:26 Jan Schneider Comment #2
State ⇒ Rejected
Reply to this comment
This is not a Horde app. It might make sense to integrate it with 
Skeleton eventually, but at the moment this is Ralf's pet.
2017-10-10 07:37:02 birnbacs (at) gmail (dot) com Comment #1
Type ⇒ Enhancement
State ⇒ New
Priority ⇒ 1. Low
Summary ⇒ fix boneyard demo application
Queue ⇒ Horde Base
Milestone ⇒
Patch ⇒ No
Reply to this comment
boneyard is a dynamic view extension of skeleton, which is basically 
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!

Saved Queries