Ticket #8748 (new defect)
Sugar cannot upload images from the Journal to TRAC
|Reported by:||gnu||Owned by:||tomeu|
|Component:||sugar||Version:||Development build as of this date|
|Deployments affected:||Blocked By:|
I was reporting #8747 from a real computer, and decided to try to upload the faulty screen image from my XO.
On the XO, from the copy of Browse that was showing the faulty screen image, I selected the entire URL and pressed Ctrl-C to copy it. An icon appeared in the lower left corner of the screen. I then navigated to dev.laptop.org/ticket/8747, logged in, pressed "Attach File", and got to the "Add Attachment to Ticket #8747" page, which has a place to enter "File (size limit 19 MB)", a button to Browse (the local filesystem), and a description field.
I could click in the File text input box, and type, but I could not Paste into it. I tried Ctrl-V. I tried Shift-Ctrl-V. Nothing happened. I tried bringing up the Frame and dragging the icon into the text box. That replaced the whole page (with an error page saying it couldn't access that file). I tried clicking the Browse (local filesystem) button. Of course you can't Browse in a laptop that doesn't have a file browser or a file open dialogue. Of course it didn't bring up the Journal. It didn't do anything.
The file name involved was a long, long, long name saying something about /isolation and a long random name ending in .jpg I was not about to try copying it out on paper and then switching web pages and then try typing it in from paper. For all I know, Browse is not *permitted* to access this file in the Journal, because it was created by a different "Activity" running under a different UID.
It is long overdue for OLPC to throw out the whole Journal/Datastore paradigm -- and the crappy nonfunctional Sugarized software -- and replace it with the workhorse software that runs on every other Linux system. The software every XO developer uses to get their work done, every day.
But hey, as long as the majority of XO users have no real filesystem or browser, and have no real computer accessible to them, they sure won't report very many bugs...which makes the Sugar developers' life much easier. And when nobody can develop on the machine, not because the machine or the kids are incapable, but because the UI doesn't allow it and the paradigm doesn't ever teach them about hierarchical filesystems, there isn't all the hassle of integrating patch contributions from hundreds of thousands of kids.