Re: More HTML_AJAX

Joshua Eichorn wrote:

Joshua Eichorn wrote:

Daniel Convissor wrote:

On Tue, Jul 19, 2005 at 10:22:06AM -0700, Joshua Eichorn wrote:

Also how do you guys manage doing development from a cvs checkout, I'm on windows at the moment so I can't do symlink tricks, and all the includes rely on the full path.

I develop in the working dir on Windows without a problem. When doing tests, I do an ini_set for include_path to head towards my CVS checkout first. What exactly is the problem you're encountering? --Dan

Well since the package is HTML_AJAX all the includes are HTML/ well actually most are HTML/AJAX/* and i don't have an HTML dir. Im not actually working in cvs right now, but if i was all the code would be in an HTML_AJAX dir. -josh

Hmm i guess the solution is to check HTML_AJAX out as HTML and put a dir below that in my include path?

No the best solution is to "pear up -f package.xml" from your CVS checkout on the devel machine. This way, you're testing the actual PEAR installation. It took me years to figure this out, so don't feel too bad :). I generally have a box open at all times, and use up-arrow/enter to redo the upgrade command. If you grab a copy of a PEAR_PackageFileManager script from any of several PEAR packages, you can get your first package.xml set up for HTML_Ajax quite painlessly, and then use that to do the installs. As for where .js goes, I've recently put it in role="data" as users can config-set data_dir=/path/to/docroot/whatever. I've also dragged the dos prompt to the Start menu right below email, makes it easier to open for PEAR junk. Greg