Gautham K (gautham)'s Public Profile in the Diigo Community

Member since Apr 11, 2007, follows 2 people, 1 public groups, 201 public bookmarks (394 total).

More »

Tags

Recent Tags:	programming(0), design(0), development(0), reference(0), productivity(0), web2.0(0), for:tohuwabohu(0), for:santhoshvkamath(0), toread(0), tutorial(0), howto(0), Business(0), funny(0), php(0), google(0), webdev(0), inspiration(0), webdesign(0)
Top Tags:	programming(30), design(26), webdesign(25), development(23), productivity(21), tools(25), reference(14), for:santhoshvkamath(15), webdev(20), for:tohuwabohu(22)

More »

Recent Bookmarks and Annotations

Map Development Platform - MapQuest Developer Network on 2009-10-12
- count, you must migrate your accounts to a My Places account. You can find inform
Create a REST API with PHP « Gen X Design | Ian Selby on 2009-03-11
- there are two main components of a RESTful response: the response body, and a status code.
The Definitive Guide to symfony | Chapter 11 - Ajax Integration | symfony | Web PHP Framework on 2009-02-18
- In XHTML, JavaScript code blocks must be enclosed within CDATA declarations. But pages requiring multiple JavaScript code blocks can soon become tedious to write. That's why symfony provides a javascript_tag() helper, which transforms a string into an XHTML-compliant <script> tag.
- Ajax actions don't include the web debug toolbar in the development environment. Also, they skip the decoration process (their template is not included in a layout by default). If you want an Ajax view to be decorated, you need to specify explicitly has_layout: true for this view in the module view.yml file.
DevPapers - article UnitTesting in PHP using SimpleTest on 2009-02-17
- The line: $this->UnitTestCase('File Manipulation Test'); is optional and it just makes a header line in the test reporter (we will talk about this later).
Chapter 6. Fixtures on 2009-02-16
- One of the most time-consuming parts of writing tests is writing the
  code to set the world up in a known state and then return it to its
  original state when the test is complete. This known state is called
  the fixture of the test.
- setUp() and tearDown() will be
  called once for each test method run.
- 2 more annotations...
- - setUp() and tearDown() are nicely
    symmetrical in theory but not in practice. In practice, you only need
    to implement tearDown() if you have allocated
    external resources like files or sockets in setUp().
    If your setUp() just creates plain PHP objects, you
    can generally ignore tearDown(). However, if you
    create many objects in your setUp(), you might want
    to unset() the variables pointing to those objects
    in your tearDown() so they can be garbage collected.
    The garbage collection of test case objects is not predictable.
  - Variations
    
    What happens when you have two tests with slightly different setups?
    There are two possibilities:
    
    If the setUp() code differs only slightly, move
    the code that differs from the setUp() code to
    the test method.
    
    If you really have a different setUp(), you need
    a different test case class. Name the class after the difference in
    the setup.
Chapter 5. The Command-Line Test Runner on 2009-02-16
- UnitTest must be either a class that inherits
  from PHPUnit_Framework_TestCase or a class that
  provides a public static suite()
Chapter 4. Writing Tests for PHPUnit on 2009-02-16
- By default, PHPUnit converts PHP errors, warnings, and notices that are
  triggered during the execution of a test to an exception. Using these
  exceptions, you can, for instance, expect a test to trigger a PHP error as
  shown in
- PHPUnit_Framework_Error_Notice and
  PHPUnit_Framework_Error_Warning represent PHP notices
  and warning, respectively.
Chapter 2. PHPUnit's Goals on 2009-02-16
- When you test an object with PHPUnit, you do so only through the
  object's public interface. Testing based only on publicly visible
  behaviour encourages you to confront and solve difficult design problems
  earlier, before the results of poor design can infect large parts of the
  system.
- PHPUnit assumes that most tests succeed and it is not worth reporting
  the details of successful tests.
- 3 more annotations...
- - PHPUnit assumes that most tests succeed and it is not worth reporting
    the details of successful tests.
  - PHPUnit assumes that most tests succeed and it is not worth reporting
    the details of successful tests
  - Hence, the first time a test fails, execution of the test halts, and
    PHPUnit reports the failure.
symfony framework forum: askeet => Creating a Robust Referer in Logins on 2009-02-06
- Hi, everyone.
  
  It seems that many of us have problems being able to direct logged-in users to the original page they were trying to access.
  
  Take note that the Request contains the original module, action, etc. that the user was trying to access. The security filter forwards the user to the login action when login is required, thus preserving all the original request information. You can use this information to set the referer in your login form and then redirect after login. It's perfectly robust, requires no special hacks and does not depend on consistent browser behavior beyond the usual form submission stuff.
  
  -Roy
The Definitive Guide to symfony | Chapter 6 - Inside The Controller Layer | symfony | Web PHP Framework on 2009-02-05
- The default mod_rewrite configuration will use index.php when the URL doesn't contain a front controller script name. So both of these URLs display the same page (mymodule/index) in the production environment:
- This process justifies the structure of the filter classes. They all extend the sfFilter class, and contain one execute() method, expecting a $filterChain object as parameter. Somewhere in this method, the filter passes to the next filter in the chain by calling $filterChain->execute().