Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Newsgroups: comp.lang.python
Date: Sat, 23 Mar 2013 08:07:07 -0700 (PDT)
In-Reply-To: <mailman.3630.1364037098.2939.python-list@python.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=96.241.97.37; posting-account=_dIAQQoAAAB7Yieol6fmkK_HviJUbJt3
References: <fdae24a7-13f1-47b2-90f2-e23881841175@googlegroups.com> <514CFEDA.4030903@gmail.com> <mailman.3621.1364007564.2939.python-list@python.org> <8b1e5da2-7f80-4f68-a4f1-b4d1f36dd198@y7g2000pbu.googlegroups.com> <mailman.3630.1364037098.2939.python-list@python.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Subject: Re: LiClipse
From: Wanderer <wanderer@dialup4less.com>
To: comp.lang.python@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: rusi <rustompmody@gmail.com>, python list <python-list@python.org>
Precedence: list
Message-ID: <mailman.3643.1364053835.2939.python-list@python.org>
Lines: 161
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:41740

On Saturday, March 23, 2013 7:11:10 AM UTC-4, Fabio Zadrozny wrote:
> On Sat, Mar 23, 2013 at 12:38 AM, rusi <rusto...@gmail.com> wrote:
>=20
>=20
>=20
>=20
> On Mar 23, 7:58=A0am, Fabio Zadrozny <fabi...@gmail.com> wrote:
>=20
>=20
>=20
> > Hello there,
>=20
> >
>=20
> > As I've proposed it, let me try to explain it a bit better (if you have
>=20
> > doubts, I should probably rephrase the proposal).
>=20
> >
>=20
> > There are 2 main targets there: keeping PyDev properly supported (which
>=20
> > hopefully doesn't need more explanation) and creating LiClipse.
>=20
> >
>=20
> > The idea for LiClipse is definitely not making a fork, but having an ea=
sier
>=20
> > way to add a basic editor inside Eclipse (while developing PyDev, I do =
get
>=20
> > many requests for adding support for editors related to Python, such as
>=20
> > Django templates, Mako, Restructured text, Cython, etc), so, this will
>=20
> > provide me with a basis to do that (and with the basis in place, the id=
ea
>=20
> > is having the possibility of creating an editor without knowledge of
>=20
> > Eclipse and in a very fast way -- current technologies for that such as
>=20
> > DLTK or XText aim much higher and are not trivial. I really want to hav=
e a
>=20
> > way to have a basic editor inside Eclipse just specifying the language =
very
>=20
> > 'loosely' -- say, something that'd take you 15-30 minutes and almost no
>=20
> > special knowledge of Eclipse internals -- and which would need more
>=20
> > knowledge of Eclipse internals only for more advanced stuff).
>=20
> >
>=20
> > As for the dark theme, it's something that annoys me a lot (so, I was
>=20
> > hoping it was also something interesting for other people -- right now,
>=20
> > it's not possible to have a professional dark theme in Eclipse, there a=
re
>=20
> > many loose ends -- so, for those that would like to work with a dark th=
eme
>=20
> > -- as myself -- it may be very annoying -- although yes, it may not be
>=20
> > applicable if you're happy with the current non-dark UI).
>=20
> >
>=20
> > As for distributions, yes, I plan to do an Eclipse distribution with
>=20
> > LiClipse / PyDev bundled -- Easy Eclipse is definitely not a solution a=
s it
>=20
> > is NOT supported (it has an ancient version of PyDev which only serves =
to
>=20
> > confuse users and Eclipse.org does not have a Python version with PyDev=
).
>=20
> > I'd hardly call that a fork thought (and it should be possible to insta=
ll
>=20
> > it as a separate plugin anyways, so, you can use the Eclipse you got fr=
om
>=20
> > anywhere and just use the update site to get those plugins).
>=20
> >
>=20
> > Cheers,
>=20
> >
>=20
> > Fabio
>=20
>=20
>=20
> I am interested in the new eclipse plugin capabilities.
>=20
> Where does liclipse stand with respect to this?
>=20
>=20
>=20
> The idea is providing a way to add a language just by saying things like =
keywords, elements (such as function or class -- if your language has that)=
, indenting words and it'll provide you an editor that has all the common f=
unctions you'd expect, such as syntax highlighting, outline, indenting, tem=
plate completion, etc. So, in LiClipse, you shouldn't need to create a plug=
in at this level, just one configuration file (which you should be able to =
fill in 15-30 minutes).
>=20
>=20
>=20
>=20
> After that, if you want more things (such as code analysis or a semantic =
aware code completion), then you'd have to go the route of actually creatin=
g an Eclipse plugin.
> =A0
>=20
>=20
> ie Eclipse-4 claims to have made plugin development (for new custom
>=20
> languages) easier.
>=20
> What is the relation of liclipse to eclipse 3<->4 plugin architecture?
>=20
>=20
>=20
> Well, it may have become a bit easier (with dltk and xtext), but it's sti=
ll far from trivial (you still have to know at least java, how plugins work=
, eclipse internals, creating a grammar, etc.).
>=20
>=20
>=20
>=20
> The editors structure for LiClipse should work in both Eclipse 3 or 4, al=
though the theming enhancements will require Eclipse 4 (as it'll need some =
features only available there).
>=20
>=20
>=20
>=20
> Cheers,
>=20
>=20
> Fabio

Thanks for the response. Now I understand better what you're trying to do. =
Eclipse can be something of a pain to get basic support to use new language=
s. I never was able to get it to work with Vpascal. I would also like the b=
undle, since I can't get the version in the lab to work like the version on=
 my desk. I've never been one for dark themes. My pet peeve is the battle o=
ver negative numbers between PyDev and pep8.py. PyDev put the space in and =
pep8.py gives me a warning.

Anyway, PyDev deserves my support and thank you for all your hard work.