Reputation: 29 Craftsman
- Active Posts:
- 549 (0.27 per day)
- 08-May 08
- Profile Views:
- Last Active:
- Sep 30 2012 02:58 PM
- OS Preference:
- Favorite Browser:
- Internet Explorer
- Favorite Processor:
- Favorite Gaming Platform:
- Your Car:
- Dream Kudos:
Posts I've Made
Posted 10 May 2012And there in lies the defining reason. A well defined scope, on paper of course , will make GUI design alot easier and less cumbersome on the development time.
In the past i have dealt with developer that make the car look like a Corvette even though when put on the road performs like a Pinto. Which means they spent 80% of their time on the GUI and 20% of their time on the content of the development. Which is "bass ackwards" and leads to developers getting a bad rapoire cause of a few "idgiots"
I just dont put alot of time or effort in developing the interface as it is fluid and can be easily changed with a few mouse clicks, drag-and-drop, or ultimately the delete. The content of the software is a different point in case and is almost always the opposite of the GUI.
Posted 9 May 2012I always work with a GUI prototype until I have an agreement on what the application is going to do and how it is going to work. It's important to me to get paid for what I do, and the people who are paying typically care a lot more about whether the program will meet their business requirements and how easy it is to use than they do about the implementation details. They just want those to be well-constructed or some other such vagary. I generally don't do any more work on the data structure than is necessary to support prototyping until we have an agreement on what they are going to be paying for.
No sense building database architecture only to have someone explain (once they fit you into their busy schedule six months into the project) that we have the business rules all wrong, and we find that we have to redesign our database to accommodate the correct ones.
There is actually no sense in spending an exorbidant amount of time developing (prototype) the GUI if all they are going to do is throw your knowledgeable design in the trash and then have you redesign based on their needs, that they of course failed to express during the "discovery phase"
Yes I had that happen to me once, and i never make the same mistake twice, so now i spend maybe 16hrs of a project on prototyping the GUI and the majority of the project is spent on content and design and then i spend usually the last 1/3, usually last 1/4, of the project on GUI LAF (look and feel) with the functionality already attached just waiting on client making decisions on placement of controls and how menus are designed.
Posted 7 May 2012Without knowing how your adding the ListItems, we wont be able to instruct you on the correct or logical approach for this.
Although it seems like you have not set the Key and Value components of the ListBox from what it sounds like.
Posted 22 Mar 2012So what exactly do you need help with?
You didnt state any error or exceptions for the design. Theoretically your logic should work.
Posted 25 Feb 2012I never design the GUI first, i always work on the library of operations first and then it makes attaching the GUI to the library alot easier.
- Member Title:
- D.I.C Addict
- 37 years old
- August 9, 1976
- Tuscaloosa, AL
- VB.net, LOTRO, Playing with kids (all 3 of em), ASP.net, Wiki content management, and anything else PC oriented.
- Full Name:
- John Wood
- Years Programming:
- Programming Languages:
- .Net Framework (VB/C#), C/C++ (recognition; last used 2000), ASP.net, MySQL, Java (as needed).