The issue of deployment is real - for sure. But I have used a both just creating an exe and install all on a server. I have found the best for me was to install all the python stuff on the client and the rest on a server. The last allows for one place to make changes.
Dabo's doc's have not helped me much. Most of what I have learned came from Ed Leaf and Paul McNett and this forum. Also I had a background with FoxPro and Dabo is patterned after Fox.
Johnf
On 01/13/2017 09:11 AM, Henning Hraban Ramm wrote:
As far as NodeJS - well I like the fact that it is well supported by the community - but so is Django. I don't believe NodeJS's asynchronous I/O is faster than Django when comes to serving data - at least not for small websites. So I wouldn't leave Django for NodeJS.
Django is good for many projects, and I guess I’ll continue using it for websites, since my workflow is comfortable enough.
But for "desktopy" web apps, where most of the coding is in JS on the Client UI anyway, Meteor/Angular/React seems to be the better framework. I’m still at the beginning of my node.js journey, but I hit too many blocks while trying to do my current project in Django. And using dabo, i.e. installing an app on every user’s computer, would be a promise for a support desaster. I used dabo only ever as a convenient UI framework, never really needed the 3-tier setup. I could stay on Python 2.7, but I found the availability of dabo’s documentation too unreliable.
Greetlings, Hraban _______________________________________________ Post Messages to: Dabo-users@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/4181D4F8-1FC5-42D3-A800-5CC4DCDDB242@fiee.ne...