Shoan,
my bad. They specify a location relative to the propel generator
directory, since that is on the include path.
This is taken from an example where the dir layout was as follows:
projroot
+-app
| \-modules
+-dev
| +-om (schema.xml, build.properties)
| \-templates (the two classes)
+-libs
| +-propel-generator
| | +-classes
| | \-projects
| +-propel
| | \-Propel.php etc
| +-agavi
| +-etc
| \-src
\-pub
\-index.php
At that time, I had just built the templates for testing, so they
were in dev/templates. libs/propel-generator is on the include path
while prope builds things (given that it's a standalone install and
you run using "../../libs/propel-genrator/bin/propel-gen" inside dev/
om), so relative from that, it's ../../dev.templates.blah (gotta use
that syntax, slashes won't work). Of course, if you bundle agavi in
your project like this, you could now use ../agavi.etc.propel.blah.
Remember that you need the very latest Propel 1.3 SVN for that to
work. Also, it doesn't work very well and has many bugs we cannot fix
without drastic changes to Propel (properly instantiable Peers). I
won't have time to work on that for the next one or two weeks. I
strongly recommend not to rely on it for now. It might be thrown out
again.
David
Am 31.01.2007 um 04:13 schrieb Shoan Motwani:
> Hi Guys,
>
> In regards to the new Agavi complex builders for propel, what is the
> path mentioned in the README (quoted below) relative to?
>
> Usage:
>
> in build.properties:
>
> propel.builder.object.class = ../../
> dev.om.templates.AgaviPHP5ComplexObjectBuilder
> propel.builder.peer.class = ../../
> dev.om.templates.AgaviPHP5ComplexPeerBuilder
>
> Thanks.
>
> Peace,
> Shoan.
>
> _______________________________________________
> Agavi Dev Mailing List
> [email protected]
> http://lists.agavi.org/mailman/listinfo/dev
>
_______________________________________________
Agavi Dev Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/dev
