Skip to content

Instantly share code, notes, and snippets.

View MelSumner's full-sized avatar
💭
Making the world a more sensible place.

Melanie Sumner MelSumner

💭
Making the world a more sensible place.
View GitHub Profile
@MelSumner
MelSumner / resume.md
Last active January 26, 2018 14:10
Current Resume

ask me!

Rails naming conventions

General Ruby conventions

Class names are CamelCase.

Methods and variables are snake_case.

Methods with a ? suffix will return a boolean.

1. run
bundle lock --add-platform x86-mingw32 x86-mswin32
2. edit lines 35 and 36 of Gemfile
gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw]
gem 'wdm', '>= 0.1.0', platforms: [:mingw, :mswin, :x64_mingw]
3. add to Gemfile
gem 'eventmachine', '1.0.9.1'
@MelSumner
MelSumner / engines-issue.md
Created January 16, 2018 20:07
documentation for ember-engines dependencies issues

Issue analysis

What is happening:

  • Engine teams are building themselves and uploading their engine-vendor.js and engine.js files - the host apps’s build is ignoring/excluding the output from their build & using one that the teams are uploading things to instead.

What should happen:

  • All engine teams should be packing up their engines and coordinating with the host app team on the latest build
  • The host app team should include these engines in their package.json file

Problems this is causing:

Learning JS

Getting Started

  • JavaScript for Web Designers Mat Marquis
  • JavaScript and jQuery by Jon Duckett (protip: take the book to Kinkos and have them spiral bind it)

Leveling Up

  • You Don't Know JS series by Kyle Simpson
  • Up & Going
  • Types & Grammar
@MelSumner
MelSumner / components.cx-navbar.js
Created February 26, 2018 18:03
contextual-navbar
import Ember from 'ember';
export default Ember.Component.extend({
tagName: 'nav',
actions:{
pathSelected: function(path){
this.set('pathToGo', path);
}
}
});

context

  • internal UI addon (hosted on something like an internal npm/artifactory)
  • to use- create ember app, add file to package.json, run npm install.
  • next run ember generate my-addon to run a custom blueprint that does some other stuff
  • it would be okay to set the theme once per app, but it would also be awesome if we could make it so the end user could select a theme from a settings menu (too ambitious?)

options for theming

  • use ember-theme-changer addon?
  • add the option to the blueprint that they have to already run anyway?

What I've tried:

  1. added a theme-service in my addon
  2. added a theme-toggle component in my addon ('theme-toggle.js', 'theme-toggle.hbs', 'theme-toggle.scss' (with an underscore in front)
  3. added a themes.scss (as per the blog post)
  4. added both the component.scss file and the themes.scss file to my addon.scss file.
  5. injected the theme service into the route of the page in the dummy app:
/* iframe with the video does have inline styles, but adding this style will fix the issues with the mobile view.*/
iframe {
width: 100%;
}
/* absolutely positioned divs - remove the absolute positioning, add a class called .call-to-action-wrapper (or something) */
.call-to-action-wrapper {
display: block;
clear: both;
width: 100%;
margin: 0 auto;

Road to 1.0 - an ember-engines roadmap

These are the items that we envision should be completed in order for the ember-engines project to get to version 1.0. This list should not imply an order or priority; all of these items need to be completed before the project can be considered ready for 1.0.

Lazy Loading for Routeless Engines

The ability to lazily load routed engines has proven to be very useful; we'd like to enable the same capabilities for routeless engines. Some work has already started (see ember-asset-loader issue #56).

These are the tasks to reach that goal:

  • write helper
  • write accompanying tests