30 ms·
Your typical CRUD app is not going to be on the bleeding edge enough to worry about many fuzzy areas and vendor specific enhancements. As to multi-select and t
by tracker1 8y ago
Your typical CRUD app is not going to be on the bleeding edge enough to worry about many fuzzy areas and vendor specific enhancements.
As to multi-select and the like... this is why groups of developers are now leaning towards tooling around React, Angular, Vue and others. If you want something not in the box, you either make it, or pay for a custom control... of find an open-source one.
Developing web apps isn't so significantly different from desktop apps from a UI perspective, it's just you get a lot more in the box. (like layouts that grow/shrink to fit with nearly 0 cost).
- tabtab 8y agoBut browser changes for other reasons may break what previously worked in a CRUD app. And we don't need gazillion widget types for most CRUD. Oracle Forms has a limited widget set, yet has been used to build a good many apps here at our shop quick and easy. It's not esthetic, but got the job done. (It has a few clunky spots, but everything does.) I'm not an Oracle Forms dev myself; I just observed productivity. Oracle should have left the "gui browser" (client engine) as a dedicated product (compiled EXE) instead of convert it into Java, because Java had too many security bugs because it tried to be too much. The concept of Java Applets failed, not Oracle Forms itself.
- tracker1 8y agoIn over 20 years of web application development, the single biggest breaking change (other than bleeding edge bits) was when IE 5.0 came out and broke the legacy api for populating select elements via JS. They added the new DOM interfaces but broke the old one. It was a little painful but far from the end of the world. Classic VB, Delphi, Access, and Flex/Flash have all been good at delivering CRUD apps, if you exclude the security concerns in talking to the backend, and storing application configurations, dealing with updates etc. In the end, I don't feel it's any better overall either way. The difference is it's far easier to automate one server (or two) in a business environment than dozens or hundreds of systems.