Well, I wanted to start somewhere :-)
(And know how my Saros/I implementation should handle that)
Holger Schmeisky; holge...@fu-berlin.de
Takustraße 9, Room 008, Freie Universität Berlin, 14195 Berlin
+49 176 64146306
Am 21.08.2014 22:58, schrieb Stefan Rossbach:
> The IPN is full of VCS/SVN stuf
The IPN is full of VCS/SVN stuff. Those ResourcePlugin calls are the
smallest problem.
On 21.08.2014 19:53, Holger Schmeisky wrote:
> I was thinking of a unified solution for example for IPN. In there we
> have lots of ResourcePlugin.getWorkspace() calls (e.g. line 357). To
> move IPN to the co
I was thinking of a unified solution for example for IPN. In there we
have lots of ResourcePlugin.getWorkspace() calls (e.g. line 357). To
move IPN to the core package that call has to be replaced by the same
mechanism. Your suggested solution is fine for Saros/I, but is there
anything that pre
On 21.08.2014 17:11, Holger Schmeisky wrote:
> Oh my.. OK for a v0.1 I would use plain files and advise the first
> user not to use anything but plain file systems with IDEA.
>
The user will not get this right, believe me. Some users for example
still fail to read the "files will get overwritten"
?
There is already an IWorkspace interface.
Implement it and put in the PICO plugin context container = problem solved
On 21.08.2014 17:02, Holger Schmeisky wrote:
>
>
> Holger Schmeisky; holge...@fu-berlin.de
> Takustraße 9, Room 008, Freie Universität Berlin, 14195 Berlin
> +49 176 64146306
>
Oh my.. OK for a v0.1 I would use plain files and advise the first user
not to use anything but plain file systems with IDEA.
Back to the original question: When I call project.getFile() and create
a plain io.File handle, it should work the same as for eclipse.IFile, at
least for "simple" file
Holger Schmeisky; holge...@fu-berlin.de
Takustraße 9, Room 008, Freie Universität Berlin, 14195 Berlin
+49 176 64146306
Am 21.08.2014 14:24, schrieb Stefan Rossbach:
> On 21.08.2014 08:54, Holger Schmeisky wrote:
>> Hi,
>>
>> I would like to refactor the IProject implementation in Saros/I and ha
oes not weaken your point.
> In fact, this should make clear that every Eclipse user (not only the
> Git-infected ones) can be affected.
>
> Franz
>
>
> -Original Message-
> From: Stefan Rossbach [mailto:srossb...@arcor.de]
> Sent: Thursday, August 21, 2014 2:24
e user (not only the
Git-infected ones) can be affected.
Franz
-Original Message-
From: Stefan Rossbach [mailto:srossb...@arcor.de]
Sent: Thursday, August 21, 2014 2:24 PM
To: Holger Schmeisky; dpp-devel@lists.sourceforge.net
Subject: Re: [DPP-Devel] Projecthandles in Eclipse
On 21
On 21.08.2014 08:54, Holger Schmeisky wrote:
> Hi,
>
> I would like to refactor the IProject implementation in Saros/I and have
> a few questions about how the Resources API works in Eclipse:
>
> * Is ResourcesPlugin.getWorkspace().getRoot() the best way to get at
> the workspace?
It is the onl
Hi,
I would like to refactor the IProject implementation in Saros/I and have
a few questions about how the Resources API works in Eclipse:
* Is ResourcesPlugin.getWorkspace().getRoot() the best way to get at
the workspace?
- If yes, We will need a unified mechanism for getting projects
11 matches
Mail list logo