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

B&S: Display and Other DB Operations

 
Muhammad Shafique
Ranch Hand
Posts: 59
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Folks,
Please help me in these two:

In B&S DB, specialty field has more than one comma separated values. What could a better way to display this data on JTable in readonly mode? I thought about using other GUI components like combo box or list but it seems they don't fulfill the purpose.

I am using MVC on client side and have implemented all methods of DBMain on DB side. According to specifications, I am not supposed to provide add and delete operations and I designed client GUI accordingly. Is it a better idea to add access to these operations in Controller? Although its not required but in case of future enhancement. Please comment!!
 
Jeroen T Wenting
Ranch Hand
Posts: 1847
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I display everything as readonly except the field for the customer number.
The application is a booking application, not an application for administering the subcontractor information.
I also pull apart that comma separated string and show the content in a separate window as a list.

This same panel (minus the input box and buttons) is also shown in my main window with the details of the selected record.

 
Joe Zhou
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think the Instruction.html asks for a client framwork which can easily enhanced in the future. You don't have inplement or partially implement anything for the future, because you never know what the enhancement will be. But you do need to make sure that you framework can easily be enhanced. For example, can a add/delete button easily added to the code and let it call the backend functions.

I use MVC. I have a controller. But I don't implement add/deleted in my controller. Instead, I implement them at the backend where I have a DB access manager to handle the business rules. In my MVC design I leave the space for the add/delete operations. I also document my class how to add a new button and how to implement new methods in the controller to do add/delete.

This is just what my understanding is. The important thing is document your choices.
 
Louis Logan
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jeroen T Wenting:
[qb]
The application is a booking application, not an application for administering the subcontractor information.
qb]


I wonder why did they have createRecord in the interface.

-logan
[ December 18, 2006: Message edited by: Louis Logan ]
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic