General Discussion issue for 0.9.0

[ofTheo]

These are just some general things that it might be good to discuss for 0.9.0 in terms of OF's API. Nothing below is definitive but I think its a good time to talk a bit more about the API, so please comment and I'll add to and edit the list below.

More General:

• Look at Towards 1.0 doc - see what should be applied. ( link to doc: https://docs.google.com/document/d/1GjgjQZCHTcOD3cT9OFSl0AZ1nhfYwwvxTl5L4OJE6qA/pub )
• Start moving towards a general load( ) method for loading. i.e. move.load(), image.load(), snd.load() etc?
• Review addons or core classes that don't fit with current API ( char * for filenames vs strings etc ) Same goes for examples. Lots of char * strings and sprintf's.
• Identify addons or core classes that work well and serve as a good model for the OF api.
• Look at areas where we can simplify OF. Not always about expanding, what is superfluous?

Specific:

• ofThread - need to make this rock solid, it is the basis of a lot in OF now.
• ofAppExit - better termination - see Directly calling exit() to exit the app is incredibly error-prone #3065
• ofFont - look at ofFont as a better alternative to ofTrueTypeFont ping @bakercp ( requires Poco 1.5 )
• ofXML - needs to be more robust at parsing, right now its fairly fragile compared to ofxXmlSettings in reading xml files.
• ofxOpenCv - Move to C++ api? - Look at ofxCv

[bilderbuchi]

I think quite a lot of the API/naming inconsistencies were already covered during the Maine code review (https://github.com/openframeworks/openFrameworks/issues?labels=code-review&milestone=&page=1&state=open) - would be useful to dig through and see what is still relevant.

[kylemcdonald]

lots of relevant thoughts! let's split this into two parts for efficiency of discussion.

Issues assigned to the 0.9.0 milestone

Let's discuss these issues in the relevant issue, otherwise we'll lose track of the discussion. It's also easier to add/remove things from milestones than to keep track of a changing checklist.

• load() Hue from ofColor should be 0..360, not 0.255 #1485
• ofAppExit Directly calling exit() to exit the app is incredibly error-prone #3065 (I just assigned it to 0.9.0)
• main ofFont discussion is ofTrueTypeFont feature discussion #1131 and https://github.com/bakercp/ofxFont but really we need a PR to milestone this, @bakercp has addressed a number of different bugs and feature requests
• ofXml issue is settings.xml creation raise an error #2901 (I just assigned it to 0.9.0)
• ofxCv issue started here Merge ofxCv into openFrameworks #3074 (not assigned to 0.9.0 yet)

General Discussion

It might be better to send this list to the mailing list, since none of these are "actionable" items.

• "Identify addons or core classes that work well"
• "Look at areas where we can simplify OF"
• how to make ofThread "rock solid"

[ofZach]

to add to general discussion of simplification: fix inconsistencies

[danzeeeman]

@ofZach by inconsistencies you mean things that take ofPoints but not ofVec3f or ofVec2f?

can we add ofVec2d, ofVec3d, and ofVec4d so we can #double all the things?

[bakercp]

+1 on doubles. Ideally (imho) through templates. If not, I made these for ofxGeo https://github.com/bakercp/ofxGeo/tree/master/src. Without templates things will get pretty nutty ...

[danzeeeman]

when I saw those I rejoiced @bakercp

[bakercp]

@danthemellowman ha. just find / replace :) but yes ... it can be hard to find your place in this world when you only go float.

[wasawi]

Hi All,
I'm not sure if this is relevant here, but i did a template of ofPoint:
https://github.com/wasawi/ofxPoint
Although i didnt try it on windows or linux..

Also there is some templates here, which they look a lot more clean:
https://github.com/diasbruno/ofCoreTest/tree/feature-ofVec-templates/src

I can easily rename/clean my code if you think it is useful.
Let me know!

[kylemcdonald]

going to close this as the relevant discussion has been happening on individual issues now.