support for remote projects (fish / ftp / etc.)

[Milian Wolff]

On Wednesday 25 March 2009, Niko Sams wrote:
> On Tue, Mar 24, 2009 at 9:29 PM, Milian Wolff <mail at milianw.de> wrote:
> > I just tried to create a remote project via fish and it did not work.
>
> Why do you need a remote project?
>
> We could use KIO in the php parser - however that would be incredibly slow
> I guess.
> The Generic Project Manager wouldn't be very fast too.
>
> And for compiled languages this would hardly ever be needed(?)

Sure, compiled languages don't make any sense here.

But for a scripting language like PHP it should "just work". And parsing is 
just as fast as locally since when you open a file in the editor it's 
downloaded once and then the editor contents are parsed.

Of course, when you parse the whole project it will be slower than locally 
because it will have to download each and every file first and parse it 
afterwards.

But in a LAN (like at my work place) it's still pretty fast.

If OTOH remote projects should be forbidden I'll implement that into the "open 
project" dialog (since right now you can use KIO / remote even though it's not 
supported).

Then we would need to wait for Quanta and it's "remote sync" feature from back 
then (though the one in KDE3 was painfully slow).

So what's the project's stand on this? The options I see right now:

1. make it possible to create remote projects, either by chaning the generic 
project manager or by introducing a remote project manager. Do project 
managers have .desktop files? We could have a X-KDevelop-Project-Can-Be-Remote 
(or whatever) flag in there. This will make it possible to prevent users from 
trying to run cmake/gdb/whatever on remote projects. If I'm not mistaken at 
least XDebug can debug remotely

2. when a user wants to create a remote projects tell him it's not possible 
and give him the option to copy the project (i.e. the chosen remote folder 
with its contents) to a local path of his choice. Then continue from there. 
Additionally introdue the "remote sync" option for those projects, i.e. in the 
context menu of the project. See Quanta3 for how this could look like.

3. forbid remote projects, wait for Quanta4 and let it do one of the above 
somehow.


Looking forward to more input on that topic!
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20090325/f97adec0/attachment.sig>