• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • paul wheaton
  • Ron McLeod
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Piet Souris
Bartenders:

initial project design

 
Ranch Hand
Posts: 182
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello JavaRanchers! I want to eventually make a small, daily bar chart, which shows the price activity for a stock or commodity over a period of time. I've read quite a bit, but I don't quite get this OO process yet.
So I'm wondering, is there a kind've flowchart-like mentality that can be used to help me decide the project's structure. Like, what classes I need to make, subclasses to make in those classes, objects, methods, etc. I'm having a hard time seeing up front how it should all fit together. I put a small outline below, to give an idea of what I'm dealing with. I'll post the code on request, as I've already taken up quite a bit of space and it probably doesn't give much insight. Thanks for any guidance.

Labels // "enter new open", "enter new high", "enter new low", "enter new close"
TextAreas // open, high, low, close - allows user to input price info.
Button /** "enter new day's prices" - allows user to update the chart if price info is in each TextArea. If the chart isn't full, a new day is added. If the chart is full, the oldest day is dropped from view, the chart info shifts to the left a day, and then a new day is added. */
x axis // each day is is dated [xx/xx/xx]
y axis // $'s/ contract - increments of $10
chart border // maybe put the chart in a container with the appropriate dimensions???
vertical lines // 1 per day
horizontal lines // price levels
priceBar // open, high, low, close
 
Sheriff
Posts: 7001
6
Eclipse IDE Python C++ Debian Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think you are missing an important point about OO design. You only seem to describe UI features, and say nothing about the underlying data, and the operations you might need to perform on it.
I strongly recommend that for any OO design you get the data model right first, and provide methods for all the operations you need. Then it's almost trivial to add a variety of differenmt user interfaces - Swing/AWT, Web/HTML, text/command-line style interfaces and their requirements should make no dfference to the model
 
Steven YaegerII
Ranch Hand
Posts: 182
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks, Frank. I really had no idea where to begin. I'm going to go finish the outline, listing what data operations I need & putting all the methods() in. Thanks again for the guidance.
reply
    Bookmark Topic Watch Topic
  • New Topic