|
From: Justin F. <je...@ey...> - 2001-07-09 12:48:48
|
Guys:
As you know, and I unabashedly tell everyone, I am developing
a number of applications/packages/modules. A lot of these
are in the "toy" category, but my motive is to learn the
environment and issues that it presents, and will present
in a production environment, plus slowly
accumulate really useful modules.
Now I have a kind of development library that does some useful
things like "where is module so-and-so" (in which package
I forgot), and other methods that traverse the ./user/mod
sub-tree and answer things about packages and modules.
What I want right now is a class that understands the
BC-used PHP coding standards, in which, there is a
method that when given the file path and method name
it parses out everything between
// {{{ Method
and
// }}}
and returns it.
Anybody know where such an animal is? I have been
looking around http://www.phpdoc.de/ and in
the /usr/share/php/PEAR directory, but haven't found
such a class.
Can anyone point me to one? I'll find it, eventually,
but maybe someone knows...
_jef
--
Justin Farnsworth
Eye Integrated Communications
321 South Evans - Suite 203
Greenville, NC 27858 | Tel: (252) 353-0722
|
|
From: Jimmy H. <ji...@ha...> - 2001-07-09 16:11:10
|
Hi, in the HelloWorld example you said for simplicity sake, you put HTML in there, but it's a no-no in real world. Well I agree, but I don't see a way to not put the HTML in there, say a module reads some rows from a database, then wants to output that in a table... How can it be done without having html in the Module->Output() ? Thanks for the hint. By the way I have went ahead and did my project in plain php, since I want to use Smarty |
|
From: Alex B. <en...@tu...> - 2001-07-09 20:05:59
|
> Hi, in the HelloWorld example you said for simplicity sake, you put HTML > in there, but it's a no-no in real world. Well I agree, but I don't see > a way to not put the HTML in there, say a module reads some rows from a > database, then wants to output that in a table... How can it be done > without having html in the Module->Output() ? With includes. > Thanks for the hint. > > By the way I have went ahead and did my project in plain php, since I > want to use Smarty You can use smarty in r2 for module output, nothing will prevent you :) _alex -- alex black, ceo en...@tu... the turing studio, inc. http://www.turingstudio.com vox+510.666.0074 fax+510.666.0093 |
|
From: Jimmy H. <ji...@ha...> - 2001-07-09 23:24:36
|
Alex, > You can use smarty in r2 for module output, nothing will > prevent you :) This means the smarty templates will just be the parts / chunks that will still eventually go together into the master tmpl php section right? It seems to me that the template system will become bloated if I also use smarty.. Like I'll have multiple template one with smarty and its syntax, and one with the bc / php template.... Will it be possible to opt to one e.g. smarty only? Cheers, Jimmy |
|
From: Alex B. <en...@tu...> - 2001-07-09 23:34:02
|
> Alex, > >> You can use smarty in r2 for module output, nothing will >> prevent you :) > > This means the smarty templates will just be the parts / chunks that > will still eventually go together into the master tmpl php section > right? It seems to me that the template system will become bloated if I > also use smarty.. Like I'll have multiple template one with smarty and > its syntax, and one with the bc / php template.... yes, you would use a bc master, but really that doesn't add any work. it means that you'll use smarty for module output, which would work quite nicely. as far as "possible to have the entire page rendered from smarty" yes, absolutely - in the future. I'd like to get to the point where master templates and layouts are just templates - nothing special about them except default module associations. > Will it be possible to opt to one e.g. smarty only? best, -alex -- alex black, ceo en...@tu... the turing studio, inc. http://www.turingstudio.com vox+510.666.0074 fax+510.666.0093 |
|
From: Alex B. <en...@tu...> - 2001-07-09 20:03:58
|
> Now I have a kind of development library that does some useful
> things like "where is module so-and-so" (in which package
> I forgot), and other methods that traverse the ./user/mod
> sub-tree and answer things about packages and modules.
Cool.
> What I want right now is a class that understands the
> BC-used PHP coding standards, in which, there is a
> method that when given the file path and method name
> it parses out everything between
>
> // {{{ Method
>
> and
>
> // }}}
>
> and returns it.
That's what PHPDoc does. It's the source of the comment standard (PHPDoc
takes its standard from javaDoc.)
So, you'll be able to generate complete API docs from your code if you
document it correctly.
> Anybody know where such an animal is? I have been
> looking around http://www.phpdoc.de/ and in
> the /usr/share/php/PEAR directory, but haven't found
> such a class.
You may be doing something different - but as far as documenting methods,
classes, etc PHPDoc is extremely useful.
> Can anyone point me to one? I'll find it, eventually,
> but maybe someone knows...
_alex
--
alex black, ceo
en...@tu...
the turing studio, inc.
http://www.turingstudio.com
vox+510.666.0074
fax+510.666.0093
|