Hi Josh, On Aug 26, 11:42 am, Josh Clayton <[email protected]> wrote:
> As for a solution, I don't have one that I support 100% as semantic > classes have always been a very rudimentary solution to a complex > issue. You could copy these semantic classes to your custom > stylesheet and modify them as needed. Yes, this is what I initially did to debug what was going on and it probably remain the neatest option. > The other solution that I've > been looking into is using LESS (http://lesscss.org) and using the > mixin capabilities. However, LESS doesn't work with the span-X > classes (yet) - if you go to the issue page for this bug (http:// > github.com/cloudhead/less/issues/#issue/62), you can vote the issue up > by clicking on the up arrow next to the issue title near the top of > the page to let him know the resolution of this issue is important to > you. Yeah, I already saw that and voted for it. Seems like the author of LESS is already committed to it, though. Good stuff. > A third solution would be to write some patches for Blueprint to > achieve what you'd like to do. Yes I am considering this. I'll play around some more and see if it is going to be worth it. Thanks Josh, your clarifications have been very helpful. Cheers, Charles --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Blueprint CSS" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/blueprintcss?hl=en -~----------~----~----~----~------~----~------~--~---
