Roadmap/Update 2.6.0
I get questions about the timing and status of XOOPS 2.6.0, along with questions about how to help. I apologize for not doing a better job of communicating in this area. It is great to know that there is such interest!
The short answer is, we've come a long way, but there is still more to do. But, the good news is the end is in sight!
I've have entered a list of issues on GitHub that represent what I consider the essential changes that are still required. These issues are tagged "roadmap" and can be seen here: https://github.com/XOOPS/XoopsCore/labels/roadmap
This roadmap is only to the completion of the 2.6.0 target and is where development resources will be directed. This roadmap gives us a great base for future enhancements.
The list is quite manageable, and even more so with more help. If you see anything on the list that you would be interested in helping with, please jump in. Even if a given issue is assigned to someone, coordinated collaborative help would likely be greatly appreciated. Just indicate your interest in a given issue as a comment, and we can make sure we are not duplicating each other's efforts.
I will be happy to answer any questions and expound on the issues as needed. The best way to ask questions is probably as a comment on the issue on GitHub, that way everyone benefits from the discussion.
We have recently added some contributing guidelines on GitHub. The GitHub environment is a bit different from the SVN environment used for earlier XOOPS versions, so it includes some explanations and links to resources that might help in the new environment. See: https://github.com/XOOPS/XoopsCore/blob/master/CONTRIBUTING.md
In addition to the the roadmap issues, there are ongoing efforts to improve the quality of XoopsCore codebase. One example is unit testing. Alain91 has been doing a fantastic job creating and maintaining unit tests. (Insert a round of applause here.
)
Unfortunately the rate of change in the remaining issues makes that effort a frustrating job. While we hope the individual developers will assist in updating the tests related to their changes, having "specialists" that watch that area and help keep up with the changes is a huge help. If you are familiar with or interested in unit testing using phpunit, this might be an opportunity to contribute.
Even if you can't program, you can still help out. Install a current copy of XoopsCore and try it out. Reporting bugs or other issues you notice is a big help.
With your help we can make this the best XOOPS ever!
Thanks for your attention. I'll get back to coding now.
-Richard
Read more... | 3 comments
The short answer is, we've come a long way, but there is still more to do. But, the good news is the end is in sight!
I've have entered a list of issues on GitHub that represent what I consider the essential changes that are still required. These issues are tagged "roadmap" and can be seen here: https://github.com/XOOPS/XoopsCore/labels/roadmap
This roadmap is only to the completion of the 2.6.0 target and is where development resources will be directed. This roadmap gives us a great base for future enhancements.
The list is quite manageable, and even more so with more help. If you see anything on the list that you would be interested in helping with, please jump in. Even if a given issue is assigned to someone, coordinated collaborative help would likely be greatly appreciated. Just indicate your interest in a given issue as a comment, and we can make sure we are not duplicating each other's efforts.
I will be happy to answer any questions and expound on the issues as needed. The best way to ask questions is probably as a comment on the issue on GitHub, that way everyone benefits from the discussion.
We have recently added some contributing guidelines on GitHub. The GitHub environment is a bit different from the SVN environment used for earlier XOOPS versions, so it includes some explanations and links to resources that might help in the new environment. See: https://github.com/XOOPS/XoopsCore/blob/master/CONTRIBUTING.md
In addition to the the roadmap issues, there are ongoing efforts to improve the quality of XoopsCore codebase. One example is unit testing. Alain91 has been doing a fantastic job creating and maintaining unit tests. (Insert a round of applause here.
) Unfortunately the rate of change in the remaining issues makes that effort a frustrating job. While we hope the individual developers will assist in updating the tests related to their changes, having "specialists" that watch that area and help keep up with the changes is a huge help. If you are familiar with or interested in unit testing using phpunit, this might be an opportunity to contribute.
Even if you can't program, you can still help out. Install a current copy of XoopsCore and try it out. Reporting bugs or other issues you notice is a big help.
With your help we can make this the best XOOPS ever!
Thanks for your attention. I'll get back to coding now.
-Richard
XOOPS Bug Squashing Week! We need your help!
We are in the process of fixing open Bugs in the XOOPS 2.5.7.
This weekend we've reviewed and closed so far following bugs:
Static Constants Needing Fixed
A session had already been started - ignoring session_start()
X_ITEM_TILE in /language/english/mail_template/default_notify.tpl
Notifications encoding
_AM_SENDMTOUSERS missied
Sorting bug in Profile module search
dhtmltextarea editor accent not displayed
Bug in fresh install in page_configsave.php
TinyEditor only loading in the 'Scoop' part of the News modu
Image Manager category creation restrictions
Calendar shows 40 days
balise code and \
News 1.67 and Xoops 2.5.4
template duplicate issue
template set is not updated based on template file
install last page no css/js
Some of them were old and already solved but not yet officially closed, some needed a solution, some bugs were reported already with a solution, but it's important that we review them all.
Our goal is to close ALL open bugs for the release of XOOPS 2.5.7!
There are still 18 bugs open, so please help us with closing them as well!
We hope, XOOPS 2.5.7 will be the last release in the XOOPS 2.5.x series, so we can then focus on helping Richard with the XOOPS 2.6.0 development!!!
JQuery Mobile Framework For Xoops
I had already created the mobile site in a third level of my site, but had no more than one page index.php
Now I have installed xoops 2.5.5 and did some tests locally with this framework as you can see from this picture is just the beginning.
I hope soon after a period of inactivity for a minor surgical procedure to resume work on this idea that you can share building a real framework to integrate into xoops with the creation of themes for this.
If you like the idea I would be happy to hear your opinion about it for more ideas.
Let's talk about the jQuery Mobile framework
Read the latest news about it and discuss it in this thread
Read more... | 6 comments
Now I have installed xoops 2.5.5 and did some tests locally with this framework as you can see from this picture is just the beginning.
I hope soon after a period of inactivity for a minor surgical procedure to resume work on this idea that you can share building a real framework to integrate into xoops with the creation of themes for this.
If you like the idea I would be happy to hear your opinion about it for more ideas.
Let's talk about the jQuery Mobile framework
Read the latest news about it and discuss it in this thread
Roadmap for XOOPS 2.6
This is a proposed Roadmap for XOOPS 2.6.0. Please read it, and provide us with feedback and suggestions.
The development of XOOPS 2.6 will take place in three stages. These three stages are characterized every time by the release of an alpha version. So we will have three alpha versions. These versions allow module developers have enough time to change their modules and make them compatible and fully functional with XOOPS 2.6.
Alpha 1
· Update the XOOPS Core and all classes to PHP5 (public, protected, static) and E_STRICT.
- This is the main goal of this version. Of course, some modules may have some difficulty in the beginning, but E_STRICT will help developers to minimize errors and significantly improve the quality of XOOPS.
· Create a central class "xoops", this class will help developers and will give a direct access to XOOPS API
- This class will help to simplify the development of XOOPS.
· Delete unused files in XOOPS.(cache and template_c).
· Remove the extra themes and have a single theme for the administration and user interface.
- Provide a "theme model" as a reference for all themes.
· Remove / clean up old source code.
- remove legacy code of older versions (eg. XOOPS 1.0 with the use of PHP in the themes).
- remove all HTML code found in the PHP files.
· Automatic loading of all XOOPS classes
· Do not use global variables, these variables can be used from XOOPS class (e.g. $xoopsModule -> $xoops->module).
· Create a folder for all multimedia public frameworks (jQuery, CSS, JS, images, ...).
· Create Module Class Admin to give the same admin interface for all modules, this class already exists in such frameworks, but now it is included in the core and uses HTML templates.
· moving of some libraries, such as Smarty, to the xoops_lib folder.
· Refactoring the system module.
· Extract some parts of the system module in order to recreate them as a separate module create as a module (eg. Banners).
· Adding a new feature: System Extensions.
- Now some modules in the admin will be called Extensions (eg. Protector). Some features of the current System module are removed and recreated as Extensions. Added to XOOPS (eg. Avatars, Smiles, User ranks, ...).
- All these Extensions are runing as modules, but they cannot be renamed, and they will be shown in a separate menu module
· Integration of CSS Frameworks Bootstrap from Twitter.
· Removal of all queries for the block templates and modules.
- Now, XOOPS reads directly the templates for each part.
· Reduction of queries in all pages.
· New theme in the Admin interface.
· New theme in the User interface.
· New contact form.
- Use of templates.
- Forms Validation with HTML5 attributes.
- CSS3 and HTML5 compatibility.
Alpha 2
· Adding a theme manager in the system module.
- This section allows you to manage themes like modules so you can install, uninstall, or disable a theme.
- We can of course add a few settings in the theme (eg. Logo, size, etc. ..) and all these settings will be visible in the theme.
· Add of new plugins.
- Comments.
- Notifications.
- Image manager.
- Search.
· Integration of PDF library.
· Content module.
- In order to easily add content "out of the box" .
· Menu Module.
- This system allow to create all kind of menus.
Alpha 3
· Integration of rewrite mode in XOOPS.
· New connectors to access the data bases.
· Modification of blocks positions.
Beta
· Adding other features..
· Bugs fixed
RC
· Correction of the latest bugs.
Estimated Dates (Subject to change!)
Version Alpha 1: July 2012
Version Alpha 2: September 2012
Version Alpha 3: October 2012
Versions Beta ( 1, …): From November to December 2012
Versions RC ( 1, …): From January to February 2013
Final Version: March 2013
This timeline seems to be long, but it is based on current available resources. If more people will get engaged in Core development, testing, and bug fixing, we'll be able to release it earlier. So it is really up to the community to speed up the process by getting involved and providing help.
XOOPS 2.6 brings many new features and several important changes in the XOOPS Core. These changes were required to keep XOOPS as a world-class CMS. The Blue Move modules might need some small modifications, but they should be pretty straight forward, and appropriate tutorials will be provided. Older modules will need to be updated to Blue Move first.
The period from July 2012 to December 2012 is necessary to make modules developer more familiar with the kernel changes, and to update their modules.
If you are interested to join the team, don't hesitate to let us know, every help is most welcome. The more help we get, the faster we'll arrive at the XOOPS 2.6.0 Final release!
Your Core Development Team
Grégory Mage (Mage) and Nicolas Andricq (MusS)
Read more... | 21 comments
The development of XOOPS 2.6 will take place in three stages. These three stages are characterized every time by the release of an alpha version. So we will have three alpha versions. These versions allow module developers have enough time to change their modules and make them compatible and fully functional with XOOPS 2.6.
Alpha 1
· Update the XOOPS Core and all classes to PHP5 (public, protected, static) and E_STRICT.
- This is the main goal of this version. Of course, some modules may have some difficulty in the beginning, but E_STRICT will help developers to minimize errors and significantly improve the quality of XOOPS.
· Create a central class "xoops", this class will help developers and will give a direct access to XOOPS API
- This class will help to simplify the development of XOOPS.
· Delete unused files in XOOPS.(cache and template_c).
· Remove the extra themes and have a single theme for the administration and user interface.
- Provide a "theme model" as a reference for all themes.
· Remove / clean up old source code.
- remove legacy code of older versions (eg. XOOPS 1.0 with the use of PHP in the themes).
- remove all HTML code found in the PHP files.
· Automatic loading of all XOOPS classes
· Do not use global variables, these variables can be used from XOOPS class (e.g. $xoopsModule -> $xoops->module).
· Create a folder for all multimedia public frameworks (jQuery, CSS, JS, images, ...).
· Create Module Class Admin to give the same admin interface for all modules, this class already exists in such frameworks, but now it is included in the core and uses HTML templates.
· moving of some libraries, such as Smarty, to the xoops_lib folder.
· Refactoring the system module.
· Extract some parts of the system module in order to recreate them as a separate module create as a module (eg. Banners).
· Adding a new feature: System Extensions.
- Now some modules in the admin will be called Extensions (eg. Protector). Some features of the current System module are removed and recreated as Extensions. Added to XOOPS (eg. Avatars, Smiles, User ranks, ...).
- All these Extensions are runing as modules, but they cannot be renamed, and they will be shown in a separate menu module
· Integration of CSS Frameworks Bootstrap from Twitter.
· Removal of all queries for the block templates and modules.
- Now, XOOPS reads directly the templates for each part.
· Reduction of queries in all pages.
· New theme in the Admin interface.
· New theme in the User interface.
· New contact form.
- Use of templates.
- Forms Validation with HTML5 attributes.
- CSS3 and HTML5 compatibility.
Alpha 2
· Adding a theme manager in the system module.
- This section allows you to manage themes like modules so you can install, uninstall, or disable a theme.
- We can of course add a few settings in the theme (eg. Logo, size, etc. ..) and all these settings will be visible in the theme.
· Add of new plugins.
- Comments.
- Notifications.
- Image manager.
- Search.
· Integration of PDF library.
· Content module.
- In order to easily add content "out of the box" .
· Menu Module.
- This system allow to create all kind of menus.
Alpha 3
· Integration of rewrite mode in XOOPS.
· New connectors to access the data bases.
· Modification of blocks positions.
Beta
· Adding other features..
· Bugs fixed
RC
· Correction of the latest bugs.
Estimated Dates (Subject to change!)
Version Alpha 1: July 2012
Version Alpha 2: September 2012
Version Alpha 3: October 2012
Versions Beta ( 1, …): From November to December 2012
Versions RC ( 1, …): From January to February 2013
Final Version: March 2013
This timeline seems to be long, but it is based on current available resources. If more people will get engaged in Core development, testing, and bug fixing, we'll be able to release it earlier. So it is really up to the community to speed up the process by getting involved and providing help.
XOOPS 2.6 brings many new features and several important changes in the XOOPS Core. These changes were required to keep XOOPS as a world-class CMS. The Blue Move modules might need some small modifications, but they should be pretty straight forward, and appropriate tutorials will be provided. Older modules will need to be updated to Blue Move first.
The period from July 2012 to December 2012 is necessary to make modules developer more familiar with the kernel changes, and to update their modules.
If you are interested to join the team, don't hesitate to let us know, every help is most welcome. The more help we get, the faster we'll arrive at the XOOPS 2.6.0 Final release!
Your Core Development Team
Grégory Mage (Mage) and Nicolas Andricq (MusS)
Multilingual features of XOOPS - White Paper
Multilingual features of XOOPS - White Paper
Michael Beck (mamba) wrote to me a number of days ago to ask me to write a basic white paper on making use of multilingual features of XOOPS better in modules, as alot of my modules including the Content Module X-Centre as well as the Forum - X-Forum make use of the multilingual centres in XOOPS and will strap with X-Language to allow content based on the language provided.
If you write modules I would encourage you to read this whitepaper it only goes for 7 pages and start to implement something similar in your modules to take advantage of multilingual centres in XOOPS so more modules support the API X-Language and/or other APIs and language centres in XOOPS.
Foreword:
This document will show you how to make your module multilingual and interact with X-Language or similar API for XOOPS to enable content and function of content to be multilingual within the module. The idea for example is to have One URL for many different languages with the same IDs etc so that XOOPS multilingual features can be used in conjunction with your module. In this module I will use X-Forum 5.78 & X-Centre 2.16 as example so you can download the source code and use it as a basis to make your module multilingual as well.
PDF Whitepaper:
Download: Multilingual-features-of-XOOPS.pdf - 192Kb
Read more... | 1 comment
Michael Beck (mamba) wrote to me a number of days ago to ask me to write a basic white paper on making use of multilingual features of XOOPS better in modules, as alot of my modules including the Content Module X-Centre as well as the Forum - X-Forum make use of the multilingual centres in XOOPS and will strap with X-Language to allow content based on the language provided.
If you write modules I would encourage you to read this whitepaper it only goes for 7 pages and start to implement something similar in your modules to take advantage of multilingual centres in XOOPS so more modules support the API X-Language and/or other APIs and language centres in XOOPS.
Foreword:
This document will show you how to make your module multilingual and interact with X-Language or similar API for XOOPS to enable content and function of content to be multilingual within the module. The idea for example is to have One URL for many different languages with the same IDs etc so that XOOPS multilingual features can be used in conjunction with your module. In this module I will use X-Forum 5.78 & X-Centre 2.16 as example so you can download the source code and use it as a basis to make your module multilingual as well.
PDF Whitepaper:
Download: Multilingual-features-of-XOOPS.pdf - 192Kb
Converting old modules to XOOPS 2.5.0 GUI: Tutorial
We've talked in the past about releasing updated “XOOPS Module Packs” for our users, focusing on some basic functionalities of the Website, e.g. Personal Website Pack, Community Website Pack, etc.
We are now working on a “XOOPS Basic Module Packs” and our goal is to modify existing modules so all of them have the same consistent GUI and thus increase the user productivity, especially for the first-time users.
Originally we took the GUI idea from the TDM Team's modules, but while we were working on implementing it, Mage came up with a ModuleAdmin class that generates the whole Admin GUI based solely on the Menu definitions in /admin/menu.php and data in xoops_version.php file - see the simplified diagram:
In order to make it easier for other developers to convert their module to this new GUI utilizing Mage's ModuleAdmin class, I've created a set of files helping with this conversion, and a short tutorial showing how to convert xDirectory (you can download the converted module here).
Files:
1) Tutorial as PDF file: view it here
2) Conversion Files incl. Tutorial as Zip file: download it here
NOTE:
a) This is just a 1st Draft of the Tutorial, so your feedback and improvement suggestions are appreciated. Please help us to make it simple and easy to read and follow.
b) Please also let us know any ideas/suggestions that you might have about improving the Module GUI:
- beginners and first-time XOOPS users: how can we make the GUI simpler and more user friendly for you?
- experienced module developers: how can we make it better? Is this ModuleAdmin class making module development easier for you?
Please discuss the GUI and the Tutorial in this thread.
Read more... | 11 comments
We are now working on a “XOOPS Basic Module Packs” and our goal is to modify existing modules so all of them have the same consistent GUI and thus increase the user productivity, especially for the first-time users.
Originally we took the GUI idea from the TDM Team's modules, but while we were working on implementing it, Mage came up with a ModuleAdmin class that generates the whole Admin GUI based solely on the Menu definitions in /admin/menu.php and data in xoops_version.php file - see the simplified diagram:
In order to make it easier for other developers to convert their module to this new GUI utilizing Mage's ModuleAdmin class, I've created a set of files helping with this conversion, and a short tutorial showing how to convert xDirectory (you can download the converted module here).
Files:
1) Tutorial as PDF file: view it here
2) Conversion Files incl. Tutorial as Zip file: download it here
NOTE:
a) This is just a 1st Draft of the Tutorial, so your feedback and improvement suggestions are appreciated. Please help us to make it simple and easy to read and follow.
b) Please also let us know any ideas/suggestions that you might have about improving the Module GUI:
- beginners and first-time XOOPS users: how can we make the GUI simpler and more user friendly for you?
- experienced module developers: how can we make it better? Is this ModuleAdmin class making module development easier for you?
Please discuss the GUI and the Tutorial in this thread.
Interview of Mage by ArabXOOPS Community
The Arabxoops Community was pleased to interview Mage in the monthly newsletters.
to meet this creative and modest person more and to benefit from his experience in XOOPS.
Below the english version of the interview :
Who’s Mage?
My name is Gregory Mage, I am from Switzerland and I live in a small town near Geneva: Lully. I am 26 year old and I work in a watchmaking industry, I'm in charge of technical development of new models.
What got you to XOOPS?
I discovered XOOPS in 2006 by chance when I researched for a CMS for an association of climbing (http://www.sertec-escalade.org ) where I am active in. I’ve tried many CMS and XOOPS was the only one that fulfilled my requirements.
Starting with XOOPS has been difficult because I didn’t know PHP and CSS, I knew just the HTML, but after few months I just was able to make changes to modules and themes.
How did you get started in programming?
I have been programming since 2001. I have started with programming on ADA95, C and C++ during my study in the engineering School of Geneva.
Since 2008 I have been interesting by PHP and took some lessons to improve my knowledge and to be able to develop Xoops modules. I learned a lot from Venom, DuGris, Kraven30 and Muss.
What do you like the most about XOOPS?
It's hard to say ... I think I like everything in xoops. There are certainly many things to improve but overall Xoops is really good
What is the most interesting experience you have ever had from XOOPS:
I learned a lot in the module development, but TDMDownloads is my best exeperience because it was my first module. Now I'm learning daily new things in php during the development of new modules.
If you could add one feature to XOOPS, what would it be?
It lacks two very important things in xoops:
- The multi-language.
- URL rewriting.
Unfortunately today the multi-language does not function well and the URL rewriting is relatively complex to implement. I hope the next version of xoops will improve these 2 points.
What is your major achievement in programming that you're most proud of?
I think my best module is TDMDownloads but I am not yet satisfied with its performance ... Actually, I work on other modules and I hope they will be better than TDMDownloads.
what about your experience in xoops 2.5 ?
Participating in the development of the new xoops core was a great experience for me because I learned a lot of things.
First I have improved my knowledge of PHP and XOOPS architecture.
Secondly I learned to know better Kraven30 and Muss.
In 2.5 I have coded the simplest things because I don't have yet the level of programming of Kraven30 or Muss. In fact, these two are really the ones who have made a lot of new development
What are your hobbies, when you're not coding?
I like sports like badminton, walking and climbing (several times a week). And to be in the mountains
What wishes and advises would you have for the Arab XOOPS community ?
I wish this community to continue to grow because there is lot of potential in it. A big thanks to Mariane and Mowaffak for all their generous participations in XOOPS and Arabxoops community.
Read more... | 5 comments
to meet this creative and modest person more and to benefit from his experience in XOOPS.
Below the english version of the interview :
Who’s Mage?
My name is Gregory Mage, I am from Switzerland and I live in a small town near Geneva: Lully. I am 26 year old and I work in a watchmaking industry, I'm in charge of technical development of new models.
What got you to XOOPS?
I discovered XOOPS in 2006 by chance when I researched for a CMS for an association of climbing (http://www.sertec-escalade.org ) where I am active in. I’ve tried many CMS and XOOPS was the only one that fulfilled my requirements.
Starting with XOOPS has been difficult because I didn’t know PHP and CSS, I knew just the HTML, but after few months I just was able to make changes to modules and themes.
How did you get started in programming?
I have been programming since 2001. I have started with programming on ADA95, C and C++ during my study in the engineering School of Geneva.
Since 2008 I have been interesting by PHP and took some lessons to improve my knowledge and to be able to develop Xoops modules. I learned a lot from Venom, DuGris, Kraven30 and Muss.
What do you like the most about XOOPS?
It's hard to say ... I think I like everything in xoops. There are certainly many things to improve but overall Xoops is really good
What is the most interesting experience you have ever had from XOOPS:
I learned a lot in the module development, but TDMDownloads is my best exeperience because it was my first module. Now I'm learning daily new things in php during the development of new modules.
If you could add one feature to XOOPS, what would it be?
It lacks two very important things in xoops:
- The multi-language.
- URL rewriting.
Unfortunately today the multi-language does not function well and the URL rewriting is relatively complex to implement. I hope the next version of xoops will improve these 2 points.
What is your major achievement in programming that you're most proud of?
I think my best module is TDMDownloads but I am not yet satisfied with its performance ... Actually, I work on other modules and I hope they will be better than TDMDownloads.
what about your experience in xoops 2.5 ?
Participating in the development of the new xoops core was a great experience for me because I learned a lot of things.
First I have improved my knowledge of PHP and XOOPS architecture.
Secondly I learned to know better Kraven30 and Muss.
In 2.5 I have coded the simplest things because I don't have yet the level of programming of Kraven30 or Muss. In fact, these two are really the ones who have made a lot of new development
What are your hobbies, when you're not coding?
I like sports like badminton, walking and climbing (several times a week). And to be in the mountains
What wishes and advises would you have for the Arab XOOPS community ?
I wish this community to continue to grow because there is lot of potential in it. A big thanks to Mariane and Mowaffak for all their generous participations in XOOPS and Arabxoops community.
"Web Tools" Package 0.9 is released
Added one new tool for manage virtual desktop (VirtualWin) to complete the package, which already contained text editors (Notepad + +, Kompozer), a Css editor (Oiky Editor), a web browser (Opera), tools for images (Gimp, PicPick), FTP transfer (Filezilla), a client Svn (subcommander), a tool compression/decompression (7zip), a file synchronizer (Toucan), a file compare (WinMerge), a task manager (ToDoList), an ability to connect remotely to any computer (TeamViewer), a link checker (Xenu), a Web Server (Apache 2.2.16, MySQL 5.1.50 and PHP 5.3.3), a software to cut files sql (SQLDumpSplitter) and a Database Browser/Editor.
List of portable applications:
- 7zip 4.65
- Filezilla 3.3.4.1 (updated)
- Kompozer 0.8b3
- DataBase Browser 3.2.2.10 (updated)
- Opera 10.62 (updated)
- PicPick 2.3.4 (updated)
- Winmerge 2.12.4
- Gimp 2.6.10 rev2
- Notepad++ 5.8 (updated)
- OikoCSSeditor 1.00 RC3
- SubCommander 2.0.0 Beta 5 (updated)
- ToDoList 6.0.8
- Toucan 3.0.3 PR6 (updated)
- Xenu 1.3.8 (updated)
- TeamViewer 5.0.9104 (updated)
- MiniServer : Apache 2.2.16, MySQL 5.1.50, PHP 5.3.3 (updated)
- VirtuaWin 4.3 - Virtual Desktop Manager (new)
You can download the package "Web Tools" on Tutos.XooFoo.org from this LINK
Read the original article in French
Read more... | 3 comments
List of portable applications:
- 7zip 4.65
- Filezilla 3.3.4.1 (updated)
- Kompozer 0.8b3
- DataBase Browser 3.2.2.10 (updated)
- Opera 10.62 (updated)
- PicPick 2.3.4 (updated)
- Winmerge 2.12.4
- Gimp 2.6.10 rev2
- Notepad++ 5.8 (updated)
- OikoCSSeditor 1.00 RC3
- SubCommander 2.0.0 Beta 5 (updated)
- ToDoList 6.0.8
- Toucan 3.0.3 PR6 (updated)
- Xenu 1.3.8 (updated)
- TeamViewer 5.0.9104 (updated)
- MiniServer : Apache 2.2.16, MySQL 5.1.50, PHP 5.3.3 (updated)
- VirtuaWin 4.3 - Virtual Desktop Manager (new)
You can download the package "Web Tools" on Tutos.XooFoo.org from this LINK
Read the original article in French
Tutorial - Build a CSS 3 Main Menu
Learn how to create a cool main menu using css 3 features.
Read more... | 85118 bytes more | 1 comment
TXMod Developer
A new website is online TXMod with new graphics to download themes and modules
link txmod: http://www.txmod.netsons.org
link directory xoops: https://xoops.org/modules/mylinks/visit.php?cid=4&lid=1710
timgno
Read more... | 3 comments
link txmod: http://www.txmod.netsons.org
link directory xoops: https://xoops.org/modules/mylinks/visit.php?cid=4&lid=1710
timgno
Login
Search
Recent Comments
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Nov 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|
Latest GitHub Commits
Archives
News archives
- January 2017
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- July 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- September 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
- July 2004
- June 2004
- May 2004
- April 2004
- March 2004
- February 2004
- January 2004
- December 2003
- November 2003
- October 2003
- September 2003
- August 2003
- July 2003
- June 2003
- May 2003
- April 2003
- March 2003
- February 2003
- January 2003
- December 2002
- November 2002
- October 2002
- September 2002
- August 2002
- July 2002
- June 2002
- May 2002
- April 2002
- March 2002
- February 2002
- January 2002
- December 2001
- December 1969