[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dojo tabs demo / using dojo in LSMB

Perhaps the "common denominator" of an area of the application.  For example, in AR lots of functionality surrounds the customer; in AP, the vendor.  There's probably much overlap in selecting an entity,  viewing (perhaps a dashboard) basic information about it, and performing operations on that entity (eg, receiving a payment).  It might be effective to have a one-page for a specific area of the application.


Brian Wolf
Phone: 410.367.2958
Email: ..hidden..
Try out Activus Secure Payments™, our recurring payments application.
On 07/29/2013 09:49 AM, Chris Travers wrote:

On Mon, Jul 29, 2013 at 4:57 AM, Brian Wolf <..hidden..> wrote:
As a developer, I've been on projects with a Dojo-based, one-page interface.  Theoretically, should be ideal.  Pragmatically, page can become bloated, with lots of competing code segments, longer load times and possibly interdependencies (eg, trying to test a code segment independently of other segments can be quite difficult).  Instead, a RESTful design multi-page design makes testing far easier and eliminates interdependencies.

To be honest, I tend to favor modularity of such things too.  That doesn't mean there may not be things we may decide to incorporate that are inspired from one-page designs.  Our application is quite complex and I would be worried about too much irreducible complexity.

One thing I would ask is that if we go with a multi-page design, what are the aspects of one-page design that we should be looking into incorporating?

Best Wishes,
Chris Travers

Efficito:  Hosted Accounting and ERP.  Robust and Flexible.  No vendor lock-in.

See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!

Ledger-smb-devel mailing list