Fixes

[AVGP]

• Fixing Firefox iframe sizing issue
• Added infos to the readme

[Karnith]

I have some ideas I wanted to run by you...

I wanted to change the "Create workspace" to open a dialog window which gives the user the ability to select boiler plates from different frameworks like flatiron, express, etc. which would by dynamically generated (to a certain degree) from the globally installed framework modules.

I'm working on a way to change from an iframe for workspace window to a more embedded approach (if possible, still playing with this)

I would like to add the ability of a db behind the scenes (sqlite maybe?) that not only stores the info from the config.js, but will allow user creation and management (none git) for local dev. I think this approach will enable multiple git users to sign in with their git account instead of all git users feeding off the same dev app id and secret.

Do you have a problem with this approach?

Thanks,

Karnith

[AVGP]

Firstly, I'd like to say thank you for your contribution and I am looking forward to what you gonna do next! The templates sound interesting - it makes perfect sense, let me know when you need help!

I wonder what you gonna to for a "more embedded approach"... I wonder if it makes sense to transform it all into a web component (e.g. with Polymer or X-Tags).

The database is something where I don't see too much value. Right now you can have multiple users signing in thru the github application and most people who work with git also have a Github account. A local auth isn't something I am personally interested in, but I don't have a problem with that (I would just not merge that into here).

[Karnith]

Thanks for your input.

The reasoning for the database auth method would be to allow those that want to develop in house and use their own project tracking / version control systems and not be entirely dependant on git hub. C9 is the best nodejs ide I've seen so far.

I could see active directory or ldap auth in the future.

Karnith

-------- Original message -------- From: "Martin N." notifications@github.com Date: 11/09/2013 09:14 (GMT-08:00) To: AVGP/cloud9hub cloud9hub@noreply.github.com Cc: Matthew Marino mmarino@jcmar.com Subject: Re: [cloud9hub] Fixes (#1)

Firstly, I'd like to say thank you for your contribution and I am looking forward to what you gonna do next! The templates sound interesting - it makes perfect sense, let me know when you need help!

I wonder what you gonna to for a "more embedded approach"... I wonder if it makes sense to transform it all into a web component (e.g. with Polymer or X-Tags).

The database is something where I don't see too much value. Right now you can have multiple users signing in thru the github application and most people who work with git also have a Github account. A local auth isn't something I am personally interested in, but I don't have a problem with that (I would just not merge that into here).

Reply to this email directly or view it on GitHubhttps://github.com/AVGP/cloud9hub/pull/1#issuecomment-28131789.

[AVGP]

Interesting idea - the AD / LDAP integrations make sense, the local DB sounds like too insulated to make much sense - but integrating with the authentication system of the local organization makes sense, tho!

[Karnith]

hi.

just curious, but I see you're using angular for routing instead of the embedded router within express. any reason for this? would this project benefit from using flatiron as the underlying framework?

thanks,

Karnith

[AVGP]

Decoupling. If you take a closer look, I am using both: Express routes for the API that is exposed to the Angular application and then Angular routing to do the navigation within the web application.

I don't see any advantage Flatiron would bring over express, but I'm excited to hear some from you :)