Be the first to post a text review of IBT PHP Library and Framework (IPL). Rate and review a project by clicking thumbs up or thumbs down in the right column.

• File released: /IPL/0.9.3 Alpha 6/0-9-3-a6.zip

  posted 1529 days ago

• IPL 0.9.3 Alpha 6 file released: 0-9-3-a6.zip

  posted 1529 days ago

• File released: /IPL/0.9.3 Alpha 5/0-9-3-a5.zip

  posted 1545 days ago

• IBT PHP Library and Framework v0.9.3-a4

  IBT PHP Library and Framework provides you with a shell of high-level PHP functionality that structures your PHP content and logic. IPL is 100% XHTML compatible, implements the Smarty templating system, a plug in system, and a new display architecture. The latest release, 0.9.3-a4, implements a mass of new features including a new graphing class, c-in-line-compiler class, JPSpan and Smarty plug ins, templating system, display architecture, structured config preparation, dot-syntax system, web query system, direct script access blocking, basic plug in system, temporary global variable container, gateway init action, and global root variable. Displays are a new feature in the 0.9.3 alpha releases that allow custom modules and code and content call orders to be defined. This allows the programmer to decide whether they would like to implement parts of IPL's framework or not, thus providing complete structural flexibility. The Smarty package is now being used in the IPL as a plug in so that the IPL displays can utilize Smarty templates as opposed to the original shell design that the IPL once provided. This allows utilization of more widely available knowledge of a system that is fully documented and stable. In this latest alpha, work has begun on modularizing all of the configuration files. So far, the variables from the configuration files have been communed in a single global variable file that is called from the main configuration script. XML scripts have been written and commented out in the old PHP config files in preparation for actual XML files that will take over as soon as the XML handler is implemented in 0.9.4. A dot-syntax system now manages act, cls, and plg instantiation methods. All necessary pieces of the IPL can now be included with dot-syntax style calls. This feature is very similar to the way that class inclusion calls for classes and packages are done in Java-based languages. IPL's dot-syntax system does not yet support wild cards. WebQuery is another feature that is being implemented in the IPL. This feature allows basic queries to the IPL Framework from the client-side browser to collect server and IPL information. This feature can be disabled in configuration. Access blocking has been placed on potentially vulnerable scripts so that hackers can no longer access pages directly without first running path through the IPL. This secures against some DOS attacks and database access attacks. A new, basic, plug in system and two plug ins have been implemented. This system was basically thrown together to provide port for plug ins that are more important to the future of the IPL Framework. To make the plug in system work, a global path variable and gateway init script/display were created. The gateway init performs IPL Framework activation but does not require a visual shell. The first of the two plug ins implemented into this system is the Smarty template engine, and the second is JPSpan. JPSpan is a package that allows for dynamic client/server calls on the HTTP protocol without the need for a complete page refresh. This plug in comes in handy when full page refreshes become counter-productive, such as the case of dynamically populating drop-down boxes. All of these features have been implemented and activated in the current release, 0.9.3-a4, of the IPL Framework. IPL continues to suffer in the documentation arena, but documentation is the next step, so it shouldn't be too long now. The currently available documentation for 0.9.2 is extremely outdated seeing that the structure of the framework has changed almost completely, and the myriad of new features has far outweighed 0.9.2. Beta docs will be available with the first beta release of the IPL after testing has completed. Please go ahead and dive into the code. The IPL Framework is now open to outside developers, comments, code fixes, suggestions, and new classes or feature code. The rough development schedule is posted below. Aaron Belovsky Lead Developer and Project Coordinator |---------------------------------------------------| Development Schedule 0.9.3 to Version 1 >> (completed features) >-> (uncompleted features) <-- v0.9.3 --> >> integrate ykcee >> further modularize library >> organize classes in directory structure >> create dot-syntax for class dial ups >> make class library portable >> allow a default-import set of classes in config >> update configuration file design >> modularize >> separate from classes >> prepare for XML integration >> remove current work flow engine to prep for new engine >> re-work display system >> modularize display script as a system action >> better modularize init class >> de-class init >> turn into an action >> create dot-syntax and call function for actions >> create WebQuery act >> add config options to turn WebQuery on and off >> change global class to system.dotsyntax action >> create individual pag file access blocker >> create plug in capability >> create new dot syntax function ipl_use() >> include smarty template engine as a plug in >> convert shl.php files to smarty template files >> header class bug fixes >> implement inline c code through php scripts as class >> integrate jpspan as a plugin >> migrate global path variables to main config file >> create new gateway init act in act.system directory >> create new global root variable >-> re-write documentation >-> write install documentation >-> write development standards >-> write developer documentation >-> modify license to provide more freedom of use >-> redo website with new version of library >-> publish all <------------> <-- v0.9.4 --> >-> connect to PHP documentor >-> create xml handler class >-> change config file to xml format >-> setup to use new XML configuration files >-> create new error handler >-> research and develop a python through php calls implementation >-> integrate zope access >-> file access >-> work flow access >-> fix queried ssl to working condition >-> create new workflow engine if zope didn't take care of it >-> implement java outlet class for plugging applets into the system >-> implement java container class for making direct java calls >-> implement python outlet class for plugging python apps into the system >-> implement python container class for making direct python calls >-> update documentation >-> update developer documentation >-> update website with new version of library >-> publish <------------> <-- v0.9.5 --> >-> System PHP version detection for compatibility scripting >-> update built-in workflow and add xml configs >-> create library administrative interface (integrated with zope management accounts) >-> create library query interface to run queries on system information >-> create basic administrative workflow management interface >-> create basic administrative access link to zope interface >-> split documentation into technical and administrative >-> update technical documentation >-> write administrative documentation (library interface instructions) >-> update developer documentation >-> update website with new version of library >-> publish <------------> <-- v0.9.6 --> >-> update action (act) implementation >-> add rss class implementing the xml class to handle simple sindication functions >-> research and implement basic ColdFusion support (sessions/cookies) >-> research and implement basic Ruby support >-> research and implement basic TCL support >-> update technical documentation >-> update developer documentation >-> update website with new version of library >-> publish <------------> <-- v1.0.0 --> >-> write or locate useful Ruby server-side operation classes >-> create classes implementing the java outlet to allow use of the java classes >-> update technical documentation >-> update developer documentation >-> update website with new version of library >-> renovate website making certain all data is current >-> publish <------------> <-- Research/Dev Post Version 1 --> >-> Apache Server Modules (Moto Programming Language) <------------------------> |---------------------------------------------------|

  posted by ambelovsky 1545 days ago

