I would like to know how others are designing this part.
Currently, a JDialog opens when you launch the application and asks for either the db path or ip/port. If the information is not valid, it does not let you through (or else you click Cancel).
Do you think such design is bad ?
Should I rather load the full GUI and provide a "connect to DB" option ?
Thanks advance for any comments
[ November 18, 2007: Message edited by: Alex Belisle Turcot ]
Originally posted by Musab Al-Rawi:
personally I would go for the first option.
the second option implies that if the user decides to change the settings then everything should work fine and there is no need to restart the application.
if this is how you intend to do it then it is ok.
OK, thanks for the encouragement Musab I setup everything like that (cannot go through without correct values)..
I underestimated this part, not that it's big, but you still have to think about that... Client without network, with network + server all got to provide the information to connect to the database.. That's a lot of scenarios right there... Some GUI handling involved in it...
- cannot go through without correct values.
- have the connect to DB option in the main GUI after application is started.
The second feature is good in that user doesn't have to restart the application if he wants to connect to a different DB.
The trickie part is to filter which properties should you show to the user depending on what he is running (server, alone or client).
once you get the trickie part fixed you do have both options.