Hey ShiftShane, congrats on getting your site up man! That's fantastic. I am also looking to add photo capabilities to my events model--I'd like to incorporate a promotional photo, as well as the ability for a promoter to add photos of the event--have you had any luck so far? Looking at the photo controller, it looks like it is entirely connected to "user" objects...any ideas on how to associate photos with an "event" object?
I'm rather noobish with this stuff, and this, honestly, seems like it could cause disastrous clutter-- perhaps create a user for each event, and associate that user with photos? I'm sure somebody else has a much better idea out there.... Throw a dog a bone? I also need to add an RSVP funtion...how is that going? Thanks! On Feb 18, 9:26 am, shiftshane <[email protected]> wrote: > Sorry for the delay. Been really busy. > > I'll be working on extending the blog area soon. I'd love to be able > to contribute my code back to CE, but like I said in my original > posting, I'm a noob and haven't actually used testing yet (I know, > I'll step in front of the firing squad now). I definitely need to get > on that. Any books or articles anyone might recommend? > > I also haven't gotten around yet to making the events model > polymorphic. I think I want to try to tackle two birds with one stone > and work on making a "groups" function at the same time, as the groups > and events seem to have very similar structures. Was the "groups" > branch in git ever updated with code? > > As far as the UI, I am indeed using the 960 grid system (960.gs). I > had never used YUI before, and even though HAML looks extremely easy > and quick to code, I didn't have the time to learn it properly. So, I > had to rewrite every single view to use my own design for it. I think > there were only a couple partials that I were able to leave intact. > > Stuff I'm currently working on: > Adding sitewide timezone support all the way down to each user. > Adding a sitewide "messaging" area where we can post important updates > that each user sees and then after they see it they will have the > ability to "hide" it so it doesn't show up again. > Integrating private messages between users (saw a few rails plugins > for this) > Implementing groups and more advanced events (like I mentioned above) > Adding geomapping visualization by putting each user on a googlemap > based on their zip code so they can see how they connect to eachother. > Will probably do this more specific to our site, where it maps the > users who are all in the same art project together, but maybe will add > the mapping feature for users to see their friends or something. > Adding individual profile display preferences so the user can turn on > or off what "elements" show up on their profile page to the public > (ie. their location, birthday, photos, etc) > > As I mentioned above, once I learn testing, I will definitely pitch > the code back to you for inclusion in CE. It helped me so much > starting out, and I would love to contribute back to it! > > Also, as I'm working on these modifications and adding new features > and stuff, would it benefit anyone if I make a new thread for each > thing I'm working on with tips and workarounds that I run into while > working on them? I got tons of little "hacks" I did for various little > things in CE that might help, too. I could make a thread full of easy > hacks and tips, too. > > Anyway, thanks again for your hardwork with CE, Bruno! > > On Feb 11, 3:21 pm, Bruno Bornsztein <[email protected]> > wrote: > > > As I said before: well done. My comments below .... > > > As far as some issues I ran into, the biggest point of confusion was > > > > how to modify the models without overwriting the pluginin's code to > > > allow for easy updates. When I first started the project, I was > > > retarded and kept overwriting them with little tiny tweaks. I > > > eventually just made a new duplicate model in my own models folder for > > > anything required changing. I remember seeing something in the FAQs or > > > in the google group about a way to submodule the models, but I didn't > > > get a chance to do that. > > > Yeah, subclassing CE's modules is probably the best way to go (I've done it > > a lot on TennisMetro, where, for example, a tennis > > bulletin<http://www.tennismetro.com/states/ca/metro/los-angeles/bulletins>is > > just a subclass ofEvent). This area obviously needs to be documented > > better and formalized to makes things easier for people. > > > Another thing I overrode was the need to supply a birthday upon sign > > > > up as well as getting rid of the account activation stuff. To do that, > > > I just removed the validation for the birthday in the user model, and > > > made the create account action add the current time in to activated_at > > > column for the user model (@user.activated_at = Time.now). > > > Nice hack. This is an example where subclassing the model for such a small > > tweak doesn't seem right. I need to think of a better way to allow this kind > > of customization without too much work. > > > A big area that I changed was the original focus in CE to have > > > > everything centered around blog posts. Our community is really > > > centered around our art "projects" and the images that people upload > > > to it. In fact, I have yet to actually implement the blog feature as I > > > want to go in and really tweak it to allow users to connect blog posts > > > with their project submissions orphotosubmissions or other items or > > > assets (I'm thinking a polymorphic table that connects a post to an > > > item). > > > If you get around to doing this (allowing any post to be polymporphically > > connected to another model), I'd love to see the code for possible inclusion > > in the core. > > > > I created my own "events" functionality because the CE one was pretty > > > limited. I needed events to have the option to "belong_to" a project, > > > but also be on their own. I'm working on adding the ability for users > > > to RSVP to events as well as upload pictures that they shot of the > > >event. > > > Again, I'd love to see this code to see if we can work it back into CE's > > core. > > > > I know there are a ton more areas that I modified that I will think of > > > later. I'll keep posting more stuff as I think of it. If anyone has > > > any specific questions about how I handled anything, please feel free > > > to respond to this thread and I'll try to help you out. And again, I > > > want to give you another huge thanks, Bruno, for making CE. Oh, and a > > > congratulations on the baby! > > > Thanks (the last three weeks have been crazy). > > I'd love to hear a little more about how you customized the UI. Looks like > > you're using a completely different CSS framework (960 vs. YUI). Any > > lessongs learned from doing this? Did you have to rewrite every view in the > > app? > > > > Shane > > > > On Feb 4, 4:21 pm, Bruno Bornsztein <[email protected]> > > > wrote: > > > > Wow. This is impressive... nice work! Noob? I think not. Looks like a > > > very > > > > well-skinned install of CE with lots of cool custom functionality. I > > > > (and > > > > I'm sure others) would love to hear about some of the > > > challenges/solutions > > > > you encountered using CE for this project. Did you save time versus just > > > > building from scratch? > > > > > Thanks for sharing! > > > > Bruno > > > > > On Sat, Jan 31, 2009 at 11:26 AM, shiftshane <[email protected]> > > > wrote: > > > > > > Hey Bruno and everyone else! > > > > > > I want to thank you, Bruno, for taking the time to make such an > > > > > excellent base for us to work off of. It still took forever (mostly > > > > > because I'm kind of a n00b), but I finally rolled out our new site > > > > > this week. I built a shopping cart in to it, extended thephoto > > > > > capabilities, added comments and tags to new models, etc. > > > > > > I imported our old users, so we started strong with over 5,000 users, > > > > > but it's so cool seeing everyone interact with eachother and comment > > > > > on eachother's artwork when given that chance. > > > > > > Thanks again, Bruno! > > > > > >http://www.arthousecoop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CommunityEngine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/communityengine?hl=en -~----------~----~----~----~------~----~------~--~---
