Hi!
On 12/9/06, Roberto Saccon <[EMAIL PROTECTED]> wrote:
to use erlide at its full capacity for erlang webdevelopment with
Yariv's erlyweb framework, the following little changes would bring
big benefits:
allow several source folders, each with a configurable output folder
or no output at all (the framework does compile modules automatically
itself and erlide is just for syntax check)
The latter is relatively easy to implement.
allow several include directories (which seems currently to be broken)
and allow relative paths.
In-project include directories can be several (enter them in the field,
semicolon separated). It is external includes that need more work.
on the long term there could bee even more integration, for example
some GUI support for starting/stopping yaws embedded from erlide, with
its own tab at the Erlang console and much more.
Yes, there are such things that wait in the pipeline. There is even a
feature request filed about supporting yaws development. On my agenda,
however, such things have quite low priority. I want to concentrate on the
general support for Erlang, where most people can benefit.
Help is welcome, and who is better qualified to define the requirements and
implement them than those who use ywas and erlyweb and whatnot? ;-) hint,
hint!
I am interested to
digg into this area, but what I am missing are some simple
instructions (and requirements) how to get started. Well, I just
installed the Plugin-Development-Environment Plugin into eclipse,
that's a first step at least ...
There is a steep learning curve, because Eclipse is so large. But for me it
worked fine by diving into it and trying to implement a plugin. Checking
other plugin sources helps too (but take some simple plugins, not the JDT).
Have the documentation handy. Read also the Eclipse FAQ. Many questions are
also answered in the forums (which can be viewed also at www.eclipsezone.com
).
What needs coordination is that we might need to define extension points in
Erlide where other plugins can add their own functionality. Also, we need to
improve how the Erlang backend is handled - right now there is only one, but
it should be possible to have one per project, either local or remote.
Please feel free to ask questions, the more specific the better.
best regards,
Vlad
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Erlide-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/erlide-devel
