my revo-developing questions

Quote from: splittingred at Jun 18, 2009, 02:05 PM

Quote from: heimdall at Jun 18, 2009, 01:28 PM

I want my super-ditto now, not tomorrow, now dammit. >:(

Then write it yourself.

This is an open-source community, not a drive-thru.

I found this quite hilarious, smiley or not!

Quote from: OpenGeek at May 29, 2009, 03:34 PM

We are eventually transitioning Resources to have no associated content whatsoever. IOW Resources will eventually not contain any content fields at all: no pagetitle, no longtitle, no introtext/summary, no content, etc. These will become standard Content Elements (a Resource Variable vs. Template Variable) with a default value and all Content Elements will allow overrides by Resource, Culture/Language, and/or Version when directly related a Resource.

Please tell me this isn’t happening any time soon (though I see the coolness of it).

Quote from: BobRay at Aug 01, 2009, 02:38 AM

Please tell me this isn’t happening any time soon (though I see the coolness of it).

Probably not until 2.1, which is a long ways off.

Quote from: splittingred at Aug 01, 2009, 10:38 AM

Quote from: BobRay at Aug 01, 2009, 02:38 AM

Please tell me this isn’t happening any time soon (though I see the coolness of it).

Probably not until 2.1, which is a long ways off.

Will there still be a modDocument object with a standard set of fields?

Otherwise, I don’t see how something like Wayfinder could exist.

I’m sure documents will still have standard content elements associated with them. It’s just a matter of how are they stored. The current way of having all those fields in the site_content table is very limiting; that’s why TVs had to be invented. The data will still be in existence, it will just be organized and stored in a more normalized manner. It probably considerably reduces the number and complexity of queries needed for things like Ditto and Wayfinder.

Yes, Susan is correct, and this is exactly what object/relational mapping (O/RM) is for. It allows the details of the relational storage schemes to be hidden behind the classes representing the objects which the developers can work with directly. It will allow us to introduce versioning of all content elements, by culture, without affecting the basic class structure, and will also allow us to define custom sets of predefined content elements that can be attached to various Resources.

Uh... yeah, that’s what I meant... I think (hope you’re going to be OK now?)