Imported release files

README

@@ -0,0 +1,34 @@
+Xoops Engine code
+
+/XoopsEngine
+The root directory for Xoops Engine code
+
+/XoopsEngine/docs
+Documents
+
+/XoopsEngine/htdocs
+Web docroot
+
+/XoopsEngine/lib
+Libraries
+
+/XoopsEngine/var
+System variable data
+
+/XoopsEngine/usr
+User or community contributed components, including apps/modules, plugins, applets, themes, etc.
+
+/XoopsEngine/usr/apps
+Xoops Engine apps, i.e. applications following new MVC
+
+/XoopsEngine/user/modules
+Non MVC style modules
+
+/XoopsEngine/usr/plugins
+Plugin folders
+
+/XoopsEngine/usr/applets
+Applet folders
+
+/XoopsEngine/usr/themes
+Theme folders

XoopsEngine/docs/Changelog.txt

@@ -0,0 +1,102 @@
+Xoops Engine Changelog
+
+
+April 20th, 2011
+=============================
+1 Added namespace for app (in /usr/apps/) as "App" and module (in www/modules) as "Module"
+2 Built WYSIWYG editor factory, integrated CKEditor and jQuery based ClEditor
+3 Built security handler and resource, added XSS filter, IP protection, super globals contamination, etc.
+4 Upgraded Zend Framework to 1.11.5
+5 Block is refactored with Xoops/Zend_Form, more controllable with style, title switch, link, etc.
+6 Added block compound, suggested by ezsky/dongbeta etc.
+7 Formulated theme schema with global namespace
+8 Changed .ini file to .ini.php for content protection, suggested by huzhenghui/ezsky/dongbeta, etc.
+9 Added QA mode: only display debug information to specified IPs, suggested by huzhenghui
+
+
+January 10th, 2011
+=============================
+1 Improved and simplified captcha mechanism
+2 Improved bootstrap to allow resource loading on-fly
+3 Added encrypt/decrypt based on 'phpseclib' package
+4 Added autoloader for legacy classes
+5 Changed class \Kernel\Service\Log name to \Kernel\Service\Logger and corresponding engine loggers to avoid conflicts between method logger::log and class name (construction method)
+6 Changed /var/caches to /var/cache, /var/configs to /var/etc, /var/data to /var/log; moved /lib/applications to separate directory /usr
+
+
+November 15th, 2010
+=============================
+1 Added multi-engine support and implemented the alternative engines "Lite", "Perfect" for non-db/non-page-cache mode
+2 Added applet mechanism for non-db widget
+3 Added ini module configs for non-db mode
+4 Added namespace for module/app (scheduled)
+5 Moved application entry files into folder htdocs/Application; Changed mainfile.php to Application/Boot.php, leaving mainfile.php to legacy applications
+
+
+November 9th, 2010
+=============================
+1 Changed namespace for Xoops_Engine to allow for multiple engines
+2 Added persist for class loader
+3 Added extended/custom pluginloader to allow for persist cache
+4 Added memcache support for session save handler
+5 Upgraded Zend Framework to 1.11.0
+6 Upgraded Smarty to 3.0 Final
+7 Refactored XOOPS/Engine APIs
+8 Refactored autoloader to allow classMap, namespace, prefix, module, plugin and adding third-party library on-fly
+
+
+October 30th, 2010
+=============================
+1 Changed Smarty plugin files name to lowercase for Smarty 3
+2 Added persistent data service, providing three storages: APC, memcached, file
+
+
+October 26th, 2010
+=============================
+1 Changed cache path from caches/xoops_cache to caches/xoops
+2 Added cache for bootstrap config
+3 Disabled pluginCache which did not help
+3 Changed hosts.ini, xoops.ini to use PHP native ini format to save time against XOOPS::processKey
+
+
+October 20th, 2010
+=============================
+1 Implementation of Xoops Plugin Engine
+
+
+September 30th, 2010
+=============================
+1 Adopted Smarty3
+
+
+August someday, 2010
+The third internal preview package
+=============================
+1 Zend framework 1.10.7
+2 Table and element builder
+3 Form compound element
+4 Autoloader refactor, removed loadClass
+5 Config/Preference refactor, using Zend_Form
+6 Theme installer, inheritance and deployment
+7 Module clone and multi-installation
+8 Comment plugin implementation
+9 Pagination improvement with customizable parameter name
+
+July 28th, 2010
+The second internal preview package
+=============================
+1 User module completeness (80%)
+2 Pagination implementation
+3 Unified authentication with enforced hash policy
+4 Zend form implementation
+5 Path configuration for upload as a writable folder with web access
+
+
+July 1st, 2010
+The first internal preview package
+=============================
+Xoops Engine new architecture with modules of system, default, search (incomplete), MVC (demo) and user (started)
+
+
+Taiwen Jiang
+Xoops Engine Developer

XoopsEngine/docs/CodingStandard.txt

@@ -0,0 +1,9 @@
+Coding Standard will be organized soon.
+
+Currently please refer to following references:
+PHP coding standard: http://framework.zend.com/manual/en/coding-standard.html
+JavaScript Code Conventions: http://javascript.crockford.com/code.html
+PHPDocumentor: http://manual.phpdoc.org/HTMLSmartyConverter/HandS/phpDocumentor/tutorial_tags.pkg.html
+
+Taiwen Jiang
+October 30th, 2010

XoopsEngine/docs/Technical.txt

@@ -0,0 +1,49 @@
+The new Xoops Engine (aka X3) is a "Next Generation" XOOPS, rewritten from scratch using Zend Framework.
+
+Why did we rewrite XOOSPS?
+XOOPS is one of the most successful Open Source CMS solution, constantly placing in top places in various competitions, and receiving various awards. But it is showing signs of aging, that would require major rewrites of the Core. We could do what others projects did, and refactor the core while staying "proprietary", or step back and consider other options, like using a standard, off-the-shelf PHP Framework.
+As a "proprietary" solution, it was clear that we're limiting ourselves, and it's hard for us to take advantage of all the great new developments, as we need to convert them every time into XOOPS environment.
+So we did what so many companies did before - took advantage of standard components. The same as first IBM PC or current Apple computers are based on standard Intel chips, or IBM that started using Linux on their mainframes, we've decided to switch to a standard PHP Framework. By doing so, we can focus our limited resources on aspects that make XOOPS unique and special, while leaving standard functionality to be addressed by an off-the-shelf PHP Framework. This way we can take advantage of latest Web developments and vast resources of the Framework team. It's like getting suddenly a whole new team of some of the best PHP programmers joining XOOPS!
+After much research, we've selected Zend Framework, the best and most popular PHP Framework on the market (http://framework.zend.com/about/overview).
+
+Why did we choose Zend Framework
+* The design and coding is professional and state-of-the-art
+* Fully Object-oriented
+* The documentation is exhaustive, with countless third-party resources available on internet
+* The development is active and sustainable, and its team is backed by PHP development team (Zend)
+* The number of contributors is growing continuously and the user community is very active
+* Strong support from major corporations (Technology partners include IBM, Google, Microsoft, Adobe Systems, and StrikeIron).
+* Use-at-will architecture with loosely coupled components and minimal interdependencies
+* Extensible MVC implementation supporting layouts and PHP-based templates by default
+* Support for multiple database systems and vendors, including MySQL, Oracle, IBM DB2, Microsoft SQL Server, PostgreSQL, SQLite, and Informix Dynamic Server
+* Email composition and delivery, retrieval via mbox, Maildir, POP3 and IMAP4
+* Flexible caching sub-system with support for many types of backends, such as memory or a file system.
+* The components are vast and loosely coupled and potentially compatible with other libraries: on-demand pickup
+* All components are fully object-oriented PHP 5 and are E_STRICT compliant
+* Proven PHPunit integration for unit tests
+* Constantly updated with latest Web development features
+* strictly PHP 5
+
+What do we inherit from XOOPS Legacy
+* Modularization
+* Theme
+* Template
+
+What do we expect to improve in new Xoops Engine
+* Flexible architecture and elegant code and implementation
+* Modern MVC architecture: faster development, state-of-the-art technology
+* Distributed deployment respecting virtual hosts
+* Contributor friendly skeleton: easy to manage
+* SEO capable URL routing
+* Solid and rich libraries and frameworks
+* Ready to implement unit test
+
+
+Challenges
+* Different way of thinking, analyzing, designing and developing
+* Unknown learning curve
+* Migration of existing themes/modules to new architecture
+
+
+Taiwen Jiang
+Xoops Engine Developer

XoopsEngine/docs/XoopsEngine-Alpha1.txt

