Skip to main content

Home/ PHP Programming/ Group items tagged ide

Rss Feed Group items tagged

qualitypoint Tech

SEO friendly URL or Pretty URL using Apache mod_rewrite |QualityPoint Technologies - 0 views

  •  
    Consider below url. http://site.com/showtopic.php?id=10 By seeing this url we can understand that this site is developed using php, and we can understand coding/database table upto some extent. For example, if you change id value to some invalid value instead of 10 we will get some error message/query which may give some details about database table.
Jungle Jar

JungleJar | Featured Web Application: PHPanywhere.net - 0 views

  •  
    This is an extremely cool and useful web application, and if it hasn't been thought of before, I'm absolutely shocked, because it makes so much sense. Essentially, PHPanywhere is a web based free Integrated Development Environment or IDE for the PHP language. In other words it is a web based application that provides PHP developers a PHP code editor that mocks a desktop application, and it does so very well.
qualitypoint Tech

News Letter QualityPoint Technologies - 0 views

  •  
    We had sent below News Letter to our email contacts. If you want to receive future news letters you can send your email id to qualitypointmail@gmail.com.
qualitypoint Tech

Workaround for inconsistent issue with mySql query handling integer id - 1 views

  •  
    We faced some inconsistent issue with MySql query.
sdiwc conferences

CFP - ICDIPC2012 - Lithuania - IEEE - 1 views

You are invited to participate in The Second International Conference on Digital Information Processing and Communications that will be held in Lithuania, on July 10-12, 2012. The event will be hel...

Digital Information Communications Conferences

started by sdiwc conferences on 17 May 12 no follow-up yet
spymek soft

Find Around Me - 0 views

  •  
    Find the places around you that you need the most and usually search for(when you are not aware of the area) at the tip of your finger. May it be ATM or gas stations or beauty sallons, you will get the list of these in few seconds. Also you will get the route map from your current location to destination. Simple and Useful app.
spymek soft

Tap Tap Words - 0 views

  •  
    A simple, addictive and informative game where you can learn words with the meaning and improve your vocabulary.
  •  
    A simple, addictive and informative game where you can learn words with the meaning and improve your vocabulary.
Sarah HL

Changelog | symfony | Web PHP Framework - 0 views

  • Updating Doctrine to 1.0.12
  • fixed form field render method so widget schema id format is applied
  • fixed missing div in admin generator used in css styles
  • ...4 more annotations...
  • upgraded lime for symfony 1.2.x
  • fixed PHPDoc
  • fixed doctrine form filter when the table method returns a query with a different root alias
  • Fixed case-insensitive check of sf_method routing requirement
Raúl - [^BgTA^]

Phantom Reference : Weblog - 0 views

  •  
    PHP Support in Netbeans
sloansteddi

How to use PHP and PEAR MDB2 (Tutorial) | David and Katherine Goodwin - 0 views

    • sloansteddi
       
      Prepare takes the $sql (with '?'s where data will go), along with the TYPES (array) of data to prepare the sql for, and a 3rd paramater for manipulating or result-getting (see next paragraph). It assigns this to $prepared_statement. Another array is created with the data (in the same order as the types, of course), and the RESULT is aquired by running the execute() method on the $prepared_statement object, passing the execute method the "$data" array to fill in the '?'s After this do everything as normal.
  • column = ?
  • id = ?
  • ...1 more annotation...
  • I have a feeling that MDB2 lower cases all field names - so you'll probably need : echo $row['name'] A good idea would be to print_r($row) or similar, to see what's in it
  •  
    A great walk through on getting started with MDB2
Raúl - [^BgTA^]

Designing For Every Browser: How To Make Your Site Fully Cross Browser Compatible > Des... - 0 views

  •  
    Designing For Every Browser: How To Make Your Site Fully Cross Browser Compatible
jdr santos

Light PHP Edit - 0 views

  •  
    PHP editor, Maked to be light, easy and simple, integrated with PHP by php4delphi component, Highlight by SynEdit component, Debuging XDebug.org DBGp protocol, has internal console for learning php easy, Run, Check, Breakpoints and Watches
Raúl - [^BgTA^]

30+ Firefox Add-ons for Web Developers & Designers - 0 views

  •  
    Las 30 mejores extensiones para Firefox:


    Aardvark - A cool extension for web developers and designers, allows them to view CSS attributes, id, class by highlighting page element individually. chromEdit - Alter the appearance of any page by editing CSS and Javascript files with this extension. CSSMate - Firefox extension to edit CSS files.
    CSS validator - Check the validity of your webpage using this CSS validator extension. CSSViewer - See the CSS properties of page elements with this extension.
    EditCSS - Play around with loaded CSS, Web Developer extension also provides this functionality.
    IE Tab - Designers and developers can view their CSS projects on Internet Explorer using this extension.
    Style Sheet Chooser II - Users can pick and choose alternate style sheets for a website. FireBug - A console for debugging JavaScript, HTML, and Ajax code snippets. HTML Validator - Cool extension to validate web pages with HTML standards of W3C. JavaScript Debugger - JavaScript debugging extension enables a strong debugging environment.

Sarah HL

10 Principles of the PHP Masters | Internet Resources | Cpworld2000.com - 0 views

  • 1. Use PHP Only When You Need it – Rasmus Lerdorf
  • PHP was created out of a need to solve web development problems
  • Lerdorf is the first to admit that PHP is really just a tool in your toolbox, and that even PHP has limitations.
  • ...9 more annotations...
  • 2. Use Many Tables With PHP and MYSQL for Scalability – Matt Mullenweg
  • 3. Never, ever trust your users – Dave Child
  • 4. Invest in PHP Caching – Ben Balbo
  • 5. Speed up PHP Development with an IDE, Templates and Snippets – Chad Kieffer
  • 6. Make Better Use of PHP’s Filter Functions – Joey Sochacki
  • 7. Use a PHP Framework – Josh Sharp
  • 8. Don’t use a PHP Framework – Rasmus Lerdorf
  • 9. Use Batch Processing – Jack D. Herrington
  • 10. Turn on Error Reporting Immediately – David Cummings
