Skip to main content

Home/ PHP Programming/ Group items tagged object

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Richard Boss

Custom Query using Database Object in CakePHP - 0 views

technet.weblineindia.com/...ing-database-object-in-cakephp

CakePHP Database Object Object PHP

shared by Richard Boss on 27 Mar 14 - No Cached
  • Richard Boss on 27 Mar 14
     
    In this article, we will see how to use custom query using database object instead of model object?
renews_

Doctrine - PHP Object Relational Mapper - 0 views

www.doctrine-project.org

Php Banco de Dados Classe

shared by renews_ on 24 Mar 09 - Cached
  • renews_ on 30 Mar 10
     
    Doctrine is an object relational mapper (ORM) for PHP 5.2.3+ that sits on top of a powerful database abstraction layer (DBAL). One of its key features is the option to write database queries in a proprietary object oriented SQL dialect called Doctrine Query Language (DQL), inspired by Hibernates HQL. This provides developers with a powerful alternative to SQL that maintains flexibility without requiring unnecessary code duplication.
jdr santos

Artisan System - A PHP5 Object Oriented Framework - 0 views

artisansystem.com

PHP PHP5 object oriented MVC framework open source

shared by jdr santos on 25 Jan 09 - Cached
  • jdr santos on 25 Jan 09
     
    An Object Oriented PHP5 Web Software Framework
jdr santos

the zoop framework - zoop - 2 views

zoopframework.com/

PHP object oriented framework

shared by jdr santos on 01 Jul 09 - Cached
  • jdr santos on 01 Jul 09
     
    Zoop is an object oriented framework for PHP based on a front controller. It is designed to be very fast and efficient and very nice for the programmer to work with. It is easily extensible, and you need only include the functionality you use.
  • jdr santos on 01 Jul 09
     
    Zoop is an object oriented framework for PHP based on a front controller. It is designed to be very fast and efficient and very nice for the programmer to work with. It is easily extensible, and you need only include the functionality you use.
Sarah HL

ongoing · Test-Driven Heresy - 0 views

www.tbray.org/...TDD-Heresy

programming tests test_driven testing lang:en

shared by Sarah HL on 02 Jul 09 - Cached
  • 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.
Yves Leloup

Object-Oriented PHP: Delving Deeper into Properties and Methods - 0 views

www.elated.com/...er-into-properties-and-methods

php object programming

shared by Yves Leloup on 05 May 11 - No Cached
  • Yves Leloup on 05 May 11
     
    Learn how to work with PHP properties and methods in depth. Looks at constructors and destructors; static properties and methods; class constants; type hinting; and overloading.
javatpoints

Node.js Tutorial for Beginners and Professionals - JavaTpoint - 0 views

www.javatpoint.com/nodejs-tutorial

nodejs whatisnodejs introductiontonodejs nodejstutorialforbeginners

shared by javatpoints on 27 Jun 16 - No Cached
  • javatpoints on 27 Jun 16
     
    Node.js tutorial for beginners and professionals with examples on first application, repl terminal, package manager, callback concept, event loop, buffers, streams, file systems, global objects, web modules and more.
Raúl - [^BgTA^]

Abstracting Database Access Using Polymorphism with Objects in PHP 5 - 0 views

www.devshed.com/...morphism-with-Objects-in-PHP-5

database php php5

shared by Raúl - [^BgTA^] on 29 Mar 07 - Cached
  • Raúl - [^BgTA^] on 29 Mar 07
     
    Usar polimorfismo en PHP5 para acceder a diferentes BD
jdr santos

Stato, a PHP5 framework - 0 views

www.stato-framework.org

fr framework mvc open source orm php

shared by jdr santos on 31 Jul 08 - Cached
  • jdr santos on 31 Jul 08
     
    Stato est en fait composé de 2 frameworks utilisables séparément : un framework d'ORM (Object/Relational Mapping) basé sur ActiveRecord et QueryObject, et un framework View-Controller.
jdr santos

wiki [TinyMVC Framework] - 0 views

www.tinymvc.org

PHP framework MVC lightweight open source

shared by jdr santos on 20 Jun 09 - Cached
  • jdr santos on 20 Jun 09
     
    TinyMVC is written in object PHP5, simple and lightweight framework which use MVC (Model-View-Controller) architectural design pattern aproach to easy and fast PHP web application developement.
qualitypoint Tech

Parsing webpage using php DOM. - 4 views

