extern/egroupware
1
0
Fork 1
mirror of https://github.com/EGroupware/egroupware.git synced 2024-10-06 18:22:49 +02:00
Code Issues Packages Projects Releases Wiki Activity
5f3f3b3e55
egroupware/phpgwapi/inc/class.iface_stream_wrapper.inc.php

18 lines
402 B
PHP
Raw Normal View History

NOT FOR 1.4: a very first step to the new vfs structure, it only does a ls via commandline of the old vfs
2007-05-29 10:35:27 +02:00
<?php
/**
moving VFS API classes into a namespaced PSR4 autoloadable structure: - PSR4 autoloader exists beside our old autloader to support old as well as new structure until everything is ported over - moved ported API stuff from phpgwapi to new api directory (idea is phpgwapi become a compatibility layer for old code, while we only port selected stuff to new api directory) - namespaces use prefix "EGroupware", then (first letter capitalised) app-name or "Api", sub-system names like "Vfs" or for apps "Ui", "Bo, "So" and at least class name starting with a capital letter and without understores eg. "StreamWrapper" plus just ".php" - examples: + egw_vfs in phpgwapi/inc/class.egw_vfs.inc.php --> EGroupware\Api\Vfs in api/src/Vfs.php + sqlfs_stream_wrapper in phpgwapi/inc/class.sqlfs_stream_wrapper.inc.php --> EGroupware\Api\Vfs\Sqlfs\StreamWrapper in api/src/Vfs/Sqlfs/StreamWrapper.php + sqlfs_utils in phpgwapi/inc/class.sqlfs_utils.inc.php --> EGroupware\Api\Vfs\Sqlfs\Utils in api/src/Vfs/Sqlfs/Utils.php - api directory is no a new svn module but exists (like home) as sub-directory under base egroupware module
2015-01-26 10:15:07 +01:00
* EGroupware API: VFS - stream wrapper interface
NOT FOR 1.4: a very first step to the new vfs structure, it only does a ls via commandline of the old vfs
2007-05-29 10:35:27 +02:00
*
* @link http://www.egroupware.org
* @license http://opensource.org/licenses/gpl-license.php GPL - GNU General Public License
* @package api
* @subpackage vfs
* @version $Id$
*/
moving VFS API classes into a namespaced PSR4 autoloadable structure: - PSR4 autoloader exists beside our old autloader to support old as well as new structure until everything is ported over - moved ported API stuff from phpgwapi to new api directory (idea is phpgwapi become a compatibility layer for old code, while we only port selected stuff to new api directory) - namespaces use prefix "EGroupware", then (first letter capitalised) app-name or "Api", sub-system names like "Vfs" or for apps "Ui", "Bo, "So" and at least class name starting with a capital letter and without understores eg. "StreamWrapper" plus just ".php" - examples: + egw_vfs in phpgwapi/inc/class.egw_vfs.inc.php --> EGroupware\Api\Vfs in api/src/Vfs.php + sqlfs_stream_wrapper in phpgwapi/inc/class.sqlfs_stream_wrapper.inc.php --> EGroupware\Api\Vfs\Sqlfs\StreamWrapper in api/src/Vfs/Sqlfs/StreamWrapper.php + sqlfs_utils in phpgwapi/inc/class.sqlfs_utils.inc.php --> EGroupware\Api\Vfs\Sqlfs\Utils in api/src/Vfs/Sqlfs/Utils.php - api directory is no a new svn module but exists (like home) as sub-directory under base egroupware module
2015-01-26 10:15:07 +01:00
use EGroupware\Api\Vfs;
NOT FOR 1.4: a very first step to the new vfs structure, it only does a ls via commandline of the old vfs
2007-05-29 10:35:27 +02:00
/**
moving VFS API classes into a namespaced PSR4 autoloadable structure: - PSR4 autoloader exists beside our old autloader to support old as well as new structure until everything is ported over - moved ported API stuff from phpgwapi to new api directory (idea is phpgwapi become a compatibility layer for old code, while we only port selected stuff to new api directory) - namespaces use prefix "EGroupware", then (first letter capitalised) app-name or "Api", sub-system names like "Vfs" or for apps "Ui", "Bo, "So" and at least class name starting with a capital letter and without understores eg. "StreamWrapper" plus just ".php" - examples: + egw_vfs in phpgwapi/inc/class.egw_vfs.inc.php --> EGroupware\Api\Vfs in api/src/Vfs.php + sqlfs_stream_wrapper in phpgwapi/inc/class.sqlfs_stream_wrapper.inc.php --> EGroupware\Api\Vfs\Sqlfs\StreamWrapper in api/src/Vfs/Sqlfs/StreamWrapper.php + sqlfs_utils in phpgwapi/inc/class.sqlfs_utils.inc.php --> EGroupware\Api\Vfs\Sqlfs\Utils in api/src/Vfs/Sqlfs/Utils.php - api directory is no a new svn module but exists (like home) as sub-directory under base egroupware module
2015-01-26 10:15:07 +01:00
* @deprecated use EGroupware\Api\Vfs\StreamWrapperIface
NOT FOR 1.4: a very first step to the new vfs structure, it only does a ls via commandline of the old vfs
2007-05-29 10:35:27 +02:00
*/
moving VFS API classes into a namespaced PSR4 autoloadable structure: - PSR4 autoloader exists beside our old autloader to support old as well as new structure until everything is ported over - moved ported API stuff from phpgwapi to new api directory (idea is phpgwapi become a compatibility layer for old code, while we only port selected stuff to new api directory) - namespaces use prefix "EGroupware", then (first letter capitalised) app-name or "Api", sub-system names like "Vfs" or for apps "Ui", "Bo, "So" and at least class name starting with a capital letter and without understores eg. "StreamWrapper" plus just ".php" - examples: + egw_vfs in phpgwapi/inc/class.egw_vfs.inc.php --> EGroupware\Api\Vfs in api/src/Vfs.php + sqlfs_stream_wrapper in phpgwapi/inc/class.sqlfs_stream_wrapper.inc.php --> EGroupware\Api\Vfs\Sqlfs\StreamWrapper in api/src/Vfs/Sqlfs/StreamWrapper.php + sqlfs_utils in phpgwapi/inc/class.sqlfs_utils.inc.php --> EGroupware\Api\Vfs\Sqlfs\Utils in api/src/Vfs/Sqlfs/Utils.php - api directory is no a new svn module but exists (like home) as sub-directory under base egroupware module
2015-01-26 10:15:07 +01:00
interface iface_stream_wrapper extends Vfs\StreamWrapperIface {}
Reference in New Issue Copy Permalink