HI
Does anyone know where I can find good documentation on the Pear module Net_DNS?
There is its End-User Documentation, on PEAR's website.
There are a couple of examples for some methods, like Net_DNS_Resolver::query().
(Yeah, one problem with PEAR package is that some of them are not that well documented... This doesn't seem to bad, on this point ; I've seen worse ^^ )
there is also the generated API docs for Net_DNS; available at http://pear.php.net/package/Net_DNS/docs/latest/
If you have the time, and feel like you would like to help the PEAR project, you could always submit an update or "Documentation Problem" bug report.
Related
Is there any good "go-to-definition" method for Atom? I tried go-to-definiton package, but it needs 2-10sec to to go to the definition. (In Sublime text it's a lot more quicker.
There is a topic on the atom discuss site about this subject. Since the last 22 days (4/08/2016) there is no native feature to go-to-definition.
Topic link: Is there a simple go-to-definition
But there is another package that you can try to use.
There's goto package which replaces symbols-view (which can be disabled); no ctags needed
The last days I was trying to install and run the xhprof.
I finally made it and I think that it brings up very interesting information. I also installed graphviz and I can generate nice graphs, but I would like to find a documentation explaining what the colors in the graphs mean? What does exactly mean each column of the profiler report and how is it calculated.
I was trying to find something the whole day, but unfortunately the only information that I found were usage documentation.
Does any of you have such documentation or know a link?
This link seems to be broken...
The documentation is still available via archive.org.
I've filed an issue with facebook about it already.
have you tried this site:
http://techportal.inviqa.com/2009/12/01/profiling-with-xhprof/
it contains all required basic information needed for digging deeper into XHProf.
you will also find windows builds here: www.phpfluesterer.de
We are about to start using PHPDoctor to auto-generate documentation for our PHP codebase at work. (It was the only one we've tried that could handle our very large codebase, and unlike PHPDocumentor, it's still being updated and supports PHP 5.3).
We'd like to try using different doclets and/or stylesheets than the default that come with it. I did some Googling but didn't see where anybody has posted any. Before we make our own, does anybody know a place where they can be found online?
If you do create your own, we'd love to see it and add it into the project if it's something other people would benefit from.
Has anyone got these to work together seemlessly? I have tried, had some success using the plugin at http://phing.info/trac/wiki/Users/Documentation/CruiseControl, but have failed to:
Get the metrics graphs working (nothing appears)
Enable the "PMD" - project mess detection - reports
Are there any other ant-specific commands that must (can) be run in addition to my phing build script?
Also, the front page of the reports section dumps a heap of log information, and I'm trying to get rid of that too.
Cheers for any help ... we are running phing 2.3.0 and phpUnderControl 0.4.7.
Paul
Our application framework makes heavy use of Phing, and we've got that integrated under CI with phpUnderControl. We do have the metrics and PMD working now, and honestly, it was a little bit of an accident that it started working. But we're still missing the code coverage (working on it) and the phpDoc output (working on that too). I'll try to remember to come back and update this when we're done.
I have found that the main reason for the metrics not showing up is an incompatibility with the ez library that phpuc uses for the rendering. You'll get this NullPointerException on the page, right? Then when you try to run a build manually, you'll get this obscure error about index and divide by 0? What's happening is the ez graphics library that ships with phpuc is old, and you have to upgrade it. I hope that's a clue for you. We didn't have trouble with PMD stuff, so I don't know why that wouldn't work for you. If you want to update your question with more specifics, maybe I can elaborate on what's worked for us?
To answer my question, in the end I figured it was easier to just use an ant build script to make everything work.
I think phing is good when starting out, and has an excellent dbdeploy feature (which I use in phpUC), but for getting the metrics and the PHPMD integrated you are better off using ant - the XML is not hard.
Cheers
I'm using a pre-commit hook to lint-check PHP source submitted by our staff, and everyone's really happy with the results. The staff have agreed it would be useful to have the code re-formatted to follow (customizable) style rules on commit. Are there any FOSS scripts which can do this from the command-line?
PHP_CodeSniffer is a nice PEAR package, but it only sniffs the PHP documents for detecting violations of coding standards - it doesn't fix the violations or re-formats the documents. However, it's a great package that every PHP-developer should at least know about - and maybe you can get your fellow staff members to sanitize their code on their own.
You can edit the sniffing-filter in PHP_CS the way you want it to work. I on the other hand likes the default settings, which is at least a good start for writing better code.
Was looking for the same thing, just came across the PHP Beautfier package in the PEAR repository:
http://pear.php.net/package/PHP_Beautifier
Hope this helps!
Not quite an answer, but since you bring it up, there should be a command line PHP beautifier. Until then you're stuck with sed to fix tabs.
The problem is, its very difficult to write something like what you want without writing a parser for the PHP language. So, if someone were to write such a tool, it should also provide lint functionality, be platform independent and released under a very unrestrictive license.
Considering the above, I think that's why one doesn't (currently) exist (that I could find). I'm posting this as an answer to say thanks for the idea, which is also why this is CW.
Not on the command-line but perhaps useful: PHP/Eclipse can do auto source formatting and I think you can run it on an entire project in one go. http://www.phpeclipse.com/ .