Is anyone besides Thomas using CodeKit with FWP? If so, how?
Todd
https://creativ.space
https://xiiro.com
freewaytalk mailing list
email@hidden
Update your subscriptions at:
To a very small extent, I have – mostly just to build hand-coded Sass files that are then pulled into a Freeway doc with the External Stylesheet action.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Perhaps I should explain myself what I’m doing and why:
####Let’s start the Why:
Basically I don’t fiddle within the default Freeway stuff. It is as is:
3 css files (Master, Default, Page)
Nothing to do here.
But what, if you like to use 3rd party stuff. I mean more than one. Perhaps 2 or 3 additional things? This will cause another 3 css calls and the registry area will grow quick’n mad - bad style (to my convenience) and slowing up my project.
####The What
So here I’m concatenating css files using codeKit creating a Compass project and using Sass (it should be noted that I can’t write Sass but this doesn’t matter at all).
As a result, I can keep each project’s css files separated and update them if necessary.
Another point here: The compass project is placed on dropbox. So I don’t need any extra action - just the referral line in the head for css and the one for js in the before end body. Even more, this compass project (which is a folder literally) is been chosen as my Freeway’s Site-Folder 
Last but not least:
####The Experiments
Such as flexbox. It’s hard to crack this - but it helps to have a lil helper called “auto-prefix”, another cool feature of codeKit.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Ooh, I like how you are using CodeKit to concatenate the CSS files – I’ll have to do that next time!
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Basically I don’t fiddle within the default Freeway stuff. It is as is:
3 css files (Master, Default, Page)
Nothing to do here.
I’ve been working with Ruby to dynamically change file extensions and wondered if that could be applied to FW’s CSS files to change them from .css to .scss then use CodeKit to merge it all. On the surface it seems (theoretically) reasonable.
But then I realized even if the first part worked there’s still no way to remove FW’s references to all the individual (now merged) files.
Close, but not really.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options
I’ve been working with Ruby to dynamically change file extensions and wondered if that could be applied to FW’s CSS files to change them from .css to .scss then use CodeKit to merge it all. On the surface it seems (theoretically) reasonable.
But then I realized even if the first part worked there’s still no way to remove FW’s references to all the individual (now merged) files.
Close, but not really.
in a CodeKIT (Compass) project this wouldn’t be enough cause it’ll need the underscore prefix and the placement into the scss (sass) folder.
I remember the grey (cool) days back in version 5.5 where I “externalized” as mad. Tim wrote a pretty cool action (nearby exclusively for me) which allowed me to print all styles into the head, I collected them from there into a brand new independent sheet and checked the magic check “remove all styles”. Can’t remember if it even deleted the refs (thought it was) and was herby able to run all styles off the app.
The action still persist but haven’t had any deeper look into it.
I love the app and can live with the “constraints” of three extra browser requests. The benefit of features dominates all. So externalizing stuff makes me a lil bit concerned.
But the topic is super cool as CodeKIT is and I am at the very first beginning of this process combining it with Freeway. But just detected bower … ouh super-hot as well, cause shortening external stuff as well.
Cheers
Thomas
I know that you’re after creating templates for MODx but I can’t be of assistance here cause I do not know how those templates need to be created.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options
Oops. I forgot about the underscore. But I suspect there might still be a way to dynamically target the “child” files with an underscore (using Ruby). It was a fun experiment.
I am completely dependent on CodeKit for processing everything: CSS, js, Sass, Compass etc. I would be lost without it.
Be careful with Bower. Bryan (the dev) has had a hell of time integrating that beast into CK. So much so at one point he considered dropping it. I’ve used to install a variety of things with mixed results. It has gotten better but I don’t think it’s quite up to Bryan’s standards yet.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
yeah Todd, understood - if not to say “got it”
It’s really nice, however I’m not smart enough to understand this all entirely. But it seems to work for my purposes and perhaps I even have another look into those artificial pre-processor languages.
But mostly I’m interested in smooth and successful integrating the product into my Freeway workflow.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
perhaps I even have another look into those artificial pre-processor languages.
I love me some Sass. 
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options
Oh - and here once again a thinkable way:
####Doc sets
Uncheck external stylesheets in document settings. The styles are now collected in a single index.css stylesheet (or in the head???). Collect the styles from there and place it in a _index.scss (you know the procedure)
####The Action
http://www.actionsforge.com/actions?q=externalize
Set it under step 3 Remove Freeway Styles to “Yes”. Now you’re running “styles free” without any referral in the head having the chance to merge it with all the other snippets.
####The downside
Naturally, if you want to add stuff or alter construction, you need to switch the action off and repeat the above mentioned steps. Or there is a chance to target this single style-sheet and make an automatism to create the underscore file??? Or even Tim can add this to the output opportunities? Well - who knows.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Interesting workaround, Thomas. Out of curiosity I may have to look into it.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Thomas,
You’re right, your suggestion has possibilities. But as you also mentioned it’s somewhat awkward and negates the “hands-off" aspect that makes CodeKit so useful in the first place.
I can’t help but wonder if SP could add some advanced preferences that would allow the user to manually set the (scss) file extension and automate the underscore prefix for partials. That would make the entire process so much simpler. But I suppose it’s not worth the effort since only 2 people would actually use it.
Naturally, if you want to add stuff or alter construction, you need to switch the action off and repeat the above mentioned steps. Or there is a chance to target this single style-sheet and make an automatism to create the underscore file???
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options
I’d have to address this question preferably to Tim who’s the author of the action (or point him at least to this list).
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Honestly I don’t know why I’m so curious about integrating CodeKit and FW in the first place, but if (big “if”) it were possible I might even be persuaded to write a tutorial.
I’d have to address this question preferably to Tim who’s the author of the action (or point him at least to this list).
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options
Hi Todd,
I think as well it is worth to think deeper and there ARE some ifs. Let’s see what Tim answers and decide then how deep we rush into it and what it could be worth for.
If he can find a way to auto-place a _index.scss (or others) into a specific scss folder, I think it’ll work as real recognizable workflow and worth a tutorial or even a lil FW for Pros video teaser.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
I put a lot of work into making exactly-named files appear in specific folders in my style accessors library, visible here: style_accessors.fwaction.library.js · GitHub
You may want to crib some of this if you are trying to do the same. It is really quite a lot of work to force Freeway to do this, since it seems to be antithetical to its entire reason for being.
Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
At Thomas’ suggestion Tim, being the clever guy he is, has already made some progress, and I believe he intends to look closely at your library, Walter. The accessors library might be the missing piece to actually having a real live CodeKit workflow in FW.
I put a lot of work into making exactly-named files appear in specific folders in my style accessors library, visible here: style_accessors.fwaction.library.js · GitHub
You may want to crib some of this if you are trying to do the same. It is really quite a lot of work to force Freeway to do this, since it seems to be antithetical to its entire reason for being.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options
… and at the end of my dream (please don’t wake me up) I see this shiny, bright rainbow - and I see a folder-structure as I’m used to use in a Compass project such as:
ProjectFolder
---- css
---- img
---- js
---- fonts
---- scss
And each folder receives the correct files, tidying up the resource folder mess.
And I don’t see any antithetical in this, Walter - promising the pot of gold.
Cheers
Leprechaun Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Nice, Thomas.
… and at the end of my dream (please don’t wake me up) I see this shiny, bright rainbow - and I see a folder-structure as I’m used to use in a Compass project such as:
ProjectFolder
---- css
---- img
---- js
---- fonts
---- scssAnd each folder receives the correct files, tidying up the resource folder mess.
And I don’t see any antithetical in this, Walter - promising the pot of gold.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options