[Lazarus] Cross Platform SQL Client/Editor

[Anthony Walter]

Michael,

Just FYI currently there is no "fpddmssql.pp" (the dd is for data
dictionary I suppose) so no, it's not as easy as just adding a unit name to
the project source. New units must be created and a register function must
be create for mssql to appear in the connections list.

And as far as your surprise at my lack of research goes, you need to
rethink about discovery. The first thing your app does is show a blank list
view of data dictionaries rather than help users create a database
connection first. Next after switching to the connections tab you have to
know to right click in the blank list view to get a context menu which
gives you the option to create a connection. Forcing users to find your
hidden options by using right click context menus is terrible design. Next
we get to the point where these is no option for mssql. You say you simply
include a unit, but in reality no mssql connection register unit currently
exists, so it's not that simple.

When you despair if people "didn't investigate very deeply", how far do you
want users to go? You need to understand that most people are not going to
go through a deep investigation before trying to resolve problems deciding
if your tool suits them or even works for their needs.

To improve your tool I'd suggest:

If there is no stored connection, you should have a database connection
setup screen as the first thing users see when launching your app.
If there are any hidden right click menus, you should supplement them with
items in a menu menu or a toolbar with appropriate icons and tooltips.
Provide in the sources code at least a comment about how to add additional
database providers.
Also calling database providers (what the rest of the world calls them)
"dictionaries" (RegisterDictionaryEngine) isn't helping the situation any.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20160102/35ec9094/attachment-0003.html>