[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [Dltk-dev] Scheme IDE posted - alpha version
|
In regards to 2)
In your site.xml add an associateSitesURL attribute to the
site element, this will point to a file that will contain a list of sites
with your external plugin dependencies, usually associateSitesURL is in the same
directory as your site.xml .
<
site
associateSitesURL="http://absolute/url/to/updates/associateSites.xml">
Inside your
'associateSites.xml', you list the sites , here is an
example:
<?
xml version="1.0"
encoding="UTF-8"?>
<
associateSites>
<associateSite url="http://download.jboss.org/jbosstools/updates/stable/site.xml" label="Hibernate
Eclipse Tools"/>
<associateSite url="http://download.eclipse.org/webtools/updates/" label="WTP/WST"/>
<associateSite url="http://download.eclipse.org/releases/europa/" label="Eclipse 3.3
updates"/>
<associateSite url="http://download.eclipse.org/tools/gef/updates/releases/" label="GEF Update
Site"/>
<associateSite url="http://download.eclipse.org/modeling/emf/updates/releases/" label="EMF" />
</associateSites>
Be
aware, that the Site Manifest Editor in eclipse, at least in 3.3 and below will
remove the 'associateSitesURL' attribute when you use the site manifest
editor , so after you have created your initial site.xml you may want to stick
with editing it by hand.
Another
way you can make it easier for your users is creating a second feature and
bundling the current version of DLTK with your release, you can do
this by editing your feature.xml inside the 'Included Features" tab and
this will include the DLTK feature(s) with your scheme plugin
feature.
congrats!
regarding your
questions:
1) i don't think so. when i prep for a release, i
bump all the version numbers on the plugin.xml files and the one in the
'feature.xml' file. on the 'plug-ins' tab on the 'feature.xml' editor, all my
plugins are listed w/ version 0.0.0, so every time i run a build, the newest
version is included. the only time i have to add a plugin to that list is if i
create a new one.
2) i believe this can be done, but have not
taken the time to investigate how to make it work b/c i am willing to cut
releases of my perl plugin against integration builds (some day that will
stop, but for now...) and those are not available via an update site.
On Mon, Sep 29, 2008 at 2:42 PM, William Cook
<william@xxxxxxxxx> wrote:
I've
uploaded a first working version of my
Scheme IDE based on DLTK. Its
called
Schemeide
http://schemeide.sourceforge.net/
I used the python
IDE as a starting point, took
out all the python-specific stuff and
added
some Scheme specific code.
On interesting thing is that I
include plugins
that contain executables for Gabmit Scheme
and a debug
engine for Gambit. Thus you can
install Schemeide and have a working
Scheme
system with debugger quickly and easily. If you
want to install
an executable within a plugin,
you can borrow code from me.
I have
mostly focused on formatting and
debugging. I have not implemented
source
outlining and folding, because I rarely use them.
There are
many other things that I need to do
first.
I have had a lot of
trouble with the update sites.
I have a few questions:
* Do you have
to re-add a feature to the update site
every time the plugin version
changes?
* Is there any way for one update site to refer
to another
update site for a dependency? I'd love
to point mine at the DLTK site to
get a full-automated
install.
Thank you all for your help on this.
I could not
have done it without DLTK. Note that the Scheme
community
in general cares little about this, because
they seem to prefer emacs and
command-line debugging
(or printf debugging). But I happy to
have
something like a real debugger for Scheme. Its still
not
completely real, because, well, you have to put in
breakpoints manually,
and then only on function entry.
But it does have stack inspection,
which
is the main thing. If anybody else wants to help,
let me know.
Its a work in progress.
William Cook
http://www.cs.utexas.edu/users/wcook
PS: I think my
plugins are still lacking some license
notices.. I'll update that over
the next few
days.
_______________________________________________
dltk-dev mailing
list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev
--
-jae