[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [atf-dev] Re: Mozilla Perspective needs Problems
|
At 08:14 AM 6/30/2006, you wrote:
In terms of thinking smaller, we can always offer "features" to install
separately, so one can check off a box or two and not take all of
ATF. The problem is that it's the JS/HTML editors right now that are
rather heavy-weight, and they're central to most of the functionality in
an IDE.
At least as far as I have seen the JS/HTML editors are far short of the
Eclipse Java editor or say Dreamweaver for HTML. I actually think the
concept of "editor-centric IDE" is a bit off the mark for JS/HTML/AJax:
these dynamic languages gain little from the kind of assistance we have
come to enjoy in Eclipse for Java. A debugger centric model is likely to
be more successful.
If you think it would be useful to have any of the other features in
isolation, such as the JS debugger or Mozilla runtime tools, let's make
sure they're available this way, if we can get the dependencies right.
As for building from CVS, if we don't have a README explaining how to do
this, we need to. Another bug [bug #149312] It should basically work,
assuming you have all the prereqs installed in your Eclipse workbench
(WTP, Rhino, etc...)
After a while I figure out that the org.eclise.atf module is really a whole
bunch of projects org.eclipse.atf.* which can be loaded with
File-Import. But since it does not compile I guess that the effective
prereq for building is the CVS tree for eclipse? Rather than, saw building
against a stable branch?
_______________________________________________
atf-dev mailing list
atf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/atf-dev
______________________________________________________
John J. Barton email: johnjbarton<at>johnjbarton.com
http://www.johnjbarton.com
