Hi Adrian<div><br></div><div>First, sorry for the late of the answer (holidays)</div><div><br></div><div>You main idea looks so great and useful for a next release. Obviously, the project will progress iteratively and will have more and more features as the mentioned</div>
<div><br></div><div>Mi first next step for the project is to improve GUI and add ajax experience, after that i will choose one of the next features recommended for seaside community (including your idea).</div><div><br></div>
<div>=)</div><div><br><div class="gmail_quote">2010/12/21 Adrian Lienhard <span dir="ltr"><<a href="mailto:adi@netstyle.ch">adi@netstyle.ch</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Christian,<br>
<br>
That's cool!<br>
<br>
My main objective for such a debugger is to be able to run kernel images that do not come with a GUI, but at the same time to be able to debug and inspect the objects as you would with VNC. I imagine that when there is an error you get a mail with an URL that directly opens the Naplo debugger for that exception (of course you want to make that secure either ssh-tunneling into your server or using https and a login). So in comparison to using VNC you would gain (also for headful images) the possibility to debug errors that appear in production where so far you had to resort to reading the stacktrace you got by mail. That would be a big productivity win!<br>
<br>
What I miss in its current state is a way to inspect/explore objects and evaluate code.<br>
<br>
Cheers,<br>
Adrian<br>
<br>
___________________<br>
<a href="http://www.adrian-lienhard.ch/" target="_blank">http://www.adrian-lienhard.ch/</a><br>
<div><div></div><div class="h5"><br>
<br>
On Dec 17, 2010, at 14:57 , Christian Eduardo Palomares Peralta wrote:<br>
<br>
> Hi seaside community<br>
> My name is Christian Palomares, I am a student at the University of Chile<br>
><br>
> For the last two months I've been working on a project called Naplo, It's<br>
> about to bring the classic debugger (i.e. Pharo debugger) to the web<br>
> interface, of this way you will can debug, fix a bug, and most of the<br>
> functionalities of the classic debugger from the web interface.<br>
><br>
> In this project i receive a big support of Alexandre Bergel and<br>
> Lukas Renggli, they supported me to finish the alfa version of Naplo.<br>
> Now i need some help of the seaside community, because we need some testers<br>
> of Naplo who want to use it for their projects, of this way we can find some<br>
> bugs in a realistic scenario.<br>
><br>
> You will found the Naplo package on<br>
> <a href="http://www.squeaksource.com/NaploDebugger.html" target="_blank">http://www.squeaksource.com/NaploDebugger.html</a> It comes with tests and loads<br>
> in a Seaside image. Adrian, since this is your idea, can you comment on<br>
> this?<br>
><br>
> --<br>
> Christian Eduardo Palomares Peralta (@ShinjiDev) -<br>
> <a href="http://learningwebdev.blogspot.com" target="_blank">http://learningwebdev.blogspot.com</a><br>
> Administrador del Grupo Python-Perú<br>
<br>
<br>
<br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Christian Eduardo Palomares Peralta (ShinjiDev) - <a href="http://learningwebdev.blogspot.com">http://learningwebdev.blogspot.com</a><br>Administrador del Grupo Python-Perú<br>
</div>