Theme setting table in Orchard 1.8

Topics: Writing modules, Writing themes
Mar 15, 2014 at 12:00 PM
I have a table for holding theme settings record in Orchard 1.7.2.
In Orchard 1.8, we have document DB mechanism that can hold some setting without table.
Do i need a table for holding theme settings in 1.8 yet?
Please note that there are no content type for theme settings. Therefore what is role of new feature about holding theme settings?

Finally, I want to know correct approach to storing theme settings such as backcolor, ... in Orchard 1.8.
Mar 15, 2014 at 12:27 PM
With the to-be 1.8 you don't have to have a separate table for such settings as indeed they can go into the infoset. You don't have to migrate anything though if you don't want, as records will continue to work.
Mar 15, 2014 at 5:41 PM
Edited Mar 15, 2014 at 5:43 PM
I cannot understand. How can i use infoset for theme settings while there is no content type for using my content part.
Also what is different between infoset in 1.7.2 and infoset in 1.8? I can see using of infoset (Data column in XML Format) in 1.7.2.
Last question: How can i sort or filter by some properties when i use new infoset mechanism? Because in most cases we need filter or sort and this force us to using record again. Correct? For example suppose i want to create revolution slider module. I want sort Sildes content items by a property such as DisplayOrder. Infoset is not useful in these cases. Correct?

Excuse me for bad English speaking.