hi timgno

clone from https://github.com/txmodxoops/TDMCreate-1.91/releases/tag/alpha-2-2

1) uninstalled previous version

2) cleaned up cache

3) installed 1.91 alpha 2 2 - ok

4) created new module - ok

5) create new table for this new module:
Fatal error: Class 'TDMCreateThemeForm' not found in C:\Homepages\Xampp\htdocs\xoops2571\htdocs\modules\tdmcreate\class\fields.php on line 115

The ratio of XOOPS (11,529) versus WordPress (74,652,825) sites on the web is 6475:1 in favor of Wordpress, so the simple math justifies the results you see in Google webmaster tools. (exact dates of surveys unknown).

XOOPS has a Wordpress powered module called xpressme, that was being maintained as of 2012-2013, that if still maintained, would provide Wordpress presence in XOOPS installations.

As we all know , since April 21, 2015 google changed their algorithm search by giving privilege to sites compatible with mobile , this update show us a lot of signs about the compatibility of xoops with search engines .

I think it's not about just the theme , but the whole systeme , i use xoops for 8 years til now , for sure its a great systeme , but i can't stop asking myself : why wordpress is compatible with search engines by difeaut installation , and xoops not !!

yes the theme can fix some issues , but there is also : googleboot can' access to some files ! and this we can't fix it with new theme !

we need a huge update to this systeme to give a smooth access to the new google updates , the future is for mobiles my friends .

I had no problems at all with it.

I've added it the same way as you did, and it is now visible in the Dutch version of the Website.

Quote:
It's always good to have translations in the Archive, in case somebody would like to do something with it in the future!

Quote:
Please follow the link to GitHub from this article

Quote:
We'll have more and more "responsive" themes based on Bootstrap, than should work fine on mobile phones.

We are currently waiting for the new theme being developed for XOOPS German Support that we might utilize on this Website as well.

http://www.xoops.org will have a "responsive theme", but let's wait to see if we can leverage what is being developed in the German-speaking countries.

Quote:
Rodney, MVC seems to be a little bit outdated, and there are some new and cool variations of it, like the ADR (Action-Domain-Responder)

An interesting article about "Alternatives to MVC" was published by Anthony Ferrara, as a follow-up to his article "A Beginner's Guide To MVC For The Web", and Paul Jones (author of ADR) responded here.

There is also an interesting comment about ADR by Akihito Koriyama, who himself is working on yet another framework called BEAR Sunday.

Please note that Richard has already experimented with ADR and there were several aspect that the he liked about it.

However, the main key will be to bring all the pieces in sync, especially the Presentation Layer that Eduardo is porting to XOOPS 2.6.0 from his "Common Utilities" and the work that Richard was doing on Core, incl. his various experiments with XMF, MVC, and finally ADR.

The opportunity for XOOPS is that because we won't have any "legacy" code written using the classical MVC, we can choose and take advantage of some of the newer ideas, and have XOOPS again on the cutting edge of development

I would like to credit here both Richard and Eduardo for their willingness to look at new ideas from others, test them, and then select the best and implement them in XOOPS! The "Not invented here" syndrome is gone from XOOPS!

The biggest things about future modules is that they MAY work with little updating with 2.6 but there are a BUNCH of things that are changing with 2.6 that will make rewriting many of the modules the best choice but before that happens we need to lock down some items within 2.6 more so we only need to rewrite modules once.

I would suggest any modules that do get rewritten to follow a strict MVC model so it makes things much easier to modify down the road. By making a module fully MVC you are forced to group things together in the same area instead of threading them through the code and it will make life MUCH easier down the road.

In Brief, MVC seperates a program into three sections...
M = Model - The code that does the actual work.. This should be the code that uses a lot of Xoops API. This will save variables, load them, and do all of the calculations etc...

V = View - This is the interface to the program. This would be written mostly in Smarty but setup with some basic PHP. There should be NO HTML code anywhere other than in here.

C = Controller - This is the decision making portion and basically interfaces between the View and Model. The View communicates with the Controller and based on what it needs the Controller communicates with the Model to actually do the work.

This forces you to NOT sprinkle HTML code throughout and by the grouping required should make things much easier to upgrade down the road. When you clone a module you may be able to just clone a portion of it instead of the whole thing too.

Rodney

Your not alone, everyone here would like to see Xoops mobile.

XoopsFrance came up with what was the first mobile compatible theme, but they dropped the ball.

But then again France built two huge helo carriers under contract for $1.2 Billion for Russia, refuses to deliver them, and will probably take them out to sea so their shipbuilders can watch as they sink them instead.

As was just announced under the News column, the 2.6 presentation layer has just begun. This is a good time for such issues to be brought into circulation.