hi,
Too bad the name of "class" are written in hard. It should take all the files and rename hand.
I have used variables, classes and functions dynamic
Look at my old modules which I use as starting skeleton.

http://sourceforge.net/projects/chgxoops/files/Modules/vide.zip/download

Nothing to rename, just a copy / paste (except for MySQL file) for an operational base module and not conflict with other modules.

This module is not perfect and is not yet the standard of practice but XOOPS 2.6 to start and especially for cloning.

Viewing:
./include/install_function.php
./class/class_class.php

There is no rush, it's better to use this module as an "experimental lab" to try different approaches, while we're researching for "XOOPS Best Practices" is module development to be incorporated here.

I had the same issue as you did, i.e. there are too many variations on how to solve a particular issue, e.g. uploading a file, do pagination or do search in a table, etc.

In the past we had several attempts with the goal to standardize our key modules, like the "Blue Move" initiated by Catzwolf, then we talked about Admin GUI standards, which resulted in a great "Module Classes Admin GUI" by Mage. This was used to convert several modules to our "Basic Module Pack" that had the same Admin GUI across all of the modules.

Irmtfan did a very good job with his Tutorial on "How to write a standard module for XOOPS"

I am glad that slowly we are finally getting to have our key modules simplified and standardized for XOOPS 2.5.7.

However, the biggest challenge, and the most fun will be to work on a conversion of our key modules to XOOPS 2.6.0, using the wonderful work on "Common Utilities" by Eduardo "BitC3R0" that he will be porting to XOOPS 2.6.0. There is also the XMF (XOOPS Module Framework) done by Trabis, on top of which Richard did some experimental MVC that actually worked. Plus some very cool approaches developed by Tad and his team from XOOPS Taiwan.

So the plan is to refactor/rearchitect the Core and prepare it to be fully MVC (based on XMF), which is currently being done by Richard. Then use Common Utilities" from Eduardo as our "Presentation Layer", while extracting all cool features that are not directly related to "Presentation" and incorporating them into the Core. At the same time, we hope to engage Tad and his team, so we can benefit from their expertise as well.

But the first step is to use the current time to convert and standardize our existing key modules, so once we start moving to XOOPS 2.6.0, we'll need to convert each feature/functionality only once, and then reuse it in all the other modules. Pretty much the same what we did with the "Admin GUI"

Please help us by testing the module created by Luciorota, and by providing suggestions, or even better: a working code, that could be used in this module.

Hi how are you all? I hope you are well and all is good, I have started up again after taking a number of months off on holidays from the project... In a week or two I will be release consectively in one hit the following new modules

• Signed 1.xx ~ based on http://signed.labs.coop -- online legal signature system for identification and sealing an aggreement! {See: XOOPS SVN}
• Radioo 1.xx ~ radio stations for your web clients {See:~ XOOPS SVN for Alpha}
• xAlky 1.xx ~ IRC Style chat rooms based on http://chat.labs.coop {See:~ XOOPS SVN for Alpha}

tnx mamba
i'm still bust in module structure
i'm working on administration side, when finished i'll set my mind on frontend side
i'll remove custom request asap, in xoops 2.5.7 request class there are some issues when managing arrays that could be better...
thanks again for your submissions, just merged!

Lucio, this looks very good - it's definitely a very good start for a discussion about standard for a modules.
I have submitted few changes to GitHub, feel free to use or reject them.

I still have problems on the Front End with the \class\common\choicebyletter.php, but didn't have the time to dig deeper there.

Questions: why are you using a separate module Request, instead of the XoopsRequest?

Hopefully within a week or two, depends when I find some free time...

No problem also the male female gifs are missing you know the circles and arrows
Do you have any idea of a time scale, im itching to get this on a production site, im aware of others having it on a live site with their pictures any idea how they get them there?

Excellent news!

I'll be testing it this weekend!

hi guys
In recent months, for my job, I've been working on updating some modules to make them compatible for use with Xoops 2.5.7 and update them using, where possible, the latest features offered by Xoops.
I saw that the differences between all those modules are huge, there is not a common standard, so I decided to create a "standard", "generic" and "empty" module that could be the starting point from which to create any other module

This is my work

https://github.com/luciorota/module_skeleton

When finished it could be a model for create modules with TDMCreate

Each contribution is really appreciated, in creating standard teamwork is essential.
So, please, contribute where and how you want.

Thanks

Thank you so much for testing!

Please keep on testing, but don't use it yet on a production site, because there will still some more changes coming. For example, the images uploaded by the users have to be moved to /uploads directory, so we're consistent with other modules.

We'll be also replacing the phpThumbnails library with another one.

In the meantime, please report any issue you find.