From: "Eric M. Ludlam" <eric@siege-engine.com>
To: Jack Tanner <ihok@hotmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: development plans for cedet / semantic / nxhtml
Date: Wed, 19 May 2010 07:40:11 -0400 [thread overview]
Message-ID: <4BF3CE1B.8030209@siege-engine.com> (raw)
In-Reply-To: <loom.20100518T175352-897@post.gmane.org>
On 05/18/2010 12:27 PM, Jack Tanner wrote:
> I'm asking this as a user, not a developer, but I think the question belongs
> here because it involves coordination of development plans. The short version of
> the question is: is there work afoot to create a nice IDE for writing web apps
> in a mixture of object-oriented PHP, JavaScript, CSS, and XHTML? If so, what
> will that involve? nXhtml? CEDET? Semantic? Other elements?
Hi,
I'll put in what my plans are, but what you are looking for requires
more than just my efforts.
I'm trying to get upstream CEDET stabilized and better tested for
Emacsen before 23.2, and XEmacs. I think it's pretty close, but also
slow going since I don't get a lot of time in the summer for this sort
of thing.
After that, I want to convert my repository to match the file naming
scheme in Emacs to simplify merges.
Once that is done I'm hoping to focus on the "interface" part, and
remove the many UI parts that have organically grown over the past many
years, and focus on integration. I can't do that alone, as I don't use
most of the languages that CEDET supports, nor do I have to even write
code for my job anymore, so it will be a big effort in that respect to
find all the common use cases and start tuning things to those situations.
From a configuration point of view, I don't have a clear picture of
that doing anything but getting simplified over time.
Eric
prev parent reply other threads:[~2010-05-19 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 16:27 development plans for cedet / semantic / nxhtml Jack Tanner
2010-05-18 18:20 ` Chong Yidong
2010-05-18 19:11 ` Jack Tanner
2010-05-19 11:40 ` Eric M. Ludlam [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BF3CE1B.8030209@siege-engine.com \
--to=eric@siege-engine.com \
--cc=emacs-devel@gnu.org \
--cc=ihok@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.