Log message #894781

# At Username Text
# Jul 17th 2009, 03:58 Phally alkemann: will do
# Jul 17th 2009, 03:53 alkemann Phally: add public $displayField = 'username';
# Jul 17th 2009, 03:49 alkemann so u think Article belongsTo User (or UserProfile) ?
# Jul 17th 2009, 03:48 alkemann bah i work from work
# Jul 17th 2009, 03:48 Phally alkemann: no, i'm at work today, off at 15:30, so home at ~16:15
# Jul 17th 2009, 03:47 alkemann Phally: i assume u cant make the changes tothe plugin before later today?
# Jul 17th 2009, 03:11 alkemann dunno
# Jul 17th 2009, 03:11 Phally there was a field named `pos`
# Jul 17th 2009, 03:11 alkemann ?
# Jul 17th 2009, 03:11 Phally pos i.e., still wondering what it meant
# Jul 17th 2009, 03:10 alkemann i removed some
# Jul 17th 2009, 02:59 Phally alkemann: (talking about (user_plug_users))
# Jul 17th 2009, 02:59 Phally alkemann: hmm looks good, are those the existing fields?
# Jul 17th 2009, 02:56 alkemann Phally: http://thechaw.com/bakery/commits/view/adebd98e05ebee3ee8e4922c68268dc7388bc599#highlight
# Jul 17th 2009, 02:53 alkemann right, those cant be in the plugin
# Jul 17th 2009, 02:53 Phally alkemann: yeah exactly
# Jul 17th 2009, 02:52 Phally alkemann: using Modelbehavior::setUp() can be used to
# Jul 17th 2009, 02:52 alkemann u mean User hasMany Articles?
# Jul 17th 2009, 02:52 Phally alkemann: it will get the app specific stuff out of the plugin
# Jul 17th 2009, 02:51 Phally alkemann: well doesn't have to be in lots of places.. before* of the model or something that can call a simple bindWithUser() from the AppModel
# Jul 17th 2009, 02:50 alkemann good night
# Jul 17th 2009, 02:49 pointlessjon i gotta sleep - see you guys tomorrow hopefully
# Jul 17th 2009, 02:49 alkemann Phally: what gain to have it lots of places in controllers instead of model?
# Jul 17th 2009, 02:48 alkemann cake joins different dbconfig tables by default if on same database, but containable doesnt. we cant know about it being on the same db, so maybe just focus on the profile?
# Jul 17th 2009, 02:48 Phally alkemann: how about binding User to the other models on the fly from app to avoid coupling from the plugin to the app?
# Jul 17th 2009, 02:47 alkemann apps needs to work through the user profile i guess,
# Jul 17th 2009, 02:47 Phally alkemann: what about the associations?
# Jul 17th 2009, 02:46 alkemann so user_profiles, groups, groups_user_profiles in the app and just users in the plugin
# Jul 17th 2009, 02:46 Phally alkemann: right, the groups are app specific
# Jul 17th 2009, 02:46 alkemann Phally: and what group user belongs to as well
# Jul 17th 2009, 02:45 alkemann Phally: i just realized that you put group in the plugin, but it has to be in the app
# Jul 17th 2009, 02:44 Phally alkemann: present
# Jul 17th 2009, 02:44 alkemann right
# Jul 17th 2009, 02:43 pointlessjon and with a flag, the category/classification of the flag could shoot the basic message on the page, with an ability to drill deeper to a detailed description of how to address the issue?
# Jul 17th 2009, 02:43 alkemann maybe just member and lower and moderator and higher
# Jul 17th 2009, 02:42 alkemann yea it would make sense to split flags into public, member, moderator
# Jul 17th 2009, 02:42 pointlessjon that actually makes more sense to me personally
# Jul 17th 2009, 02:41 alkemann valid points has been made that it is both hard and destructive to do inline markers, so probably will have to be article wide tags
# Jul 17th 2009, 02:41 pointlessjon containing the flags that may or may not apply / be visible to your user
# Jul 17th 2009, 02:41 pointlessjon maybe it'd be classier to come up with some sort of sidebar block element, etc.
# Jul 17th 2009, 02:40 pointlessjon yeah that was good stuff. personally i think what wikipedia does works well - then again, it's kind of in your face