Hi, all
By accidentally checking the list, I found this topic.
Since I'm pretty much affected both with questions and answers, here are some of my opinions:
- Jam.py is strictly focused on developing a web database app in the enterprise.
- Jam.py has a good old event handler development system, like other developmental systems, above all with GUI development.
- Jam.py have a unique way - hierarchically way of chains event handler follow of structure of application!!!.
- Development is strictly divided into server - python part and client - javascript part.
- Many features of today's newer javascript frameworks have been built in.
- Many nice features from the world of web database app have already been built.
- The programmer definitely deals with programming of business scenarios, not the level of the web, http etc ...
- It may be too much to say, Jam.py is for the web database app development as Access or Delphi at its ranking.
- All, but all of the accounting applications can be done in Jam.py in less time, code, and effort.
I personally tried several times and in the end I gave up web2py. Too much code and too much attention on the low-level web.
It's not a framework for app programming. It is the framework for creating complex websites. Dot.
Although the idea is remarkable, the way of development, the error tracking system, the debugger, the structure of the application, etc.,
work with many of protocols, however, when it comes to serious web database development, there is a lot of detail missing and
of course there is a lack of serious work on the client.
EXAMPLE: Adding two layout details on the client, over click on buttons
function on_view_form_created(item) {
item.add_view_button('Detail2').click(function(){
set_visible_detail(item, item.detail2);
});
item.add_view_button('Detail1').click(function(){
set_visible_detail(item, item.detail1);
});
item.table_options.height = $(window).height() - $('body').height() - 270;
set_visible_detail(item, item.detail1);
}
function set_visible_detail(item, detail) {
item.visible_detail = detail;
detail.create_table(item.view_form.find('.view-detail'), {height: 250});
detail.open(true);
}
var ScrollTimeOut;
function on_after_scroll(item) {
clearTimeout(ScrollTimeOut);
ScrollTimeOut = setTimeout(
function() {
item.visible_detail.open(true);
},
100
);
}
To be honest, I'm putting great hopes in web3py, hopefully Mr. Massimo will turn to the water of database app support.
With respect