On 8 June 2017 at 07:18, Ben Coman <b...@openinworld.com> wrote:
> From a marketing perspective, it might be more palatable for existing
> Visual Studio users to install Pharo as an extension rather than install
> Pharo as a whole new IDE (i.e. Pharo) - a common complaint about Smalltalk
> in general.
>
JFYI: I have a very new project called Studio that will use Pharo as the
front-end for "add on" development tools.
The notion is to have a UI based on Pharo/Glamor that presents a unified
interface to a back-end built on many and various diagnostic tools (e.g.
perf, wireshark, etc, depending on what is relevant to a given application.)
The assumption is that people already have an editor, etc, but what they
don't have is an easy way to create application-specific development and
diagnostic tools. That's my situation, anyway, and I am initially the main
target user here.
Currently I am working towards teaching the Inspector to explore internal
data structures in a tracing JIT. This will provide end-users with
visibility into the way the JIT generates code (currently completely
inscrutable) and make for easy cross-referencing with profilers and
benchmarks. I am taking a semi-generic approach where the JIT will log raw
C structs and then the Studio IDE will use DWARF debug information to
import them for meaningful inspection ("gdb-style").
Link: https://github.com/studio/studio
Cheers,
-Luke
