https://speakerdeck.com/xoops 2014-05-28 04:04:20 -0400 XOOPS 2.6.0 alpha 3 introduces a Service Manager component: - Services located by service name, not provider - Service interface established by Contract - Returns a standardized Response object that includes result, status and messages - Request is based on a well known interface - Actual provider does not matter to caller - No need to check for a specific module - If the service is not available, that status is returned just like any other error condition. - Service providers are only instantiated when explicitly requested, and then kept for the duration of the PHP run. - A locate event is not triggered until a named service is first requested, so if a service is not used, it has no overhead cost. - If no providers for a service are installed, the locate trigger has little cost, and any subsequent calls go straight to a NullProvider that minimizes resource use. XOOPS 2.6.0 alpha 3 introduces a Service Manager component: - Services located by service name, not provider - Service interface established by Contract - Returns a standardized Response object that includes result, status and messages - Request is based on a well known interface - Actual provider does not matter to caller - No need to check for a specific module - If the service is not available, that status is returned just like any other error condition. - Service providers are only instantiated when explicitly requested, and then kept for the duration of the PHP run. - A locate event is not triggered until a named service is first requested, so if a service is not used, it has no overhead cost. - If no providers for a service are installed, the locate trigger has little cost, and any subsequent calls go straight to a NullProvider that minimizes resource use. Wed, 28 May 2014 00:00:00 -0400 https://speakerdeck.com/xoops/xoops-2-dot-6-0-service-manager https://speakerdeck.com/xoops/xoops-2-dot-6-0-service-manager A web page consists of a base HTML document and any additional files it may include, such as stylesheets, scripts, images and fonts. We will refer to these additional files as assets. Assets are a very important part of the user experience. For today's rich, highly interactive web applications, the asset performance may be more significant than the backend application and database performance. In XOOPS 2.6.0 we'll use Assetic, developed by Kris Wallsmith, to manage all the assets. A web page consists of a base HTML document and any additional files it may include, such as stylesheets, scripts, images and fonts. We will refer to these additional files as assets. Assets are a very important part of the user experience. For today's rich, highly interactive web applications, the asset performance may be more significant than the backend application and database performance. In XOOPS 2.6.0 we'll use Assetic, developed by Kris Wallsmith, to manage all the assets. Wed, 28 May 2014 00:00:00 -0400 https://speakerdeck.com/xoops/xoops-2-dot-6-0-assets-management-using-assetic https://speakerdeck.com/xoops/xoops-2-dot-6-0-assets-management-using-assetic The recent Project of the Month on SourceForge, XOOPS (http://www.xoops.org) was designed from the very beginning as an object-oriented CMS, which is even reflected in its name: eXtensible Object Oriented Portal System. Michael will present the OOP oriented architecture of XOOPS, and show how OOP makes development of XOOPS modules easy and fun, promotes reuse of code, while keeping GUI consistent across all modules. The recent Project of the Month on SourceForge, XOOPS (http://www.xoops.org) was designed from the very beginning as an object-oriented CMS, which is even reflected in its name: eXtensible Object Oriented Portal System. Michael will present the OOP oriented architecture of XOOPS, and show how OOP makes development of XOOPS modules easy and fun, promotes reuse of code, while keeping GUI consistent across all modules. Fri, 28 Sep 2012 00:00:00 -0400 https://speakerdeck.com/xoops/oop-adventures-with-xoops https://speakerdeck.com/xoops/oop-adventures-with-xoops FirePHP is a Mozilla Firefox plugin/extension that merges with Firebug and enables you to log to your Firebug Console using a simple PHP method call. All data is sent via response headers and will not interfere with the content on your page, therefore it is ideally suited for AJAX development where clean JSON and XML responses are required. In this tutorial we'll show you how to use FirePHP/FireBug to debug XOOPS. FirePHP is a Mozilla Firefox plugin/extension that merges with Firebug and enables you to log to your Firebug Console using a simple PHP method call. All data is sent via response headers and will not interfere with the content on your page, therefore it is ideally suited for AJAX development where clean JSON and XML responses are required. In this tutorial we'll show you how to use FirePHP/FireBug to debug XOOPS. Mon, 28 May 2012 00:00:00 -0400 https://speakerdeck.com/xoops/firebug https://speakerdeck.com/xoops/firebug Tutorial for XOOPS Headlines module Tutorial for XOOPS Headlines module Mon, 28 May 2012 00:00:00 -0400 https://speakerdeck.com/xoops/xoops-headlines-module-tutorial https://speakerdeck.com/xoops/xoops-headlines-module-tutorial Mon, 28 May 2012 00:00:00 -0400 https://speakerdeck.com/xoops/xoops-2-dot-5-x-installation-guide https://speakerdeck.com/xoops/xoops-2-dot-5-x-installation-guide Mon, 28 May 2012 00:00:00 -0400 https://speakerdeck.com/xoops/xoops-2-dot-5-x-operation-guide https://speakerdeck.com/xoops/xoops-2-dot-5-x-operation-guide