1 and 2. Blueprint generates the default files in the blueprint
directory instead of blueprint/portfolio. The file screen-custom.css
exist in blueprint/portfolio.
3. I don't know what this means. I'm new to blueprint. The compressor
uses the default values but I'd like to use 60px colums instead of
30px.

But another thing. where do I have to place the settings.yml file?

When I put it in the lib directory (like the example file) I get the
following ruby error

/usr/local/lib/ruby/1.8/yaml.rb:133:in `load': syntax error on line 3,
col 16: `     custom_css:' (ArgumentError)
        from /usr/local/lib/ruby/1.8/yaml.rb:133:in `load'
        from /Applications/MAMP/htdocs/three/css/lib/blueprint/../../
lib/blueprint/compressor.rb:79:in `initialize_project_from_yaml'
        from /Applications/MAMP/htdocs/three/css/lib/blueprint/../../
lib/blueprint/compressor.rb:35:in `initialize'
        from /Applications/MAMP/htdocs/three/css/lib/compress.rb:
149:in `new'
        from /Applications/MAMP/htdocs/three/css/lib/compress.rb:149


On 25 Apr., 21:55, Josh Clayton <[email protected]> wrote:
> So, could you verify a few things for me?
>
> 1. Confirm that there are the three generated Blueprint stylesheets
> within the folder /Applications/MAMP/htdocs/three/css/blueprint/
> portfolio after you run the generator (screen/print/ie)
> 2. Confirm that there is a file at the path /Applications/MAMP/htdocs/
> three/css/blueprint/portfolio/screen-custom.css (this is the custom
> file you're trying to attach)
> 3. Confirm that the grid is correct
>
> Thanks, and let me know what you find!
>
> On Apr 25, 3:47 pm, Breathe Makes Smoke <[email protected]>
> wrote:
>
> > sorry, my mistake. I've changed it now but the same.
>
> > portfolio:
> >      path: /Applications/MAMP/htdocs/three/css/blueprint/portfolio
> > namespace: custom-namespace-1-
> >      custom_css:
> >        screen.css:
> >          - screen-custom.css
> >      custom_layout:
> >        column_count: 20
> >        column_width: 60
> >        gutter_width: 10
>
> > On 25 Apr., 15:44, Josh Clayton <[email protected]> wrote:
>
> > > You can't use an http:// protocol; you have to use an absolute file
> > > path on your computer.
>
> > > On Apr 24, 7:39 pm, Josh Clayton <[email protected]> wrote:
>
> > > > First thing, you might want to check under the /portfolio directory;
> > > > with the path set like that, I think it'll build from your root
> > > > directory.
>
> > > > That's all I can think of right off the bat; the reason why I think
> > > > that is because it has to be an absolute path, first off, and second
> > > > off, it's printing out the string "Assembling to default blueprint
> > > > path", which means it's not picking up the path setting properly.
>
> > > > On Apr 24, 7:32 pm, Breathe Makes Smoke <[email protected]>
> > > > wrote:
>
> > > > > This is the complete settings.yml file:
>
> > > > > portfolio:
> > > > >      path: portfolio
> > > > >      custom_css:
> > > > >        screen.css:
> > > > >          - custom.css
> > > > >      custom_layout:
> > > > >        column_count: 24
> > > > >        column_width: 60
> > > > >        gutter_width: 10
>
> > > > > Thanks!

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to