#emberjs

It might be worth a shot, it's gotten pretty solid

jkarsrud, Does ember-cli support crafting the index.html by injecting the built js and styles for production and such?

we use ember-cli on all our ember projects now, and quite honestly I can't see why you wouldn't use it for new projects

T-Co: Yep

I have to give it a go then

jkarsrud, Can I run test with mocha and expect.js?

not sure about expect.js, but you have https://github.com/switchfly/ember-cli-mocha for mocha testing

cool

I have karma now running mocha and expec.js

There is a lot of migrating to be done. Let's see if I have the time to take it all in :)

right. Shouldn't be a problem to get it over to testem + mocha and expect though

I don't know if there are plans to make the runner pluggable

T-Co: maybe you should try it on a new project, to get to know it a bit better, and know if you can take the time to migrate? :)

hello!

Hello! I know it's not a good practice to declare a model inside a controller. Anyone knows how to declare a model inside a controller without using a route?

sprinkle: So like instantiating a model inside a controller?

What are you trying to do exactly?

yes @pzu

I have a modal-dialog and I am not using a route for it

but I need to get a different model than from the parent controller

sprinkle: Well you could use route actions to instantiate the model

but inside the controller?

jkarsrud, Yeah. I have 2 ongoing projects now using Ember. Let's see if I have the time to look into it with the third :)

sprinkle: You could pass a model into the action that opens the dialog and set that as the model on the dialog-controller

Actions can be triggered from within the controller, I would put this particular action on the route for separations of concerns

controllers tend to be computed properties and state, routes tend to be data management

is it correct that the itemController in #each is deprecated? thought this would be case, but I can not find any information on this...

how do you create a readonly computed property in the non-prototype extension way?

but I have a parent with some list, already with a modal. When I click to open the modal, I have the openModal action. But the model for the modal, is totally different than the one from the parent

pogopaule: Not sure if it's deprecated just yet, but I think they plan to do it as they remove controllers completely

amk_221: Does it need to do something special, or will this work? http://emberjs.com/api/classes/Ember.computed.h...

jkarsrud: ok thanks

jkarsrud: but how can I have 2 different models in a route?

sprinkle: you *pass* it in through the action, you don't use the model from the parent

`?

but I need to use a different model on the parent.

sprinkle: So you can render the modal with a different controller

and set the model on *that* controller

yes, I am doing that. It's a different controller

and I have the model defined on that controller, but Ember is ignoring that model

so you can set the model on that controller via the action that triggers the modal

can you gist your code?

Is there maybe an upgrade guide for migrating to a prototype extension-less addons? Not really sure how `.observes('foo').on('init')` should be migrated.

jkarsrud: I'm being daft, that's what I want, but I only know how to use it .property().readOnly() How do you do Ember.computed.readOnly?

Like they do it in the example?

martndemus: that's my problem too. I don't know how to chain them

Ember.computed === .property()

Ember.computed.readOnly === .property().readOnly()

right

do i `on('init', observer('foo', function() { }))`

pzu: https://gist.github.com/daminufe/3870ebb8b0d787...

martndemus: not sure. would like to know

jkarsrud: ty

martndemus: that does actually work for me.

I haven't tested it tbh, I at first wrote fooDidChange:

`fooDidChange: observer('foo'), initFoo: on('init', function() { this.fooDidChange() })`

amk_221:

amk_221: I think you can chain them though?

jkarsrud: observer().on() does not chain without prototype extension

what about the other way?

thats possible

because observer returns a function

I was thinking they might return something from 'on' that would make it chainable

ah, so does on

so I guess they're not chainable then

but actually separating them seems to be a better pattern to me anyway, because they could call "private" methods

jkarsrud, When using link-to and I have a nested route. How to retain the first id and just change the latter?

you need to pass both

iirc

when they both have dynamic segments, I mean

Does anyone have a clue what 'Properties can only be defined on Objects.' means, stack trace is not helping me. Is also triggered by disabling PE.

martndemus: are you trying to make a property on something that's not an Ember.Object?

jkarsrud: not that i know of