qualitypoint.blogspot.com/...ing-webpage-using-php-dom.html

php workaround php dom

shared by qualitypoint Tech on 12 Dec 09 - Cached
  • qualitypoint Tech on 12 Dec 09
     
    PHP is having DOM functionality for parsing webpage by considering the HTML content of the webpage as XML data. If you assign the $data with the HTML content of the webpage, below code will load the HTML content in DOM object.
qualitypoint Tech

print_r() Versus var_dump() - 3 views

qualitypoint.blogspot.com/...printr-versus-vardump.html

php workaround

shared by qualitypoint Tech on 24 Nov 09 - Cached
  • qualitypoint Tech on 24 Nov 09
     
    PHP is having various functions for debugging a variable. Seeing values stored in an array or in any other object is important for doing any troubleshooting in a code.
ptutorial

php tutorial - 0 views

http:://www.ptutorial.com

php tutorial example function online exam c programming demo ptutorial

shared by ptutorial on 16 Nov 14 - No Cached
  • ptutorial on 16 Nov 14
     
    ptutorial, programming tutorial, php tutorial, php function, php example, c tutorial, c example, object oriented programming in php, error handling in php, array handling with sorting
sloansteddi

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

codepoets.co.uk/_php_database_howto_quickstart

MDB2 how-to tutorial database abstraction PEAR database dba PHP

shared by sloansteddi on 02 Mar 09 - Cached
    • sloansteddi
      sloansteddi on 02 Mar 09
       
      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
  • sloansteddi on 02 Mar 09
     
    A great walk through on getting started with MDB2
Sarah HL

Building semantic Web CRUD operations using PHP - 0 views

www.ibm.com/...os-php-crud

php programming crud api tutorial lang:en opensource

shared by Sarah HL on 01 Dec 08 - Cached
  • When developing a Web application, it's standard practice to create a database structure on which server-side code is placed for the logic and UI layers. To connect to the database, the server-side code needs to do some basic creating, updating, deleting, and — most importantly — reading of records.
    • Sarah HL
      Sarah HL on 01 Dec 08
       
      Interet du CRUD
  • SPARQL — Simple Protocol and RDF Query Language
    • Sarah HL
      Sarah HL on 01 Dec 08
       
      PHP works with SPARQK to implement CRUD
  • Why move from SQL to SPARQL? There are many reasons why you would want to move from SQL to SPARQL. The details extend beyond the scope of this article, but you could be motivated by the following points: You want a more distributed data solution. You want to expose your data on the Web for people to use and link to. You may find Node-Arc-Node relationships (triple) easier to understand than relational database models. You may want to understand your data in a pure object-oriented fashion to work with an OOP paradigm (PHP V5 and later supports OOP). You want to build generic agents that can connect to data sources on the Web.
    • Sarah HL
      Sarah HL on 01 Dec 08
       
      Interest of SPARQL
  • Sarah HL on 01 Dec 08
     
    "When developing a Web application, it's standard practice to create a database structure on which server-side code is placed for the logic and UI layers. To connect to the database, the server-side code needs to do some basic creating, updating, deleting
Sarah HL

Learning JavaScript from PHP - a Comparison | Lullabot - 0 views

www.lullabot.com/...ning-javascript-php-comparison

javascript php programming

shared by Sarah HL on 02 Sep 09 - Cached
  • In PHP, all variables are local in scope unless declared as global. JavaScript is opposite, and all variables are global unless declared with the var keyword.
  • Both PHP and JavaScript are loosely typed
  • JavaScript is a bit mixed concerning undeclared variables, if you attempt to modify or compare with an undeclared variable, the script will break entirely, but you can check the variable status using typeof() or in conditional statements containing only that variable.
  • ...6 more annotations...
  • JavaScript only recognizes the keyword true in all lowercase. PHP accepts both uppercase and lowercase
  • PHP is not case-sensitive in function or class declarations, but JavaScript is case sensitive for these also.
  • The key difference between PHP and JavaScript is that JavaScript does not have associative arrays.
  • JSON strings having become very popular as a faster alternative to XML, and can be read and created with the PHP functions json_encode() and json_decode().
  • Let's take one more look at defining an object in JavaScript and see how it can be used to compensate for the lack of associative arrays in JavaScript.
  • // Note that variables should always be// prefixed with "var" to define a local scope.for (var n = 0; n < 10; n++) {  alert(n);}
1 - 20 of 22 Next ›
Showing 20▼ items per page