- Status
Awesome work!
@Fillmore may I start shelling feedback now or it's too soon?
1) Pager is inconsistent with rest of the site, just wrap div.PageNav with new div.pageNavLinkGroup, also add pager at the bottom of the devtracker.
2) Was it necessary to introduce new classes? I fear this decouples devtracker from the main theme so if there is update to theme, devtracker won't reflect that and break. For example instead of div.threadWrapper you can perhaps use div.message ?
Thank you very much for this.
@Fillmore may I start shelling feedback now or it's too soon?
1) Pager is inconsistent with rest of the site, just wrap div.PageNav with new div.pageNavLinkGroup, also add pager at the bottom of the devtracker.
2) Was it necessary to introduce new classes? I fear this decouples devtracker from the main theme so if there is update to theme, devtracker won't reflect that and break.
For example instead of div.threadWrapper you can perhaps use div.message ?Thank you very much for this.
Likes:
engjang
Awesome work!
@Fillmore may I start shelling feedback now or it's too soon?
1) Pager is inconsistent with rest of the site, just wrap div.PageNav with new div.pageNavLinkGroup, also add pager at the bottom of the devtracker.
2) Was it necessary to introduce new classes? I fear this decouples devtracker from the main theme so if there is update to theme, devtracker won't reflect that and break. For example instead of div.threadWrapper you can perhaps use div.message ?
Thank you very much for this.
@Fillmore may I start shelling feedback now or it's too soon?
1) Pager is inconsistent with rest of the site, just wrap div.PageNav with new div.pageNavLinkGroup, also add pager at the bottom of the devtracker.
2) Was it necessary to introduce new classes? I fear this decouples devtracker from the main theme so if there is update to theme, devtracker won't reflect that and break.
For example instead of div.threadWrapper you can perhaps use div.message ?Thank you very much for this.
Awesome work!
@Fillmore may I start shelling feedback now or it's too soon?
1) Pager is inconsistent with rest of the site, just wrap div.PageNav with new div.pageNavLinkGroup, also add pager at the bottom of the devtracker.
2) Was it necessary to introduce new classes? I fear this decouples devtracker from the main theme so if there is update to theme, devtracker won't reflect that and break. For example instead of div.threadWrapper you can perhaps use div.message ?
Thank you very much for this.
@Fillmore may I start shelling feedback now or it's too soon?
1) Pager is inconsistent with rest of the site, just wrap div.PageNav with new div.pageNavLinkGroup, also add pager at the bottom of the devtracker.
2) Was it necessary to introduce new classes? I fear this decouples devtracker from the main theme so if there is update to theme, devtracker won't reflect that and break.
For example instead of div.threadWrapper you can perhaps use div.message ?Thank you very much for this.
I'll go ahead and try out wrapping the Pager, and I'll add it to the bottom of the page as well.
As for the new classes, I agree with you about them not working well between themes, and I want as few of them as possible. I tried to recycle as many standard classes as I could while building the DevTracker. I'll check out using .message instead. I appreciate any suggestions.
Unfortunately, there are some classes I don't think I can get away from, like .threadLeftColumn and .threadRightColumn. The way the thread based navigation works in the Tracker is different than anything else in XenForo and needed a bit of custom work.
Thanks a jillion.
Likes:
Mahdi, Xeevis and engjang
WOOHOOO!!! That's what I'm talking about! Fillmore, god dammit son you must make your mother proud. Keep up the good work, Reaper
Likes:
Faeryl and Fillmore
Devtracker has been updated to fix the RSS feed and add a new icon. Thanks again, @Fillmore!!!
- Status