Yea I had thought about that, which is why i was throwing it out for discussion.
My thought is that _toString wouldn't contain rendered content, i.e. html code. but that is obviously a bias opinion. i wouldn't mind overriding the __toString() method to contain the values that I needed, but was thinking that there should be some overrideable method that was consistent across the Qobjects, that would allow me to pull the values or text needed. I couldn't really override, the ->Name and ->Text variables, because that would affect the display and results of my object.
I was thinking that something like __toString() could be the consistent overridable method that could be globally used. maybe something like ValueOf()
here is what the java docs say on their use of _toString
toString
public String toString() - Returns a string representation of the object. In general, the toString method returns a string that “textually represents” this object. The result should be a concise but informative representation that is easy for a person to read. It is recommended that all subclasses override this method.
The toString method for class Object returns a string consisting of the name of the class of which the object is an instance, the at-sign character `@', and the unsigned hexadecimal representation of the hash code of the object. In other words, this method returns a string equal to the value of:
getClass().getName() + '@' + Integer.toHexString(hashCode())
Returns:
a string representation of the object.
anyway.. just a thought. =)