S
smat-consulting
Guest
@agent_008_nl: you call it library we call it framework. You need some heavy-duty tools to build something big. Supporting Mike's question: Why do you still hang around us if what we choose to use as tool is so bad? Seems to me, that despite your dislike of PSC, you, too, find OE to be about the best "complete" development tool around to get real work done... 
@patrick Re: JS skills being rusty - if you can hire a JS specialist you'll save yourself a lot of headache. JS is the ultimate disgrace of human ingenuity - worse than the Trabant and the Hummer! 
Re: Framework: It is my believe that it is not just important to have a tool that allows building a unit quickly, but also, that provides the means to build many units automatically in a way that they basically work, and where only few have to be customized. Secondly, it is important that changes to the data-model, as well as additional features are easily implemented. I found Rollbase' idea about UI organization quite nice. Very easy to understand for users, very powerful with all the automatic linking of referenced IDs to actual records pointed to, and flexible for customizations. What Rollbase was missing (aside of simple things like transaction scoping, locking, a decent backend, and decent language to implement business-logic) is a way to build a full application quickly. It is extremely tedious to build all the UI components for all the tables manually - even though the process per unit is quickly, building 400 components for a 100 table DB takes forever and is extremely boring. However, using their UI organization idea and implementing it in OE seemed a good approach to me. So I did. And you can too (if you want to duplicate the work, or approach it slightly different). It works beautifully, is easy to maintain, enhance, and customize, and is easy for users to learn. In any case, I can not imagine anybody building a whole application from scratch without such a thing as a framework providing the plumbing plus a way to get components done quickly... Good luck!
Continue reading...
@patrick Re: JS skills being rusty - if you can hire a JS specialist you'll save yourself a lot of headache. JS is the ultimate disgrace of human ingenuity - worse than the Trabant and the Hummer! Re: Framework: It is my believe that it is not just important to have a tool that allows building a unit quickly, but also, that provides the means to build many units automatically in a way that they basically work, and where only few have to be customized. Secondly, it is important that changes to the data-model, as well as additional features are easily implemented. I found Rollbase' idea about UI organization quite nice. Very easy to understand for users, very powerful with all the automatic linking of referenced IDs to actual records pointed to, and flexible for customizations. What Rollbase was missing (aside of simple things like transaction scoping, locking, a decent backend, and decent language to implement business-logic) is a way to build a full application quickly. It is extremely tedious to build all the UI components for all the tables manually - even though the process per unit is quickly, building 400 components for a 100 table DB takes forever and is extremely boring. However, using their UI organization idea and implementing it in OE seemed a good approach to me. So I did. And you can too (if you want to duplicate the work, or approach it slightly different). It works beautifully, is easy to maintain, enhance, and customize, and is easy for users to learn. In any case, I can not imagine anybody building a whole application from scratch without such a thing as a framework providing the plumbing plus a way to get components done quickly... Good luck!Continue reading...