0.9.6 final

you mean your post is a sarcasm or whole thread?

:) My "No, no progress" response.

The next RC should be out this weekend.

Quote from: rthrash at Apr 07, 2007, 02:04 PM

:) My "No, no progress" response.

The next RC should be out this weekend.

Hey Ryan, has the trunk been updated yet by chance?

One more update to go to Trunk... the short of it if you’re impatient is to remove the "date," from the &extenders param on doc id 2 (the blog page) with default/demo content. After that I think we’ll be ready for RC2 ... everything else looks good to go.

rthrash, i don’t think someone impatient. Do all the stuff needed to release proper RC2. To me the only modX functional disability is complexity due to no integration of many tools (chunks/snippets) avi into MODx’s framework. At some points it becomes as frustrating as writing code myself.

I think if that applied with keeping in mind non programmer user, i think MODx could beat any other cms. Though im more than sure you aware of that and will implement all needed tools inside of 1.0.0 (prolly commercial) MODx version and make it easy to configure without reading wiki about each tool.

Huh? 1.0 won’t be commercial. [?]

And, yes... RC2 is running my life... Looking forward to it way more than anything else [no rush 4 sure] ... i’m getting the hang of MODx and it makes all other CMS experiences feel like just a run up to where we all are now. Greatest thanks!

Quote from: pr0ph3t at Apr 14, 2007, 11:04 AM

To me the only modX functional disability is complexity due to no integration of many tools (chunks/snippets) avi into MODx’s framework. At some points it becomes as frustrating as writing code myself.

I think if that applied with keeping in mind non programmer user, i think MODx could beat any other cms. Though im more than sure you aware of that and will implement all needed tools inside of 1.0.0 (prolly commercial) MODx version and make it easy to configure without reading wiki about each tool.

MODx is not targeted at every enduser right now, nor has it been, though that will change starting around our 1.0 release. Until then, we’re still focusing on getting the framework right. 1.0 will not be commercial, though there will be commercial support and possibly a commercial license available for companies that demand such licensing scenarios (they do exist in enterprise). The only difference there will be the license.

I hope the licensing doesn’t get mad as with some other cms.
In example per user licenses. This is not windows it’s a cms. Oh lord...why

A good strategy would be a licensing policy like http://www.ip-cms.com/.
Feature based licensing costs.^

But I know you’re smart devs and I’m sure you gonna find some revolutionary new licensing strategy.
This is the web, everything is possible.

Licensing will be straightforward. Some companies won’t run "free" software, and will need commercial licenses. Same exact software, different license. Some components with incompatible licenses would possibly need to be removed. See http://extjs.com/license for a better example.

Thank you .

The ’extjs.com’ link [and supporting comments] make the benefits to companies/certain parties [getting a commercial license] very clear. When 1.0 hits! it seems obvious that there will be beneficial ’energies’ available all round, for the CMS Devs, general users, and corporations etc... [as touched on above]