Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Back when <insert-SQL-database-vendor's-name-here> "Forms" SDK's and tools where the way that data-centric applications were developed, do you think there was any consensus on naming and components?

You might have been able to leverage some conceptual knowledge from Oracle's tools to the ones associated with Postgres, but everything was different at the syntactic level.

When <insert-software-development-corp-here>'s GUI toolkit were the way that data-centric applications were developed,do you think there was any consensus on naming and components? Not all. People using MS GUI tools would flounder amidst Cocoa, and vice versa. Qt users would have to constantly read the GTK manual, and vice versa.

You might have been able to leverage some conceptual knowledge from one vendor's tools to the ones associated with another's, but everything was different at the syntactic level.

It might be a good idea to settle on some "global" definitions and components, but that hasn't happened before, and I can't see any particular reason it will happen for applications developed around the web platform.



> It might be a good idea to settle on some "global" definitions and components, but that hasn't happened before,

But it has. We all know what buttons, dropdowns, forms, windows, text boxes, etc. are. Windows and macOS gave us these concepts and the Web adopted them.


It's not as if the web-UI "toolkits" that openui is attempting to "standardize" don't already have those things either.

The issue seems to be that the way they work, and the way to work with them, differs from toolkit to toolkit.

I.e. just like ye olde SQL forms tools and ye not so olde desktop-native toolkits.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: