-
Notifications
You must be signed in to change notification settings - Fork 10
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
Icon Support #4
Comments
yes to rename the project, starting with the nuget package id. |
By "there" I'm figuring you're meaning the Twitter.Bootstrap.Mvc project...so, it likely makes sense to leave the interfaces for rendering here as well, and put the Bootstrap implementation of rendering in Twitter.Bootstrap.Mvc. |
Yes. Sorry about the vauge pronouns.
|
:) |
Okay...so, some simple interfaces here, and we'll do the actual Bootstrap implementation in the TBM project. I like that. That will mean moving the icons...no biggie...and the rendering helpers. I like that though, cleaner. I'll be able to pick things back up on Monday evening, checking out for the weekend. |
Please note that there already is a similar icon helper class in TBM, in the htmlhelpers package. |
Ah, cool, thanks @serra. The helper there will be a good foundation for that, too, but I do prefer the c# style casing. Any objections to that? |
No objections to that - considering TBM is a bootstrapper, I don't necessarily mind breaking backwards compatibility. As long as we don't have multiple icon support implementations, I'm happy. |
We had talked about plugging in the icons so I dug up a class I made before Christmas with the icon names. The more I look at it, the more I think we should do a separate package for the rendering bits, and leave the nav base implementation and rendering interfaces in the NavigationRoutes project (which...I think we agreed we're going to rename to NavigationManager).
The text was updated successfully, but these errors were encountered: