Scotch.io has posted the second part of their series today showing you how to build a simple time tracking application with Laravel and AngularJS. In this latest part of the series he finishes the application and connect the two pieces.

This is the second of a two-part series on using Laravel 5 and AngularJS together to build a simple time tracking application. If you’ve gone through part 1, you’ll have seen that we put together the front-end first and used a simple JSON file with some mocked-up data to test with. We left off with the ability to add new time entries and have the total time from all of them display on the side. We didn’t include any way to edit or delete the time entries, and of course there was no persistence to a database. In this part we will complete the application so that the time entries get stored in a database and our Angular front-end and Laravel backend work together to create, read, update and delete from it.

He starts by helping you get a Laravel application up and running (time-tracker-2), set up the database and modify the configuration to point to the database location. He helps you run the migrations to set up the database tables and generate the related model code. Next up he shows how to inject the seed data, setting up the main index view and adding in routes for the Angular code to access. The rest of the article is just about as detailed and covers steps to:

• View all the Available Routes
• Return all Time Entries
• Return All Users
• Updating the front-end
• Setting up the users list
• Creating time entries
• Updating time entries
• Deleting time entires

Finally he wraps it all up with a few possible things that could be done to improve the application, both simple and a bit more complex. He challenges you the developer to implement those features.

On the Scotch.io site there's a new tutorial showing you how to build a time tracking application with a combination of Laravel and AngularJS. This is the first part of a new series and focuses on the basic principles and getting some of the first parts of the application up and running.

Laravel and AngularJS work great together, but it can be a little tricky to get going at first, especially if you are new to the frameworks. In a previous article, Chris showed you how to make a Single Page Comment App with Laravel and Angular. This tutorial will again bring the two frameworks together as we build out a simple time tracking application.

We’ll be going into a lot of detail in this tutorial, so to make things manageable it has been broken into two parts. The first part will focus on getting the front-end setup with AngularJS and the second part on getting the backend setup with Laravel 5.

He starts with an overall look at the application and what functionality it will have. From there he walks you through:

• Setting up the folder structure
• Installing dependencies
• Creating Javascript files
• Setting up the view
• Adding extra styling
• Fetching the time data

He makes use of the Moment.js library to perform some of the time calculations for the difference and total time elapsed. He ends the post by tying up some loose ends with the controller and updating the view with the new calculated time values.

Continuing on from the first part of their tutorial series about creating a simple ad tracker for your web application, Developer Drive is back with part two, a more in-depth look at the actual object design and code.

In our last PHP Ad Tracker lesson, we constructed the database tables for our ad banner application. Now we are ready to construct the data object that will hold the variables and functions that will display, add, edit and delete the data in those tables.

They cover each of the variables they'll be using with a summary of what they're used for as well as the various functions to be defined and what they'll return. Following this, they get into the actual development - creating an "ads" class and defining the methods to get the current ad count, get the number of clients and pull the actual client/ad data.

On Developer Drive today there's a new post (the first in a series) from Gerald Hanks about building an ad tracker in PHP. In this first part he sets up some of the background - the database that will hold the tracker information.

Banner ads for services related to the web site owner’s industry allow customers to view products that tie into the site owner’s core business. In exchange, the web site owner can charge the banner ad owner for every impression (banner ad appearance) or click-through (when a user clicks the banner ad). In order to build a banner ad management system, we must first create the database tables that will hold the ad information, the client data and the activity schedule for each ad.

He includes the SQL you'll need to create a few tables - the tracking table for the ads themselves (their metadata), the clients table to handle the groups wanting the ads and the activity table to track views and click-throughs.

The Zend Developer Zone has announced the release of the latest preview of the Zend Framework - the Preview Release for 1.7.

We are excited to announce that the Zend Framework 1.7 Preview Release is now available from the Zend Framework download site! While 1.7PR is not a feature complete release in the 1.7 series, it nevertheless contains some very important features scheduled for the 1.7 production release.

Updates included in this release are things like the Zend_Amf component, an update of the Dojo toolkit, support for the dijit editor, some performance enhancements and other locale and internationalization changes.

You can download this latest release from the Zend Framework download page and be sure to log any problems you find into the issue tracker and help the ZF team make the framework even better.

According to this new post on Lukas Smith's blog today, the PHP project has started a new effort aimed at helping out developers upgrading their PHP installations - a new README file with details on each upgraded version and its install.

In order to make the transistion for users upgrading to new minor (middle number increment) and major (leading number increment) version of PHP easier, the PHP project has recently begun adding a README with upgrade information with new releases. This guide steps through any issues that users are likely to be faced when upgrading their PHP installations.

Lukas also reminds developers that testing these releases is the only real way to find the bugs that are there and catch them before the final release for that version. Bug issues can be reported to the tracker and, if you'd like to see an example of this new README file for PHP 5.2, check out this example.

According to this new post on Lukas Smith's blog today, the PHP project has started a new effort aimed at helping out developers upgrading their PHP installations - a new README file with details on each upgraded version and its install.

In order to make the transistion for users upgrading to new minor (middle number increment) and major (leading number increment) version of PHP easier, the PHP project has recently begun adding a README with upgrade information with new releases. This guide steps through any issues that users are likely to be faced when upgrading their PHP installations.

Lukas also reminds developers that testing these releases is the only real way to find the bugs that are there and catch them before the final release for that version. Bug issues can be reported to the tracker and, if you'd like to see an example of this new README file for PHP 5.2, check out this example.

Back with more from his experiences at this year's OSCON, Chris Shiflett has posted a few of the more random things he experienced while there.

One of the great things about OSCON is how it brings people together, and this year's conference was no different. I had the privilege of meeting a number of people for the first time.

People on his list include Cal Evans, Andrew van der Stock, Kevin Yank, Jeremy Johnstone, and Ed Finkler. He also mentions a "cool idea" from Zak Greant - the use of a bug/issue tracker to deal with community issues.

Chris also briefly mentions the "PHP trading card game", the PHP Security Hoedown, and the OmniIT book signing.

Back with more from his experiences at this year's OSCON, Chris Shiflett has posted a few of the more random things he experienced while there.

One of the great things about OSCON is how it brings people together, and this year's conference was no different. I had the privilege of meeting a number of people for the first time.

People on his list include Cal Evans, Andrew van der Stock, Kevin Yank, Jeremy Johnstone, and Ed Finkler. He also mentions a "cool idea" from Zak Greant - the use of a bug/issue tracker to deal with community issues.

Chris also briefly mentions the "PHP trading card game", the PHP Security Hoedown, and the OmniIT book signing.

The Zend Developer Zone has posted a new article about the latest offering when it comes to the Framework - the introduction of a bug tracker/source browser application on the Framework's site to help manage the project.

The post also includes some screenshots from the application, showcasing each of its many pages of functionality - source browser, issue tracker, timeline, and the search function.

For direct access to the site, head over to the Zend Framework site and click on the Developer tab.