Greetings to all, After having contacted both Steve Wampler and Robert Parlett, I am putting out a request for feedback on the merging of both sets of unicon code into one standardised unit.
As a result of looking at both code bases, i find that there are a number of different class Class definitions. In some areas they overlap, in others they give quite different facilities. In my own code base, I have a number of classes that duplicate some of the facilities as provided by each of the aforementioned code bases. My question to everyone is: What code outside the unicon and UniLib libraries do you use that depend on either of these code bases? Is there specific functionality from either that your own code uses and must not change? Steve has nodded to merge as long as it doesn't drop current functionality. I have found useful additions to my own code in both code bases and will be walking down the path of merging. However, I really don't want to kill anyone's code by making changes that will require major rewrites by anyone. Mostly this push has come from my own projects and I want a relatively uniform approach that I can then share and give back to the unicon project. I know that Clinton et al are working on making changes to advance the art behind unicon and are adding to the unicon library as time progresses. My work is running parallel to this and will incorporate the unicon teams changes as they are released. regards Bruce Rennie ------------------------------------------------------------------------------ _______________________________________________ Unicon-group mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unicon-group
