-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about tabs #26
Comments
How about this? import {MaterializeDirective} from "../../src/index";
import {Component} from "angular2/core"
@Component({
selector: "tabs",
directives: [MaterializeDirective],
template: `
<div class="row">
<div class="col s12">
<ul class="tabs" materialize="tabs">
<li class="tab col s3"><a href="#test1">Test 1</a></li>
<li class="tab col s3"><a class="active" href="#test2">Test 2</a></li>
<li class="tab col s3 disabled"><a href="#test3">Disabled Tab</a></li>
<li class="tab col s3"><a href="#test4">Test 4</a></li>
</ul>
</div>
<div id="test1" class="col s12">Test 1</div>
<div id="test2" class="col s12">Test 2</div>
<div id="test3" class="col s12">Test 3</div>
<div id="test4" class="col s12">Test 4</div>
</div>
`
})
export class Tabs {
} |
@rubyboy well, it working just fine :) |
@rubyboy unfortunately it's working well with my seed app (HashLocationStrategy) Any suggestion? I will for sure write a blog post "How to" After I resolve this issue :) |
I've added the simple tabs example to the repo. Also, deployed the latest version (bundled) to http://angular2-materialize.surge.sh . |
Thanks for helping me, simple tabs are working nice :) But it looks like at http://angular2-materialize.surge.sh routing tabs are failing :( |
I just needed to deploy the latest version (after the angular upgrade) :) |
Yes, almost everithing is fine now :) and for path location strategy resut is unknown because we made decision not to go for angular2 so quickly :) Wait until it will be stable and more UI components will be available :) |
Yeah, unfortunately things still break with every beta release. I wish it was most stable and we wouldn't need to make changes every week or two :( |
I want to use tabs like in original materialize-css project. And In you exampel tabs are used only for navigation. Do you have any suggestion how to implement them to follow original structure?
I don't want to use brute solution like bunch of
*ngIf
calls...(and not sure if it is really possible)In other hand it's quite nice to load content for each tab separately...But it looks too complex because not all pages contain tabs (in my app)... And each page that contains tabs contains different set of tabs....
I'm open to hear any suggestion :)
The text was updated successfully, but these errors were encountered: