Include web-console in new projects Gemfile #11667

Merged
merged 1 commit into from Sep 24, 2013

Conversation

Projects
None yet
10 participants
@gsamokovarov
Contributor

gsamokovarov commented Jul 30, 2013

As part of the Google Summer of Code 2013, me and @guilleiguaran has been working on bringing rails console to the browser. Today we are proud to announce that we hit 0.1.0 and we have enough of it, to let you guys test it.

The project development lives in https://github.com/gsamokovarov/web-console and we'll be happy to get any feedback about how we can make it better. That this is more of a demo release and we will really appreciate all of the extra testing we can get. Feel free to open issues on https://github.com/gsamokovarov/web-console/issues with any bugs, feature requests or general feedback.

/cc @guilleiguaran, @rafaelfranca, @pixeltrix, @spastorino, @drogus

@dmathieu

This comment has been minimized.

Show comment
Hide comment
@dmathieu

dmathieu Jul 30, 2013

Contributor

As this is a demo, I don't think it should be included into the default Gemfile for now.

Contributor

dmathieu commented Jul 30, 2013

As this is a demo, I don't think it should be included into the default Gemfile for now.

@gsamokovarov

This comment has been minimized.

Show comment
Hide comment
@gsamokovarov

gsamokovarov Jul 30, 2013

Contributor

I'm opening the PR just to keep track of the integration of it into core Rails and how we should proceed with that. So yeah, we shouldn't merge at 0.1.0, but it will help with the discussion about it.

Contributor

gsamokovarov commented Jul 30, 2013

I'm opening the PR just to keep track of the integration of it into core Rails and how we should proceed with that. So yeah, we shouldn't merge at 0.1.0, but it will help with the discussion about it.

@dmathieu

This comment has been minimized.

Show comment
Hide comment
@dmathieu

dmathieu Jul 30, 2013

Contributor

I understand. Unfortunately, issues aren't for discussion, but bug report.
Any feature discussion should happen in the google group.

Contributor

dmathieu commented Jul 30, 2013

I understand. Unfortunately, issues aren't for discussion, but bug report.
Any feature discussion should happen in the google group.

@dmathieu

This comment has been minimized.

Show comment
Hide comment
@dmathieu

dmathieu Jul 30, 2013

Contributor

Despite all my saying, your GSOC project looks awesome BTW. 💖

Contributor

dmathieu commented Jul 30, 2013

Despite all my saying, your GSOC project looks awesome BTW. 💖

@pftg

This comment has been minimized.

Show comment
Hide comment
@pftg

pftg Jul 30, 2013

Contributor

agree with @dmathieu (with both comments :) )

Contributor

pftg commented Jul 30, 2013

agree with @dmathieu (with both comments :) )

@ghost ghost assigned guilleiguaran Jul 30, 2013

@rafaelfranca

This comment has been minimized.

Show comment
Hide comment
@rafaelfranca

rafaelfranca Jul 30, 2013

Member

I don't see any problem to leave this PR open here since it is a GSoC project.

Member

rafaelfranca commented Jul 30, 2013

I don't see any problem to leave this PR open here since it is a GSoC project.

@steveklabnik

This comment has been minimized.

Show comment
Hide comment
@steveklabnik

steveklabnik Jul 30, 2013

Member

Leaving PRs open while working on features is 100% legit.

Member

steveklabnik commented Jul 30, 2013

Leaving PRs open while working on features is 100% legit.

@vipulnsward

This comment has been minimized.

Show comment
Hide comment
@vipulnsward

vipulnsward Jul 30, 2013

Member

👍
@gsamokovarov could you mention any milestones or work needed on rails-end if any.

Member

vipulnsward commented Jul 30, 2013

👍
@gsamokovarov could you mention any milestones or work needed on rails-end if any.

@egilburg

This comment has been minimized.

Show comment
Hide comment
@egilburg

egilburg Jul 30, 2013

Contributor

+1 to open PR, but I'd prefix it with [wip] to indicate it's not ready for merge yet.

Contributor

egilburg commented Jul 30, 2013

+1 to open PR, but I'd prefix it with [wip] to indicate it's not ready for merge yet.

@gsamokovarov

This comment has been minimized.

Show comment
Hide comment
@gsamokovarov

gsamokovarov Jul 31, 2013

Contributor

@vipulnsward I don't think that I need anything from rails, as of now. I have a couple of ideas that would make the integration a bit easier, from my perspective and I'll present those in separate PRs.

Contributor

gsamokovarov commented Jul 31, 2013

@vipulnsward I don't think that I need anything from rails, as of now. I have a couple of ideas that would make the integration a bit easier, from my perspective and I'll present those in separate PRs.

