[PHP] Re: PHP, OOP and AJAX

2009-05-28 Thread Jo�o C�ndido de Souza Neto
Julian,

could you please show us an example of this problem?


-- 
João Cândido de Souza Neto
SIENS SOLUÇÕES EM GESTÃO DE NEGÓCIOS
Fone: (0XX41) 3033-3636 - JS
www.siens.com.br

Julian Muscat Doublesin opensourc...@gmail.com escreveu na mensagem 
news:5e0039ed0905280431o2e9d8036u217b0449eccd...@mail.gmail.com...
 Hi Everyone,

 This is the first time that I am posting in the PHP forum, so hope that I 
 am
 osting in the right place.

 I would like to say that before submitting to this forum I have done some
 research looking for a solution without success.

 I had been programming in ASP.NET for years using Object Oriented
 Princeliness but decided to walk away from that.  I am now researching and
 specialising in the open source world.

 I have started to develop a project using MySQL, PHP and OOP. So far I 
 have
 succeed. However I got stuck once I started implement AJAX using the AJAX
 tutorial from w3schools.com.

 What I have discovered is: for some reason when you call a file that
 requires other fies using the REQUIRE or INCLUDE it just does not work. I
 can conform this as I have tested with out the the functions.

 Has anyone ever meet such a situation can you give me some feedback 
 please.

 Thank you very much in advance for your support.

 Regards

 Julian
 



-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] Re: PHP, OOP and AJAX

2009-05-28 Thread kranthi
i never faced such a problem and i can assure you that it will never
happen. try...

main.php
?php
require('second.php');
?

second.php
test

call main.php via AJAX and see the responseText.
many things can go wrong in your coding. dont come to the conclusion
that this particular thing is not working.

i recommend you firebug firefox adddon (just go to the net tab and you
can see all the details of the communication between client and
server)
and i find it helpful to use a standard javascript(jQuery in my case)
library instead of highly limited plain javascript  language

and for you case its difficult to comment without seeing your actual code.

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: Re: [PHP] Re: PHP, OOP and AJAX

2009-05-28 Thread oorza2k5

Two things:

1. Try using the fully qualified path (ie /var/www/foo/bar.php instead of  
foo/bar.php)
2. Look at setting up autoloading so you don't need to manually include  
anyway. If you're going OOP, autoloading is a must!


On May 28, 2009 8:49am, kranthi kranthi...@gmail.com wrote:

i never faced such a problem and i can assure you that it will never



happen. try...





main.php




require('second.php');



?





second.php



test





call main.php via AJAX and see the responseText.



many things can go wrong in your coding. dont come to the conclusion



that this particular thing is not working.





i recommend you firebug firefox adddon (just go to the net tab and you



can see all the details of the communication between client and



server)



and i find it helpful to use a standard javascript(jQuery in my case)



library instead of highly limited plain javascript language





and for you case its difficult to comment without seeing your actual code.





--



PHP General Mailing List (http://www.php.net/)



To unsubscribe, visit: http://www.php.net/unsub.php






Re: [PHP] Re: PHP, OOP and AJAX

2009-05-28 Thread Lenin
2009/5/28 kranthi kranthi...@gmail.com



 i recommend you firebug firefox adddon (just go to the net tab and you
 can see all the details of the communication between client and
 server)
 and i find it helpful to use a standard javascript(jQuery in my case)
 library instead of highly limited plain javascript  language

I also recommend using FirePHP with FireBug here's a nicely written tutorial
on how to use them both together for Ajax'ed pages. http://tr.im/iyvl
Thanks
Lenin
www.twitter.com/nine_L


Re: [PHP] Re: PHP, OOP and AJAX

2009-05-28 Thread Olexandr Heneralov
Hi!
Do not use low-level AJAX.
There are many frameworks for ajax (JQUERY).
Try to use PHP frameworks like symfony, zend framework. They simplify your
work.


2009/5/28 Lenin le...@phpxperts.net

 2009/5/28 kranthi kranthi...@gmail.com

 
 
  i recommend you firebug firefox adddon (just go to the net tab and you
  can see all the details of the communication between client and
  server)
  and i find it helpful to use a standard javascript(jQuery in my case)
  library instead of highly limited plain javascript  language
 
 I also recommend using FirePHP with FireBug here's a nicely written
 tutorial
 on how to use them both together for Ajax'ed pages. http://tr.im/iyvl
 Thanks
 Lenin
 www.twitter.com/nine_L



Re: [PHP] Re: PHP, OOP and AJAX

2009-05-28 Thread Luke
2009/5/28 Olexandr Heneralov ohenera...@gmail.com

 Hi!
 Do not use low-level AJAX.
 There are many frameworks for ajax (JQUERY).
 Try to use PHP frameworks like symfony, zend framework. They simplify your
 work.


 2009/5/28 Lenin le...@phpxperts.net

  2009/5/28 kranthi kranthi...@gmail.com
 
  
  
   i recommend you firebug firefox adddon (just go to the net tab and you
   can see all the details of the communication between client and
   server)
   and i find it helpful to use a standard javascript(jQuery in my case)
   library instead of highly limited plain javascript  language
  
  I also recommend using FirePHP with FireBug here's a nicely written
  tutorial
  on how to use them both together for Ajax'ed pages. http://tr.im/iyvl
  Thanks
  Lenin
  www.twitter.com/nine_L
 



Moo, I would say learn to do PHP by itself before you go using frameworks.

AJAX is a bit different though because there will be few reasons that you
will ever need to write low level code when you're using a library like
Prototype =)

