Assuming that its the included test framework that stinks rather than the premise of having a generator to create an initial folder+file structure for a project, the code base is on git so its easy to fork, change the generators to use your own test framework etc.
If there's something specifically you want and can't figure out how to modify the generators, let me know.
On Feb 17, 3:18 am, Dr Nic <drnicwilli...@gmail.com> wrote:
> > How about feedback right here? It stinks.
> Assuming that its the included test framework that stinks rather than > the premise of having a generator to create an initial folder+file
I didn't bother to read the premise. The error alert popped up and I closed the window. Nobody is going to bother with a utility that throws script errors in IE.
> structure for a project, the code base is on git so its easy to fork,
On git?
> change the generators to use your own test framework etc.
> If there's something specifically you want and can't figure out how to > modify the generators, let me know.
I am still not sure what it is supposed to be, but best of luck with it.
> I recognize that code and comment. It's the wonderful Prototype > loader.
This code is from my blog - not code generated by newjs. Sorry, I didn't know what code you were looking at.
But yep, its currently broken (plus has unnecessary firefox console.log references in it). I'm currently rewriting it under tests. The new version also has no dependency on another library. When I threw the original version together, it did use prototypejs but the console.log reference is for firefox debugging. Before I had tests I had to use debugging. The console.log shouldn't be there in production of course :)
Re: git - its a source control system - http://git.or.cz/ originally written by Linus Torvalds.
Re: newjs - sorry I've not explained very well what its purpose is. In the past for Ruby development, its awesome having a starting point for a new library, instead of a blank folder and having to copy+paste over useful files from other projects as a starting point. I codified my preferred starting point for a new project - READMEs, generators, folders, helper tasks (e.g. Rakefile/Makefile). That's what newjs is - a codification of a starting point.
> > I recognize that code and comment. It's the wonderful Prototype > > loader.
> This code is from my blog - not code generated by newjs. Sorry, I > didn't know what > code you were looking at.
I wasn't looking at any code. I just clicked your supplied link and got the error.
> But yep, its currently broken (plus has unnecessary firefox > console.log references > in it). I'm currently rewriting it under tests. The new version also > has no > dependency on another library. When I threw the original version > together, it did use prototypejs > but the console.log reference is for firefox debugging. Before I had > tests I had > to use debugging. The console.log shouldn't be there in production of > course :)
You might have waited to post the link until the site was ready for production.
> Re: newjs - sorry I've not explained very well what its purpose is. In > the past for Ruby development, > its awesome having a starting point for a new library, instead of a > blank folder and having to > copy+paste over useful files from other projects as a starting point. > I codified my preferred > starting point for a new project - READMEs, generators, folders, > helper tasks (e.g. Rakefile/Makefile). > That's what newjs is - a codification of a starting point.
Sounds like a Ruby group would be a better place to announce this product.
> > > I recognize that code and comment. It's the wonderful Prototype > > > loader.
> > This code is from my blog - not code generated by newjs. Sorry, I > > didn't know what > > code you were looking at.
> I wasn't looking at any code. I just clicked your supplied link and > got the error.
> > But yep, its currently broken (plus has unnecessary firefox > > console.log references > > in it). I'm currently rewriting it under tests. The new version also > > has no > > dependency on another library. When I threw the original version > > together, it did use prototypejs > > but the console.log reference is for firefox debugging. Before I had > > tests I had > > to use debugging. The console.log shouldn't be there in production of > > course :)
> You might have waited to post the link until the site was ready for > production.
My poor blog template has been suffering under various JavaScript lipstick I've written over the years. This is one of the reasons I wrote newjs - so all the projects looked the same and were easier to maintain. Currently all my blog extensions are being rewritten so they are easier to live with over time.
I agree it would have been good to have done this before posting about a project that supposedly makes the lifecycle of JS projects easier. I was excited to share, I guess.
> Sounds like a Ruby group would be a better place to announce this > product.
The ideas come from working with Ruby dev; the project is for JavaScript development. It would be a 1000x more work to create all the support infrastructure in JavaScript, and then require ppl run Rhino etc in order to run the app.
I'm very sure its useful to other readers of comp.lang.js. Even ppl not using prototypejs :)
David Mark wrote: > On Feb 17, 4:42 am, Dr Nic <drnicwilli...@gmail.com> wrote: [...] >> Re: git - its a source control system -http://git.or.cz/originally >> written by Linus Torvalds.
> Okay. The name (acronym?) seems unfortunate.
But completely in character - the original name for Linux was Freax.
"Get it? Freaks with the requisite X"
Linus Torvalds, "Just for Fun", 2001
He has also said of git:
"I'm an egotistical bastard, and I name all my projects after myself. First Linux, now git."
-- Rob "We shall not cease from exploration, and the end of all our exploring will be to arrive where we started and know the place for the first time." -- T. S. Eliot
