On segunda-feira, 23 de dezembro de 2013 05:16:38, MANASIJ SUR ROY wrote: > Hi All, > > We are going to adopt a glib based open source library for one of the Tizen > 3.0 features. > > The open source core library is using plugin based architecture and we wish > to provide Tizen Native APIs to write plugins too. However we are facing > one conflict with current Tizen coding idiom standard in order to achieve > the same. I will describe the situation below:
Hello Manasij This needs to be done with a lot of care. On one hand, I think that it's a great step to take something established and built upon it, rather than reinvent the wheel and take the risk of having unstable code. On the other, this is adding glib as a mandatory dependency for applications, visible to end application developers (if I understood correctly). The API styles clash badly with one another. If it's possible to mitigate it by not requiring the end developer have to know glib or write glib-style code, it would be a lot more palatable. Anyway, the decision is not mine. Since this is potentially quite big, I recommend you make a more detailed explanation and submit to the Arch Workgroup (the API change process). It would probably be interesting if you explained what the options are, what the cost and drawbacks for the other options would be, and how much this impacts the end application developer. PS: discussing in the mailing list is fine, but it looks like we need the big- picture-experts to approve it. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
