Code refactoring:

Moved runtime customization into the separate script. This script shall contain 'core' variables
defining the YAVIDE environment.
Code refactoring:

Moved editor specific settings into the separate file
Code refactoring:

Moved user-configurable settings into the separate file.
Code refactoring:

Moved plugin(s) specific configuration into the separate file. Now one may define plugin
configuration per file. This should be easier to maintain and provides more modularity.
Major system architecture redesign / Feature implementation

Simplified and modularized system architecture by introducing separate modules with well defined responsibilities:
    '.vimrc'
        Main module being executed as the first one upon Yavide start-up.
        Serves as a central module defining system execution path. Calls all other modules.

    '.core.vimrc'
        Module containing system-wide core parameters such as definition of a runtime execution path.
        This is also a good place to define filesystem-separators and stuff alike which would ease
        porting process to another platform.

    '.user_settings.vimrc'
        Module exposing all user-configurable settings such as editor settings, system-dependant paths,
        source code parser settings, etc. Plugin-specific configuration shall not be put here. Look at
        '.plugins.vimrc' description to see how to handle plugin configuration.

    '.editor.vimrc'
        Module defining editor settings such as indentation, line numbers, fonts, colorschemes and alike.
        One should not modify the settings directly in this module but instead one should use '.user_settings.vimrc'
        to customize the behavior.

    '.plugins.vimrc'
        This module is in favor of running all plugin-specific configuration scripts. One may define one
        configuration script per plugin if needed. This mechanism gives us more granularity and flexibility in
        plugin management. In future, it shall be possible to retain specific plugins from running on user request.
        To be compatible, plugin configuration scripts filename need to follow '*.plugin' pattern.
        For simplicity, there is currently only one script ('common.plugin') defining configuration
        for all of the plugins present in the system.

    '.api.vimrc'
        Module defining an API to be used throughout the system. This is a central point for providing implementation
        details which define specific Yavide behavior.
        It currently consists of following APIs:
            'Project Management'
            'Session Management'
            'Buffer Management'
            'Text Management'
            'Search Utilities'
            'Layout Management'
            'Source Code Navigation'
            'Source Code Parser'
            'Static Analysis'
            'Build System'

    '.autocommands.vimrc'
        Module which provides a powerfull interface (via Vim 'autocommand') which enables customization of Yavide behavior
        in specific aspects. It utilizes hook mechanism to enable the automation of specific scenarios. For example,
        automation of source code parser is defined via these hooks.

    '.commands.vimrc'
        Module which basically defines a public interface towards the API from '.api.vimrc'.
        It consists of a list of commands which can be run by the user. Usually, most of these commands are mapped to
        keyboard shortcuts to ease the usage of it.

    '.keyboard.vimrc'
        Module which does the mapping of keyboard shortcuts to commands defined in '.commands.vimrc'.