<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16544" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=644450214-19112007><FONT face=新細明體
color=#0000ff size=2>Hi Ahmad:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=644450214-19112007><FONT face=新細明體
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=644450214-19112007><FONT face=新細明體
color=#0000ff size=2>If we plan to do that, then it is must for Life Type 2.x or
later, it is quite big change. And as I said, it will break the core code
backward compatibility. :)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=644450214-19112007><FONT face=新細明體
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=644450214-19112007><FONT face=新細明體
color=#0000ff size=2>Mark</FONT></SPAN></DIV>
<DIV dir=ltr align=left>
<HR tabIndex=-1>
</DIV>
<DIV dir=ltr align=left><FONT face=Tahoma size=2><B>From:</B>
plog-svn-bounces@devel.lifetype.net [mailto:plog-svn-bounces@devel.lifetype.net]
<B>On Behalf Of </B>Ahmad Saleh<BR><B>Sent:</B> Monday, November 19, 2007 10:01
PM<BR><B>To:</B> LifeType Developer List<BR><B>Subject:</B> Re: [pLog-svn]
Modularize our action/view/dao and templates<BR></FONT><BR></DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV></DIV>Hi Mark<BR><BR>Are these changes for lifetype 2 or 1.x<BR><BR>
<DIV class=gmail_quote>On Nov 19, 2007 3:50 PM, Oscar Renalias <<A
href="mailto:oscar@renalias.net">oscar@renalias.net</A>> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">I
doubt that it will bring any advantage other than simplifying
the<BR>directory structure, but it's probably going to be easier to get
a<BR>feeling of your idea if you try to implement it in a branch,
for<BR>now...<BR>
<DIV>
<DIV></DIV>
<DIV class=Wj3C7c><BR>On Nov 19, 2007 3:18 PM, Mark Wu <<A
href="mailto:markplace@gmail.com">markplace@gmail.com</A>> wrote:<BR>>
Hee, hee, I plan to do that. But before create a new branch for this, I
<BR>> really like to hearing everyone's opinions .. ^_^<BR>><BR>>
Mark<BR>><BR>><BR>> > -----Original Message-----<BR>> >
From: <A
href="mailto:plog-svn-bounces@devel.lifetype.net">plog-svn-bounces@devel.lifetype.net
</A><BR>> > [mailto:<A
href="mailto:plog-svn-bounces@devel.lifetype.net">plog-svn-bounces@devel.lifetype.net</A>]
On Behalf Of<BR>> > Oscar Renalias<BR>> > Sent: Monday, November
19, 2007 8:32 PM<BR>> > To: LifeType Developer List <BR>> >
Subject: Re: [pLog-svn] Modularize our action/view/dao and templates<BR>>
><BR>> > How about you create a new branch for this and do
some<BR>> > prototyping work?<BR>> ><BR>> > On Nov 19,
2007 2:10 PM, Mark Wu < <A
href="mailto:markplace@gmail.com">markplace@gmail.com</A>> wrote:<BR>>
> ><BR>> > ><BR>> > > Hi All:<BR>> >
><BR>> > > I really want to modularize our current code
structure. But <BR>> > it maybe<BR>> > > break the "backward
compatabability" if user change thier<BR>> > code in core<BR>> >
> level instead of plugin level ..<BR>> > ><BR>> > > I
propose we add a new folder for modules, this folder will include <BR>>
> > current actions, views, dao of summary, index and
admin<BR>> > ... the new<BR>> > > structure looks<BR>>
> > like:<BR>> > ><BR>> > >
./class/dao/model.class.php <BR>> > >
./modules/index/actions/viewarticlection.class.php<BR>> > >
./modules/index/views/viewarticleview.class.php<BR>> > >
....<BR>> > ><BR>> > >
./modules/admin/post/actions/adminnewpostaction.class.php <BR>> >
><BR>> > >
./modules/admin/post/actions/adminaddpostaction.class.php<BR>> > >
./modules/admin/post/views/adminnewpostview.class.php<BR>> >
><BR>> > > ./modules/admin/post/dao/article.class.php <BR>>
> > ./modules/admin/post/dao/articles.class.php<BR>> >
><BR>> > ><BR>> > > .....<BR>> > ><BR>>
> > The same in templates, so the ./templates/admin folder
will<BR>> > seperate<BR>> > > to small modules like:<BR>>
> ><BR>> > > ./templates/admin/post/<BR>> > >
./templates/admin/comment/<BR>> > > .....<BR>> > ><BR>>
> > So, we can modularize our code into several small modules, it can
<BR>> > > easier for us to do the further develpement, debug and
modification.<BR>> > ><BR>> > > The biggest advantage is
take a shorter time to find a specific<BR>> > > action.
:(<BR>> > ><BR>> > > So, here comes the
steps:<BR>> > ><BR>> > > 1. Reorgnaize the folder and
code<BR>> > > 2. Rewrite the controller map<BR>> > > 3.
fix all includes<BR>> > > 4. testing .... <BR>> >
><BR>> > > Any ideas? Or someone can share your tips about how
to find<BR>> > a specific<BR>> > > action scripts in 195
files (files under<BR>> > ./class/actions/admin) in a<BR>> >
> very short time ...<BR>> > ><BR>> > > Mark<BR>>
> > _______________________________________________<BR>> > >
pLog-svn mailing list<BR>> > > <A
href="mailto:pLog-svn@devel.lifetype.net">pLog-svn@devel.lifetype.net</A><BR>>
> > <A href="http://limedaley.com/mailman/listinfo/plog-svn"
target=_blank>http://limedaley.com/mailman/listinfo/plog-svn</A><BR>>
> ><BR>> > _______________________________________________
<BR>> > pLog-svn mailing list<BR>> > <A
href="mailto:pLog-svn@devel.lifetype.net">pLog-svn@devel.lifetype.net</A><BR>>
> <A href="http://limedaley.com/mailman/listinfo/plog-svn"
target=_blank>http://limedaley.com/mailman/listinfo/plog-svn
</A><BR>><BR>> _______________________________________________<BR>>
pLog-svn mailing list<BR>> <A
href="mailto:pLog-svn@devel.lifetype.net">pLog-svn@devel.lifetype.net</A><BR>>
<A href="http://limedaley.com/mailman/listinfo/plog-svn"
target=_blank>http://limedaley.com/mailman/listinfo/plog-svn</A><BR>><BR>_______________________________________________<BR>pLog-svn
mailing list<BR><A
href="mailto:pLog-svn@devel.lifetype.net">pLog-svn@devel.lifetype.net</A><BR><A
href="http://limedaley.com/mailman/listinfo/plog-svn"
target=_blank>http://limedaley.com/mailman/listinfo/plog-svn</A><BR></DIV></DIV></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>