@gsamokovarov

This comment has been minimized.

Show comment
Hide comment
@gsamokovarov

gsamokovarov Jul 31, 2013

Contributor

By the way, guys, if you are into Pry, we just released an adapter for it. Its a separate package, so we aren't introducing a dependency to Pry. It's an opt-in thing.

Contributor

gsamokovarov commented Jul 31, 2013

By the way, guys, if you are into Pry, we just released an adapter for it. Its a separate package, so we aren't introducing a dependency to Pry. It's an opt-in thing.

@miry

This comment has been minimized.

Show comment
Hide comment
@spastorino

This comment has been minimized.

Show comment
Hide comment
@guilleiguaran

This comment has been minimized.

Show comment
Hide comment
@guilleiguaran

guilleiguaran Aug 19, 2013

Member

@spastorino Thanks for your review!!! The support for Rails 3 was extracted to web-console-rails3, so I think is fine remove related code in project.

Member

guilleiguaran commented Aug 19, 2013

@spastorino Thanks for your review!!! The support for Rails 3 was extracted to web-console-rails3, so I think is fine remove related code in project.

@gsamokovarov

This comment has been minimized.

Show comment
Hide comment
@gsamokovarov

gsamokovarov Aug 19, 2013

Contributor

Hey @spastorino, thanks for the review! As @guilleiguaran pointed out, we did this for Rails 3 support, as there were some people that requested it. We decided to keep the code in one place and backport it on releases for the web-console-rails3 gem, which explicitly depends on Rails 3.2.

We did this, since the backport process would be easier for us, that way, but it is a fair point for you to argue that it can live in the web-console-rails3 gem. If you think that this is the better place for the code, we can move it there.

Contributor

gsamokovarov commented Aug 19, 2013

Hey @spastorino, thanks for the review! As @guilleiguaran pointed out, we did this for Rails 3 support, as there were some people that requested it. We decided to keep the code in one place and backport it on releases for the web-console-rails3 gem, which explicitly depends on Rails 3.2.

We did this, since the backport process would be easier for us, that way, but it is a fair point for you to argue that it can live in the web-console-rails3 gem. If you think that this is the better place for the code, we can move it there.

@spastorino

This comment has been minimized.

Show comment
Hide comment
@spastorino

spastorino Aug 19, 2013

Member

cool guys 👍

Member

spastorino commented Aug 19, 2013

cool guys 👍

@guilleiguaran

This comment has been minimized.

Show comment
Hide comment
@guilleiguaran

guilleiguaran Sep 13, 2013

Member

@spastorino we will be releasing 1.0.0 soon, do you want to do a final review? 😄

Member

guilleiguaran commented Sep 13, 2013

@spastorino we will be releasing 1.0.0 soon, do you want to do a final review? 😄

@gsamokovarov

This comment has been minimized.

Show comment
Hide comment
@gsamokovarov

gsamokovarov Sep 13, 2013

Contributor

As @guilleiguaran said, we're coming to a point, where we are happy with the current feature-set and we haven't discovered any major show stoppers, so we'll release 1.0.0 early next week.

If you guys want to help out with a review, we'll greatly appreciate it!

Now its also a good time to decide whether we should link to the project in the new rails project's Gemfile. Right now I have it commented in there, as I think it's an unobtrusive way to introduce the project, should someone find it useful. If you think that we should leave it off the Gemfile or mention it in the documentation, or something along those lines, we can do that too.

Contributor

gsamokovarov commented Sep 13, 2013

As @guilleiguaran said, we're coming to a point, where we are happy with the current feature-set and we haven't discovered any major show stoppers, so we'll release 1.0.0 early next week.

If you guys want to help out with a review, we'll greatly appreciate it!

Now its also a good time to decide whether we should link to the project in the new rails project's Gemfile. Right now I have it commented in there, as I think it's an unobtrusive way to introduce the project, should someone find it useful. If you think that we should leave it off the Gemfile or mention it in the documentation, or something along those lines, we can do that too.

@spastorino

This comment has been minimized.

Show comment
Hide comment
Member

spastorino commented Sep 21, 2013

guilleiguaran added a commit that referenced this pull request Sep 24, 2013

Merge pull request #11667 from gsamokovarov/introduce-web-console
Include web-console in new projects Gemfile

@guilleiguaran guilleiguaran merged commit f55e178 into rails:master Sep 24, 2013

@gsamokovarov

This comment has been minimized.

Show comment
Hide comment
@gsamokovarov

gsamokovarov Sep 24, 2013

Contributor

❤️ 💛 💚 💜 💙

Contributor

gsamokovarov commented Sep 24, 2013

❤️ 💛 💚 💜 💙

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment