clever paths for kit compiler

[wernerglinka]

Hi Brian, Could you implement clever path like described here: http://hammerformac.com/docs/tags/paths For more complex static sites that would be a real time saver Best, Werner

[bdkjones]

Hi Werner,

Thanks for getting in touch. While this sounds like a nice feature, it really has two major drawbacks:

1. It encourages lazy programming and introduces a large failure point. What happens when your project has 400 images and you forget that there’s already one in a different folder named “mac.png” and you add “mac.png” again? Now, it’s a crapshoot which one gets used.

2. It makes your project reliant on CodeKit. For folks that work in teams and with people that don’t use my app, they would not be able to use your code. I definitely don’t want to lock people into using CodeKit, so I’m sensitive about adding features that do just that.

I haven’t rule the idea out and I may implement it as part of the Kit language. 

-Bryan

On 21 Mar 2015, at 17:35, Werner Glinka [email protected] wrote:

Hi Brian, Could you implement clever path like described here: http://hammerformac.com/docs/tags/paths http://hammerformac.com/docs/tags/paths For more complex static sites that would be a real time saver Best, Werner

— Reply to this email directly or view it on GitHub https://github.com/bdkjones/CodeKit/issues/536.

[wernerglinka]

Hi Brian, Thank you for the reply.

I often build html templates that will be integrated later into dynamic apps. My deliverables are fully linked static web pages which may be organized in several folders. I typically use header, footer and other html partials. Before delivery I go through all files in folders and adjust nav links according to their folder location. That is the use case that would be helped with this feature. I used HammerForMac before I switched over to Codekit and really liked this feature. They also automatically added an active class to a link if the link url is pointing to itself... little things that make live easier.

From your website I have gathered that you don't want to lock people into Codekit. Frankly, Codekit is such a tremendous time saver that I am locked in... gladly. I am a freelance web developer and work mostly alone. When I am working as part of a team, then I'll adopt their workflow, but I always return to Codekit because it just works.

Thanks for this great tool, Werner

Send from my iPad

On Mar 23, 2015, at 00:14, Bryan Jones [email protected] wrote:

Hi Werner,

Thanks for getting in touch. While this sounds like a nice feature, it really has two major drawbacks:

1. It encourages lazy programming and introduces a large failure point. What happens when your project has 400 images and you forget that there’s already one in a different folder named “mac.png” and you add “mac.png” again? Now, it’s a crapshoot which one gets used.

2. It makes your project reliant on CodeKit. For folks that work in teams and with people that don’t use my app, they would not be able to use your code. I definitely don’t want to lock people into using CodeKit, so I’m sensitive about adding features that do just that.

I haven’t rule the idea out and I may implement it as part of the Kit language.

-Bryan

On 21 Mar 2015, at 17:35, Werner Glinka [email protected] wrote:

Hi Brian, Could you implement clever path like described here: http://hammerformac.com/docs/tags/paths http://hammerformac.com/docs/tags/paths For more complex static sites that would be a real time saver Best, Werner

— Reply to this email directly or view it on GitHub https://github.com/bdkjones/CodeKit/issues/536.

— Reply to this email directly or view it on GitHub.