[Eclipsedotnet-developers] RE: I'm getting an error checking out from SVN

[<jpp...@gm...>]

I think that, for the current version of Eclipse (SWT-based, 2.1.3-based
Core, etc.), we should only do bug-fixing, and that we should start =
working
out the new SWF-based UI, for one. That would certainly have a =
much-greater
impact in the .NET community than the SWT-based version.


So, I would say that the most important for that is to start looking at =
the
semantics of Jface and start adapting it to .NET + SWF, meanwhile =
creating
additional useful mechanisms/features of our own for it. I had already
created a project in Development/SWF_UI/Nface to do exactly that. If you
wish to start adapting some Jface mechanisms (such as Actions, Wizards,
Windows, etc.) or create your own, feel free to do so - pick a mechanism =
(or
mechanisms) that you would like to work on, and go for it :) . Anyway, =
this
developing-something-new should be a lot more fun than =
bug-hunting/fixing ;)
.

Also, I would say that, when we begin this new-version development, we
should start taking a more test-oriented approach. I unfortunately had =
to
neglect that part last year, as I had only some months to create a =
working
platform, and porting the existing tests at the time would be (even =
more)
nightmar-ish.
One thing I've been meaning to do for a long time is take a good, long =
look
at Nunit and its internals and try to adapt it (or create a wrapper =
around
it) that would allow us to have test-plugins in the Platform (i.e., =
there
would be a Test core plugin - with some of Nunit's dlls included - that
would provide a framework for testing other plugins). So, if one wanted =
to
run all the tests available for the platform (assuming that the testing
plugins were present), one would only have to run Eclipse.NET specifying
that the application to run would be something like "Tests" (like =
Eclipse
itself does, nowadays).


So, pick your favorite, if you have one. If you don't have a favorite, =
I'd
recommend Jface/Nface, as it involves less research and most likely will
present a lot less problems to solve (so you can consider your time
well-spent :-) ).


I had forgotten to do so, but I'm attaching a svn-commit hook to our =
commits
mailing list.



BTW, just out of curiosity: for the OSGi-part that you have been doing, =
do
you already have a prototype of the API (i.e., the API more-or-less =
created,
even if it does nothing yet)? Are you basing your R&D on any particular
documentation? It's just that I would like to do some reading too, to
realize to some extent how currently existing plugins will be affected
(i.e., if we will/would use attributes to identify plugin classes, =
etc.).



Best regards,
JS



P.S.: I hope you don't mind, but I'm also sending this to the developers
mailing list, just for archival purposes, as it is related to the
development of Eclipse.NET .

=20

> -----Original Message-----
> From: Kunle Odutola [mailto:kun...@vi...]=20
> Sent: s=E1bado, 18 de Mar=E7o de 2006 15:01
> To: 'Jo=E3o Saraiva'
> Subject: RE: I'm getting an error checking out from SVN
>=20
> > Hey again.
> >=20
> > I've been trying out with the latest version of TortoiseSVN and it=20
> > sometimes still gives me the error. However, if I continue making=20
> > Update over the
> > (incomplete) checkout, it gets some more files.
>=20
> ;-)
>=20
> I worked that out and managed to get it to complete before=20
> you replied.
> Thanks anyway. I am doing an export right now to see if the=20
> same issues still apply.
>=20
> > I guess this means that we should, in future releases, also=20
> release a=20
> > zip file with the source code _and_ the .svn directories (so that=20
> > people can just get the source zip, extract it and then=20
> Update it to=20
> > get the latest - yet unreleased - source).
>=20
> Not sure about that. Sounds like a format that's more=20
> appropriate for nightly builds etc. A normal zip (without=20
> .svn dirs) with binaries-only and sources-only (or=20
> binaries+sources) is more suited to a release.
>=20
> Incidentally, I've got a little free time so, which=20
> tasks/moduels are highest priority?. I've had to put the OSGi=20
> for 3.x stuff on hold for the mo' due to time restrictions.... ;-(
>=20
>=20
> Thanks
>=20
> Kunle
>=20