![[Main Page]](/modules/mediawiki/images/mediawiki.png)
To Discussion Talk:RoadMap_UnOfficial
If you have a good idea to include in xoops, send your request. In Preference, showing where to find the code working.
Not Invent the wheel, our desire is to make it rotate.
Welcome EndUser for add this list. The list is started by Marco, great collaborator xoops (see the original post)
Well, here are the most awaited features by end users :
http://img152.imageshack.us/img152/6030/mapqi1.jpg
Merging the two branches
*- merging the two branches -> Merging 2.0* with 2.2*
*- Extended user profiles *- Modularized private message *- Blocks cloning (Present in version XT e XM) *- Separate user login and display names *- class XoopsPersistableObjectHandler *- Administration *- Misc fixes/improvements *- Code Security. *- Bug-Fix *- Install new version- modules and themes in install *- Compatible Code modules 2.0*
Security Features:
login attempt
*- notify about attempt login error *- Set the amount of errors in your password *- Who should be informed of attempts to access the account with errors in the password. *- What attitude to take when many of passwords occur. *- Prompt user via email. *- Prompt user, your account is suspended temporarily *- Adjusting for multiple levels of passwords errors *- Aditional information By Catz #10 *- See you too
constraints of pass
password level
captcha
important addition Captcha Functional Request By Mboyden
Audio-Visual Code Display - If we are going to add captcha to the system to deal with robots, assuming this is the best way to deal with this, we still need something for the people with sight impairment, which means an aural method of hearing the captcha code. I've built several sights for visually impaired community, and we can't use captcha because of that. I know this exists, because I've seen it out there in the community, but I don't know who's doing it yet. Nor do I know how long it would take the blackhat community to come up with a captcha-audio converter.
- RESPONSE BY BlueStocking. - Maybe this will help... - Home Page - Demo - Dev. Pricing
Move user Ban
Module profile not core
*- Module profile not core -> extend profile system with module.(extended perfil and using xoopsuser) -> permission for use others modules profile. -> Formulize/RegCodes (extended perfil and using xoopsuser)
Wish - protector in core
*- not as module *- protector in core, not as module. -> (the security shall not be an option)
Core Multilanguage
*- Multilanguage (now is core kernel) (Finished)
Kernel extended
*- Kernel extended
Pdf Generation
-> Inclusion of tcpdf
*- end of duplicate code within modules packages :
Others in Kernel
-> (pre_carga) or pre_called or other.
-> Add called in the archive mainfile.php
-> Add called in Header.php
-> Add called in kernel.php
-> Add called in modules.php
-> Add called in themes.php
Other places exist where we could affix these hooks that will be able to give a new
form to include features through plugins to give a complement to the modules and thus
to prevent hack in Core.
Communs translations
- - Some new translations in global.php like, for example :
Go to the module Settings Administration Categories Ok Data was saved successfully There was a problem while saving data Action Add an item Do you really want to delete this item ? Id Modify Add Save Online Offline etc
Provide hooks for modules
RFC - Hooks for Module Developers
Initial Author: Akitson (Ashley Kitson)
Date: 06/06/2007
Analysing By: Nekro
Complements By: GibaPhp
Objective
This functional requirement is for the Xoops CMS and is aimed at providing hooks into the Xoops core where module developers can extend the functionality of the core.
The primary aim is to avoid end users having to hack core files in order to make certain modules work.
Classic examples of this are:
Peak's Protector - requires mainfile.php to be hacked in order to provide site security.
XBS's Metatags - requires footer.php to be hacked to provide MetaTag Keyword optimisation.
Myreferrer (Solo) - Required interference in....
XT-Monitor (Claudia/GibaPhp) - Required adjust in /class/logger.php , no final da function addQuery(...)
RWbanner (TheRpLima) - Necessary adjust in fhooter.php
Statistic - required mainfile adjust or fhooter.php
And others modules not mencioned here.
There are others.
Limitations
Xoops is not event driven.
If it were then module developers could hook into events to provide this functionality. Xoops is (currently) mainly procedural and this puts a limitation on how this functionality can be added to it. Any technical design that is a result of this requirement should bear in mind what is likely to happen in the future and should be written to take advantage of the core objects within Xoops so that any future changes in Xoops core processing strategy can take this functionality with it. As a result of this limitation, some thought needs to be put into where hook points are placed in the xoops core files.
Design proposal
1/ A new class (inherited from XoopsObject) is defined: XoopsHook()
XoopsHook() has an underlying data table to store non transitory information.
All processing of hooks is done via XoopsHook().
2/ xoops_version.php for modules is extended to allow $modversion[] to carry new data for module installation i.e.
$modversion['hook'][$n]['file_to_run'] = "example.php";
$modversion['hook'][$n]['file_where_run'] = "mainfile.php";
$modversion['hook'][$n]['stage_where_run'] = 1;
A new subdirectory for modules is defined called 'hooks' where hook files are located, e.g. in this example for a module called 'mymodule', the hook is in XOOPS_ROOT_PATH/modules/mymodule/hooks/example.php.
Module installation processes this new $modversion information and stores it in the hooks data table, e.g.
Table xoops_hooks
id : 1
modid : 23
file_where_run: mainfile.php
stage_where_run: 1
file_to_run: example.com
run_order: 0
3/ Deinstallation of the module clears any hook data. Any module update must be handled to cater for changed hooks.
4/ A new administration screen is provided that allows the administrator to;
a - change the run order of multiple hooks vying for the same file and stage spot b - deactivate/activate a hook (deinstallation of a hook occurs when the module is deinstalled)
5/ A singleton xoops_hook() object is instantiated on Xoops Core startup that reads in the data for the hook table and stores in memory.
6/ At strategic points in mainfile.php, footer.php and header.php (as a starting point - we need to canvas module developers here,) a call is made to xoops_hook() object i.e.
xoops_hook->run($current_file_name,$stageId);
This call quickly sees if any code is 'hooked' in and if required, runs it.
7/ Documentation is provided for developers to allow them to create hooks
- and as importantly, rules and parameters are set within which such hooks
must run.
Caveat
There may be better ways of doing this.
to be continue....
Unification FrameWorks
*- end of private frameworks (DJ's, marcan's)
Editor WYSIWYG
-> WYSIWYG, etc. *- refactor the WYSIWYG/DHTML editor
Miscelanius
*- speed display enhancements, scalability improvements
*- refactored redirect page,
-> that is old fashioned, slow, and generate bad feeling about the system
*- refactored image manager,
-> add the feature to manager other media
->streaming,
->videos,
->flash files, etc.),
*-improved mimetypes manager :
-> in a way transform the image manager to a file manager
*- integrated dynamic menu system
*- integrated environment manager (xoopsinfo)
*- integrated maintenance manager (xoopscare)
*- full php5/mysql 5 compatibility
*- refactored admin panel
*- full SEO
*- embedded url rewritting swith on/off
*- multi-site management
*- wide section/category management
*- notification on PM (marcan's hack)
*- refactored PM module
*- refactored user's profile panel
-> Who visited my perfil.
*- Built-in multi-language support
*- Automatic thumbnail generation support
*- Build in RSS Feeds
*- trash bin
*- improved search features
- - Xoops Search - A Better Implementation? - Updated.
*- meta data on documents/files (ECM) *- ajax integration *- Improve comments management.
Added Debug Functionality
Proposal by: Wizanda.
Did you know in 2.2.5 you can set multiple Debug settings on…. This means that as well as having standard PHP debug output….You can also combine them all together and leave the popups behind the browser, to then also see what errors exist in Smarty templates_c files also….
Connecting with other DBs:
*- Connecting with other databases:
MySql
-> <<MySql>> default (ok)
Postgree
->Postgree (development) *- Detail important about DB acess for modules
Others
->SQL Server MS (analysing)
->Oracle
->Sybase
->DbII
->FireBird
PDO Class
-> Pdo class can conection with (mysql, Oracle, SqlServer, DbII, PostGree, etc...)
Install modules directly:
*- Install modules directly: -> select the tar.gz file and do it without use a ftp client.
Install themes directly:
*- Install themes directly: -> select the tar.gz file and do it without use a ftp client.
New Install core.
*- Install core.
-> Detect if exist or possible Trust_path (to write below of root)
-> Create random name for Trus_path.
-> Save database local trust_path
-> if not exist, create Trust_path crypth in root site web.
-> New install compatible version 2.3 (Wish)
New Admin Area refactored
*- Admin Area refactored
Admin Ajaxed
-> Admin Ajaxed.
google analytics
-> Add google analytics - stats and more.
Editor WYSIWYG/DHTML
-> New Configs for WYSIWYG/DHTML editor
Module System refactored
*- Module System refactored
Image Manager
- - Auto Resize Uploaded Images
- - Subfolders in uploads folder (One for each category)
- - Options to manipulate and apply filters on the images
- - Option to create thumbnails
- - Option to use some effect to show the image like lightbox for example
New Position Blocks
- - Create via Admin site new positions for blocks. (Finished) OK
- - Adjust your theme with new positions. Very Easy. (Example Finished for user)
- - You can define one position for one page. (This is equal content for page) Best soluction. (Example in development)
Clone all Blocks
- - Clone blocks in all admin sections. (Finished) OK
Disable/Enable view Users
- - Preferences admin define.
-> User can select your preference view perfil.
-> If Yes (users can define your preference)
-> Example: Yes (admin select in your perfil NO)
- - Define if in perfil of user can select not view your perfil.
-> Yes/no -> If Yes (logged or anonimous)
Others in Module System
-> New section configs in admin system. -> Automatic Update version - integration with module XoopsInfo (dugris) -> Security and configs of the level password for users. -> E-mail and info protection.
Xoops Multi-Site
*- Xoops Multi-Site -> Analysing compatible work and wish End-User. -> Xoops MultiSite beta Release
Return Xoops Packarge
*- Xoops Packarge for New End-User
-> Version complet for End-User.
-> Security
-> Monitor of archives
-> Protector.
-> Admin Area
-> Content
-> Directory
-> Downloads
-> Newsletter
-> Forum
-> Generation Forms
-> Menus
-> Profile
-> NetWork
-> Spreading and banners
-> Seo
-> Multilanguage (now is core kernel)
-> Gallery
-> Poll
-> Wiki
Executing RoadMap
*- Executing RoadMap
-> Started
-> Analysing interessant codes
-> Tagging
RoadMap Pictures Examples
http://www.future-fab.com/assets/Images/ff16_roadmap_diebld.gif
http://wiki.engardelinux.org/images/engarde-roadmap-200512.png
http://www-07.ibm.com/software/sg/offers/identity_management/i/img_roadmap_big.gif
http://www.eclipse.org/tptp/home/project_info/devplans/projectRoadmap_07.GIF
http://www.albrightstrategy.com/images/roadmap_topics.gif
Last HTML save
BS Dec 18th, 2007 :-)
GibaPhp 13:04, 11 November 2007 (EST) Recorded :-)
--GibaPhp 05:35, 21 November 2007 (EST) Recorded ;-)
Conversations
- - Dec. 17th 2007 (from XEU)
- - NOTE: @ Giba, please see discussion page tab for comment and add properly to your roadmap.
- - Quick link
