I said to hell with it and put all the related images in a slideshow alongside the entry.
On Jul 25, 11:05 am, "Kai Kuehne" <[EMAIL PROTECTED]> wrote: > Hi Patrick, > > On 7/25/07, Patrick <[EMAIL PROTECTED]> wrote: > > > What I did in one of my projects is to use a JS editor (at this point I > > opted for WYM Editor), which has a function to insert image tags if you > > give it a URL. I think that is the most-widely used approach. > > I don't like such editors, so this isn't an option. > > > In my project, I also have a photo gallery app, which members can use to > > upload and organise their photos. They can grab a thumbnail image > > location using their browser context menu and paste it (or I could > > provide the whole img tag with a 'src', 'title' attributes wrapped in an > > anchor tag pointing to that page, I haven't decided on it yet.). > > > The photos are not related to a blog post entry, as they could also > > include photos from other sites, if they wanted. > > This is exactly the point where I stuck. Actual there is no need > for a relation between Entry and Image because in the template > filter-solution you can refer to every image via $image[id] no matter > if its related or not. I just wanted a list in the Entry admin page > so the user can see the available images and the corresponding ids. > This looks like: > > 1: blog_entry_images\343566.jpg > 2: blog_entry_images\36767jhjg.jpg > > If there were a possibility to show up such a list without having > a relation, this would solve my problem. > > (In the version a posted above, I have a problem. I try to explain: > If you select image A from the list and insert "$image0" this works > great. But after saving if you select image B an use "$image0" to > refer to it, it will still include image A instead of image B.) > > > The problem is that if the image is not available anymore, I have no way > > of checking it and it won't show in the post. > > I don't understand the problem, sorry. If the image isn't available, you > cannot show it. :) > > > The way you designed it ensures that the image(s) remain with the post, > > so to speak, but how do you decide how to display them within the post > > body text? > > I'm still not sure whether to use the templatetag-solution or the replace- > some-weird-placehoders-before-saving solution. In the latter I just include > them via markdown (which is applied after replacing $imageX with the > actual image path). > > Thanks for your answer! > Kai --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
