Martin Wood wrote:
im really interested in helping out, maybe a quick guide to 'working
with asdt' would help a lot of people just get past that first hurdle
of having the pieces they need.
http://www.eclipse.org/articles/index.html
i invested in some erich gamma eclipse books. but for an idea how things
work reading the asdt cvs and the link should be enough
Im particularly interested in working on the refactoring features, so
my first question is, whats the minimal set i need from CVS to start
working?
u should checkout the whole project to get an overview (where things
belong etc)
to organize this just create a new workspace (eclipse is great!)
refactoring should be a part of org.asdt.editor (i think)
Or do i need to check out all the pieces (org.asdt.*) ?
Then what would also be great is an example workflow for developing
asdt features.
hack. run/debug (repeat this step until it works) refactor. commit.
(run-> run/debug ..-> eclipse application)
I might end up writing some of this myself, but not within the next 2
weeks. Deadlines approach :)
thanks
Martin
p.s. would moving asdt to svn as part of osflash be a good idea? I get
no end of trouble with CVS from sourceforge, its really slow and its
forever flaking out in the middle of operations.
i like cvs... the whole thing works fine (yeah sf.net lags some times
but it should be ok for now)
moving an opensource project is very time consuming...
@carlos i know what ur talking about ;)
time will never come. time will rush away. thats time. but think of the
time u have
when asdt works like jdt (time will continue rushing away thats true).
anyway would be great !
i wish plenty of time for all of you !
if u get some take the time for friends and/or family rather than for
asdt ;)
Martin Schnabel
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
