That's probably true for stepping through the code - I hadn't thought
of that. OTOH, it still might be valuable for auto-complete - without
the source, Eclipse doesn't know what variable names to use when you
create a new class or method - they all come out as "arg0", "arg1",
etc. It's very convenient not to have to look at the Javadoc when you
want to override or implement a method.
We could also consider including debug binaries, in addition to the
release ones.
On Jun 5, 2009, at 12:58 PM, Todd Volkert wrote:
This only makes sense if we turn on debug info in our binary jars --
we
currently don't. Without debug info, the IDE won't know which line is
executing anyway, so the source is meaningless. I'd suggest that
someone
wanting to step through Pivot code when they debug their app should
just
download the source distribution and build it themselves, then point
their
IDE there.
-T
On Fri, Jun 5, 2009 at 11:07 AM, Greg Brown <[email protected]> wrote:
Hi all,
I'm wondering if it might be valuable to add source JARs to the
binary
distribution; e.g. in addition to pivot-core.jar we'd also include
pivot-core-src.jar. This would allow projects using Pivot to step
into Pivot
code as necessary as well as take advantage of auto-complete features
provided by an IDE. Anyone else think this is worth doing?
Greg
