|
From: <php...@li...> - 2009-10-30 17:01:28
|
Alan, I don't understand your argumentation. The phpdebugger does not replace existing debuggers except "xdebug"; we want to get rid of this: http://bugs.xdebug.org/view.php?id=463 Unless your product uses xdebug code, there's nothing to worry about, I think. Regards, Jost Boekemeier On 29 Oct 2009 20:35, <php...@li...> wrote: >> Why isn't this a separate project > > Creating a new project for a single PHP file doesn't make m... I think it's a really interesting idea and it's very confusing having it buried in the php-java-bridge project. Even just having a single-file "project" on GitHub would be preferable IMHO. This is a *really* cool idea which is getting lost in the complexity of PJB. From a marketing perspective it deserves its own "space." >> What debug client do you use with it? PDT? > > Currently PDT. Ok... > With the new JavaBridge.war you can debug your PHP scripts > directly from your browser (Firefox ... Now you've got me confused again. What does the war file have to do with debugging php in the browser if the debugger is a single php file? I hope that you don't feel I am being harsh or antagonistic. I have the utmost respect for your technical achievements (PJB is awesome and this debugger thing seems very promising) but as hard as I try to understand what's going on with these projects I find myself very confused about them -- what they do, how they work, how they're related to other projects. I think maybe that there are a lot of assumptions in your head that aren't in mine (esp since I am *not* coming from a Java background). But typically I am not a guy that gets easily confused... in any case I think most of your "users" are coming from a php background as well instead of java. Alan ------------------------------------------------------------------------------ Come build with us! ... php...@li... https://lists.sourceforge.net/lists/listinfo/php-java-bridge-users |