[osflash] ASDT class paths
flashdev at relivethefuture.com
Wed Jun 15 03:32:16 PDT 2005
the perfect solution would be the ability to use both the project
references settings (right click -> properties on the project)
in combination with class path variables.
e.g. when doing java work i have a lot of common libraries set up as
classpath variables, 'XERCES', 'LOG4J' which point to where i keep them
on my computer, then the project just uses these variables to add to the
so, then i have the same set of variables setup whichever machine i use,
but the files dont need to be in similar locations.
id love to dig into extending the ASDT, and have read some of the PDE
docs, but its still a huge morass of confusion for me :)
i guess i should point an email towards the developers and ask 'how the
hell do i start adding X ?'
but if any of them are here, or anyone else can give some quick pointers
that would be damn handy.
i'll add these items to the list on the wishlist page, but my main
desires for ASDT would be (aka make it work like the JDT):
1. Automatic insert of import statements.
if i just wrote in my class private var someVar:SomeType; then id like
that handy red cross box on the left which i can click and it inserts
import statements for me.
2. Automatically creating interface methods
If im using implements, fine the compiler complains that ive not
implemented the interface, but again id like the handy button that
generates the method stubs.
3. Automatic unit testing classes
At the moment i have a similar set of templates as keith for generating
my asunit test classes, but would love to be able to generate test
methods for the class im testing, like, erm, the JDT :)
and so much more (like try / catch code, a plugin like Log4E etc..), but
they are a good start.
its only when leaving the warm comforts of the JDT do you fully realise
how much typing you have to do!
like i said, im willing to dig in and code some of these things, but its
quite a steep learning curve for plug in development (esp. while working
on another project at the same time..)
even just a pointer to some articles / tutorials about getting your
development cycle right for the PDE, common testing / debugging
techniques and that kind of thing would help.
Francis Bourre wrote:
> I use this way, the only prob is when i make an ant build, i can't use
> relative paths with virtual folders, i must hardcode the full path to
> access to the real folder.
> ----- Original Message ----- From: "Keith Peters" <kp at bit-101.com>
> To: "'xp at dr-dr'" <drmingdrmer at gmail.com>; "'Open Source Flash Mailing
> List'" <osflash at osflash.org>
> Sent: Wednesday, June 15, 2005 3:32 AM
> Subject: RE: [osflash] ASDT class paths
>> Ah. That definitely helps.
>>> -----Original Message-----
>>> From: osflash-bounces at osflash.org
>>> [mailto:osflash-bounces at osflash.org] On Behalf Of xp at dr-dr
>>> Sent: Tuesday, June 14, 2005 9:00 PM
>>> To: drorex at berkeley.edu; Open Source Flash Mailing List
>>> Subject: Re: [osflash] ASDT class paths
>>> in eclipse navigator,you can link an exist directory to a
>>> folder in your project,by selecting 'new fold' form context
>>> menu,& choose 'link the fold to file system'.then you can add
>>> this virtual folder to your project classPath,without moving
>>> ur pounds of classes:) but there still seem to be some
>>> problems,the class contained in virtual folder cant be found
>>> by the 'mtasc view' of asdt,while errors occur & you click
>>> 'go to problem' button in 'mtasc view'..
>>> On 6/15/05, David Rorex <drorex at gmail.com> wrote:
>>> > I agree, we use a large library of common classes shared
>>> among all our
>>> > projects, which would be nice to have support for
>>> > -David R
>>> > On 6/14/05, Keith Peters <kp at bit-101.com> wrote:
>>> > >
>>> > > One enhancement I'd love to see in ASDT is the addition
>>> of multiple
>>> > > class paths.
>>> > > Currently, you have the chance to enter a class path to
>>> > > core classes only.
>>> > > In a project, you can enter class paths only to
>>> directories within
>>> > > the project.
>>> > > I usually store my own utility classes in a separate
>>> directory like
>>> > > c:\classes. There is no way to add that to my class path
>>> in Eclipse.
>>> > > I wound up moving them into the MM folder, but it would
>>> be good to
>>> > > be able to specify multiple non-project class paths in this way.
>>> > >
>>> > > Keith
>>> > > _______________________________________________
>>> > > osflash mailing list
>>> > > osflash at osflash.org
>>> > > http://osflash.org/mailman/listinfo/osflash_osflash.org
>>> > >
>>> > >
>>> > >
>>> > _______________________________________________
>>> > osflash mailing list
>>> > osflash at osflash.org
>>> > http://osflash.org/mailman/listinfo/osflash_osflash.org
>>> osflash mailing list
>>> osflash at osflash.org
>> osflash mailing list
>> osflash at osflash.org
> osflash mailing list
> osflash at osflash.org
More information about the osflash