JDev Tools

From Joomla! Documentation


JdevTools aims to help developers create components. A lot of tasks during extension development are very repetitive tasks such as setting up files, creating database tables and writing classes for the mcv structure. With JDevTools, it will be easy to automate this process, either by creating simple scripts taking care of the process, or by using scripts that are already made. JDevTools will include tools for:

  1. Setting up files
  2. Create mcv boilerplate code
  3. Setting up tables and registering the component in the database
  4. Creating common functions for getting and displaying data
  5. Creating Admin tables and forms
  6. Creating pagination
  7. Creating language files
  8. Package extensions

This is the project for developers and tools for developers. And developers enjoy creating their own tools for themselves. The main goal of such project is to create a platform (or environment, call it as you want) for rapid development of J! stuff (components, modules, plug-ins).

The idea is not to create as many features as we can during the summer, but create a “framework” which can be flexible and extendible. The second idea is to show developers some “Kung Fu” style of creating extensions. This will be done by our packages with best practices of J! development (i.e. component, module/plug-in scripts).

How will it work

The purpose of JDevTools is to create an environment where developers easily can execute scripts, make their own scripts and use other peoples scripts. There will continuesly be new scripts added, but anyone should with ease be able to write their own.

The base of JDevTools will be an application (like the joomla installer) which will take the user through 4 steps in order to create the component:

  • Select script, or create new script: Here the user will se a list of scritps, which is in fact php files collected in the script directory of JDevTools
  • Verify and run script: Here a short warning about trusting the provider of the script will appear. The script will be shown in a text-field where the user can check it's ok and modifying it if they want to. A button will be placed, executing the script. The reason for providing this step is to make users aware that creating scripts or changing scripts is a pretty easy affair
  • [optional] Script input: If the script requires user input, it will be shown in a form on this page, where the user can fill out details and press ok
  • Page showing any errors in the script execution or saying that the script executed without problems

This will enable a developer to create the base for a component by clicking a couple of times, providing some input and click run. It's important to notice that this will not create a working component on it's own. It just creates an easily extendable base for developing a component.