Heya! W dniu 22 kwietnia 2012 14:40 użytkownik Georg Ehrke <owncloud...@georgswebsite.de> napisał: > Am 22.04.2012 um 14:37 schrieb Bartek Przybylski: > >> Heya! >> >> W dniu 22 kwietnia 2012 14:28 użytkownik Frank Karlitschek >> <fr...@owncloud.org> napisał: >>> Hi everybody, >>> >>> currently all Classes in ownCloud start with OC_ >>> This leads to a problem if one app wants to use a class name thats already >>> used in the core or in another app. >>> A second problem is that we want to build a public api that's stable across >>> different ownCloud version. If apps calls all the internal >>> classes/functions or session variable we run into a problem in the long run. >>> >>> Because of that I propose this new namespacing schema: >>> >>> OC_ "ownCloud " Reserver for internal classes and session variables or the >>> core >>> OCP_ "ownCloud public" Reserved for the new public API that has to be used >>> by apps exclusively. (Still has to be build) >>> OCA_"appidentifier"_ "ownCloud App" Reserver for use in ownCloud apps. The >>> unique identifier has to be in the class name so that it doesn`t clash with >>> other apps. >>> >>> >>> What do you think? >>> >> >> Why not use namespacing builded in language ? >> http://php.net/manual/en/language.namespaces.php > I would appreciate this too.
Obviously this will require more amount of work but might make owncloud true OOD and OOP product. >> >>> >>> Cheers >>> Frank >>> >> >> bartek >> _______________________________________________ >>> Owncloud mailing list >>> Owncloud@kde.org >>> https://mail.kde.org/mailman/listinfo/owncloud >> _______________________________________________ >> Owncloud mailing list >> Owncloud@kde.org >> https://mail.kde.org/mailman/listinfo/owncloud > > _______________________________________________ > Owncloud mailing list > Owncloud@kde.org > https://mail.kde.org/mailman/listinfo/owncloud _______________________________________________ Owncloud mailing list Owncloud@kde.org https://mail.kde.org/mailman/listinfo/owncloud
