Re: Where implement Upload Profiles?

On Thursday 14 February 2008 10:16:45 am Niko Sams wrote:
> Hi,
>
> >  Ah... what I always wanted to stop short of because I would argue that
> > the only intelligent way to do this was CVS or SVN.
>
> Yep, absolutely true.
>
>
> What do you think about a Sync-Tool? Probably integrated in the
> Upload-Dialog - or as additional tool.

Actually...

> It could work like this great application:
> http://www.kde-apps.org/content/show.php?content=33545

Ha! I could build that in Kommander in a few hours! Seriously though, looks 
nice, but also looks only local.
>
> With such a tool you can before starting to work on a project check if
> there are changed files on the
> server and download them. If the file is changed on both sides it
> won't work of course.

Actually now that Kommander can make KParts and Andras put in the project menu 
to easily load a part with a file name this was one of the things I was 
thinking of doing now for the KDE3 version. It would be a KPart, and I was 
thinking of using a PHP file for remote, but as I can do KIO in some ways 
that is also possible. However I might need have a challenge listing a 
directory with KIO and I don't want to embed a part for this.

However for the KDE4 version my primairly thought was that anything we do 
should integrate with the Actions. So if someonewanted to use a program like 
Sitecopy or something else, or include a script that ran on site, that we 
could insure they could access what they want easily either through the 
upload dialog or even in place of it.
>
>
> Another idea:
> When uploading a file store the file somewhere hidden in the local
> filesystem. The next time the user
> uploads the file again it can be compared to the server-side-file.
> This might also work with checksums.

It would be best just upload checksums with a file and check them on upload.
>
> > we could consider offering to synchronize prior to upload, or get updates
> > first from SVN/CVS
>
> That sounds very good (or at least check for updates before upload and
> stop the upload if there are
> updates)

Possibly, but you're on the right track. You can have it do an Action before 
or after upload. So now the question is whether the Action just processes or 
can halt the upload, or whether the upload checks the status of an action and 
can halt if it is negative... probably the better course. It is a matter of 
how to most rationally insure the two are aware of each other.
>
> Niko

My compliments Niko. You really do a good job thinking about the 
possibilities. Thankfully Andras still lets me take responsibility for a few 
of the ideas in Quanta too. ;-)


-- 
Eric Laffoon
Project Lead - kdewebdev module