| Re: Converting Modules between XOOPS 2.5 to 2.6 |
| by iunderwood on 2013/6/20 11:43:46 I'll look at the link. There was no such helpful information when I first started writing these things. Though my peeve so far is that for whatever reason, one of my modules won't let me go to its admin area. "You don't have permission to access this area." I'll need to see what's missing, because it's making me batty. |
| Re: Converting Modules between XOOPS 2.5 to 2.6 |
| by irmtfan on 2013/6/20 2:54:49 while xoops 2.6 is a big step forward, developers can write/modify 2.5.X modules with the most compatibility with it. Just follow the "How to write standard module for xoops" tutorial: https://xoops.org/modules/newbb/viewtopic.php?topic_id=76036 |
| Re: Converting Modules between XOOPS 2.5 to 2.6 |
| by iunderwood on 2013/6/16 18:11:07 I really like what I see coming up in 2.6.0, and I am very much aware that it's still in an early alpha stage of testing. I will, however, state my surprise that some of what I just converted to the 2.5.5 Admin GUI won't actually work in 2.6.0. Admittedly, this disappointed me, and looking at the changes, my first thought was "Damnit ... I just changed the GUI!" I also do not mind learning another set of changes, either. However, until there's a shim layer in place so I don't have to go in and change all my $xoopsDB object calls, I can't say I'm in favor of calling this a v2 release. And you are spot on as far as versioning being somewhat meaningless. XOOPS 2 has had many forks, many of which work fine with other XOOPS 2 modules. But with the changes to the backend, it might be time to move it up. I think I've thrown enough cents at this opinion today. I eagerly anticipate future releases as 2.6 goes through further refinement. |
| Re: Converting Modules between XOOPS 2.5 to 2.6 |
| by Mamba on 2013/6/16 16:31:50 Quote: That said, and after the debacle with XOOPS 3, I think the upcoming release is a big enough deal to call XOOPS 4. I've said it on many occasions before: let's not be so hanged up on version numbers. We've done so many times before when we talked about XOOPS 4.0 with Skalpa, and than back to XOOPS 3.0, but we never delivered. Let's focus on one version, which is currently 2.6.0, and let's deliver on it!  Versioning nowadays is becoming meaningless. See the evolution of Firefox from 3.0 to 4.0, and now they follow Chrome versioning, so they are jumping every few months to a new version, and are now at 22.0. The same is with Chrome. Pretty soon they will be at version 1054 Ubuntu has a totally different versioning scheme, and everybody is happy there too. XOOPS 2.6.0 is a new series. This implies that there will be changes. How big and how much we'll break existing modules, we don't know yet - we are at Alpha, i.e. there are many new additions being experimented with, and tested. Then we'll need to figure out if we can make them compatible with existing 2.5.6 modules. The focus of XOOPS has been always to provide as much compatibility as possible. I hope, we'll do a good job with 2.6.0 as well. |
| Re: Converting Modules between XOOPS 2.5 to 2.6 |
| by iunderwood on 2013/6/16 15:23:44 I won't participate in the Simon beating at this time, but I did get a chance to look through the white paper highlighting the changes. From my perspective as a module developer and a user, it appears to me that modules written before 2.6 will not work with 2.6. I accept this as the way it goes, particularly with the work done on the back end. However, XOOPS has been perfectly content in the 2.x series to largely work with modules written for previous minor releases. I've still got some modules I've written for XOOPS 2.3 that work fine under 2.5. There have been tweaks and such along the way, but minor revision upgrades have been by and large inconsequential, especially from XOOPS 2.3 up through the recent 2.5.6. That said, I think all the back end work in 2.6 justifies a major version bump. The changes in 2.6 alpha from 2.5 justify moving to a new major revision. Here's why: * Module changes to support 2.6 are incompatible with prior releases entirely. This isn't an issue of writing a couple of checks in code to support some of the quirks either. * Site dependencies on modules incompatible with 2.6 will slow its adoption. * Users who expect another minor revision upgrade are in for a nasty surprise, no matter how good the documentation is written. That said, and after the debacle with XOOPS 3, I think the upcoming release is a big enough deal to call XOOPS 4. |
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|