Sarah HL

ongoing · Test-Driven Heresy - 0 views

  • As a profession, we do a lot more software maintenance than we do greenfield development.
  • the deep-TDD rules: ¶ Never write code until you have a failing test. Never write any more code than is necessary to un-fail the test.
  • we do way more maintenance than initial development. And in my experience, the first-cut release of any nontrivial software is pretty well crap.
  • ...38 more annotations...
  • But to do that well, you absolutely must have enough test coverage that you just aren’t afraid to rip your code’s guts out
  • I always end up sketching in a few classes and then tearing them up and re-sketching, and after a few iterations I’m starting to have a feeling for X and Y.
  • once you’re into maintenance mode, there are really no excuses. Because you really know what all your X’s and Y’s are
  • I freely admit that this is not really truly TDD
  • Writing the tests points out all the mistakes you might make in signatures, prerequisites, etc. If the tests are too hard to make then you know that your API will be too hard to use, you're doing it completely wrong, and may as well pause for a rethink.
  • While the approach you advocate makes sense, it does require professionalism, not just from the developer but from management too.
  • the person left to maintain the code isn't the person who wrote it, leaving the maintainer with an unholy mess to untangle. Getting unit tests into such code is a monumental task.
  • he failure to address how unit tests can be introduced to an existing non unit-test codebase. (i.e. go from non-TDD to TDD)
  • I feel the TDD community only wants to focus on greenfield projects and has ignored maintenance/legacy issues. Which is strange when as you say code spends most of it's time in maintenance
  • The thing is that as long as the project is small you really don't see the benefits of TDD. I've done a couple of small projects and never had to go back to them ever again
  • Never use mocks unless you are mocking an interface that will almost never change
  • You are writing the client code (in the form of a test) so you are thinking how the worker code will be used. What is its public interface and what do you want it to do when it's called
  • From: Tathagata Chakraborty (Jun 24 2009, at 07:31)TDD is useful in another situation - in a commercial setting and when detailed specification documents have already been created by say a technical expert/architect. In this case you don't have to do a lot of designing while coding, so you can start off with the test cases.
  • writing the tests *first* is that it helps keep your code focused on exactly what it's meant to do, and no more
  • When work on production code begins, most of the code should fall into the categories of things that are not to be tested.
  • In theory, TDD is a great idea. The problem with TDD can be expressed in one word: money.
  • One approach to the unknown X and Y problem that I've been using recently has been to pretend that class X has been written already, and then write code that uses this pretend X object/API. I usually write this directly in the file that will become my unit test. Since X doesn't exist, I'm allowed to call whatever methods I want and pretend it all works. Once I'm satisfied with how it all looks, I cut and paste everything into a bunch of failing tests.
  • I get really bored adding tests to code that already runs
  • the seductive TDD trap
  • religious zealots
  • There is nothing wrong with building tests after you have built your product.
  • that goes a long way towards taking software development from a form of artisanal craftsmanship to a real engineering profession.
  • using tests to drive development cripples innovation, dramatically slows development
  • It always seem to me to be a codified form of reverse engineering, or at least a way to force the programmers into looking at their code from two separate angles at the same time.
  • If you're just adding tests at the end, then it's normal unit-testing, isn't it?
  • I do realize that this type of exercise might help younger coders in getting better structure, they do often rush in too quickly and focus more on the instructions than the abstractions.
  • TDD is test-driven *design*
  • He said he didn't write tests in cases where it would have taken him several hours to get a working test for a small piece of code.
  • In some applications, objects are self-contained, activities are sequential, and algorithms are tricky
  • I've seen cases where people have wrecked the architecture of systems in the name of making them testable... But have never written the tests.
  • Yes, it's possible to make peace with testability, and in the best situation, testability can improve the architecture of a program, but it can also lead people away from highly reliable and maintainable KISS approaches.
  • Like any infrastructure, it is always beneficial to provide unit testing. The most benefit is derived from installing it as early on in the project as possible.
  • The value of an untested feature, to a client, is ... zero. So, it doesn't matter how many of these you have rattled off in the past week, your net throughput is effectively... zero."
  • You can see in this thread the word "professionalism" (substitute "morality" with little gain/loss of substance) and even "sin" (used in jest, but not really!)
  • if I delay writing unit tests until after all the units are working together then because the system "already works" my subconscious enthusiasm for writing unit tests falls markedly, and so their quality and coverage fall
  • Experience teaches that if I generate that output by hand (1) it takes *much* longer (2) I almost always get it wrong. So I often write the code, get its output, carefully check it (really...) and then use it as the correct result.
  • My main objections to TDD are: 1) it promotes micro-design over macro-design and 2) it's hard to apply in practice (i.e. for any code that is not a bowling card calculator or a stack).
  • the tests are just a persistent artifact of the exploratory coding I've already done.
renews_

Linha de Código - Sistema de autenticação de usuários em PHP usando sessões e... - 0 views

  •  
    Esse artigo é um passo-a-passo da criação de um simples sistema de autenticação de usuários usando banco de dados MySQL e principalmente, as poderosas sessões do PHP. Mostro também como trabalhar com senhas em MD5 e permissões para os usuários.
1 - 20 of 23 Next ›
Showing 20 items per page