Re: nautilus gvfs-afc property page info



Sorry, I don't understand what the issue is. I see properties item for the devices I have.
So I do not know what we are supposed to do.

Best regards,
Carlos Soriano

-------- Original Message --------
Subject: Re: nautilus gvfs-afc property page info
Local Time: October 10, 2016 7:19 PM
UTC Time: October 10, 2016 5:19 PM
From: gtwa001 gmail com
To: Carlos Soriano <csoriano protonmail com>
nautilus-list gnome org

Hello,

Just clarifying what you mean by upstream.

Would it be possible to add this RFE to nautilus as I opened a bug against gvfs-afc
which was closed with a link on the original bug in gnome. - and the words
Nothing to do with gvfs itself.

https://bugzilla.gnome.org/show_bug.cgi?id=741302

https://bugzilla.gnome.org/show_bug.cgi?id=771967

Regards
Timothy Ward



On Mon, 2016-09-26 at 01:40 +1000, Timothy Ward wrote:
Hello,

Sorry for any confusion the cross post came from

https://lists.fedoraproject.org/archives/list/devel lists fedoraproject org/thread/SQCBUTTROOM6GRX3MUZZN3WKZSP42K3E/

My thoughts are that the functionally should be available to be able development of sync of contacts, notes, photos, calender  and meeting info etc
which is clearly lacking between any linux device and an idevices, That which is considered the IP or copyright of the idevice owner or is considered
in the public domain.

But should not extend to the music database or any other area that may infringe the commercial or legal writes of the manufacturer of the idevice
or developers of any software on the idevice or any non idevice owners copyrighted material  in any form whatsoever.

Unfortunately when you open the door it could be extended to area's above, so even having the support optional when we are dealing with
floss software with released source code may be impossible to actually stop.

I am not aware of any restriction but the post on fedora devel mailing list may reveal something in that regard.

I hope that a path can be found to allow integration for the above which in my opinion is overdue for the linux device.

Best Regards

Timothy Ward


On Sun, 2016-09-25 at 10:15 -0400, Carlos Soriano wrote:
Hello,

The email without context was hard to follow. Would be nice to have some explanation what is the email about for next time :)

Regarding the properties in the sidebar, no idea why we decided to not show it. To me it makes sense to show that in every entry in the sidebar (except Other Locations).
Also, this should go directly into gvfs or so and I think some part of the UI integrated in Nautilus would be cool too.

Any reason to not do that upstream? We can make the support optional if there are legal issues for some distributions.

Best regards,
Carlos Soriano


-------- Original Message --------
Subject: nautilus gvfs-afc property page info
Local Time: September 25, 2016 3:38 PM
UTC Time: September 25, 2016 1:38 PM
From: gtwa001 gmail com
To: nautilus-list gnome org

Posted from a thread on fedora develop list as info for nautilus
maintainers and developers.

Yup. The "normal" mount contains nothing that normal users should
access.
> Accessing the photos will leave ghosts on the device, and there have
been no
> ways to update the music database in Linux for a few iOS releases.

I very much doubt that anyone would release any code to touch an
idevice music database due to fear of
legal action from the manufacturer. It may exist already.

The ability to sync contacts, calendars and events, meeting info,
notes, pictures etc ( anything that would be considered the personal
data entered by the idevice owner is another matter entirely. Anything
that the law provides in most countries such as the IP to that person
or the copyright of documents or photos etc, and yes it can be a very
grey area between the laws in different countries. This is just the
other side of the coin but this time from the owners perspective and
legal rights.

is 

> You can still access the device by editing the URL in the "Documents
on..."
> location. Just remove the ":3" at the end.

Thanks for this info,

> If you have use cases that aren't the 2 mentioned above, or using
your iDevice
> as a thumb drive, please file bugs against gvfs in the upstream
GNOME Bugzilla.

> Cheers


While I agree for the normal non developer user, the removal, to be
able to access what you could originally access, on the idevice before
the code change, may be of little value.

It is frustrating if you are developing applications and need access
to these areas for debugging, checking directory, files and structure
etc of the idevice. 

It is even more frustrating when the Fedora workstation is being
targetted as a developer's platform, and it also affects any
downstream distribution developers in the same way.

While nautilus still exposes the pictures on an idevice
through  gphoto2 system does not seem to have changed. 

As far as I am aware it is possible to copy pictures from the idevice
but transfers of pictures to the idevice will succeed, but will not be
shown on the idevice by native apps without further hacking.

The other mount exposes the so called document folder of some user
installed apps on the idevice and may be useful for someone developing
but is off limited use to a normal non developer user, unless the
normal non developer wants to use the phone as a usb drive to
transport files without carrying an extra usb drive.

The removal of the nautilus properties page on a connected idevice
does have an effect that a nautilus-ideviceinfo extension that has
been in gnome git for many years cannot be easily exposed and used and
a gnome bugzilla entry has been active from last year without even a
comment to date. 

https://bugzilla.gnome.org/show_bug.cgi?id=741302

https://git.gnome.org/browse/nautilus-ideviceinfo/log/?ofs=100

http://blog.sukimashita.com/2015/01/09/gtk-3-support-for-nautilus-idev
iceinfo/

I hope this can  be resolved in the short term as it provides all
users of idevices with info that is expected today and further
benefits the foss community and the goals of Fedora, Gnome and
downstream distributions etc.
_______________________________________________




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]