The biggest issue/goal with asdt was trying to get real time error detecting in. That never happened... because its hard, and they were trying to do their own parser based on antlr. This is hard stuff, particularly if its not your area of expertise.
Again, this is why I made the other post around a strategy for that issue. Because beyond that, making an eclipse program that makes projects and edits text is really no big deal. We already have that in asdt/hxdt. I'm not saying that more work in the basic areas doesnt need to be done with asdt/hxdt, but without dealing with the hard stuff, prettying up these apps is a little like putting lipstick on a pig. Regards, Hank On 8/30/06, Keith Peters <[EMAIL PROTECTED]> wrote: > So who was working on ASDT originally? > Can we just ask them why they stopped, if they could be convinced to > start again, what it would take, would money help? > If they aren't interested in carrying it on, is there anybody else who > would be interested in picking up the ball? If so, what would it take to > get them to dive in? Would money help? > Seem silly to talk about raising money if we don't have a person / team > named to work on it, or know if money is even something they are > interested in. > > Aral Balkan wrote: > > I think we need to identify the main issue here: Is it lack of funds > > or lack of expertise or a lack of need? > > > > Lack of funds: > > > > It's possible that this is holding people back and may explain the > > success of FDT (where there is a clear profit motive.) That said, not > > sure how well FDT is doing in terms of generating profit (I hope it's > > doing well.) > > > > Which brings me to: > > > > Lack of expertise: > > > > As I understand it (and correct me if I'm wrong) the FDT folks played > > a very important role knowledge-wise in the dev of ASDT. Advanced > > Java devs who also have intimate Eclipse platform knowledge don't > > really grow on trees (and if they do, send me seeds now baby 'cos I > > wanna plant some!) > > > > But the most important thing is: > > > > How big a need is there for an Eclipse-based solution? Would > > FlashDevelop, for example, be a better solution to support and > > perhaps port to Mono for cross-platform compatibility. (I do use/ > > enjoy Eclipse greatly but I am also aware of its weak points -- > > mostly that it is an all-or-nothing behemoth of a solution that may > > be overkill for most users.) That said, if you took my Flex Builder 2 > > from me it wouldn't be a pretty sight. So perhaps I am being very > > biased here because I already have a great solution for writing AS3/ > > Flex 2 in an Eclipse-based tool (FB2.) > > > > This message isn't really meant to offer a solution but spark some > > debate. > > > > Thoughts? > > > > Aral > > > > On 30 Aug 2006, at 11:39, Matthias Dittgen wrote: > > > > > >> I am thinking much the same as iiley in this point. I enjoy using > >> open-source projects and I am also giving back to the os community by > >> offering my code as open-source when possible, but I can't afford a > >> lot of money and I a haven't yet programmed eclipse plugins. I might > >> try, if I would have time. It's not a question of time and knowledge, > >> but of time, too. > >> > >> Btw. Where do I find the ASDT sources to take a look at it? I can't > >> find at www.asdt.org > >> > >> Matthias > >> <snip> > >> > > > > _______________________________________________ > > osflash mailing list > > [email protected] > > http://osflash.org/mailman/listinfo/osflash_osflash.org > > > > > > > > > > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org > _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
