These are chat archives for dabblewriter/dabble

20th
Jan 2016
Tyler Wright
@xtyler
Jan 20 2016 06:42
no components? :(
I know it's more of an organizational difference, but it can be such a nice one
Jacob Wright
@jacwright
Jan 20 2016 14:29
Chip has moved to a component oriented approach. We are using components, but not native web components.
Matt
@matthopson
Jan 20 2016 14:32
Well howdy Tyler!
How are you building the app, Jacob?
Jacob Wright
@jacwright
Jan 20 2016 14:48
That’s a big question. Could you be more specific?
Matt
@matthopson
Jan 20 2016 14:51
So you use sublime or atom? How much coffee do you consume? What temperature do you leave the room at while you work? Cracked pepper?
I mean the build tool. Looks like you're using browserify, just making sure that's how you're building it to run it
I was getting into it last night and was stabbing in the dark on how you're were doing it. Making sure I'm not missing something obvious.
Jacob Wright
@jacwright
Jan 20 2016 14:57
Browserify + stringify for templates + node-lessify for the css
budo to start a server and deliver the browserify with automatic reloads.
I haven’t done the build/deploy script yet
run npm start
and in package.json you can see the ”scripts” section to see what is being run
Sublime, none, 70deg F, no thank you
Matt
@matthopson
Jan 20 2016 14:59
Ah. Budo
That's what I was missing
Stringify isn't in dev dependencies, so I had to install it. Are you running it globally instead?
This is where I was confused.
I was running browserify with the stringify / lessify filters and pointing to public/js. I'm like dude we gotta make a script for this
Jacob Wright
@jacwright
Jan 20 2016 15:02
I did some last minute fixes yesterday when I saw the build failing. I got stringify and the other dependencies in there
be sure to pull latest
should all be good now, tests are passing
git pull
npm install
npm start
npm test
growing pains
let me know if you have it running and showing the project screen
Matt
@matthopson
Jan 20 2016 15:07
Yeah, I got it running last night
Just a round-about way :P
I didn't even notice the start script in package.json - AND I LOOKED IN THERE FOR IT
running browserify -t node-lessify -t stringify app/index.js -o public/js/app.js got it going for me pretty quickly, but I knew I was missing something - felt too cumbersome
Jacob Wright
@jacwright
Jan 20 2016 16:04
So when we have a new PR, could we paste the link into here to alert the channel?
Matt
@matthopson
Jan 20 2016 16:04
Sure
Jacob Wright
@jacwright
Jan 20 2016 16:04
otherwise they can get lost or take awhile to be noticed (in my experience)
jacwright/dabble#5
Matt
@matthopson
Jan 20 2016 16:07
Regarding icons, I like using font-awesome... have used before and was really happy with it
Jacob Wright
@jacwright
Jan 20 2016 16:07
yeah, and they have quite the extensive set.
Matt
@matthopson
Jan 20 2016 16:07
Do you have some mockups of the screens so we can work out what we'll need? Or should this come as pages are built out?
Jacob Wright
@jacwright
Jan 20 2016 16:08
You can see the initial prototype at www.dabblewriter.com/alpha/
Matt
@matthopson
Jan 20 2016 16:08
Ah, seems like I tried to go to that at one point and it was off
Jacob Wright
@jacwright
Jan 20 2016 19:24
#6
Matt
@matthopson
Jan 20 2016 20:24
Curious if these ids will ever be exposed in the URL?
  • and if so, are we stripping the prefix off for those purposes?
Jacob Wright
@jacwright
Jan 20 2016 20:56
Good point. I'd say yes and yes
Matt
@matthopson
Jan 20 2016 20:56
Yeah, was curious about the seperator in that case
Shouldn't affect this PR if you plan to strip it later for display
But note for later
Jacob Wright
@jacwright
Jan 20 2016 21:04
I think we can just remove the prefix. It makes sense to have /productId/docId as a URL
Matt
@matthopson
Jan 20 2016 21:08
:+1: