Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Question about GUI

 
Yanxin Zhao
Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi: everyone.
I got a problem about my GUI designing.
I am not sure how many things should I implemment in my GUI. I have implemented Read, Add, Delete, Find, all of my given interface mentained things. but I think I do not need implement so many. so I want to ask how many and what things should I implement?
[ August 04, 2004: Message edited by: Yanxin Zhao ]
 
Hanna Habashy
Ranch Hand
Posts: 532
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yanxin,
How many functions you should provide in your GUI is up to you and to your project requirments. IMO, you should provide the user the ability to take advantage of your business logic. For example, if your business methods provide function to search, update, book and delete, then your GUI should implement function for the user to search, update, book and delete.
What will be the benifits if you implement for example the search function, but you don't give the user the interface to search records...??!
Some poeple will argue that you should implements only what you asked for. I agree %100 with them in real world. However, you can take advantage of the opprotunity provided to you implementing this project, and learn as much as you can.
At last, I suggest first to meet the project requirments, then you can add any additional function for your personal satisfaction.
 
Yanxin Zhao
Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes, great, I think so. Thanks for your reply, Hanna.
 
Anton Golovin
Ranch Hand
Posts: 530
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Yanxin Zhao:
Hi: everyone.
I got a problem about my GUI designing.
I am not sure how many things should I implemment in my GUI. I have implemented Read, Add, Delete, Find, all of my given interface mentained things. but I think I do not need implement so many. so I want to ask how many and what things should I implement?

[ August 04, 2004: Message edited by: Yanxin Zhao ]


In my project, I must use a DB interface implemented by Data. DB contains methods such as read, write, etc. This is not what the program does "in English." In English, the program searches records, books vacancies, creates and deletes records.

Therefore, I also implement an interface DBClient, which is implemented by DataAdapter class. The adapter masks direct functionality of Data class into more understandable form.

My remote class is called DataImpl, and it implements a DBRemote interface (which extends DBClient and Remote.)

Thus, I also need my client controller class to implement DBClient interface for the "contractual agreement" to be valid.

Ideally, the functionality to be implemented in the GUI is the direct reflection of this DBClient interface and has buttons mapped to every method in it.
[ August 04, 2004: Message edited by: Anton Golovin ]
 
Omar Kalaldeh
Ranch Hand
Posts: 58
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
your GUI should implement function for the user to search, update, book and delete.


I disagree with you Hanna, I don�t think you should implement all the operations at the client side, for many reasons:
  • If they don�t require it don�t do it, and you will have no extra credit for donning It.
  • In real life as you said Hanna, clients do not have to implement all the functionalities came in the server side.
  • I think at Sun they want to see your client not complete, to find out how easy it will be to add new functionalities.

  • But still you server side must provide all the functionalities.

    This how I see it.
    [ August 05, 2004: Message edited by: Omar Kalaldeh ]
     
    Hanna Habashy
    Ranch Hand
    Posts: 532
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Omar,
    If they don�t require it don�t do it, and you will have no extra credit for donning It.

    I agree with the second part of your statement, but I disagree with the firest part. If they don't requier it, why would you implement it in your data access layer. Code in the data access layer not exposed to users, is useless.
    In real life as you said Hanna, clients do not have to implement all the functionalities came in the server side.

    In real life you would seperate server code, and client code. Client GUI implements function available and implemented for clients, and same way for server.
    I think at Sun they want to see your client not complete, to find out how easy it will be to add new functionalities.

    Part of the statement is true, and the other part is a personal opinion. Like what I said before, one should implement the requirement first, and if desired, can implement additional functions for learning process and self satisfaction.
     
    • Post Reply
    • Bookmark Topic Watch Topic
    • New Topic