This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
start [2019/09/02 13:21]
start [2020/06/27 12:22] (current)
Line 3: Line 3:
 {{:phsphor.png?nolink&355x104}} {{:phsphor.png?nolink&355x104}}
-Main website: [[|]] Bug tracker: [[|]]+Main website: [[|]] Bug tracker: [[|]]
-Current used library versions: PHP: (5.6, deprecated), 7.1, 7.2, 7.3 (7.4 under development); Bootstrap: 4.3; JQuery: 3.4.1+Current version 1.0 RC 2\\ 
 +Currently supporting: PHP: (5.6, deprecated), 7.1 .. 7.4; Bootstrap: 4.4; JQuery: 3.4.1
-==== Introduction ====+**Important news:**
-PHsPeed is a component based, RAD PHP (7.x) development tool based upon Bootstrap 4 (PHP 5.6 and BS 3 are still available but deprecated) , PDO (database independent) and JQuery/AjaxWith PHsPeed you can build robust, responsive web applications within a very short timeframe. Based upon a database table, you can generate a full working Crud or Grid application in seconds that can be used as a basis for further development. PHsPeed is also great for prototyping, contains debugging facilities (based upon XDebug (PHP) and Chromium (JavaScript), and generates cleanreadable object-oriented PHP code.+**We have entered the RC status which means that we are now getting ready to release the productWe will now focus on our documentationvideo's etc**
-| \\  {{:agile:plan-min.png?nolink&200x112  }}Before you start, you must have thoughts about what you want to build. A few common ways are using 'stepwise refinement' or 'modular approach.' Using 'stepwise refinement' you would start with building your menu with all you know now, create very basic applications and then start refining. On each cycle, you deliver a more detailed function for your users to test. \\ In an agile way, you might want to start to break down your functionality what needs to be done. Depending on your time frame you might decide to plan your design and follow the 'sprint' approach of realizing functions. Either way, PHsPeed is very well suited for situations like this. Within your next phases, you can maintain to-do lists of all the tasks that might not be forgotten. \\  \\ {{  :agile:sc_todo-min.png?nolink&400x259  }}| 
-|{{:agile:design-min.png?nolink&200x112  }}If you create a GUI application then designing your form is one of the first steps in creating your application. Usually, you will need a database containing your tables and fields. To maintain your database, PHsPeed has PHPMyAdmin for MySQL/MariaDB and Adminer as a general database management tool integrated (if you are using the embedded Xampp package). Next, you can generate a fully working PHP application, including a form design by using the embedded application generator in a few minutes. Another approach is designing the form yourself by using the forms designer. A bit slower, but you are in full control. A third option is to combine both steps. In general, the first step is used for fast prototyping, the second to make the application more smooth and functional. \\   \\ It is important that during your design phase you design your database well. PHsPeed can generate forms and (crud) applications on the fly, but making changes can be very time consuming if you have already made a lot of modifications in the predefined modules. \\ {{  :agile:sc_xampp-min.png?nolink&270x217  }}| 
-|{{:agile:develop-min.png?nolink&200x112  }}Based upon your form, you can add PHP and JavaScript code to events. PHsPeed contains different syntax-aware code editors. Within the PHP editor, you can verify your PHP syntax to avoid errors during runtime. There are several ways to enter the code editors. To add an event you need to click on the component of which you want to apply the code to, select the server event tab for PHP events, click on the event and the … box and the editor will open with the generated function. All events will appear in the same code file. So if you need to change the code and you know that the function already exists, then you can use function key F12 to go directly to your PHP code. Applying a JavaScript event is similar, just select the Client Events tab. Some events are **automatically **applied if needed. So a form component will automatically apply the onDocumentReady event as it contains necessary code to make your form work. \\   \\ {{  :agile:sc_event-min.png?nolink&767x240  }}| 
-| \\  {{:agile:test-min.png?nolink&200x112  }}Once you have generated your applications, you will need to test. Within web applications, there are a lot of components that can generate errors. You could have PHP issues, javascript issues, and CSS issues. Within PHsPeed you have a lot of utilities that help you trace and fix issues. First of all, PHsPeed has an XDebug client built-in. You're able to create breakpoints in your PHP code, step through the code to see it's flow, request detail information about variables objects, etc. Secondly, PHsPeed has Chromium debugger build in. You get, the same functionality as hitting F12 in your browser. Investigate javascript, CSS and trace your JavaScript code. It is also possible to have PHsPeed insert 'enter and leave' code on procedures to see the full flow. You can trace the communication between your application and the web server, parameters that are sent in a post/get structure, and even JSON objects as well. \\  \\ {{  :agile:sc_debug-min.png?nolink&766x344  }}  | 
-| \\  {{:agile:review-min.png?nolink&200x112  }}Within PHspeed you deploy your application including libraries to a full working Xampp environment (or your own configured web server). Your users can look at this to review your application. You can create a full Development/Test/Acceptance and Production environment and use one of the deploy options to set your application in your desired environment. The internal logging facilities will create log files for you to see if the application performs well as expected. \\  \\ {{:agile:sc_review-min.png?nolink&819x273}}  | 
-| \\  {{:agile:release-min.png?nolink&200x112  }}If your development process is done you want to deploy your application in your production environment. Before you do that you must 'promote' your code for production. This process will remove all debugging code, comments, and database/email properties from your application. Within the released project you have access to a configuration utility to set up the required database connection and email server. All preferences are saved in a encrypted form for enhanced security. \\  \\ {{  :agile:sc_deploy-min.png?nolink&305x246  }}  | 
-|[[:createlayout|Layout your forms with bootstrap]]| 
 |[[:theide|The IDE]]| |[[:theide|The IDE]]|
 |[[:magicapp|The magic around $app, $$ and components]]| |[[:magicapp|The magic around $app, $$ and components]]|
  • start.1567423273.txt.gz
  • Last modified: 2020/02/04 18:28
  • (external edit)