cmelion

Have you considered a lighter-weight solution? A pure CSS makes for a great cross-framework alternative. http://cssslider.com/wordpress-slideshow-32.html

@pavanpodila agreed

@pavanpodilla: absolutely! I was a big fan of the way we separated routes in SalesLink, where the route was co-located in the same file with the page/component and we just...

I like the idea of .route, similarly I like .async and .async.route but XXXRouteComponent is pretty verbose. See https://github.com/cmelion/generator-ng2-webpack/wiki/I-hate-that-all-the-files-are-named-index.ts,-style.scss-and-template.html! It might be a good idea to make naming conventions a...

It seems to me that the long-names convention is an artifact of everything being dumped into the same directory in "toy" apps.

I'm ok with the long-names for classes though.

How about just naming it routes.ts and putting the file directly under app? ``` // src/app/routes.ts import {Home} from './components/home'; // ./components/home/index.ts export default [ {path: '/', component: Home, name:...

Yeah, I was thinking about that, the components are nested, wouldn't just repeating the pattern on the child components work? My reading of http://plnkr.co/edit/Bim8OGO7oddxBaa26WzR?p=preview implies that it would, but sanity...

Upgrade is on my TODO list. I just haven't had time to look at how the new router works. see https://github.com/cmelion/generator-ng2-webpack/issues/45 Happy to accept Pull Requests!

It will be a while before I get to it, but happy to contribute if no one else beats me to it.