Hey Christophe, 2017-08-19 8:29 GMT+09:00 Christophe Sadoine <[email protected]>:
> Hello, > > When making a new release, would it be possible to get a list of > breaking changes of the beta api until it is released? > A list of changes and how to fix it. > I know you shouldn't use it if you are not ready to make the changes > etc... but I am ready to do them, just it would be nice to have this. > Also this could get more application developers to use/test it before > release? (unless of course you don't want that) > > Anyway if this takes too much time or else you can ignore the request. > I very well understand why you want to use beta or EO APIs but it comes at a cost. It's your responsibility to track the changes in the beta API and adapt your code to it. No way we will list the changes in beta API. Often it will trigger compile time or run time errors when it's changed, so it shouldn't be too hard to migrate. > Second topic: I'm sure you must have thought about it, but what about > a library (taken out of enlightenment or not) for making your own > window manager more easily? > I guess you considered it but everything is time consuming I know :) > E is also constantly moving, including the WM part of the code. So I'm not sure how easy it would be to split off what you would need. -- Jean-Philippe André ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
