Showing posts with the label Ducksauce

Project: DuckSauce Notes Part 5

I've been secretly working on this project again (of course there's my game I am still working). However I wanted to take a step back and look at what this project has done for me. The biggest thing is that it has done is get me to question my work follow and think about how to improve it.

This project must
create filescreate templatesclean up code build manual.New Approach
Working with the chrome work-space has its limits and it appears there is a method to set the contents of a particular however it is not implemented and is filed as a bug. This is a long outstanding bug so chances are slim.

The guts



Project: DuckSauce Notes Part IIII

A lot of this article not going to make sense to people because it relates to my thoughts as I wrote them down and what I researched or tried to understand. Some of it is wrong, and looking back probably could have approached somethings better but that's just a natural way of learning. Also a lot of my notes are going to appear as if I'm going in circles (or that's just how I see it). Previous articles can be found here.

Day 1- 10/2/14
    I started looking at thechrome.devtools.panels.openResource, by resources I think the docs means a web page's resources not the devtool's resources (something that work-spaces might have access to). The next part, "Requests DevTools to open a URL in a Developer Tools panel." 
"The real power of Work-spaces lies in being able to map a local file to a URL (or “Network Resource”). Whenever Chrome loads the mapped URL, it displays the work-space folder contents in place of the network folder contents. It’s as if it’s…

Project: DuckSauce Notes Part III

It's been a couple of weeks since I've released an update on this project, but much of it is due to the fact that I have completely reimplemented my approach. I now have a better understanding where browserify will come into place and where grunt will come into place. Most importantly I understand the v8 javascript engine which runs underneath the chrome browser; this is a major win for me. Here is my previous article...

Day 1 Day 7: GruntJS LiveReload--Take Productivity to the Next Level | Openshift BlogI basically want to remove the need for LiveReload.Moving from CodeKit to Grunt Watch + LiveReload for Real-time JavaScript/LESS/SASS Compilation - Justin KlemmAnother great example what LiveReload can do.Chrome Apps Office Hours: NodeJS in Chrome packaged apps - YouTubeExample with Browserify but you can't using it against Grunt.Iced Blog - node js in chrome…

Project: DuckSauce Notes Part II

Working on the second part of my project... I now need to automate bootstrap builds and compare the bootstrap's unmodified version of bootstrap to the new styles that I have added or modified on the bootstrap compiled css. From there DuckSauce should separate the style changes and place them in a .less file and recompile, which will then override or append the proper styles.
Day 3Managing module dependencies - How To Node - NodeJS
package.json - More reading...
Getting started - Grunt: The JavaScript Task Runner - Docs, docs and more docs
Moving from CodeKit to Grunt Watch + LiveReload for Real-time Compilation - Lots of help
Day 4gruntjs/grunt-contrib-watch - This is the direction I am heading now! No compatible version found: chalk@'0.4.0'  - Helping myself.

This week had to cut my research a little short but I feel I am really close to a solution with little effect on my part since a lot what I need is already built and simply needs to be configured to my preferences.

Project: DuckSauce Notes

What is Ducksauce
    Ducksauce is a small pet project I am working on to make everyday work easier with css and javascript cleanups. The hope is to automate those cleanups in controllable way I see fit, and to also make my code more scalable with third party libraries.

Listen to CSS changes and separate them into a .less file.

Features (Just for starters focusing on css cleanups)
Console system to attach files/directories.Listen to CSS filesRemove changes and separate into a less file.Compile new less files with Unmodified Third party styles (Overridering the css results)Log changes.Refresh page to see the changes? I would like this but it might get annoying.Day 1

Challenges: Listening to file, watch changes, find what those changes are.
filesystems - Node.JS: How does "fs.watchFile" work? - Stack OverflowNode.js: Event Emitters and Listeners | ScribblingsAccessing the File System in Node.jsObserve file changes with node.js - Stack OverflowIssues: No issues.

Day 2Challeng…