phpgroupware-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Phpgroupware-tracker] [bug #4090] problem with createobject if classes


From: nobody
Subject: [Phpgroupware-tracker] [bug #4090] problem with createobject if classes are called 'appname.ui'
Date: Sun, 29 Jun 2003 03:32:22 -0400
User-agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3.1) Gecko/20030425

=================== BUG #4090: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4090&group_id=509

Changes by: Anonymous user        Date: Sun 06/29/2003 at 03:32

------------------ Additional Follow-up Comments ----------------------------
i think it is handy for all apps to use uiapp* for at least their ui classes to 
reduce namespace conflicts - until PHP5 takes over :)



=================== BUG #4090: FULL BUG SNAPSHOT ===================


Submitted by: ceb                     Project: phpGroupWare                 
Submitted on: Tue 06/24/2003 at 17:43
Category:  API - phpGWapi             Bug Group:  devel cvs                 
Severity:  5 - Major                  Priority:  High                       
Resolution:  None                     Assigned to:  None                    
Status:  Open                         Component Version:  CVS               
Platform Version:  None               Reproducibility:  None                

Summary:  problem with createobject if classes are called 'appname.ui'

Original Submission:  example: home-screen -> hook home;
several apps called their ui class just 'ui'. i.e. news_admin and stocks. in 
their hook_homes they both create an object 'appname.ui'. it fails to create 
the second object, because there exists already an object 'ui'. we have to 
rename our app_classes to i.e. *uiappname* (uistocks,uinews) or change the 
createobject function...

Follow-up Comments
*******************

-------------------------------------------------------
Date: Sun 06/29/2003 at 03:32       By: None
i think it is handy for all apps to use uiapp* for at least their ui classes to 
reduce namespace conflicts - until PHP5 takes over :)

-------------------------------------------------------
Date: Sat 06/28/2003 at 19:15       By: totschnig
it depends. classes bonews and boadmin, and sonews and soadmin duplicated a lot 
of fonctionality, but in a very inconsistent way, so it made sense to 
standardize and merge them. I merged classes uinews and uiadmin for symetry's 
sake, but I could have let them separate.

-------------------------------------------------------
Date: Sat 06/28/2003 at 11:48       By: mdean
You also don't want to necessarily pile all of your HTML code into one class.  
Splitting the different screens out into their own classes would keep the files 
smaller and more maintainable.  It also would help to force picking real names 
instead of generic ones ;-)

-------------------------------------------------------
Date: Sat 06/28/2003 at 00:31       By: totschnig
I will rename news_admin.ui back to news_admin.uinews. (I had named it ui when 
I merged the two classes uinews and uiadmin). sorry for the trouble.


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4090&group_id=509

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]