Developer tools

Introduction

There seems to be no unified library to simplify integrating with webserver softwares and their configuration files like .htaccess (Apache) web.config (IIS) etc. Which makes it almost impossible for Drupal developers to fully integrate with all the powerful features these webservers have to offer without having to be worried about differences, manually editing files, conflict with changes made by other modules and a safe way to keep these settings up-to-date with latest modules’ changes.

These module is an attempt to address all these issues and finally making proper integration with webservers possible.

Version 1

In first version there will be no unified syntax since it’s not an easy thing to implement and requires good understanding of difference between popular web servers. However it will come with some very useful features:

• Module hook to introduce supported webservers , require webserver configs and define some indicators so webserver integration can check whether their changes is applied or not
• Module hook to alter webservice configuration file in text format (For example using regular expression). The running webservice will be send in as a parameter
• Hook for defining new configuration files in different locations (by default root and sites are already defined)

Configuration inspector uses the core built-in configuration system as well as schema system to let you inspect configuration values and the use of schemas on top of them. This makes it possible to have a developer focused overview of all your configuration values and do various testing and verification tasks on your configuration schemas. The module also checks whether your configuration is valid and allows you to inspect which plugins are used to validate it.

The module provides a menu item under: Reports > Configuration inspector that lets you inspect configuration, comparing raw configuration data with schemas; looking at configuration through the schema in a table of summary, in a tree view or in a form.

• Read more about the Drupal configuration system at http://drupal.org/node/1667894
• Documentation of the schema system can be found at http://drupal.org/node/1905070
• Tips on how to use this module to find schema issues at http://drupal.org/node/1910624#comment-7088154
• Gábor Hojtsy published a config schema cheat sheet at https://www.hojtsy.hu/blog/2021-dec-22/major-drupal-configuration-schema...
• Wim Leers demonstrated how to use the Drush commands provided by this module to add validation to configuration: https://wimleers.com/talk/config-validation-lille

This module also powers Drupal core's Config validatability CI job!

This is not a Drupal module but an exported set of language-aware code templates to enhance Drupal development with the NetBeans IDE versions 7.0 a

Activable

Declarative UI components | 2K, 0 dependency, IE8 compatible
Activable helps you build modern UI components quicker and keep your code clean. Here is all the code needed to create a tab component:

<script src="activable.js"></script>
<ul data-activable>
  <li class="active"><a href="#t1">Tab1</a></li>
  <li class=""><a href="#t2">Tab2</a></li>
  <li class=""><a href="#t3">Tab3</a></li>
</ul>
<div>
  <div id="t1" class="active">Raw denim you probably haven't heard of.</div>
  <div id="t2">Mustache cliche tempor, williamsburg carles.</div>
  <div id="t3">Cosby sweater eu banh mi, qui irure terry.</div>
</div>

Since Activable uses a global event listeners, once the components are appropriately styled with CSS they are fully functional: no need to initialize them with JS, ever.

Demo

Activable can be used to create common click-based UI components, as illustrated in the demo.

Documentation

The declarative markup used to create activable components and the JS API used to extend them have a zero to hero documentation.

License
MIT licensed, by @louis_remi.

What does it do:

This module uses the target databases to set a number of 'extra' databases in which the users can connect at login.

A framework to allow integration of web forms to industry standard CRM systems. The first CRM plugin will be Microsoft CRM.