That is such a beautiful table full of old tools!
Introducing Rec Room
31–40 of 65 posts
Re: Introducing Rec Room
#32At the end of this road, I foresee a full IDE baked into Firefox. I can't wait. It would so great if you could just open the App Manager, click "Create New App", check the boxes of the libraries you want to include by default (jQuery, Ember, etc.), and it would then generate a Hello World app folder with all those files included. Heck, Firefox Developer Tools is practically already an IDE. All that really remains for…
Well isn't that what Netscape had :) everything comes around. I actually think this part was really good part of Netscape Navigator and was in spirit of how html was intented to be used.
Re: Introducing Rec Room
#33At the end of this road, I foresee a full IDE baked into Firefox. I can't wait. It would so great if you could just open the App Manager, click "Create New App", check the boxes of the libraries you want to include by default (jQuery, Ember, etc.), and it would then generate a Hello World app folder with all those files included. Heck, Firefox Developer Tools is practically already an IDE. All that really remains for…
It's already there :-D
https://hacks.mozilla.org/2014/06/webide-lands-in-nightly/
(Well, in the nightlies anyway.)
Re: Introducing Rec Room
#34It's kinda like Google's Web Starter Kit[1], isn't ? For me, it's really helpful when we can use some guidance from great players in the industry when choosing which framework to use. We recently forked Web Starter Kit, added some bower instructions, integrated Twitter BootStraped and now we've got some internal guidelines for new SPA. [1] https://github.com/google/web-starter-kit
That's really good to hear. I think you're right about it being like Google's Web Starter Kit. The WSK feels a bit more sparse and less idiomatic than recroom, but it's definitely in the same vein. I haven't checked it out since it was announced a few months back though, so maybe it's grown since then. I'd love to see people do that to recroom -- add what they think is missing. Pull requests are definitely welcome. M…
Yeah, exactly this!
On the front end part, it's a real pain to choose a tool over another, since there so many.
I'll be evaluating recroom this week, and will integrate it to my internal tools.
A question: something that I think is really broken, is how to integrate bower (or something like it) in the weapp. This is something that WSK left away, but you will always need.
Re: Introducing Rec Room
#35That is such a beautiful table full of old tools!
[deleted]
Re: Introducing Rec Room
#36At the end of this road, I foresee a full IDE baked into Firefox. I can't wait. It would so great if you could just open the App Manager, click "Create New App", check the boxes of the libraries you want to include by default (jQuery, Ember, etc.), and it would then generate a Hello World app folder with all those files included. Heck, Firefox Developer Tools is practically already an IDE. All that really remains for…
It's already there :-D https://hacks.mozilla.org/2014/06/webide-lands-in-nightly/ (Well, in the nightlies anyway.)
You're right! recroom works well with WebIDE. You build your app and can then use WebIDE (and even the Ember Inspector Firefox add-on) to debug your app, for instance in the Firefox OS Simulator.
Future plans of ours include having recroom (and really, any toolchain; this is not a privilege we only want Mozilla projects to have) integrate even more smoothly with the WebIDE, with more direct integration points like "pre-push hooks".
Re: Introducing Rec Room
#37I can see that yeoman is one of the included tools, but I don't see what Rec Room adds on top of the capabilities of Yeoman. Couldn't this entire toolchain be encapsulated as a Yeoman generator?
Re: Introducing Rec Room
#38Earlier quoted context omitted.
That's really good to hear. I think you're right about it being like Google's Web Starter Kit. The WSK feels a bit more sparse and less idiomatic than recroom, but it's definitely in the same vein. I haven't checked it out since it was announced a few months back though, so maybe it's grown since then. I'd love to see people do that to recroom -- add what they think is missing. Pull requests are definitely welcome. M…
Yeah, exactly this! On the front end part, it's a real pain to choose a tool over another, since there so many. I'll be evaluating recroom this week, and will integrate it to my internal tools. A question: something that I think is really broken, is how to integrate bower (or something like it) in the weapp. This is something that WSK left away, but you will always need.
recroom uses bower for package management at this point. Like many other parts of the picture, the "market" surrounding package management is in flux (there's also npm, for instance), so we'll monitor what's going on there. But for now, bower seems like a great choice for developers.
Also, it enables the modular aspect of recroom, that you can add/replace pieces you want, so package management is definitely vital.
Re: Introducing Rec Room
#39I can see that yeoman is one of the included tools, but I don't see what Rec Room adds on top of the capabilities of Yeoman. Couldn't this entire toolchain be encapsulated as a Yeoman generator?
It would limit its abilities to do things going forward, like integrate with Firefox's Web IDE. We'd like to, in the future, allow you to package your web app and push it directly to the simulator from a recroom command, so we wanted to make it more than just a set of yeoman templates.
Re: Introducing Rec Room
#40"Rec Room is a Node.js utility ..."
I am curious why there is no SpiderMonkey* based Node.js ?
* SpiderMonkey is Mozilla's JavaScript engine: https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Sp... , https://wiki.mozilla.org/JaegerMonkey . Node.js is using Chrome's V8 JavaScript engine. Both JS engines are fast and have their advantages and disadvantages.