Hi,
Excellent module, for which we were waiting for a long time....
At chintha.com, we have a monthly magazine and is currently created with the help of book module. But we are going to use epublish for our future editions. You can see the magazine at www.chintha.com/tharjani
Every month we have a cover page for that edition. So is it possible to have an option to specify cover page image? It can be similar to the url option for the pdf. On the index page, the image will be at the top and the index of the current edition will be below that cover page image.
thanks for the excellent module!!
Paul
www.chintha.com
Comments
Comment #1
mhutch commentedIndeed that would be a nice feature. However, I have a workaround - add an html image tag to the edition description. The img_assist module will generate it for you.
Might I add a description field for the volumes to the request?
Great module btw!
Comment #2
sheldon rampton commentedMikalH wrote: "I have a workaround - add an html image tag to the edition description."
In fact, that's exactly how we intend for the "description" field to be used. The most common use for the description field is that you can enter text into it. However, it can also contain a URL or anything else you want to put there. Also, the functions that display layouts, editions, volumes and publications are all themeable, so you can override the default functions and use "description" any way you want. On our website (www.prwatch.org), we themed it so that all we put into the description field for each edition is a path to a PDF version of that edition, and the theme turns that URL into a clickable image.
With a little ambition you could also use the description field to pass through multiple parameters, entered as XML or CSV or whatever encoding scheme you want.
Initially when I started to develop this module, I thought I'd put in several fields, one for an optional URL, one for an image path, one for a description, etc. Eventually I concluded that this approach would put too many constraints on the type of supplementary information that could be passed through to the layouts, and no matter how many fields I provided, there'd always be some unanticipated use that predetermined fields wouldn't accommodate. (For example, what if someone wants to add an MP3 or a video feed?) In the end, therefore, I decided that the best approach would be to have a single field, with theming providing flexibility in how it gets handled.
Comment #3
mkpaul commentedThanks a lot. I never thought that I can use html tags in description field. Excellent!! We will be moving to epublish soon.
thanks,
Paul
Comment #4
Patricia Barden commented