Граф коммитов

26 Коммитов

Автор SHA1 Сообщение Дата
Paul Osman d5a2d890fb Move emailing to a celery task. Also, email users when they receive a message, someone starts following them or a project they have created. 2010-12-29 23:29:52 -05:00
Paul Osman 36467c8998 Bringing the activity application back 'in house'. Work on generalized work will continue, but for now this is easier / faster. 2010-12-28 21:44:09 -05:00
Paul Osman d6ca62759d Display featured, popular and newest users on people page 2010-12-22 20:43:00 -05:00
Paul Osman 5967a6b398 Use select_related where we know ahead of time we'll be using all of the data 2010-12-22 12:55:09 -05:00
Paul Osman 809af58684 Send the user instance for follow activities, not the userprofile 2010-12-20 21:28:35 -05:00
Paul Osman 7fe2d1486a Remove ContentType from Relationship model. Instead just have a field for Project and a field for UserProfile. Reduces number of queries required by a lot. 2010-12-20 16:28:35 -05:00
Paul Osman daeb551481 Make sure source is a User instance in relationship post_save signal 2010-12-19 19:27:01 -05:00
Paul Osman 47daeb0006 Adding a base model class that uses django-cache-machine. 2010-12-19 19:13:08 -05:00
Paul Osman 185e65b7e6 Merge branch 'master' into caching 2010-12-11 20:15:55 -05:00
Paul Osman 8aeb9bbe4e Removed followers_count and following_count methods. Use followers|length in templates instead. Also added some data to project pages 2010-12-11 00:16:33 -05:00
Paul Osman 18dd77067e Experimenting with django-cache-machine 2010-12-08 15:34:43 -05:00
Paul Osman 7fd0bd7985 Moving activity application into separate project (django-activity) 2010-12-07 20:45:51 -05:00
Paul Osman fdc717ec61 Gardening - cleaning up code, adding tests, removing unused code from relationships application 2010-12-01 16:40:04 -05:00
Paul Osman cf9f2158a1 There's really no excuse for a model to *not* have a created_on field. Also, created_on is a better name than timestamp. 2010-11-29 23:38:57 -05:00
Paul Osman 80ef83b5f7 Add followers_count and following_count methods to models that can be followed / have followers 2010-11-28 16:22:50 -05:00
Paul Osman e5bb17042d Wrap activity sending in a try/catch. in case activity app is not installed, nothing happens 2010-11-12 08:08:51 -05:00
Paul Osman b4f7e66027 Removing unused and ambiguous imports 2010-11-09 23:34:18 -05:00
Paul Osman c9dffb1e84 Simplify checking of source / target in relationship.save 2010-10-28 14:29:05 +01:00
Paul Osman fa72d4dbff Genericize following. Users can follow any object type. 2010-10-21 17:01:58 -04:00
Paul Osman f3da655b30 On second thought, I prefer monkey patching to trying to use mixins in Python 2010-10-13 15:40:59 -04:00
Paul Osman f425d54d79 Coming back from vacation makes you want to do crazy things like scrap all the work in progress you had before vacation. 2010-09-14 18:38:37 -04:00
Paul Osman 1a4d28b39f Filter for user objects 2010-08-25 20:47:08 -04:00
Paul Osman 0e52e05023 Make relationship model type neutral (going to reuse for users following projects, etc) 2010-08-25 17:27:00 -04:00
Paul Osman abbba4d44f Work in progress on adding activity streams with atom feeds 2010-08-25 15:02:33 -04:00
Paul Osman 0c08438e84 Get rid of get_relationships_from and get_relationships_to. Replace with more intuitive methods in a User class mixin 2010-08-20 22:25:37 -04:00
Paul Osman bd576cd834 Very basic user listing, follow / unfollow functionality 2010-07-29 16:11:43 -04:00