• IPL 0.9.3 Alpha 5 file released: 0-9-3-a5.zip

  This is a bug-fix release which makes the global path variable completely dynamic.

  posted 1545 days ago

• File released: /IPL/0.9.3 Alpha 4/0-9-3-a4.zip

  posted 1552 days ago

• File released: /IPL/0.9.3 Alpha 3/0-9-3-a3.zip

  posted 1552 days ago

• IPL 0.9.3 Alpha 4 file released: 0-9-3-a4.zip

  <-- v0.9.3 --> >> integrate ykcee >> further modularize library >> organize classes in directory structure >> create dot-syntax for class dialups >> make class library portable >> allow a default-import set of classes in config >> update configuration file design >> modularize >> separate from classes >> prepare for XML integration >> remove current workflow engine to prep for new engine >> re-work display system >> modularize display script as a system action >> better modularize init class >> de-class init >> turn into an action >> create dot-syntax and call function for actions >> create webquery action >> add config options to turn webquery on and off >> change global class to system.dotsyntax action >> create individual pag file access blocker >> create plugin capability >> create new dotsyntax function ipl_use() >> include smarty template engine as a plugin >> convert shl.php files to smarty template files >> header class bug fixes >> implement inline c code through php scripts as class >> integrate jpspan as a plugin >> migrate global path variables to main config file >> create new gateway init act in act.system directory >> create new global root variable !!-- the following are not yet complete --!! >-> re-write documentation >-> write install documentation >-> write development standards >-> write developer documentation >-> modify license to provide more freedom of use >-> redo website with new version of library >-> publish all !!-- --!! <------------>

  posted 1552 days ago

• IPL 0.9.3 Alpha 3 file released: 0-9-3-a3.zip

  posted 1552 days ago

• Functional Alpha

  Hi folks, I have just released 0.9.3 Alpha 2 which is basically another progress report. However, unlike the first alpha release, this one is functional. The last alpha was more of a structural representation of my current direction with the library. Even though this alpha is functional, the library is still waiting for the instantiation global function to be created, so it is not yet ready for production use. There are also many other things that I would like to accomplish before the final 0.9.3 release, so the instantiation function will most likely be released with the beta assuming I don't run another alpha. Basically, for 0.9.3 Alpha 2, there are a lot more structural changes and modularization. There were a few new features added as you will see from the change log at the end of this article, and the entire Alpha was tested to a functional state, so feel free to experiment. Changes: In this release, the following things were implemented: &lt;-- Change Log --&gt; &gt;&gt; created a display system so that there is much more modular separation between the core parts of the site such as the index default loader page and the process in which content is loaded up. &gt;&gt; modularized the display script as multiple system actions (act) including one main action (act) and multiple operational module actions (act). &gt;&gt; better modularized the init class &gt;&gt; de-classed init &gt;&gt; turned init into an action (act) &gt;&gt; created dot-syntax access for actions (act). &gt;&gt; created a system query action (act) script &gt;&gt; created a globalize action (act) script that will be modularized into a class in the next release. &lt;-- End Change Log --&gt; -Aaron

  posted by ambelovsky 1646 days ago