Comments (12)
Hi all,
I have been accepted as a student in the Google Summer of Code 2016 again this year (under the ruby-org). In this summer, I will be working on three things with the @gsamokovarov's help:
- _Auto-completion_
- _Console fired from "anywhere"_
- _Built-in commands_
The last year, I have developed a prototype of a Chrome Extension and touched on a Firefox Add-on. And also, I will make the chrome extension is production ready, and touch on Firefox and Safari supports in this summer.
And, just for your information, anyone can see the project details of the above ideas in here: https://git.io/vaMkL
Thank you :-)
from web-console.
And also I'm not fluent in English, so I've prepared some figures to describe my proposal. The figures are pseudo-images (they are fake screens).
1. Main Feature
The browser extension allows to display the console aside from the web application's view (i.e., the console will be displayed in the web browser's developer tools):
2. Context Viewer
And one more thing - I'm thinking of implementing the context viewer which allows to view all variables in the current context. It will be something like the CSS viewer of Chrome DevTools, and its window will be docking with the console view:
from web-console.
Hello, again ✌️
Today, I have made an animated gif of context viewer as a mock-up (and fixed misunderstanding):
The change than before is that an array can be expanded in the viewer. Here is an example diff showing that change:
- @items: ["hello", "foo", "bar"]
+ @items: ▼
+ #<Item id: 1, ...> ▼
+ id: 1
+ name: "hello"
+ #<Item id: 2, ...> ▼
+ id: 2
+ name: "foo"
+ #<Item id: 3, ...> ▼
+ id: 3
+ name: "bar"
I think the context binding of the viewer will be the same as the console.
from web-console.
Yo @dhh, @jeremy, @chancancode and anyone interested in the development of this project: do you guys wanna chime in and share your ideas about our direction?
One of the ideas I want to explore is have the web-console be optionally always on. Meaning, you can introspect and evaluate code in every binding of the current execution stack. We may crash them Rubies, but its something I'm interested in trying out.
Whatever ideas and directions you guys have, we'll be thankful for all your feedback!
Cheers!
from web-console.
Love the idea of having the console be always on in development mode.
On Tue, Apr 21, 2015 at 11:03 AM, Genadi Samokovarov <
[email protected]> wrote:
Yo @dhh https://github.com/dhh, @jeremy https://github.com/jeremy,
@chancancode https://github.com/chancancode and anyone interested in
the development of this project: do you guys wanna chime in and share your
ideas about our direction?One of the ideas I want to explore is have the web-console be optionally
always on. Meaning, you can introspect and evaluate code in every binding
of the current execution stack. We may crash them Rubies, but its something
I'm interested in trying out.Whatever ideas and directions you guys have, we'll be thankful for all
your feedback!Cheers!
—
Reply to this email directly or view it on GitHub
#121 (comment).
from web-console.
Hi, all. This is an intermediate progress report of GSoC 2015, in short. 🍵
1. Add JavaScript Test Environment
PR #138
2. Add Close Button to Web Console
PR #140
3. Web Console in Chrome DevTools
http://brx-web-console.blogspot.jp/2015/06/web-browsers-developer-tools.html
And Next?
From this week, I will start to implement the context viewer experimentally. And so, welcome any comments, and welcome any claims. Let me know your thoughts about this project if you feel something in your heart.
Thanks.
from web-console.
Now that we have prototypes of the browser extensions, let's discuss where they should actually live.
- Let them live in
rails/web-console
. I like this approach as everything is in one place and we can easily reuse the JavaScripts across every project. However, it does have the drawback of blowing up the repo with extension specific commits. We may also end up with extension specific maintainers and they will have access to all the codebase. - Let each of them live in own repositories. This has the benefit of easier to track history and project specific maintainers. The drawback is tricker JavaScripts reuse and maybe desynchronization of the projects. Say, the Chrome maintainers are more active and it has more features/less bugs than the Firefox and Safari extensions. This can happen in option 1 too, of course.
I generally lean over option 1, but I would like to hear your thoughts.
from web-console.
I haven't sorted out my ideas of that yet, but I think the browser extensions should be located as a sub-project of Web Console, and I think it is better, in that point, to put the code of the browser extensions under the rails/web-console
, so plus one to the option 1 so far.
However, it does have the drawback of blowing up the repo with extension specific commits.
Yeah, that is my concern.
The drawback is tricker JavaScripts reuse and maybe desynchronization of the projects.
That is also. I need to think of that.
Thanks.
from web-console.
Any news on that one? :)
from web-console.
from web-console.
Thanks @sh19910711. I may take a look and start something (Unless you already did?)
from web-console.
We haven't worked on them in a while, but the code we have is at: https://github.com/rails/web-console/tree/master/extensions
from web-console.
Related Issues (20)
- Disable web console
- `WebConsole::EvaluatorTest#test_Evaluator_callers_are_cleaned_up_of_unneeded_backtraces` test failure HOT 1
- Breaking with Rails 6.1.rc1.
- CurrentAttributes gets reset for web-console requests HOT 10
- Wildcard host for ngrok HOT 2
- Still not working with Rails 6.1
- web-console gem error in ruby 2.7 and rails 6.1 HOT 2
- Missing template rails_web_console/console/run HOT 1
- Support for multiple web workers (websockets?) HOT 2
- Do not render web console for non-HTML requests HOT 5
- NameError: constant WebConsole::SourceLocation not defined HOT 13
- Faulty message: Web Console is activated in the test environment HOT 3
- Could web-console support meta keys? HOT 2
- Extend UI options for the console HOT 4
- web-console complains about being active in the test environment when tailwindcss-rails gets update HOT 8
- \
- web console failing to build on master
- Console not showing on error page HOT 4
- Permissions are not working when runs thru ngrok HOT 4
- Uncaught Error: Internal Server Error
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from web-console.