During the last years, a lot of people have been looking at the webdifferently, and showing the will to use more advanced tools. As such,the number of users subscribed to xoops.org have been multiplied by X.And if the XOOPS community has grown in number, it has also grown indiversity.
Last year, when we realized that the XOOPS projectwasn’t organized to handle so many people, we also had to admit thatthe XOOPS core architecture wasn't able to evolve as people wanted. Notso long ago, this program was just a php portal system, not even partlyObject-Oriented as it is today, and made in an almost monotheisticmanner. For the users, the enhancements added to XOOPS then XOOPS 2have been quite positive, but for developers this legacy has beenpulling us down. It has become harder and harder to contribute to thecore, and to fix some problems, and it was time for a new start.Several other reasons were also convincing us that, if that had tohappen, it had to be right now: PHP5 is already here, has greatfeatures, and one day we’ll have to decide to exploit them and forgetabout PHP4. Considering the re-architecure we plan will require severalmonths, it was best for us to do this switch right now. We cannot askdevelopers to change their methods like this every year.
Acrossthe years, the XOOPS core has evolved to become more than just a portalscript. Hovever as of today it cannot be seen as a real ContentManagement System neither as an applications framework, while in themeantime it is a bit of all of this. For this reason, people havebecome unable to define what was XOOPS, and it was the first problem wehad to solve before trying to go anywhere.
So we first tried todesign a global architecture that could be able to integrate all therequired components we could already imagine. The objective here wasnot to list all these components or to detail their individualimplementation, but to give an overall unrestrictive structure to ourfuture system mainly describing how its composing parts will relate toeach others, giving a precise place to each of them.
Once itsfirst layers implemented, starting from the lowest ones, this globalarchitecture will be enhanced, detailed, grow to include new classesand frameworks until we reach our final objective: have a platform thatwill allow us to run and maintain all the xoops.org web sites as wewould like them to be (while they are actually too much built aroundXOOPS and its limitations).
At first, the Xoosphere project is about a way more than it is about a particular program or features:
Adequatemethodology should allow us to obtain a system able to satisfy as manyof the various expectations actual XOOPS users have manifested duringthe last two years as possible:
Exxoswill be an object instantiation and runtime configuration frameworkdesigned to help building efficient, yet configurable and flexible PHPapplications. It will allow every object to be switched between several“execution modes” to allow programmers to make flexible, configurableand adaptive versions of their components on one side, while providingan optimized and more scalable version at the same time.
Exxositself will exploit this ability, and provide a powerful runtimeconfiguration layer that should allow people to configure every aspectof their system. In development mode its factories will create andconfigure objects according to user preferences, to generatepre-configured extended classes that they will be able to instantiatedirectly in production mode.
This framework will also providestandard text encoding services made available locally (text encodingbeing the key to higher level internationalization functionalities)that will minimize the differences between existing back-ends like theiconv or mbstring extensions, as well as a standardized way toimplement observers (or event handlers).
The kernel will be our own Exxos implementation, providing a globalfactory responsible of the instantiation of all the objects of thissystem, and taking care of the global boot and shutdown sequences. Itwill bring the following paradigms and features:
The lastpart of this operational layer will consists of architectural services.This layer will contain various low-level frameworks providingstandardized APIs to external services or systems. As most of theclasses it contains will be used regularly and on every page request (alot of them being tools that will be used by higher level components),they will be designed to stay simple and optimized, and to bringstandardization and modularization more than features.
TheXoopsDb framework will benefit from the standardization PDO willfinally bring to PHP 5.1. The new version of our framework will bemodeled after the PDO interfaces, ensuring this extension can be useddirectly if it's available (giving out of the box support for all thePDO supported platforms: Ms-SQL, MySQL, Firebird, Oracle, PostgreSQLand SQLite), but we'll also provide a fall back MySQL driver (and wouldalso like to provide a MySQLi driver if people are available to do it).
Thisversion of XoopsDb will also be encoding-aware, and automatically takecare of text encoding conversion (using native driver support ifavailable, or the Exxos provided engine otherwise).
TheXoopsHttp frameworks will contain some of the Http specific components,like session handlers. An important point here is that we will ensureXOOPS 4 is build on the Http protocol, not against it. Throughout ourwhole development process, we will ensure XOOPS stays a Web buildingplatform that uses the most obvious standards like this protocol asadequately as possible. Not only will this allow us to imagine XOOPS asjust a part of a bigger platform or system, it will also be the reasonbehind some of our architectural choices, like the fact XOOPS4 willinternally manipulate canonical, human-readable URIs, that will staylike this if possible, or get transformed to infamous xxx.php ones inthe worst cases (as opposed to other programs that manipulate scriptlocations later transformed using “shortURL functions”).
Smartywill be the first engine to be implemented in the XoopsTemplateframework (though differently than it was in XOOPS2 and with theaddition of custom extensions to the default engine ), but depending onthe way things go, we might add our custom template engine here,implemented with a compiler similar to the one Smarty has (but withoutsome its almost never used features, to keep something simple and morescalable than what Smarty has become).
Thecore services layer will provide primary services built above the lowerlevel architectural components, and acting as intermediary betweenapplication level MVC-oriented components.
TheAuthentication framework will provide two services: the authenticationservice (handling the whole authentication process) will be separatedfrom the authentication driver (taking care of checking credentialsvalidity), this last one becoming configurable. Several default drivers(LDAP, XoopsDb...) will be provided, but people will be able to designcustom ones to extend this framework possibilities.
XoopsUiwill bring the base tools later used to build advanced XOOPS4applications user interfaces. One of the key elements for this will beUser Interface Files that developers will be able to use tocreate/describe UIs (some kind of super-templates that can instantiateobjects and provide several versions of an interface, made fordifferent display technologies: HTML, but also XUL, or whatever). Basedon XML, user interface files will be compiled in the same manner Smartytemplates are, to ensure a fast access on production sites.
XoopsThemewill encapsulate the functions of the page building service, that wrapsmodule output into a themed page. Page building will be enhanced willthe addition of an intermediary application-level template, and thepossibility will be given to objects to manipulate page-level meta data(so a widget inserted into a page can ensure its required style sheetsand script files are fetched from the page header). More power willalso be given to themes, as resources containers: people will now beable to use themes to customize any resource used to build the output(whether it is a template, style sheet, script file or image). Whenaccess to a themed resource will be requested, XoopsTheme willautomatically check if a custom version exists in the theme, and modifythe resource URI if it does. Access to these last features will beprovided with the help of custom Smarty compiler functions, to ensurethis doesn't become a scalability killer.
We are also considering the possibility of making some of this new framework features available in the 2.1/2.2 branch.
XoopsDatawill be designed to address some of the most important areas offunctionality in document-based web applications: object graphmanagement and persistence. The classes it will provide will leveragemodules developers from having to take care of retrieving or savingobjects properties from/to persistent stores, or from having tovalidate these properties values before they are saved to a persistentstorage. Some of its key features will be:
TheApplication Services layer will contain several frameworks based on theMVC pattern, to help build document (model) oriented applications asfast and easily as possible. The ApplicationKit will bringXoopsData-based Object controllers made to create, view or edit manageddocuments. The WidgetsKit will provide several default widgets thatpeople can use to build powerful user interfaces (tool bars, enhancedform controls). While we don't think XOOPS should provide a full-blowncontrols library, at least we will have to provide a few defaultcomponents as well as some standardization here, so 3rd-partydevelopers can make their own custom XoopsUi widgets.
The modules delivered with this new platform will fall into several categories:
Ourmain objective during the development of this version, will be to makeXOOPS a real open-source project, made highly collectively. From what Isaw in recent forum posts, I guess most of the actual XOOPS users maynot realize this importance of this change: this has never been thecase in the past, the worst consequence of this being the inability ofthe XOOPS2 architecture to be easily enhanced in a way that could haveallowed us to continue its development by a more collective effort.
Thisgoal will bring a lot of changes to the traditional XOOPS developmentmethodology. This means everybody can forget about the “code privately,release when finished” way adopted by previous core development teams,and say “Hello” to early alpha core releases, or to the longly awaitedtechnical documentations. More precisely, these are the things youshould be able to see during the next weeks:
The following is subject to change as development progresses.
Version/codename | Release date | Summary of major items |
---|---|---|
XOOPS 3.99 m1 Ganbarimasu | June 2005 | Early preview release. First implementation of most of the low-level components, with unfrozen interfaces. Launch of the first core sub-projects (XoopsDb and XoopsAuth frameworks, registration module...) |
XOOPS 3.99 m? Catalysis | 3rd quarter 2005 | First official document drafts. Very cold operational layer. Working core services, and first application level frameworks classes implemented. Usable (and used) by contributors as a base platform: beginning of the new core development site construction. Start of the final high-level core modules dev (content explorer, stores manager, pages builder...) |
XOOPS 4.0 beta1 Reaction | Early 2006 | Beta level classes and frameworks (with frozen interfaces). Early version of most of the core modules. Safely usable by developers and site builders. Start of the re-implementation of the XOOPS2 core. Launch of the new xoops.org building project between all the XOOPS teams. |
XOOPS 4.0 RC1 | ||
XOOPS 4.0 Xoosphere | 1st half of 2006 | Stable release / Full developer documentation Full 2.1.x backward compatibility implemented Launch of the new xoops.org websites |
发表者 | 树状展开 |
---|---|
longskys | 发表日期: 11月17日 22:54 更新: 11月17日 22:54 |
中级会员 注册日期: 08月22日 来自: 发表总数: 46 |
xoops 4.0 ??? xoops 4.0 ???
schedule 上说2006年中期就应该release了,怎么现在还是2.015啊. 这个到底怎么回事 |
domecc | 发表日期: 11月18日 18:02 更新: 11月18日 18:04 |
网站管理员 注册日期: 10月29日 来自: 北京 发表总数: 2214 |
计划不等于执行结果
|
ansir | 发表日期: 09月20日 10:21 更新: 09月29日 08:47 |
新进会员 注册日期: 09月20日 来自: 发表总数: 18 |
north face North Face UK jackets are remarkable of the north face coats clearance superb quality and fantastic worth for money.north face coupons With this sort of amazing function, men and women around the cheap north face clothing world dreamed of owning these North Face Jackets in winter,north face clothing outlet to assure that they can have a comfotable trip outside,north face mens coats hey all can apparel fashionable in your street. earliest well-known in America, nowadays,north face mens jackets clearance has key in the global market. These classic North Face Jackets are north face Fleece available at our North Face Outlet online outlet store . Customers around the world can enjoy the North Face 3 In 1 Jacket nice price and good quality now.
|
ansir888 | 发表日期: 09月20日 10:53 更新: 09月20日 10:53 |
中级会员 注册日期: 07月20日 来自: 发表总数: 53 |
cheap replica handbags Wholesale Replica Purses in China,we have most brand Cheap Purses louis vuitton,gucci purses,replica D&G,Fendi,MIUMIU,Coach handbags,jeans,Chloe,Chanel purse style with matching Balenciaga wallets.Cheap Replica Purses Great low We have the most of popular of cheap coach purses and cheap replica handbags the Cheap Replica Handbags for cheap with.
|