Use of Java API classes unrelated to the problem domain

Question

Hi,
I am designing a public API.
java.awt.Dimension getScreenSize(); // rows, columns
java.awt.Point getCursorLocation(); // row, columnDo you consider the above returned values abuses/misuses of existing AWT classes in a totally non-graphical context?
Should I rather:
1. Use my own (immutable) equivalent classes with better names such as getRows(), getColumns() instead of getY(), getX()?
2. Should I use separate getters like getCursorRow(), getCursorColumn() etc. and forget about Point or Point-like classes (and loose the atomicity of the operations)?
Thanks!

Answer 1

I also feel you should roll your own classes with class and method names that better describe the intention. I base my conclusion on the very existence of the two classes Dimension and Point in the same java.awt package, both of which encapsulate two int values and nothing else. Theoretically just one class could have served the purpose of both of these.
JTable has a constructor that takes two int arguments for numRows and numColumns, and methods getRowCount() and getcolumnCount() so would you consider using JTable as a return type for your getScreenSize()? No? I thought not.
db