• View
  • Changes
  • Options
  • Related
  • Edit
  • , ,  Add +commit
     
  • View
  • Changes
  • Options
  • Related
  • Edit
  • Want to avoid making people come up with a name for a file they're about to upload.

     

  • View
  • Changes
  • Options
  • Related
  • Edit
  • whenever there's a [pointer]+*autoname card. (Apply Ruby's next to get the next name, (1->2, AZ->BB, etc. (We could soft format *autoname+*rform to 0, and update +*autoname whenever we create a card.)

     

    Implement full for Pointer input and implement autoname by right. Then, if:

    • "Working Drafts+*rform" is a Pointer and soft,
    • "Working Drafts+*input" == full,
    • "Working Drafts+*autoname" exists, and
    • "Working Drafts+*options" finds Files or Images, you'd see something like this:

     

    Also see add ability to limit number of Pointer items and add min number of Pointer items

     

    Add +example

     

    Related support tickets: 
    Relevant user stories: 
     add one

  • View
  • Changes
  • Options
  • Related
  • Edit
  •  

    Thoughts:

    1. why have special functionality for images and files when we might want these for lists of any type?
    2. right now we only have one interface for adding new cards, and there are a lot of good code reasons for trying to keep it that way.
    3. Seems weird to take away the old way, at least if there are still examples of people wanting to reuse already uploaded cards
    4. also seems weird to make people make several correct clicks in order to see an upload button.

     


    My current thought is that this needs to be done as a new pointer type. more later

      --Ethan McCutchen.....Fri Feb 18 10:31:34 -0800 2011

     

    Notes

    add a note

    Download Docs Sandbox Hosting Support

  • View
  • Changes
  • Options
  • Related
  • Edit
  •  

    Wagn News

    1 to 5 of 24Next-page 1 to 5 of 24Next-page

     

    Ideas

     

     

    Support Tickets



    Wagn at github

    Wheeled by Wagn v. 1.7.2