Hi Bogdan,

AFAICT you can use Eclipse with the EPIC perl editor that also includes a graphical interface to the Perl debugger, giving you full execution control. I tried that once, but as Mike said it is not really needed in everyday work.

Best regards, mg

Am 11.09.12 09:09, schrieb Bogdan Iosif:
Thanks for the input.

I was "afraid" of that. I'm familiar with this type of debugging from writing shell scripts running under Jenkins but I've never done debugging like that for a code base as large as OTRS seems to be.

With shell scripts it was, kind of, simple to assess if the code is valid because I knew exactly where the script will be invoked from and my only concern was to explore the context of the call (mainly env vars). With these Perl scrips, without an IDE that halts execution on a breakpoint or a possibility to statically explore all callers on an object's method, I find it hard to imagine how I can ensure a change I make on some of the code OTRS ships with will not break some code paths or, worse, produce undesirable side effects.

I assume you mean Apache HTTPD's STDERR. I'll try to setup Fred. I hope this info is still valid (http://lists.otrs.org/pipermail/dev/2007-October/001728.html) because I haven't found much else in the form of a guide on how to use / install it.

/bogdan

On Mon, Sep 10, 2012 at 12:40 PM, Michiel Beijen <michiel.beijen@gmail.com> wrote:
Hi,

Setting up the 'dev' environment is pretty much the same as setting up
a 'regular' OTRS environment; you would set up an OTRS environment
including database and web server on your local machine.

For editing the files you can use pretty much any editor, some people
use complete IDE's such as ActiveState's Komodo IDE, Eclipse EPIC or
similar, or Padre, some people prefer to use text editors such as vim
with lots of plugins, or even simply Notepad++.

If you do OTRS development you typically do not use a debugger all
day; and inspecting elements can be achieved by printing them to
STDERR and looking in the server error log and/or using Fred
(http://ftp.otrs.org/pub/otrs/develtools/packages/); or by logging
them to the LogObject in OTRS.

Hope this helps.

--
Mike

On Mon, Sep 10, 2012 at 11:12 AM, Bogdan Iosif <bogdan.iosif@gmail.com> wrote:
> Hi,
>
> I'm trying to setup a dev env for OTRS on Windows and I'm new to Perl. After
> some poking around for a few days trying to understand Perl distributions
> and development, I'm still pretty much where I started.
>
> If a guide for setting up a specific dev env is available, can someone
> please provide me with its URL?
>
> If such a guide is not available, please help with the following direct
> questions:
>
> Is OTRS dev normally done via an IDE, and if so what is the preferred one? I
> tried to find an ide-project like grouping in the OTRS sources and couldn't
> spot one.
> Is it possible to load all the source files in an editor capable of finding
> method / object definitions? (I don't mean full text search but something
> like Intellisense)
> Is interactive debugging possible for OTRS? By this I mean setting
> breakpoints and exploring values for variables when a breakpoint is hit.
> Is there such a thing as syntax check, source compilation or unit testing so
> that I can be as sure as possible that changes I've made do not immediately
> crash when they are executed?
>
> I'm familiar with the dev workflow from Visual Studio (C#) and Eclipse
> (Java) and hoping to achieve something similar with OTRS, if possible. If
> someone can answer and is also familiar with those IDEs, please use them for
> comparison.
>
> Thanks,
> Bogdan
>
> What I've already done:
>
> - Got the sources from a zip package
> (http://ftp.otrs.org/pub/otrs/otrs-3.1.9.zip) because a direct CVS link
> doesn't work from my organization (port 2401 is blocked).
>
> - Looked over the dev manual
> (http://ftp.otrs.org/pub/otrs/doc/doc-admin/3.1/en/pdf/otrs_admin_book.pdf)
> and Searched the mailing lists (http://lists.otrs.org/pipermail/dev/) with
> Google. Couldn't find any references to an IDE.
>
> - Found info about debugging a running OTRS env by enabling a debug mode
> where I would get a lot of info logged to files.
>
> _______________________________________________
> OTRS mailing list: dev - Webpage: http://otrs.org/
> Archive: http://lists.otrs.org/pipermail/dev
> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev



_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

-- 
Martin Gruner
Senior Developer R&D

OTRS AG
Europaring 4
94315 Straubing

T: +49 (0)6172 681988 0
F: +49 (0)9421 56818 18
I:  www.otrs.com/

Geschäftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751, USt-Nr.: DE256610065
Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: André Mindermann (Vorsitzender), Christopher Kuhn, Sabine Riedel

It's raining... OTRS Feature Add-Ons! Bis zu 10 kostenlose OTRS Feature Add-Ons und professionellen Hersteller-Support  – Werden Sie jetzt Service-Subscription-Kunde!