Quote:

Totally agree!

Plus - focus on work, and not on politics. After all, it's all about the SOURCE!!!!

I am new to all of this, being in the middle of setting up my very first full-blown XOOPS site, a community portal, for a client. (When things are more stable I'll share it.)

The hint that I'd gotten over the past few weeks that there was trouble in Xoops-land disturbed me, but I decided that I would "keep my head down," plug away, and form an opinion after having some more XOOPS experience of my own.

Since I need to develop some of the functionality for this site, the issue of which platform to use is especially relevant, but at this point I'm somewhat locked into XOOPS 2.0.1.17, and I'll just use that for now. As a (potential) module developer, though, I can think of one thing above all else that could help "bring back" the diverging product forks:

* Clear directions on what are the platform differences from a developer's perspective

If I code for Xoops, but want to make my module available for XOOPS Cube et al., what would I have to do?

First step is to explain the differences, so a developer (like me) can be aware of them, and plan the design accordingly.

Second step is to detail the differences, so that a developer can (relatively) easily write platform-independent code that will work on all of the different forks.

Third step is to converge the differences at the level of a theme or a template or a module, so that a single set of switches, or a single extra file, or whatever, can be used to customize for each target platform.

If someone could start this effort, for example by just making a list of the differences between XOOPS and XOOPS Cube for a developer to be aware of, that would be a good start in the right direction, IMHO.

-- Eliyahu

Maybe this will be of some help..

Nachenko is writing some documentation, that explains How XOOPS rendered the page you're viewing

He offered to include in this documentation how the page was rendered in XoopsCube.

SEE: XOOPS Cube page rendering

Hope this is of a little help...
There should be more to come in the future.

Quote:

Sorry, I'd have to update this.

I consider my article finished. A version for advanced users could be fine, but it's unlikely I write anything in the next few months.

BTW, I'm not interested in XOOPS Cube at this moment, XOOPS forks are not interesting for me, as they don't make much difference. If any of these forks offered any killer feature such as full multilingual support, custom hooks like Xaraya, or CCK and Taxonomy for all content types just like Drupal, that would make a real difference.

RE:by nachenko on 2007/12/11 22:26:19

Nachenko,

Would you be willing to put your document into the xoops.org wiki.

I will be glad to help in any way I can to migrate it to the XOOPS wiki.

Any suggestions?

Thanks
...darcy

Hi,

I suggest you to visit xoopscube.org wiki (end-user)
and the sourceforge wiki (end-user and developers).

And you'll discover what XOOPS Cube + D3 Modules can achieve
that you can't with this 3 years old and nice Xoops2.
User Interface improvements (usability, ergonomics..)
More secure (search for actionfilter and actionform)
Much more freedom with Legacy render system.
But as a developer you will also discover what XCube
is able to do that you can't even imagine with Joomla,
Drupal or Xaraya! Check your-self and ask experts!


Ref.
Sourceforge Wiki
Minahito Sand Box
Mikhail's 1000 themes and 500 modules without frameworks (ie. wordpress)
+ Admin Themes, Extensions without hack your Core
+ Module for Multilinguage
+ A safe WYSIWYG FCKEditor

And much more to set you free and have Fun with your site !

Quote:

Looks like impresscms will have multi language by gijoe right out of the box.

Lots and lots of other little goodies as well.

change log

Something like CCK would be a show stopper...

@script_fu

What is impresscms and its relation to this thread !?
Thanks

whttp://www.impresscms.org
http://sourceforge.net/projects/impresscms/

Will start seperate post...