1. <label id="w2g2v"><ruby id="w2g2v"></ruby></label>

        <output id="w2g2v"></output>
        <blockquote id="w2g2v"><ruby id="w2g2v"></ruby></blockquote>
        Previously on the blog
        RSS feed
        1. Using POG with Flex
        2. Optimizing your web application
        3. Regenerating large objects
        4. PHP4 or PHP5
        5. New and Improved
        6. Evolution of a cube
        7. POG Museum
        8. POG 3.0 alpha
        9. Initial Performance results Part 2
        10. Initial performance results
        11. Proposal: POG 3.0 object model
        12. Suggest a feature
        13. A new year, A new POG release
        14. Many-Many relations
        15. POG 2.5 Released
        16. POG 2.5 beta
        17. Automatic table alignment
        18. New version: 2.1.2 released
        19. RSS should work well now
        20. RSS feed glitches
        21. What's new in 2.1.0
        22. PHP Objects 2.1.0 (preview)
        23. PHP Object relations FAQ
        24. PHP Object Relations
        25. Searching base64 encoded text
        26. How to debug POG-generated objects
        27. POG UI Tips
        28. Featuring Of Interest links
        29. PHP CRUD
        30. POG 2.0.1: A better code generator
        31. A look at the POG SOAP API
        32. POG 2.0.0 released
        33. Coming soon: Generate parent-child objects
        34. Generated abstraction v/s dynamic abstraction
        35. Zend Framework preview
        36. Coming soon: Generate Objects through SOAP
        37. Easily save images and files to a database
        38. PHP, Paypal & POG
        39. Five advanced Code Generator tips
        40. PHP Pagination using generated objects
        41. PHP Code Generator benchmarks
        42. Representing database objects using an AJAX Tree interface
        43. Using SETUP in a production environment
        44. Description of the generated object package
        45. Introducing PHP Object Generator version 1.6
        46. Using AJAX and PHP Object Generator
        47. When to use Object->SaveNew()
        48. Generating PHP objects in 2006
        49. Happy Holidays
        50. A short video of the POG Setup process
        51. A sneak peek at POG 1.6
        52. POG Tip: Field limits
        53. Previous versions.
        54. Searching the blog and tutorials sections
        55. Generating code with "Other" SQL data types
        56. Five general POG tips
        57. POG source code locations
        58. Microsoft SQL 2005 Express Edition
        59. Impatiently awaiting PHP 5.1 and PDO
        60. Php Object Generator goes open source
        61. POG generates PDO compatible code
        62. Oracle to offer free database
        63. POG Google group
        64. Database Wrappers and POG
        65. Revisions
        66. The generator blog
        67. An explanation of the 'Escape' function.
        68. Mirror, mirror
        69. Using POG to solve real world problems
        70. A php object-relational database tool
        71. A simple and flexible Object Oriented approach to PHP


        Want more Php Object Generator?
        Back to the Code Generator
        The POG Google group
        The POG tutorials/code samples
        The POG mirror site




        Representing database objects using an AJAX Tree interface

        written 4825 days ago

        If you’ve used POG setup, you’re probably aware by now that we’ve decided to adopt an AJAX Tree to represent the database interface in the setup app. This approach is closer to a debugging interface than the database interface we tested during 1.6 beta. (using a table structure with rows and columns).

        There main reason that pushed us towards this decision is that the row/column interface that we were experimenting with during BETA did not scale well enough with objects containing a large number of attributes (>10). Those of you who helped us beta test version 1.6 during January are probably aware that if your objects had many attributes, you had to use the horizontal scroll bar to see all the attributes. Horrible!

        The new tree interface (see screenshot below) scales better and is closer to a real “object” representation in debugging interfaces used in IDEs such as Zend Studio.

        Tree view interface to PHP Objects

        To dynamically generate this Tree View, we use xPandMenu, an open source PHP tree library offered by Patrick Brosset under the BSD license. We had to extend the xPandMenu library to accommodate for some POG-related business rules. For example, if an object in the list is deleted, all objects below it are shifted up by 1 and all node states (expanded or collapsed) are preserved. We also used AJAX to communicate with the xPandMenu library to improve the overall responsiveness of the interface. As a refresher, there’s a simple tutorial which demonstrates how to create a simple to-do list using POG and AJAX.

        All in all, creating the Tree view interface was an occasion to eat our own dog food and experience how POG actually accelerates PHP database programming. We didn’t have to write a single SQL statement and almost forgot about the database altogether. We’d like to finish this post by thanking Patrick Brosset for providing the xPandMenu library under the BSD license. It saved us many hours of coding!


          Textile Help
        About Php Object Generator
        This is a weblog about the Php Object Generator (POG) project, OO PHP, databases and Php code generators in general.

        Php Object Generator, (POG) is an open source PHP code generator which automatically generates clean & tested Object Oriented code for your PHP4/PHP5 application.

        Subscribe to our RSS feed

        Feedback, Feature Requests, Bugs to:
        The POG Google group

        Send us a Hello through email
        时时彩安徽快三遗漏
        1. <label id="w2g2v"><ruby id="w2g2v"></ruby></label>

              <output id="w2g2v"></output>
              <blockquote id="w2g2v"><ruby id="w2g2v"></ruby></blockquote>
              1. <label id="w2g2v"><ruby id="w2g2v"></ruby></label>

                    <output id="w2g2v"></output>
                    <blockquote id="w2g2v"><ruby id="w2g2v"></ruby></blockquote>