Page 1 of 1

pSouper's wishlist

Posted: Sat 15. May 2004, 09:55
by pSouper
hello Oliver et al,
I am revitalising my wishlist so that I may have a home for my thoughts* (*Demands! or the kittens will be sleeping with the fishes tonight ;) )
  • IMAGES Allow a rollover image &/OR a link+_self/_top/_blank etc to be optionally specified for all images including repTags & content parts.
    {IMAGE:myPic.png;mypic1.png} etc.
  • ROLLOVER IMAGES
    • The ability to set the Width*Height of thumbs and the number of row*columns to display them in(replaces the current horiz/vert list).
    • a different colour border for the current thumbnail and the selected thumbnail
    • start loading in all the images once the page has loaded, reducing the wait time between image views
  • Enlarge Image popups to have templates
  • FLASH a new set of flash based image replacement tags for FLASH_IMAGE, FLASH_LINK, FLASH_BUTTON etc.
  • REPTAGS A set of BBCODE style repTags
    • Code
    • Quote
    • List
    • search
    • Smilies
  • CODE The 'code' content part to have 'colour coded' languages via a droplist (extendable as with backend languages) this would allow sites to make code sections easier to read as code.
  • 'BIND_to_NEXT (linking)' toggle Icon on all content parts. This would Bind that content part to the next content part. so, if one content part is moved down by one, and it has been bound to the next, they would both be moved down by one. this would maintain there reletive order.
    If you bind cp1 to cp2 and cp2 to cp3 and cp3 to cp4 then move any of those cp's down by one then cp1,cp2,cp3,cp4 would all move down by one in a single click.
    If cp3 now has it's Bind toggle switched off, only cp1>cp2 are linked.
    you can not link from cp2>cp4 unless cp4 is moved above cp3 and directly next to cp2.

    I guess it's a kind of parent/child link as with moving structures around currently.

    This could also be go for 'articles' as well as 'content parts'.
more to follow i'm sure :)

...more

Posted: Wed 25. Aug 2004, 17:54
by pSouper
  • STRUCTURE editing: extend the structure area in the backend by showing articles as well, these would also have a cut/paste, moveup, movedown & visible icons allowing users to move articles across structures

Posted: Sat 28. Aug 2004, 09:55
by pSouper
  • TEMPLATES: preload all images used in a template and a numberfield for how many images in the content to preload. This would be good for the menu and for some content parts.
  • CONTENT PARTS: the before/after to accept a 3 digit number instead to just two. if you use an image in the summary but little or no text you sometimes must use a larger number than 99 to force the first content part below the summary image

Posted: Wed 8. Sep 2004, 15:42
by pSouper
  • FILE CENTER:'Update file'. Each file in the file center could have an extra Icon that would allow you to update a file. eg. If I change an existing .doc file or image etc, I would then want to update the existing file in the filecenter (database) with the newer version instead of always using a new file and deleteing the old file (as this currently doesn't really delete the file form my server).

email form content part

Posted: Wed 22. Sep 2004, 13:04
by pSouper
  • EMAIL FORM: Templates or Some kind of item formating to place items side by side.
  • new items for date & time specific fields with logic tests for dates.
  • logic tests for phone numbers & emial addresses. as each country has thier own rules to telephone numbers and zip codes so these rules could be alterable in a template or stored in the language file.