First time I've had a look at it since my presentation.

Alright, enabled registrations, simplified group.py controller logic and
added a search feature to the events page.

Could I please get some advice—i.e.: code-review—and suggestions on how to
scale it—e.g.: where+when to cache and how to reduce # of db queries?

Also I should be able to directly reference the group name from the events
table, rather than just its ID. This would save many queries and simplify
my code. How can I do this?

Thanks for all suggestions,

Samuel Marks


On Fri, Aug 3, 2012 at 4:58 AM, Derek <sp1d...@gmail.com> wrote:

> Looks good. I would like to see how exactly I can login via facebook. All
> I see on your demo site is a login page - no signup, no 'login using
> facebook'. It's quite ugly, but I won't hold that against you, it looks
> better than most websites I create.
>
>
> On Thursday, August 2, 2012 9:56:54 AM UTC-7, Samuel Marks wrote:
>
>> With meetup.com, groupspaces and even facebook groups rising in
>> popularity; it is only fitting that an open-source alternative be developed
>> at the same time.
>>
>> Currently *GiantPicnic* supports:
>>
>>    - CRUD groups
>>    - CRUD group events
>>    - Join/leave groups
>>    - RSVP to group events
>>    - View profile
>>    - Facebook login
>>    - Mobile apps made with PhoneGap
>>    - An API exposed for doing common tasks
>>
>> With more features to follow, including:
>>
>>    - Membership dues
>>    - Per group and per event management
>>    - Sellable event RSVPs (i.e.: tickets)
>>    - E-commerce
>>    - Threaded group and event comments
>>    - Section for ranking of suggested talks/topics
>>    - Fine-grained RBAC within groups
>>
>> Source: 
>> https://bitbucket.org/**SamuelMarks/giantpicnic<https://bitbucket.org/SamuelMarks/giantpicnic>
>>
>> I've released it under a BSD license—with one extra condition, so feel
>> free to send me merge requests
>>
>> This is my first web2py project, so you will notice a bit of hacky code
>> here and there, and lack of caching. Please recommend where+when I should
>> cache, and how to de-hackify the code.
>>
>> Thanks and I hope you enjoy my project,
>>
>> Samuel Marks
>>
>  --
>
>
>
>

-- 



Reply via email to