Re: [Spindle-user] A feature to discuss

I think this is a very good idea and would streamline a lot of
developers cycle. To address your questions:

Preventing IDE hijacking can be as simple as limiting the interface
the servlet listens for connections on to localhost. This would be
suitable for most everybody and takes the least amount of work to
implement.

To address generacism the tapestry exception page could be made
generic and the communication parameters public so that anyone can
implement a servlet that runs inside their IDE.

To address development vs production... require a system property that
is present that specifies the IP address of the computer to send the
browser to when the user clicks a stack trace link.

On 2/15/06, Geoff Longman <[email protected]> wrote:
> A long time ago, as a lark, I implemented a feature in Spindle that
> improved the developer experience when debugging/running their
> Tapestry apps during development.
>
> It was possible to link the Exception page back into the IDE. In other
> words the Exception page rendered with links back into Eclipse.
>
> I only got as far as turning the stack trace entries into links. When
> you clicked on an entry in the stack trace, Eclipse would come to the
> front and open an editor on the file in question, highlighting the
> line in question. It was *really* cool.
>
> I was running a mini servlet container inside Eclipse and the
> generated links passed enough information back to open the right file.
>
> I never deployed it as it involved pretty ugly hacking in Tapestry 3.
>
> I understand that the Exception page is more configurable in T4 and
> hacks would not be required (I haven't tried it yet though).
>
> Would like to revisit this feature and solicit discussion. I know it
> seems strange to talk about GUI features when the core isn't working
> yet. I thought throwing this topic out now would be nice change from
> the long winded blathering of late.
>
> What are the issues you see in such a feature?
>
> I can think of a couple off hand:
>
> - how to ensure that someone does hijack your IDE window!
> - how to implement this in an IDE agnostic way so tools like tapidea
> can also benefit?
> - what would be the mechanism by which this feature is enabled during
> development but not there at all in production?
>
> Has anyone already taken advantage of the new "configurability" of the
> Exception page? What was the experience like?
>
> Geoff
>
> --
> The Spindle guy.          http://spindle.sf.net
> Get help with Spindle:
> http://lists.sourceforge.net/mailman/listinfo/spindle-user
> Blog:                     http://jroller.com/page/glongman
> Feature Updates:          http://spindle.sf.net/updates
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642
> _______________________________________________
> Spindle-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/spindle-user
>


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642