Re: PhpQT / PhpKDE

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: PhpQT / PhpKDE
by Marcus Whitney on Monday 27/Sep/2004, @07:38

http://us2.php.net/manual/en/language.oop5.overloading.php

Note the __call magic method that does exactly what you are describing. We're ready :)

Related Links

·   Articles on Developer
·   Also by Marcus Whitney
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: PhpQT / PhpKDE
by markc on Thursday 13/Jan/2005, @05:52

So it's early 2005 and I am wondering if there has been any progress realizing a php-qt application anywhere on the planet ?

Better still php-kde. I just did a google search and this is one of the few pages that came up :-) I guess I can always try again in 2006.

[ Reply To This | View ]

Re: PhpQT / PhpKDE
by Jackson on Wednesday 21/Dec/2005, @00:59

I did some work on it and got some of the Smoke stuff working, but then had to put it aside for other stuff (i.e. stuff that feeds my family).

It would be cool though.

[ Reply To This | View ]

Re: PhpQT / PhpKDE
by markc on Wednesday 13/Jun/2007, @06:04

Well Well, half way thru 2007 and still no sign of a PhpKDE. There is a php-qt project that has been picked up, although there is still no viable release that I am aware of, and it is still not a PhpKDE.

Anyone heard of anything out there somewhere, particularly based on KDE4 ?

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"I'm adding spaces everywhere so that Charles doesn't edit the files." -- Stephan Kulow
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.