This week's book giveaway is in the Mac OS forum.
We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line!
See this thread for details.
The moose likes Developer Certification (SCJD/OCMJD) and the fly likes swith between local/nework, please comment this Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Certification » Developer Certification (SCJD/OCMJD)
Bookmark "swith between local/nework, please comment this" Watch "swith between local/nework, please comment this" New topic
Author

swith between local/nework, please comment this

Mihai Radulescu
Ranch Hand

Joined: Sep 18, 2003
Posts: 916

Hi, people

I am pretty close to my submission and I just notice that I miss something, at least I have this feeling.
In my specification I have something like :

... the program must allow the user to specify the location of the database, and it must also accept an indication that a local database is to be used, in which case, the networking must be bypassed entirely.


If I follow this logic my client(s) does not care about the command line parameter(the alone or "") because every time when the client starts the configuration/connection dialog pop-up and allows the user to specify it options. The command line parameter only sets the connection mode (local/remote) and nothing more - the user can validate this or he can change this.

I have also the extended theory about this. If the user starts a client with a specific parameter (like alone), this means he knows what he want/does, and if an valid configuration file exist will be loaded and the connection done, automatic. If the connection fails from any reasons the configuration dialog pops again and the user can correct/adjust the actual configuration. If the user needs to change the actual configuration it just call the configure dialog (I have a menu menu for this).

Is this correct ? What you guys are thinking ?

Regards M.


SCJP, SCJD, SCWCD, OCPJBCD
Jeroen T Wenting
Ranch Hand

Joined: Apr 21, 2006
Posts: 1847
No, you should not assume that just because he selects networked or local mode that he also wants to connect to the same database as last time.


42
Mihai Radulescu
Ranch Hand

Joined: Sep 18, 2003
Posts: 916

Hi Jeroen

Thanks for your answer, I also think that "always" ask for connection is the best solution but I don't have any "strong argument" to favor this.
How you justify your decision ?

Regards M.
Jeroen T Wenting
Ranch Hand

Joined: Apr 21, 2006
Posts: 1847
As I said, NEVER assume.
If an assessor loads your application once, and on next startup doesn't get presented with a choice, I think he may well give you an automatic failure there and then for not allowing settings to be changed.

If there's an option hidden in some menu to change settings on the fly but it's not shown on application start, that's not especially userfriendly (especially if your users are likely to change settings often).
If you do decide to go that way anyway, at least provide an override. A checkbox for example which the user has to check to enable autologin at future application startup.
At least then it'll be his conscious decision to forego the config dialog, and not forced on him.
Mihai Radulescu
Ranch Hand

Joined: Sep 18, 2003
Posts: 916

Hi Jeroen,

You're right.
I also think that I can hide in some menu an "auto" mode but I still think about.
I have an other related question. Do you think is make sense to let an user to change his mode (e.g. from local to remote) on the fly.
I means something like :
start -> config(or connect dialog) -> remote client -> config(or connect dialog) -> local client dialog.
Or the user can choose his running mode when he starts the application. For an other more he must restart the application.

What you think ?

Regards M
Jeroen T Wenting
Ranch Hand

Joined: Apr 21, 2006
Posts: 1847
Changing on the fly (while logged in) I don't consider advisable.
I have built in an option to switch without closing the application though. When the user logs out from the database he's presented again with the connection dialog which contains a checkbox to select local or remote mode (with the last used option selected).
He can of course also quit the application instead of just logging out, in which case he'll be logged out automatically.
 
GeeCON Prague 2014
 
subject: swith between local/nework, please comment this