Re: [Dltk-dev] IScriptBuilder/IBuildParticipant questions

[Alex Panchenko <alex@xxxxxxxxx>]

One can use external checker without programming - it is developed for end users and is fully configurable via UI.
Preferences - DLTK - Validators - [Add] and so on.

Alex

----- Original Message -----
From: "Jae Gangemi" <jgangemi@xxxxxxxxx>
To: "DLTK Developer Discussions" <dltk-dev@xxxxxxxxxxx>
Sent: Monday, September 29, 2008 8:49:59 AM GMT +06:00 Almaty, Novosibirsk
Subject: Re: [Dltk-dev] IScriptBuilder/IBuildParticipant questions

  i'm confused by what you mean about first testing it and then building a
perl specific implementation.

On Sun, Sep 28, 2008 at 9:45 PM, Alex Panchenko <alex@xxxxxxxxx> wrote:

> They are similar.
> tclchecker is designed to run one specific application,
> external checker could run any application - user is able to configure
> patterns to be parsed in the UI
>
> I mean first you could test it with the external checker and after that
> make a specific implementation for perl.
>
> Alex
>
> ----- Original Message -----
> From: "Jae Gangemi" <jgangemi@xxxxxxxxx>
> To: "DLTK Developer Discussions" <dltk-dev@xxxxxxxxxxx>
> Sent: Monday, September 29, 2008 8:38:45 AM GMT +06:00 Almaty, Novosibirsk
> Subject: Re: [Dltk-dev] IScriptBuilder/IBuildParticipant questions
>
>
>
>
> are there any working examples of something run via an external validator?
>
> how does an external validator differ from what is used in the 'tclchecker'
> implementation?
>
>
> On Sun, Sep 28, 2008 at 9:24 PM, Alex Panchenko < alex@xxxxxxxxx > wrote:
>
>
> Hi Jae,
>
> IScriptBuilder is a general DLTK API to help with implementing builders -
> it accepts the list of source modules that should be built.
>
> IBuildParticipant is an API to provide simple "steps" to be executed by
> some standard builder. The idea is that subsequent steps may need some
> information provided by the previous - e.g. the AST, so file would be parsed
> only once.
>
> Regarding the 'perl -c' - first you should try running it via external
> validator (this is a separate plugin to run external modules and parse the
> output).
>
> Regards,
> Alex
>
>
>
>
> ----- Original Message -----
> From: "Jae Gangemi" < jgangemi@xxxxxxxxx >
> To: "DLTK Developer Discussions" < dltk-dev@xxxxxxxxxxx >
> Sent: Monday, September 29, 2008 6:50:59 AM GMT +06:00 Almaty, Novosibirsk
> Subject: [Dltk-dev] IScriptBuilder/IBuildParticipant questions
>
>
>
> hello all -
>
> i was wondering if someone could explain the direction that is being taken
> with the IBuildParticipant and associated interfaces that have been added to
> 'org.eclipse.dltk.validators.core' and the different between implementing an
> IScriptBuilder interface.
>
> i'd like to add compiler support to my plugin (ie, 'perl -c') - i started
> looking into implementing an IScriptBuilder, but it also seems that i could
> implement an IBuildParticipant as well, but that is controlled by the
> ValdatorRuntime, which itself is an implementation of an IScriptBuilder, so
> these things are all related.
>
> perhaps there should be something like a 'BuilderRuntime' that controlled
> IBuildParticipants, and the ValidatorRuntime would control
> IValidatorParticipants. things like compiling, task tag parsing, etc would
> be executed by the BuilderRuntime and anything that serves to validate
> source would be executed by the ValidatorRuntime, both would run as part of
> an auto build and the validators could still be run independently.
>
> --
> -jae
>
> _______________________________________________
> dltk-dev mailing list
> dltk-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dltk-dev
> _______________________________________________
> dltk-dev mailing list
> dltk-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dltk-dev
>
>
>
> --
> -jae
>
> _______________________________________________
> dltk-dev mailing list
> dltk-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dltk-dev
> _______________________________________________
> dltk-dev mailing list
> dltk-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dltk-dev
>



-- 
-jae

_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev