If you don't mind, I'm putting your message onto the developer list. I initiated an OB-3.0 release plan on GitHub because I think the changes you've made so far are significant and backwards-incompatible. I think that's really worth signaling. (As in, if you have code that uses OB-2.x APIs, you'll probably need to do at least some updating.)
So yes, while I didn't have a chance to say "2018 Plans" yet, I'd like to see some discussion on when 3.0 should be released and any remaining projects. I think the projects you mention are good. Other ideas? (Opening this to the list..) -Geoff > On Jan 7, 2018, at 3:45 PM, Noel O'Boyle <baoille...@gmail.com> wrote: > > Hey Geoff, > > Happy New Year and all that. > > I saw the github project for release 3.0, and so I've been thinking about > whether I might be able to make additional changes before the API is set in > stone. > > I don't know what timeframe you had in mind but here are a couple of things I > wouldn't mind doing before then... > 1. Refactoring reaction handling. > 2. Removing convenience functions. > 3. Removing vestiges of the original stereo handling that no longer apply > (like one or two functions and maybe a flag or two) > 4. Tidy up the valence methods, e.g. OBAtom::GetValence() does not return the > valence, nor is there any function that does. > > And that's basically it. I need to look into (1) to figure out how much work > it is (and write up the proposal), but the others are fairly small though (2) > and (4) obviously require some discussion. > > So what do you think? Had enough of changes, or willing to hold off for a > while? Or have any other ideas? > > Regards, > - Noel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ OpenBabel-Devel mailing list OpenBabel-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbabel-devel