-- 
Luke Slater
:O)


Re: Re: [PHP] Re: PHP, OOP and AJAX

2009-05-28 Thread Tony Marston

oorza...@gmail.com wrote in message 
news:000e0cd6ad1a9f7d3d046af89...@google.com...
 Two things:

 1. Try using the fully qualified path (ie /var/www/foo/bar.php instead of
 foo/bar.php)
 2. Look at setting up autoloading so you don't need to manually include
 anyway. If you're going OOP, autoloading is a must!

I totally disagree. I have been doing OOP with PHP for years, and I have 
never used autoloading. It is just a feature that can be used, misused or 
abused just like any other. I choose not to use it, and my code does not 
suffer in the least!

-- 
Tony Marston
http://www.tonymarston.net
http://www.radicore.org




-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: Re: [PHP] Re: PHP, OOP and AJAX

2009-05-28 Thread Tony Marston
Eddie Drapkin oorza...@gmail.com wrote in message 
news:68de37340905280737t3e1ad844y188ab8fa08f17...@mail.gmail.com...
 Your code might not, but you sure do!  Spending all that time writing
 require statements = :(

If you are too lazy to write require statements then you are probably too 
lazy to write readable, well structured and efficient code. Besides, I don't 
use require statements, I use
$dbobject = singleton::getInstance('classname');

I don't use autoload because *I* want to be in control. I prefer not to rely 
on automatuic features which may not work as expected.

-- 
Tony Marston
http://www.tonymarston.net
http://www.radicore.org

 On Thu, May 28, 2009 at 9:49 AM, Tony Marston 
 t...@marston-home.demon.co.uk
 wrote:


 oorza...@gmail.com wrote in message
 news:000e0cd6ad1a9f7d3d046af89...@google.com...
  Two things:
 
  1. Try using the fully qualified path (ie /var/www/foo/bar.php instead 
  of
  foo/bar.php)
  2. Look at setting up autoloading so you don't need to manually include
  anyway. If you're going OOP, autoloading is a must!

 I totally disagree. I have been doing OOP with PHP for years, and I have
 never used autoloading. It is just a feature that can be used, misused or
 abused just like any other. I choose not to use it, and my code does not
 suffer in the least!

 --
 Tony Marston
 http://www.tonymarston.net
 http://www.radicore.org




 --
 PHP General Mailing List (http://www.php.net/)
 To unsubscribe, visit: http://www.php.net/unsub.php


 



-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: Re: [PHP] Re: PHP, OOP and AJAX

2009-05-28 Thread Eddie Drapkin
There's a huge difference between laziness and opting in to use an
incredibly useful (and easy to properly deploy) feature to save myself time
so that I can spend more time writing that structured and efficient code of
which you speak.  And the problem with what you're saying is that you still
have to include 'singleton.php' somewhere in order to call its static
methods, and I'd rather just spend 30 minutes writing an autoloader object
and letting it deal with finding any of the classes I use then trying to
keep track of legacy code I didn't write and require'ing them all over the
place.

The way I look at it, if you spend all your time handling things that you
could automate - and if written properly, will always work as expected (it's
called unit testing and debugging) - then you have no time to write that
structured and efficient code in order to meet your deadlines! :)

On Thu, May 28, 2009 at 10:53 AM, Tony Marston 
t...@marston-home.demon.co.uk wrote:

 Eddie Drapkin oorza...@gmail.com wrote in message
 news:68de37340905280737t3e1ad844y188ab8fa08f17...@mail.gmail.com...
  Your code might not, but you sure do!  Spending all that time writing
  require statements = :(

 If you are too lazy to write require statements then you are probably too
 lazy to write readable, well structured and efficient code. Besides, I
 don't
 use require statements, I use
$dbobject = singleton::getInstance('classname');

 I don't use autoload because *I* want to be in control. I prefer not to
 rely
 on automatuic features which may not work as expected.

 --
 Tony Marston
 http://www.tonymarston.net
 http://www.radicore.org

  On Thu, May 28, 2009 at 9:49 AM, Tony Marston
  t...@marston-home.demon.co.uk
  wrote:
 
 
  oorza...@gmail.com wrote in message
  news:000e0cd6ad1a9f7d3d046af89...@google.com...
   Two things:
  
   1. Try using the fully qualified path (ie /var/www/foo/bar.php instead
   of
   foo/bar.php)
   2. Look at setting up autoloading so you don't need to manually
 include
   anyway. If you're going OOP, autoloading is a must!
 
  I totally disagree. I have been doing OOP with PHP for years, and I have
  never used autoloading. It is just a feature that can be used, misused
 or
  abused just like any other. I choose not to use it, and my code does not
  suffer in the least!
 
  --
  Tony Marston
  http://www.tonymarston.net
  http://www.radicore.org
 
 
 
 
  --
  PHP General Mailing List (http://www.php.net/)
  To unsubscribe, visit: http://www.php.net/unsub.php
 
 
 



 --
 PHP General Mailing List (http://www.php.net/)
 To unsubscribe, visit: http://www.php.net/unsub.php




Re: Re: [PHP] Re: PHP, OOP and AJAX

2009-05-28 Thread Tony Marston

Eddie Drapkin oorza...@gmail.com wrote in message 
news:68de37340905280801m6964d355l2d6d8ef773f3b...@mail.gmail.com...
 There's a huge difference between laziness and opting in to use an
 incredibly useful (and easy to properly deploy) feature to save myself 
 time
 so that I can spend more time writing that structured and efficient code 
 of
 which you speak.  And the problem with what you're saying is that you 
 still
 have to include 'singleton.php' somewhere in order to call its static
 methods,

I have a single general purpose include file which autmatically includes all 
other standard files, so I never have to explicity load my singleton class.

 and I'd rather just spend 30 minutes writing an autoloader object
 and letting it deal with finding any of the classes I use then trying to
 keep track of legacy code I didn't write and require'ing them all over the
 place.

I'd rather not waste 30 minutes of my time writing a feature that I don't 
need.

The difference between using and not using the autoload feature does not 
have any measurable impact on either my development times, nor the execution 
of my code, so I choose to not use it. That's my choice, and I'm sticking to 
it.

 The way I look at it, if you spend all your time handling things that you
 could automate - and if written properly, will always work as expected 
 (it's
 called unit testing and debugging) - then you have no time to write that
 structured and efficient code in order to meet your deadlines! :)

Not using autoload does not have any noticeable effect on my deadlines, so I 
have no incentive to use it. Just because you say that I *should* use it 
carries no weight at all.

-- 
Tony Marston
http://www.tonymarston.net
http://www.radicore.org

 On Thu, May 28, 2009 at 10:53 AM, Tony Marston 
 t...@marston-home.demon.co.uk wrote:

 Eddie Drapkin oorza...@gmail.com wrote in message
 news:68de37340905280737t3e1ad844y188ab8fa08f17...@mail.gmail.com...
  Your code might not, but you sure do!  Spending all that time writing
  require statements = :(

 If you are too lazy to write require statements then you are probably 
 too
 lazy to write readable, well structured and efficient code. Besides, I
 don't
 use require statements, I use
$dbobject = singleton::getInstance('classname');

 I don't use autoload because *I* want to be in control. I prefer not to
 rely
 on automatuic features which may not work as expected.

 --
 Tony Marston
 http://www.tonymarston.net
 http://www.radicore.org

  On Thu, May 28, 2009 at 9:49 AM, Tony Marston
  t...@marston-home.demon.co.uk
  wrote:
 
 
  oorza...@gmail.com wrote in message
  news:000e0cd6ad1a9f7d3d046af89...@google.com...
   Two things:
  
   1. Try using the fully qualified path (ie /var/www/foo/bar.php 
   instead
   of
   foo/bar.php)
   2. Look at setting up autoloading so you don't need to manually
 include
   anyway. If you're going OOP, autoloading is a must!
 
  I totally disagree. I have been doing OOP with PHP for years, and I 
  have
  never used autoloading. It is just a feature that can be used, misused
 or
  abused just like any other. I choose not to use it, and my code does 
  not
  suffer in the least!
 
  --
  Tony Marston
  http://www.tonymarston.net
  http://www.radicore.org
 
 
 
 
  --
  PHP General Mailing List (http://www.php.net/)
  To unsubscribe, visit: http://www.php.net/unsub.php
 
 
 



 --
 PHP General Mailing List (http://www.php.net/)
 To unsubscribe, visit: http://www.php.net/unsub.php


 



-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] Re: PHP, OOP and AJAX

2009-05-28 Thread Ashley Sheridan
On Thu, 2009-05-28 at 16:17 +0300, Olexandr Heneralov wrote:
 Hi!
 Do not use low-level AJAX.
 There are many frameworks for ajax (JQUERY).
 Try to use PHP frameworks like symfony, zend framework. They simplify your
 work.
 
 
 2009/5/28 Lenin le...@phpxperts.net
 
  2009/5/28 kranthi kranthi...@gmail.com
 
  
  
   i recommend you firebug firefox adddon (just go to the net tab and you
   can see all the details of the communication between client and
   server)
   and i find it helpful to use a standard javascript(jQuery in my case)
   library instead of highly limited plain javascript  language
  
  I also recommend using FirePHP with FireBug here's a nicely written
  tutorial
  on how to use them both together for Ajax'ed pages. http://tr.im/iyvl
  Thanks
  Lenin
  www.twitter.com/nine_L
 
Real coders use low-level ajax... and code with rocks too ;)


Ash
www.ashleysheridan.co.uk


-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php