[
https://issues.apache.org/jira/browse/SHINDIG-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606821#action_12606821
]
bruno rovagnati commented on SHINDIG-321:
-----------------------------------------
yeap, true
i sent the patch for the first two i had issues, cache and userPrefs, but
definitely we have to change "all"
so i decided to start with all under opensocial model.
is a "start".
u imagen then size of a patch that rename "everything"?
so i think we should go for sections.
we can define a roadmap for the renaming and do it by steps...
last patch was the first step :D
what do u think?
bruno
On Fri, Jun 20, 2008 at 9:13 AM, Chris Chabot (JIRA) <[EMAIL PROTECTED]>
--
.-. --- .--. ..-
R o p u
> NameSpace collition in PHP Classes
> ----------------------------------
>
> Key: SHINDIG-321
> URL: https://issues.apache.org/jira/browse/SHINDIG-321
> Project: Shindig
> Issue Type: Improvement
> Components: Common Components (PHP), Gadget Rendering Server (PHP)
> Reporter: bruno rovagnati
> Attachments: namespace_email.patch,
> namespacer_cache_setpref_setprefs.patch, shindig_namespace.patch
>
>
> Some classes are having conflicting names such as Cache, Name, Email, Person
> etc... (mainly src/socialdata/opensocial/model/*)
> I suggest to move those class name to a Shindig_Cache, Shindig_Name, etc.
> (Zend-like namespace convention)
> i'll start adding patched to these classes that are conflicting while
> implementing shindig
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
