X-Git-Url: https://codewiz.org/gitweb?a=blobdiff_plain;f=README.devlib;h=bff80749173a59344fc9e0b4a97ab8ea3dda3d0c;hb=49d4f9b278ec7da35bbf2dcd3f5013940d1a74e3;hp=11e207bf4aace502c7453d59eb6d98b2dcb7d312;hpb=201ffee317b51ececed2ee6cc140eda6ce69f5e0;p=bertos.git

diff --git a/README.devlib b/README.devlib
old mode 100755
new mode 100644
index 11e207bf..bff80749
--- a/README.devlib
+++ b/README.devlib
@@ -38,17 +38,21 @@ you can configure out features you don't need.
 
 The modules are sorted in subdirectories by their category:
 
+ - cfg/ - Configuration and portability headers;
  - kern/ - Simple multitasking kernel implementation;
  - drv/ - Hardware drivers;
+ - dt/ - Object oriented framework for simple GUIs.
+ - gfx/ - Simple bitmap graphics functions;
  - mware/ - Algorithms, containers and other standalone code;
  - io/ - Infrastructure of I/O-related modules for hosted applications;
  - os/ - OS-abstraction layers for hosted environments;
+ - qtext/ - Qt extension classes;
 
-The top-level directory contains a few support headers that are meant
-to be usable by any C or C++, embedded or hosted application.  The
-top-level directory also contains a few example templates for files
+The cfg directory contains a few support headers that are meant
+to be usable by any C or C++, embedded or hosted application.
+The top-level directory contains a few example templates for files
 that are meant to be customized on a per-application basis.  These
-files are hw.h, config.h, verstag.h and arch_config.h.
+files are hw.h, appconfig.h, verstag.h and arch_config.h.
 
 To achieve the highest possible reusability, most DevLib components
 are designed for fine-grained modularity and minimal external