search

nsabiyera / Oak

Frictionless development for ASP.NET MVC single page web apps. Prototypical and dynamic capabilities brought to C#.
http://amirrajan.github.com/Oak
MIT License
6 stars 7 forks source link

Peeps sample app to include EmberJS #39

Open amirrajan opened 11 years ago

amirrajan commented 11 years ago

Peeps is one of Oak's sample apps. Currently it shows how Oak can be integrated with Plain 'Ol jQuery, BackboneJS, BackboneJS+Marionette, AngularJS, KnockoutJS. Needs EmberJS (it's kind of there, but not fully implemented). If you don't know anything about Ember, and would like to learn, this is a great way to start! Here are instructions on how to get the sample app up and running. http://amirrajan.net/Oak/#peeps

eugman commented 8 years ago

I'm on it.

amirrajan commented 8 years ago

\o/ yay!

Everything in the peeps sample app should be self contained. So you should be able to work in there and not have to muck with any of the Oak source code.

Also, feel free to upgrade the project to ASP.NET MVC5 if you'd like (we can make that another up-for-grabs issue if that makes more sense).

eugman commented 8 years ago

I'm hoping right now to get some quick wins first. I'm excited about my first pull request. So far I've got the project to run, but need to get the SQL piece working.

amirrajan commented 8 years ago

you should be able to run rake reset that should gen the database for you.

amirrajan commented 8 years ago

Typing rake -D should give you all the available build tasks

eugman commented 8 years ago

Woot. I got everything running now, thanks for the help. Now to build out the Ember part.

amirrajan commented 8 years ago

Hopefully it wasn't too painful. Any feedback? Do these instructions need to be updated?

eugman commented 8 years ago

As a new person coming in, the layout made things a bit painful. I didn't even realize there were app-specific instructions.

I kept bouncing between "First Time" and "Start Coding Now", thinking that those steps were representative and that I was just missing something. I honestly assumed I just needed to figure out what to edit in the web-config and some ORM-voodoo-Magic would happen when I ran the app.

When I saw things like "Growl", "Continuous development", and all the video titles, I thought "Oh this is all whatever.js type bonus features to make the development experience easier." So I would scroll back up. It wasn't easy to tell which parts were essential to the experience (rake tasks) versus convenience (canopy/scaffolding).

When I did scan through the sample apps section, the beginning part only talks about downloading the source, running bundler and installing VS 2013. So I assumed that there weren't any other "getting started" instructions there. And even when I looked at the specific apps, the big focus was on the app description and especially the JS libraries it supported. So I never even realized there were special instructions for each app.

It's a little embarrassing to have made such a simple mistake, but scanning on the web is really common. I'll put together an issue with some suggestions. If you are okay with the suggestions, I can make a pull request with the changes.

amirrajan commented 8 years ago

That would be really helpful thank you. Anything that makes the next person not feel the pain would be great :-)