Forum — studiograsshopper

Please make sure that you have read the documentation and extensive resources provided on this site before posting your question!

Dynamic Content Gallery Resources

DCG Version 4.0 beta is now available for download and testing. This is a development version and not recommended for live sites. Read more here.

Note that the current stable release of the DCG is version 3.3.5.

	You must be logged in to post	Login Register

Home Forum Serial Posts Some suggestions

Some suggestions

Page: 1

User

Post

7:50 am
December 24, 2009

javier

Guest

Post edited 8:19 am – December 24, 2009 by javier

Regarding the internacionalization and the css issues (á,é,ñ and so on) we talked in previous post, I would suggest you to do a very easy change in the code. Actually, two changes:

1. Use 2 different personalized fields: one for the title of the series (that would be shown in the title area) and another one for building the list, let's name it "series-key". series-key would not have any international character on it, an its use would be double: first, to build the list and, second, optionally to have a personalized div area in css.

Having this way series could have international characters, and also would permit to have different title names in the same list (for example, in a book splitted in different volumes, you could have "Title Vol. 1″ in several chapters, "Title Vol 2″ in other, etc)

2. Have a general div formatting in css (for all) and the option to personalize div formatting with series-key exists.

To do this two changes, as I see it in the code of your plugin, you should only have to change two lines of code and insert an if condition (say, "if series-key exists, then personalize the div formatting; if it does not exist, use general div formatting"). (Edit: I wrote this very quickly and could be a little more tricky: in fact series-key will always exist; what would or would not exist is the div class; that could be solved with another personalized field: "series-div": if it exists, apply the format; if not, the general div format… but would require css knowledge from the user).

I would even include another personalized field, let's name it "series-chapter-title": sometimes it would be nice to have a different name in the list as of the title. For example, you could have the title "The Lord of the Rings Chapter 15″ in the article but only want to show on the index list "Chapter 15″; that would be the use of this "series-chapter-title" personalized field. Also it would only cost you to change a little code.

Hope it helps. Thanks again for a great idea.

10:07 am
December 24, 2009

Ade

Admin

posts 2384

Thanks for the suggestion, Javier. I will give it some thought. Smile

Dynamic Content Gallery: Have you read the Configuration Guide and FAQ?

10:50 am
December 24, 2009

Ade

Admin

posts 2384

javier said:

1. Use 2 different personalized fields: one for the title of the series (that would be shown in the title area) and another one for building the list, let's name it "series-key". series-key would not have any international character on it, an its use would be double: first, to build the list and, second, optionally to have a personalized div area in css.

Having this way series could have international characters, and also would permit to have different title names in the same list (for example, in a book splitted in different volumes, you could have "Title Vol. 1″ in several chapters, "Title Vol 2″ in other, etc)

I'm not sure I quite follow this. How would this allow different title names in the same list? The actual items in the list are simply the post/page titles.

As we discussed in the other thread, I agree that the div name should not be pulled directly from the Serial Name – because of the problems with non-valid CSS characters (punctuation other than hyphens, international characters, etc).

Are you saying that "series-key" would be the key that builds the list, ie would be the custom field added to every post/page in the Serial, and the existing Serial custom field would just be a way of titling the list?

javier said:

2. Have a general div formatting in css (for all) and the option to personalize div formatting with series-key exists.

To do this two changes, as I see it in the code of your plugin, you should only have to change two lines of code and insert an if condition (say, "if series-key exists, then personalize the div formatting; if it does not exist, use general div formatting"). (Edit: I wrote this very quickly and could be a little more tricky: in fact series-key will always exist; what would or would not exist is the div class; that could be solved with another personalized field: "series-div": if it exists, apply the format; if not, the general div format… but would require css knowledge from the user).

I would even include another personalized field, let's name it "series-chapter-title": sometimes it would be nice to have a different name in the list as of the title. For example, you could have the title "The Lord of the Rings Chapter 15″ in the article but only want to show on the index list "Chapter 15″; that would be the use of this "series-chapter-title" personalized field. Also it would only cost you to change a little code.

Hope it helps. Thanks again for a great idea.

I guess the answer depends on whether users need to change the CSS on a list by list basis. I'm not convinced (yet) that this is a requirement.

I'm interested in your thoughts, so don't be put off by my replies – I'm just trying to understand what the issues really are. Laugh

Happy Christmas to you too!

Dynamic Content Gallery: Have you read the Configuration Guide and FAQ?

1:57 pm
December 24, 2009

javier

Guest

Post edited 2:06 pm – December 24, 2009 by javier

Ade said:

I'm not sure I quite follow this. How would this allow different title names in the same list? The actual items in the list are simply the post/page titles.

As we discussed in the other thread, I agree that the div name should not be pulled directly from the Serial Name – because of the problems with non-valid CSS characters (punctuation other than hyphens, international characters, etc).

Are you saying that "series-key" would be the key that builds the list, ie would be the custom field added to every post/page in the Serial, and the existing Serial custom field would just be a way of titling the list?

Let's define three custom fields:

1. series-key: the unique serial id for every series. only alfabet and numeric standarized symbols. This will be used only to build the lists (it will not appear in the list formatting itself).

2. series: the title of the series (or whatever we want to put between pre-text and post-text of the formatting).

3. series-chapter-title: the name of the chapter that will appear in the series list.

Let's say we have two entries of the same book:

One entry with:

Title: The Lord of the Rings, chapter 1
- series-key: rings
- series: The Lord of the Ring, first chapter
- series-chapter-title: Chapter One

Title: The Lord of the Rings, chapter 2
– series-key: rings
– series: The Lord of the Ring, second chapter
– series-chapter-title: Chapter Two

With your 1.1 programming, what people would see (in both entries) is (I put in bold my comments, in cursive what people see:

You are Reading: The Lord of the Rings (your series key). Full index:

The Lord of the Rings, chapter 1 (the title of the entry)
The Lord of the Rings, chapter 2 (the title of the entry)

My proposal is this:

when people read the first entry, what they would see is this:

You are Reading: The Lord of the Rings, first chapter (my series key). Full index:

Chapter One (not the title of the entry, but the series-chapter-title)
Chapter Two (not the title of the entry, but the series-chapter-title)

but when people read the second entry, what they would see is this:

You are Reading: The Lord of the Rings, second chapter (my series key). Full index:

Chapter One (not the title of the entry, but the series-chapter-title)
Chapter Two (not the title of the entry, but the series-chapter-title)

I hope I made myself clear

Ade said:

I guess the answer depends on whether users need to change the CSS on a list by list basis. I'm not convinced (yet) that this is a requirement.

Not a requirement, obiously. A fixed css would be enough in most cases. But sometimes maybe can be fun to change the stiling between lists.

Thanks again.

2:18 pm
December 24, 2009

Ade

Admin

posts 2384

Great description, Javier. That clarifies your proposal very nicely. Thanks. Smile

Yes, I can see the extra flexibility the additional fields would bring.

Dynamic Content Gallery: Have you read the Configuration Guide and FAQ?

6:35 am
December 25, 2009

javier

Guest

Post edited 6:37 am – December 25, 2009 by javier

Just for downgrade compatibility, I would change the names of the keys I suggested:

List of keys:

- Serial-Chapter: new name for previously explained "series-chapter-title"

- Serial-Name: new name for previously explained "series"

- Serial: the same key you use in 1.1 version (new name for previously explained "series-key").

In programming some "if" should be added for downgrade compatibility, when building the list:

- If Serial-Name does not exist, use Serial instead.

- It Serial-Chapter does not exist, use Title of the entry instead.

Regards.

11:42 am
December 25, 2009

Ade

Admin

posts 2384

Thanks for the suggestions. As mentioned on the other thread, I'm going to see if I can implement your proposal without using custom fields. I'll come back to this in a couple of days (a bit tied up with Christmas and family at the moment Smile ).

Dynamic Content Gallery: Have you read the Configuration Guide and FAQ?

Page: 1