Enhancing the volumes function (was Volume Size)

[JB]

I would like the proper info about the volume path, size in
bytes, available space in bytes and amount of bytes used
along with the type of drive etc and if it is mounted so I can
sector read and write to the volume.

I have no intention of creating a program for people to sector
read and write files.  It is simply a part of my file handling.  But
for those who are interested in sector reading and writing for
any reason below is a link to a free app that works on Mac ppc,
windows and linux.

http://apps.tempel.org/iBored/

In one of the updates it mentions he improved it so you can
even sector write to a volume that is not mounted.  This is
very powerful software and you can damage your info if you
do not know what you are doing but if you do know what you
are doing it can be very helpful.  It is a good tool to have!

John Balgenorth



On Oct 16, 2014, at 7:24 AM, Richard Gaskin <ambassador at fourthworld.com> wrote:

> The other day I wrote:
> 
> > Warren Samples wrote:
> > > The dictionary does indicated, by omission of the penguin icon,
> > > that 'volumes()' is not supported under Linux.
> >
> > Seems a silly omission, so I just submitted a request for that:
> > <http://quality.runrev.com/show_bug.cgi?id=13673>
> 
> That request has gotten some healthy attention from the core dev team at RunRev, but the nature of the request has expanded beyond the original goal of simply making volumes() work on Linux.
> 
> It occurred to me shortly after posting it that the current return value, consisting of volume names only, is close to useless on all three platforms.
> 
> On Mac, is the volume mounted at /Volumes/ or at /?
> On Linux, is it at /mnt/ or /media/<user>/, or somewhere else?
> On Windows, what drive letter is it mapped to?
> 
> In short, the volume name alone is insufficient to actually do anything meaningful with it.  In fact, I'm hard pressed to think of any circumstance where it might have been useful beyond Mac Classic.
> 
> The team is exploring many options, but the key to all of this boils down to this question:
> 
> What do we want to use a volumes function for?
> 
> Knowing the use cases the function should support will be very helpful in guiding the design decisions around this enhancement.
> 
> If you have a specific use case in mind, please feel free to add it in the comments for that request.
> 
> -- 
> Richard Gaskin
> Fourth World Systems
> Software Design and Development for the Desktop, Mobile, and the Web
> ____________________________________________________________________
> Ambassador at FourthWorld.com                http://www.FourthWorld.com
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>