carolinagc / webcalendar Goto Github PK

We don't have to do it ourselves, they did it for us. https://github.com/mcasimir/devise-i18n-views

See https://travis-ci.org/carolinagc/webcalendar/jobs/18156921. This also happens on master.
Run rspec spec/integration/events_spec.rb --order rand:15224 to reproduce

Steps so far:

• Check out from git
• bundle install
• bin/rake db:migrate RAILS_ENV=development
• rails s

When locations are created and the dropdown menu appears in the Events create view, once you've selected a location and saved the event, an alert message will appear on top saying "Error, something went wrong" but actually the location was associated and everything seems to go ok.

Good resource tutorial:
http://reefpoints.dockyard.com/2014/05/07/building-an-ember-app-with-rails-part-1.html
http://reefpoints.dockyard.com/2014/05/08/building-an-ember-app-with-rails-part-2.html
http://reefpoints.dockyard.com/2014/05/09/building-an-ember-app-with-rails-part-3.html
http://reefpoints.dockyard.com/2014/05/31/building-an-ember-app-with-rails-part-4.html

Even this is use a EmberCLI and Broccoli instead of Grunt (or similar), I found very interesting for us in order to understand how organise our Ember/Rails project

I like a lot their clear division in two subfolder:
WebCalendar
|_ _ Rails
|_ _ Ember

https://github.com/bostonember/website

For what I got the division is more or less like:

Ember:
Js test
templates (with Handelbars)
stylesheets
define models (which kind of data they are)
routers
bower.json
grunt.json

Rails:
model
data
routes
controller
BE tests

This will involve some refactoring of tests... More info here http://www.andylindeman.com/2012/11/11/rspec-rails-and-capybara-2.0-what-you-need-to-know.html

Using the English localization as a basis, feel free to create new locales or fix existing ones. You can even do this from the GitHub editor.

To get started:

1. Fork the repository
2. Pull up the right locale file in config/locales on your fork.
3. Compare the locale file you want to improve with the English locales, making updates to your locale file.
4. Submit a pull request with your changes.

If you have any questions, feel free to ask by creating a comment below.

There's a gem that can take on a lot of the heavy stuff: https://github.com/icalendar/icalendar/
#16 needs to be finished first

This is related to voormedia/rails-erd#65 as we are using i18n tasks.

However, running erd still works.

Currently events are independent of each other and don't belong to a specific calendar.
As discussed in #2, in the initial version, a user should be able to:

• Add a new calendar (New users should start with an example calendar to start off with)
• Add events to the calendar
• Remove events from the calendar
• Remove the calendar, including all events
• Share the link to the calendar

What we have to integrate:

• Ruby on Rails (Rake and Sprockets)
• Ember.js (Bower and Grunt)

Solutions:

1. Get rid of Sprockets and totally relay on GruntJS through Gruntfile.js
   Write a Gruntfile.js which can compile, minify and build.
   http://blog.pedago.com/2014/01/21/goodbye-sprockets-a-grunt-based-rails-asset-pipeline/

I like a lot but I guess it required a very good Gruntfile and knowledge of grunt.
It will take more time but is for sure a good way to learn.

2. Using Yeoman
   http://www.emmanueloga.com/2013/07/23/Using-AngularJS-with-a-Rails-backend.html
   http://www.base2.io/2014/03/14/using-multi-buildpacks-to-deploy-a-yeoman-bower-grunt-application-on-rails/

I”m not so sure that this solution is actually helping us or it just make us use another tool.
Anyway using another tool but for good reasons, let’ go for it.

3. Use just rails (Ember gem)
   http://robots.thoughtbot.com/emberjs-with-a-separate-rails-api
   https://github.com/dockyard/ember-appkit-rails
   http://www.ember-cli.com/

This will not allow us to separate easily BE and FE. If the project will grow up we’ll probably have some trouble.

I want to highlight this sentence which i totally agree with:
“While it is possible to include AngularJS(or Ember for us) as part of the rails assets, I think it is better to setup the angular code base on a standalone folder, leaving the rails app as a (more or less) isolated backend.
By keeping the frontend isolated from the backend you get an amazingly fast development environment and draw a clear line between backend and frontend (great for making sure you are writing the right unit/integration tests).”

Other questions:

• Don’t commit and ignore .css files
• Better solution for main.css file? Right now we compile in local, not commit it and then compile in deploy, but seems not really working because main.css is not ignored! (we have to uncommit every time!) and it always give a problem during deployment

Good Practice:

• Don’t commit /bower_packages. Just bower.json WITH packages versions specified!
  Write a bower init task on deploy task

Hey,

this came up when @carolinagc told me about the calendar project and I just wanted to know how far we could take this.

It would be nice to have a service like etherpad.org but for creating calendars. Right now, there's not a lot of web calendars out there, so I think this is something a lot of people would like.

There would be no user login required, to keep things simple for the user.
You could exchange calendars by using a random url. Everyone with access to the url would be able to add, modify and remove events.

Add device for authentication

A replacement for the standard rails error pages. It allows you to debug the code from within the browser. If you have used pry before, it's pretty much the same, but in the browser.
See https://github.com/charliesome/better_errors for installation instructions.

How to do the internationalization
http://guides.rubyonrails.org/i18n.html

An event should be able to be public or private. If private public views should not show it and only registered users should be able to see it.