what happens w/ multiple uploads of same image name w/ current attachment_fu setup?
--Lewis Hoffman.....Mon Mar 23 16:40:04 -0700 2009
in general, if you call create it seems to put it in a new place each time.
--Lewis Hoffman.....Mon Mar 23 16:58:54 -0700 2009
gonna try rendering from db, just to see how it goes, and see if it's easy to switch off between db & file.
--Lewis Hoffman.....Mon Mar 23 17:11:51 -0700 2009
got new image working end-to-end last night. today working on
* √editing & revisions
* √accessing image sizes via transclusion syntax (ok this is working but it's a total hackjob)
* √check multi-edit -- seems good
* √case that card is saved before file/image is uploaded/interface -- added some interface here
* √files as well as images -- this requires some significant refactoring.
* migration
* permissions checks (see next comment)
--Lewis Hoffman.....Wed Mar 25 12:24:53 -0700 2009
thinking that upload permissions should be global-ish. ie. anyone who can create image cards can upload image files, anyone who can create file cards can upload files. this creates the odd case where if you have edit permission but not create permissions effectively you can't edit. the other way- you have create permission but not edit, also isn't perfect, you can upload but won't be able to associate the file with any card. both of these seem ok to me.
--Lewis Hoffman.....Wed Mar 25 14:06:14 -0700 2009
would be nice to have it re-populate the iframe after upload, so you could do it again if something looked screwy. involves modifying API and implementation of responds to parent.
--Lewis Hoffman.....Wed Mar 25 15:33:39 -0700 2009
--John Abbe.....Tue Apr 07 16:24:11 -0700 2009