#630 closed defect (invalid)
Journal full message has issues
Reported by: | wadeb | Owned by: | wadeb |
---|---|---|---|
Priority: | Unspecified by Maintainer | Milestone: | |
Component: | Sugar | Version: | Git as of bugdate |
Severity: | Critical | Keywords: | sugar-love |
Cc: | eben, sascha_silbe, km0r3, tch, smparrish, humitos | Distribution/OS: | Unspecified |
Bug Status: | New |
Description
Currently there is no way to dismiss the modal "Journal full" dialog that appears when the Journal is out of space. The user is forced to go to the Journal.
Then, when reaching the Journal, the dialog appears redundantly on top of the Journal itself.
If the user is unable to fix the problem using the Journal (say the file system filled up some other way), it becomes impossible to open a Terminal activity to fix the problem, without being forced back into the Journal.
1) There should be a way to close the dialog without going to the Journal.
2) When the Journal is active, the dialog should be suppressed, and instead an Alert should indicate that the Journal is almost full, with extra details like percentage remaining.
3) In my opinion, Journal Full should not be a modal dialog at all, but a notification similar to the way Chat and IRC notify you when you have a new message. As you can continue to use Sugar, this feels like an abuse of a modal dialog.
Attachments (1)
Change History (22)
comment:1 Changed 14 years ago by sascha_silbe
- Cc sascha_silbe added
comment:2 Changed 14 years ago by FGrose
- Bug Status changed from Unconfirmed to New
comment:3 Changed 14 years ago by tomeu
- Severity changed from Major to Blocker
comment:4 Changed 14 years ago by erikos
- Milestone changed from Unspecified by Release Team to 0.84
comment:5 Changed 14 years ago by tomeu
- Milestone changed from 0.84 to 0.86
comment:6 Changed 14 years ago by eben
I think this is another instance of an incomplete feature, in some ways. The modal alert you mention is supposed to be modal, because it's supposed to appear only when the space left is so critically low that it's unsafe to do something other than delete things. This modal alert should only appear after one or more non-modal notifications. This requires some effort to be put into the notification system, which isn't fully developed yet.
I definitely agree that the dialog should be suppressed when the Journal is brought to the foreground. The whole idea behind the dialog is to push you there. I think that, given these other preliminary notifications, and the automatic suppression of the dialog when reaching the Journal, that it's OK that there is no other way to dismiss the dialog.
comment:7 Changed 14 years ago by tomeu
- Milestone changed from 0.86 to 0.88
- Severity changed from Blocker to Critical
Too late in the cycle to block this release.
comment:8 Changed 14 years ago by wadeb
- Owner changed from tomeu to wadeb
- Status changed from new to accepted
comment:9 Changed 13 years ago by walter
- Milestone changed from 0.88 to 0.90
revisit for 0.90? Seems important.
comment:10 Changed 13 years ago by sascha_silbe
- Component changed from sugar to SoaS
- Distribution/OS changed from SoaS to Unspecified
Bulk change distribution=SoaS -> component=SoaS
comment:11 Changed 13 years ago by sdz
- Component changed from SoaS to sugar
This is a sugar issue that got accidentally assigned to SoaS during an auto-tag. Reassigning - sorry for the confusion.
comment:12 Changed 13 years ago by bernie
- Cc km0r3 added
comment:13 Changed 13 years ago by bernie
- Cc tch added
- Keywords sugar-love added
Martin, perhaps you'd like to give it a shot?
comment:14 Changed 13 years ago by smparrish
- Cc smparrish added
Martin, do you want to take a stab at this or would you prefer me to find someone else for it.
comment:15 Changed 13 years ago by smparrish
- seeta_dev set to Mukul
comment:16 Changed 13 years ago by tch
From what I can see in the previous conversations, a messages notification extension is required as a preemptive method to be used _before_ the modal window appears, considering this modal window the last resource.
Sadly, not everyone agree on the necessity of a messages notification extension even though here we have another concrete example of a valid use case.
Since I have implemented a messages notification extension for dextrose, I will also fix this problem for dextrose in order to test and eventually probe its value as a GUI element.
Hopefully after this, we can consider such extensions for mainstream too. I will continue this topic on dextrose mailing list for the ones interested.
Changed 11 years ago by FGrose
comment:17 Changed 11 years ago by FGrose
On Sugar 0.94.1 in a window on Fedora 16 Live USB, I'm getting the Journal full dialog after installing too many Activities. The Show Journal button takes me to the Journal, and if the dialog appears again, clicking the button dismisses it, allowing me to sort the Journal entries, etc.
comment:18 Changed 11 years ago by greenfeld
In Sugar 0.97x the Journal full message still appears when doing even minor actions in the Journal (with less than 50 MB free). It also appears when Sugar is first started and whenever an activity starts.
However the "Show Journal" button does not take us to the Journal except when the Journal already is showing, which given the frequency that this happens almost is a good thing.
comment:19 Changed 11 years ago by garycmartin
- Cc humitos added
Hi Humitios, I know you were working (with or near) the Journal full case (Browse at least). Just thought you might want to be cced on this related ticket.
comment:20 Changed 10 years ago by dnarvaez
- Resolution set to invalid
- Status changed from accepted to closed
I don't see an agreement here. If someone care about this please bring up the issue with design and open tickets with concrete suggestions of what changes should be made.
Eben, could you comment?