Would this be interesting to have in pharo?? What do you think? ---------- Forwarded message --------- From: Amjad from Repl.it <[hidden email]> Date: jue., 6 de dic. de 2018 21:55 Subject: Announcing Repl.it Multiplayer To: <[hidden email]> |
Hi Santiago, On Thu, Dec 6, 2018 at 1:52 PM Santiago Bragagnolo <[hidden email]> wrote:
There is already previous relevant work. Look up Kansas for Self http://wiki.squeak.org/squeak/1357 and Nebraska for Squeak http://wiki.squeak.org/squeak/1356. Focussing on the Multiplayer like UI would be a major regression. Note that we already have lots fo relevant infrastructure, such as a VNC server that allows desktops to be shared. Building a shared programming environment for Pharo doesn't need to start from such limited models as the Multiplayer.
_,,,^..^,,,_ best, Eliot |
Yeah I think I see your point. I'm going to check out those projects and learn some :). Thx! El jue., 6 de dic. de 2018 23:03, Eliot Miranda <[hidden email]> escribió:
|
In reply to this post by Eliot Miranda-2
One advantage of their seemingly text-based system might be bandwidth, but Pharo is a graphical system.
It might be worthwhile for dispersed teams working on web hosted Pharo systems, but we already have remote tools. I guess it might almost already be able to have multiple people using them simultaneously on the one image(?), but everyone would be looking at different Inpectors. It could be cool for a common Inspector instance to show up on multiple user screens. But is it that much better than the other suggestions?? cheers -ben On Fri, 7 Dec 2018 at 06:03, Eliot Miranda <[hidden email]> wrote:
|
True, bandwidth is a pain, especially for a FullHD or more screen. I am doing lots of remote work with ssh and tmux/tmux attach. Works wonderfully well. I wish we had a fuse filesystem for Pharo so we could basically edit stuff out of a mounted image with things like vim. With true headless mode, I guess we will have those topics coming to the forefront. Phil On Fri, Dec 7, 2018 at 2:06 AM Ben Coman <[hidden email]> wrote:
|
In reply to this post by Ben Coman
With XMPPTalk, I had the idea to have one server doing the messenging and instead of sharing an image, we could have source code shipped around. DiscordSt is nice but depends on a proprietary service, so have one's own self hosted infrastructure would be nicer. Also, if we associate this to Telepharo, we could have one image doing the messenging in a safe area and a remote image (running on the same machine) doing the evaluations of the code. So that we wouldn't have a lockup in the main UI. End of year holidays may be a good time to try these ideas out. Best, Phil On Fri, Dec 7, 2018 at 7:27 AM Tim Mackinnon <[hidden email]> wrote:
|
Actually I'm working on a hobby project for creating a Web IDE for Smalltalk.
The idea is to have people (actually kids) work together in it. Purpose is to have an environment for kids to learn to program with the help of other kids and one or more experienced programmers/mentors/coaches. My current plans are to create a REST or Web API on top of a Smalltalk image which allows querying the image as well as execute code. The Web API should ideally be general enough to support different Smalltalk flavours. (This will require some tweaking though ;-) The actual IDE will be a web application in Pharo which can access other Smalltalk images through the Web API. The Smalltalk image with the IDE itself will likewise be query-able and editable. It should be real Smalltalk in that the IDE can be edited by the 'user'. Web API could look something like (this is just from the top of my head): GET /packages GET /packages/<package-name>/classes GET /packages/<package-name>/classes/<class-name> POST /packages/<package-name>/classes/<class-name>/<method-name> GET /workspaces POST /workspaces/<workspace-id>/doit POST /workspaces/<workspace-id>/inspect Some names will have to be more general since Cuis uses Category instead of Package for example. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html |
Free forum by Nabble | Edit this page |