ELearn World - Learn the Tutorials online

In this article, we're going to explore one of the most important and least discussed features of the Laravel web framework—exception handling. Laravel comes with a built-in exception handler that allows you to report and render exceptions easily and in a friendly manner. In the first half of the article, we'll explore the default settings provided by the exception handler. In fact, we'll go through the default Handler class in the first place to understand how Laravel handles exceptions. In the second half of the article, we'll go ahead and see how you could create a custom exception handler that allows you to catch custom exceptions. Setting Up the Prerequisites Before we go ahead and dive into the Handler class straight away, let's have a look at a couple of important configuration parameters related to exceptions. Go ahead and open the config/app.php file. Let's have a close look at the following snippet. ... ... /* |---------------------------------

Technology is rapidly changing, and today's latest device becomes completely outdated in a flash. In such a dynamic and emerging tech environment, developers might get somewhat confused. We all want to find the best avenues to channel our learning and development efforts. Many technologists believe that the golden age of smartphones is nearing its end. A whole new batch of hi-tech wearable devices are about to replace smartphones in the near future. What would these technologies and devices look like? Wearables can range in size from watches through to smart glasses and smart rings. Every day, they are becoming smaller in size and are boosting their performance too. These devices have already started to redefine user interaction patterns, user behaviour, and sometimes even the user's lifestyle. In this article, you'll learn about the latest emerging wearable device platforms for which you could develop apps. 1.  Smartwatches Although smartwatches are the obvious next st

One of the ways to relieve strain on a server is by caching data. This is done by caching data after it has been processed and then serving it from the cache the next time it is requested. This tutorial will give a detailed discussion of Redis, explaining how to install Redis and cache data in Python applications. Introduction to Redis and Caching Caching refers to storing the server response in the client itself, so that a client need not make a server request for the same resource again and again. A server response should have information about how caching is to be done, so that a client caches the response for a time period or never caches the server response. A cache, on the other hand, is a hardware or software component that is used to store data so future requests for the same data can be served faster. In this age where users expect results within a second, it is wise to serve requests by reading data from the cache, which is ultimately faster than reading from a slower dat

In Part 2 of this series, I covered a range of different analogue and iOS options suitable for creating keyboard sounds on guitar. There’s a third way, however, that introduces the convoluted, technical world of MIDI. In The Beginning… MIDI stands for Musical Instrument Digital Interface . Introduced to the public in 1983, its basic function is to pass information such as note pitch, velocity, duration and so on from the controller —guitar, in this case—to the  sound module  such as synthesisers, samplers, and so on).  Unlike conventional audio, event messages produce no sound of themselves serving as a set of instructions to trigger the sound module. So far, nothing here to interest guitarists. However, MIDI goes beyond simply being just a trigger for notes; indeed, its ability to manipulate whole hosts of variables via anything MIDI-compatible means you aren’t just limited to keyboard sounds.  For a band or artist needing a broad palette of tones, it’s worth investigating.

Overview This is part five of a five-part series of tutorials about making games with Python 3 and PyGame. In part four we detected collisions, responded to the ball hitting various game objects, and created a game menu with custom buttons.  In this last part, we'll cover diverse topics such as the end game, managing lives and score, sound effects, music, and even a flexible special effects system. For dessert, we'll discuss potential improvements and future directions. The End Game Eventually, the game has to end. In this version of Breakout, the game ends in one of two ways: either the player loses all their lives or they hit all the bricks. There is no next level (although it would be easy to add). Game Over! The game_over field of the Game class is set to False in the __init__() method of the Game class. The main loop goes round and round until the game_over  variable is set to True: class Game: def __init__(self, caption, wi

Overview This is part four of a five-part series of tutorials about making games with Python 3 and Pygame. In part three, we dove into the heart of Breakout and learned how to handle events, met the main Breakout class, and saw how to move the different game objects. In this part, we will see how to detect collisions and what happens when the ball hits various objects like the paddle, the bricks, the walls, the ceiling, and the floor. Finally, we will review the important topic of game UI and in particular how to create a menu with our own custom buttons. Collision Detection In games, things bump into each other. Breakout is no different. Mostly it's the ball that bumps into stuff. The handle_ball_collisions() method has a nested function called intersect() , which is used to test if the ball hit an object and where it hit the object. It returns 'left', 'right', 'top', 'bottom', or None if the ball didn't hit the object. def handle_ball_co

Overview This is part three of a five-part series of tutorials about making games with Python 3 and Pygame. In part two , we covered the TextObject class used to render text on the screen, created the main window, and learned how to draw objects like bricks, the ball, and the paddle.  In this part, we will dive into the heart of Breakout and learn how to handle events, meet the main Breakout class, and see how to move the different game objects. Handling Events In Breakout, there are three types of events: key press events, mouse events, and timer events. The main loop in the Game class takes care of the key press and mouse events and delivers them to subscribers (by calling a handler function).  While the Game class is very generic and has no Breakout specific knowledge, the subscription itself and how to handle each event are very specific. The Breakout Class The Breakout class is where most of the domain knowledge about the Breakout game is managed. We will meet the Breakout