True. But isn’t that called HTML CSS? Different forum.
I think we agree more than disagree, it’s just that we’re talking about two different aspects of Base. I’m referring to the visual layout of controls. I think you (and @Villeroy ) are focusing more on the database schema structure configuration of tables etc.
With regard to the former, I agree that control dimensional attributes should also be easily available (and they mostly are, somewhat).
But some retro comments here remind me of the early days of 3D graphics - I recall one guy commenting: Who needs a GUI when you can just enter the point coordinates manually? Now any 3D artist would laugh at you for even suggesting one do art purely with text. Yes, of course there are settings that can be configured, esp. in 3D used for CAD, where precision is critical, but they all have GUI WYSIWYG viewport . Same with programs like Inkscape, GIMP (or Photoshop).
Plus, there are other ways to get OCD pleasing alignments - see Google Draw for example. Select multiple object (controls?), choose Distribute > Horizontally (or Vertically) and voila! Very visually pleasing result. No copy pasting Position X, Y attributes etc. But if you want to, you can easily do so.
Again, CLI MySQL is a beautiful thing - just not LO Base’s raison d’être.
MS Access, despite its age, sounds more refined than Base from your description (I haven’t used it for 10 years) but I no longer want to depend on Windows and Base seems to be the best alternative despite its obvious shortcomings (which may be fixed eventually one would hope). The truly unique attributes which both share, and few or no others have (I would love to hear of an alternative):
- Ability to create form interfaces to view/enter/delete data (mini-apps)
- Ability to create & save mini-databases in one file (.mdb or .odb).
- Ability to optionally move migrate such mini-database prototypes to connect to & manage external servers
These are the three killer features – everything else is gravy.
How they are implemented is of no interest to me – I would be perfectly happy if all the internal database creation and configuration was done in standard SQL (preferably with code formatting preserved).
In fact, I suspect that such direct SQL would be less bug prone. I know there is a “direct SQL” button in Base, but I read that it can cause problems due to the way it is implemented - I don’t recall specifics. If anyone knows of a guide how to do the 3 things listed above in Base using Relationships (or MySQL) without dealing with the awkwardness of linked fields Forms/Subforms/SubSubforms etc