[Padre-dev] Portable Padre - what is missing?

[Adam Kennedy]

I'm pondering this problem more generally, I think what is needed is
access to Portable.pm's intrinsic understanding of the concept of a
relative path.

I'm going to see if I can expose that functionality to the larger
world, and then Padre can just hook into that.

Adam K

2009/2/25 Gabor Szabo <szabgab at gmail.com>:
> So what is missing from Padre to be really portable
> as in "I can put it on a portable perl on a stick, plug it in
> a computer and run it" ?
>
> The only thing I know is the file pathes that the Padre remembers
> There are two types of files:
>
> Files located on the same device as Padre files that are loceted on the
> host computer. For the latter we should keep the file pathes as they
> are now as those files are not moving.
> On the other hand  files that are on the same disk as Padre is
> installed should be
> saved starting from the mounting point.
>
> In case of windows that means to leave off the drive letter: (d: k: or x:)
> In case of Linux it means we need to find the mount point which is a bit more
> complex.
>
> Any other things?
> Any ideas how to solve the above?
>
> Gabor
> _______________________________________________
> Padre-dev mailing list
> Padre-dev at perlide.org
> http://mail.perlide.org/mailman/listinfo/padre-dev
>