This week's book giveaway is in the Go forum.
We're giving away four copies of Head First Go and have Jay McGavren on-line!
See this thread for details.
Win a copy of Head First Go this week in the Go forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Devaka Cooray
  • Junilu Lacar
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Tim Holloway
  • Claude Moore
  • Stephan van Hulst
Bartenders:
  • Winston Gutkowski
  • Carey Brown
  • Frits Walraven

B&S GUI => Getting the db info from client  RSS feed

 
Ranch Hand
Posts: 516
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

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
Alex
[ November 18, 2007: Message edited by: Alex Belisle Turcot ]
 
Ranch Hand
Posts: 231
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
Alex Belisle Turcot
Ranch Hand
Posts: 516
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

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...

Thanks,
Alex
 
Musab Al-Rawi
Ranch Hand
Posts: 231
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
To be honest with you both features are nice to have:
- 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.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!