Are there plans for a FULLY FEATURED MULTILINGUAL version of MODx?

I have a similar system, but there is also a TV for each document to specify the ID of its counterpart in the other language(s). For dynamic sections, such as the News section, I set the individual News pages to the main News page of the other language, since it is quite likely that these pages are not going to be perfectly coordinated. But the contact, About, Home, and other static pages are all linked directly to their counterparts.

Quote from: charliez at Feb 19, 2008, 05:34 PM

@ryan
Have you seen the ImmerseCMS translation implementation?
I know that it is from Alex and all the historical shtuff...
BUT it really is very good...

I’ll shut up now...

Since ImmerseCMS is dead (uh... just checked, there is a "immersecms.org will return soon!" message instead of the error page there was for several weeks -> more info here and here), if anyone needs the latest release to give it a look, I can provide the install file... but my understanding is with 0.9.7 this will be handled very differently than immerse. I might not be right but I think the notion of context will play a part into this. But I’ll let those who know say more about this...

You are correct David. But rather than discuss the technical details that make this happen, I’d like to continue thinking about a UI with which non-coders (site maintainers) can work on a daily basis.

Yes, let’s talk features please; it’ll have a much better chance at being listened to than continuing to reference ImmerseCMS, which I will instantly ignore.

Quote from: OpenGeek at Feb 20, 2008, 11:15 AM

Yes, let’s talk features please; it’ll have a much better chance at being listened to than continuing to reference ImmerseCMS, which I will instantly ignore.

That is the same "not invented here" mentality that I have to deal with at work. Which is one reason why I can’t introduce MODx here at my day job.

If someone has already demonstrated a useful feature in a piece of software which failed for other reasons, why dismiss it?

I don’t think it’s this mentality at all. But what good is a reference to a long-gone CMS that hasn’t even got a working site / demo up, much less a download link? If only a minority of folks know that tool, it’s going to be cumbersome to explain to others what exactly was so great about it.

Quote from: bwente at Feb 20, 2008, 11:36 AM

That is the same "not invented here" mentality that I have to deal with at work. Which is one reason why I can’t introduce MODx here at my day job. If someone has already demonstrated a useful feature in a piece of software which failed for other reasons, why dismiss it?

I think you’re absolutely mistaken, and since I am familiar with both MODx 0.9.7 and the latest Immerse I can understand the reason why it’s disregarded. What we’re saying is, what feature / UI element of it you liked that you’d like to see in the future MODx

Quote from: bwente at Feb 20, 2008, 11:36 AM

That is the same "not invented here" mentality that I have to deal with at work. Which is one reason why I can’t introduce MODx here at my day job.

If someone has already demonstrated a useful feature in a piece of software which failed for other reasons, why dismiss it?

bwente: I am well aware of the "not invented here" mentality and am in no way dismissing the features; there are more technical reasons for wanting to avoid all references to this system: mostly the fact it was written by the same person that wrote Etomite from which MODx was forked. I have spent an enormous amount of effort freeing MODx from the Etomite legacy and IP for the upcoming releases, and want nothing to do with anything else Alex is or was involved with.

It’s also a matter of philosophy; there are no generic solutions to this problem that will meet everyone’s need. Sure the Immerse UI for this is nice and simple, but does it meet every possible need for translation workflow or organization? I highly doubt it, but feel free to correct if I’m wrong by discussing the features. In other words, I want to make sure these features are crafted as add-ons to MODx, and that they are as easy to plugin and customize (without hacking the core) as the rest of MODx. This means exploring the features you are referencing in terms of how it applies here, in the MODx framework, and making sure all the integration points are covered.

Sorry, I was not aware of any of the history. In fact I have never even heard of ImmerseCMS. I was just commenting on what seemed to be a case of "throwing the baby out with the bathwater" syndrome. You will have to excuse the knee-jerk reaction. I am a designer working at a place were the developers continually re-create a news admin system everytime from scratch. Who will not embrace a CMS system, for any reason.

Sounds suspiciously like the buggy-whip industry.