@@ -0,0 +1,56 @@
+
+As announced back in August 2010[http://xoops.org/modules/news/article.php?storyid=5675], XOOPS is moving forward with a brand new architecture.
+After some refactoring during the past few months, today we are releasing the XoopsEngine for the public for testing as an official Alpha 1.
+
+XOOPS, or eXtensible Object Oriented Portal System, well known as a leading open source CMS and portal system, now becomes an application engine platform for web and mobile applications.
+XoopsEngine, as the new brand of the XOOPS Project, supports open and extensible engines backboned with its multi-engine architecture. As for now there are three engines available:
+- Xoops: the official engine with new architecture utilized Zend Framework as primary library and Smarty as default view templating engine, as well as some third-party libraries. Demo is hosted on xoopsengine.org;
+- Lite: a lite version of the 'Xoops' Engine with no MySQL required, aimed for high performance scenarios;
+- Legacy: for backward compatibility to support legacy modules and templates.
+During the time of refactoring, the multi-engine mechanism has been examined and proven with a couple of independent engines for different type web applications.
+By taking advantages of PHP frameworks like Yii, more engines will be provided by Xoops Engine development team, and community developers are encouraged to develop their custom engines as well.
+
+Relevant documents are still being prepared, some selected features that are most wanted by community:
+* Built-in cache mechanism for high performance
+* Clear M-V-C with AOP and event hook
+* Extensible URL rewrite for better SEO
+* App/module clone w/o code change
+
+
+And the current Roadmap for Xoops Engine development in 2011:
+
+* Alpha 1 in end January (this release), open to community conrtibution
+* Alpha 2 in middle February, mainly for developers to review code and write most wanted applications
+* Beta 1 in  early April, for end users to start testing
+* RC 1 in June, reasonably stable for production development
+* Final in early December, celebrating XOOPS 10's Anniversary
+
+From now on, based on our experiences with previous Xoops Engine group organized in Googlegroup, we'll be forming five public teams:
+1) Engine development: primary architecture, backend and front-end development
+2) User extension development: application, module and plugin development
+3) Documentation: development tutorials and user guides
+4) Theme and design: prototype design, graphics and front-end coding
+5) Testing: functionality and performance testing
+If you are interested in or available for any of the teams, please feel free to join.
+
+Few important resources, as we go forward:
+
+1) XoopsEngine source code:
+http://p.sf.net/xoops/trunk
+
+2) Nightly builder for testing:
+http://p.sf.net/xoops/nightly
+
+3) Code contribution guide:
+http://p.sf.net/xoops/contribution
+
+4) Xoops Engine teams:
+http://p.sf.net/xoops/team
+
+5) Project wiki:
+http://p.sf.net/xoops/wiki
+
+
+We invite the whole XOOPS community to contribute to this new and exciting chapter of XOOPS!
+
+The XOOPS Development Team

XoopsEngine/docs/XoopsEngine-Architecture.txt

@@ -0,0 +1 @@
+Coming soon ...

XoopsEngine/docs/XoopsEngine-Contribution.txt

@@ -0,0 +1,37 @@
+Xoops Engine code is hosted on sourceforge git and synchronized automatically to sourceforge svn, googlecode and github.
+
+/XoopsEngine
+The root directory for Xoops Engine code
+
+/XoopsEngine/trunk
+The trunk and working directory, approval for write permission is needed.
+For trunk write permission, please submit request at http://sourceforge.net/projects/xoops/forums/forum/1280117, or send message to [email protected] with subject of "Xoops Engine Trunk Request [username]".
+All code must be tested before submitting to trunk and will be reviewed before accepted.
+
+/XoopsEngine/branches
+The branches for developers, no need of write permission approval.
+All code are self organized, no code review.
+All top folder names should be intuitively informative.
+
+/XoopsEngine/releases
+Placeholder for all official releases.
+Maintained by core development team.
+
+/XoopsEngine/usr
+User or community contributed components, including apps/modules, plugins, applets, themes, etc.
+
+/XoopsEngine/usr/apps
+Xoops Engine apps, i.e. applications following new MVC
+
+/XoopsEngine/user/modules
+Non MVC style modules
+
+/XoopsEngine/usr/plugins
+Plugin folders
+
+/XoopsEngine/usr/applets
+Applet folders
+
+/XoopsEngine/usr/themes
+Theme folders
+

XoopsEngine/docs/XoopsEngine-Feature.txt

@@ -0,0 +1 @@
+Coming soon ...

XoopsEngine/docs/XoopsEngine-Roadmap.txt

@@ -0,0 +1,9 @@
+Xoops Engine development road map in 2011
+
+* Alpha 1 in middle February, mainly for developers to review code and write most wanted applications
+* Beta 1 in  early April, for end users to start testing
+* RC 1 in June, reasonably stable for production development
+* Final in early December, celebrating XOOPS 10's Anniversary
+
+
+More details will be available soon ...

XoopsEngine/docs/XoopsEngine-Route.txt

@@ -0,0 +1 @@
+Coming soon ...

XoopsEngine/docs/XoopsEngine-Skeleton.txt

@@ -0,0 +1,3 @@
+See
+XoopsEngine-Skeleton.png
+XoopsEngine-Skeleton.pdf

XoopsEngine/docs/XoopsEngine-TODO.txt

@@ -0,0 +1,8 @@
+1 Legacy engine for Xoops 2 modules and themes compatibility, end of March
+2 User module/app, end of March
+3 New theme, April
+4 Essential apps, April
+5 Essential plugins, including comment/notification/tag/rating, April
+6 Backend/administration, May
+7 Online distribution, i.e. server-to-server distribution, June
+6 Useful apps/modules for production sites, November