phpgroupware-developers
[Top][All Lists]
Advanced

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

RE: [Phpgroupware-developers] Dont update your CVS HEAD code


From: Bob Schader
Subject: RE: [Phpgroupware-developers] Dont update your CVS HEAD code
Date: Wed, 29 May 2002 12:53:04 -0400

So what does this mean to me if I am in the middle of porting
my timetrack app to use templates? Would it be best to wait
for the part you are working? If the end result will be easier
porting to use templates, then I think it would be best for me
to wait, especially since I don't have much time to work on it
lately anyway.

Bob Schader
World Designs
203 S. Cutler
Spring Lake, MI 49456
(616) 844-2184
(616) 844-2187 Fax


> -----Original Message-----
> From: address@hidden 
> [mailto:address@hidden On Behalf Of 
> Dan Kuykendall (Seek3r)
> Sent: Wednesday, May 29, 2002 12:28 PM
> To: address@hidden; address@hidden
> Subject: [Phpgroupware-developers] Dont update your CVS HEAD code
> 
> 
> I am making some rather large changes to the code which require 
> temporarily breaking lots of stuff.
> I suggest that everyone refrain from doing a cvs update of this code 
> until I make a further announcement letting you all know its safe.
> 
> Here are some of the changes I am making:
> 
> 1) phpGW will now have 5 display parts. They are top, left, 
> body, right, 
> bottom. Template sets will be using how many or how little of 
> these they 
> want, but the base set will be fixed. This allows for more 
> stability in 
> the final html out put as well as tightly integrated support 
> for using 
> FRAMES.
> 
> 2) I am restructuring the flow of the startup process 
> (phpgwapi/inc/functions.inc.php) to make it more straight 
> forward and to 
> allow for frames.
> 
> 3) There will only be one instance of the template class. All 
> apps will 
> parse their output into the template var phpgw_body. The 
> resulting page 
> (unless using frames) will all be done at the end
> 
> Apps will need to use NOT use the templates pfp() or p() or any other 
> one that prints out. All output will be done at the end by the API 
> (unless special situations needs different).
> 
> 4) I am going to be implementing lots of security features 
> and will be 
> detailing these later.
> 
> The goals here are performance, a little more consistancy and 
> to make it 
> easier for new developers to follow the code.
> 
> Seek3r
> 
> 
> _______________________________________________
> Phpgroupware-developers mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
> 
> 




reply via email to

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