[buddypress-trac] [BuddyPress Trac] #6290: Avatars, an extensible UI

buddypress-trac noreply at wordpress.org
Sat Apr 4 00:27:42 UTC 2015

#6290: Avatars, an extensible UI
 Reporter:  imath                   |       Owner:  imath
     Type:  idea                    |      Status:  assigned
 Priority:  normal                  |   Milestone:  2.3
Component:  API - Avatars           |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |

Comment (by imath):

 Replying to [comment:37 DJPaul]:
 Let's just call it `/bp-legacy/buddypress/assets/_avatars/`.

 it wouldn't be "juste" actually :)

 > I don't see why this directory should be called attachments

 Because we are "visionnaires", we can predict the future :)

 More seriously, here's how it's organized now :
 `assets/_attachments/uploader.php` < this template can be used '''by any
 component or feature''' requiring a file upload ('''not just Avatars''').
 `assets/_attachments/avatars/index.php` < the main avatar template file
 that is using the above file and the following ones
 `assets/_attachments/avatars/crop.php` < the cropping template
 `assets/_attachments/avatars/camera.php` < the camera template

 Here's how it could be after a few releases :

 What you suggest is:

 imho it's not the best organization. It means the uploader will only be
 used for avatars forever. But I understand your concern. If the name
 `_attachments` is annoying, let's use something else.. What about
 `_files` ?

 I guess we can do `assets/_avatars/` for the introduction of the feature
 of course, but we'll need to change it as soon as we will use uploads in
 another component.

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/6290#comment:38>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac

More information about the buddypress-trac mailing list