Thomas, This structure seems counter-intuitive. The Blueprint file structure exists for a reason and the file "magic" (auto-loading my-(screen| print|ie).css) is meant to help bundle a user's custom CSS with the Blueprint output.
I'd suggest you generate the custom files and move the generated files afterwards. On Apr 8, 10:25 am, TomasGF <[email protected]> wrote: > I found out another approach using custom_css. > > My critique would be that I prefer to have the custom_css inside the > src directory and not in the output one, as these files are pre- > production ones. Therefore, I modified compressor.rb accordingly: > > src_path = Blueprint::SOURCE_PATH > > - overwrite_path = File.join(destination_path, (custom_css || > "my-#{current_file_name}")) > + overwrite_path = File.join(src_path, (custom_css || "my-# > {current_file_name}")) > > Now I can add this to settings.yml: > > myProject: > path: /path/on/my/server/css > custom_css: > screen.css: > myProject/screen.css > ie.css: > myProject/ie.css > > and so on. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
