[prssr-devel-ml] Re: one longstanding problem I have with pRSSreader
- From: David Andrs <pda@xxxxxxxxxxxxx>
- To: prssr-devel-ml@xxxxxxxxxxxxx
- Date: Sun, 29 Oct 2006 14:41:27 +0100
On Sun, 2006-10-29 at 09:04 -0400, Hal Rottenberg wrote:
> On 10/28/06, David Andrs <pda@xxxxxxxxxxxxx> wrote:
> > I have read the article. I agree that restoring the session is necessary
> > and useful. Well, for me it is not - my device have 128MB of RAM (but
> > this one is extreme). But, I understand that devices of other users are
> > not equipped with the same amount of memory as mine is and therefore low
> > memory conditions can occur very ofen.
>
> I'm never buying a 64MB PDA again...
>
> > So, I'm thinking about the restoring feature for 1.3.3 - it should not
> > be much complicated to do it. For the begining, I'm considering full
> > dialog restore. Example: If you are in URL rewriting dialog, pRSSreader
> > should restore 3 windows (main window, Site Properties Window and URL
> > rewritting window). For now, I can not say if I could go further in
> > restoring and my stand is that dialog restoring should be sufficient
> > enough for most of users.
>
> Well the case where I notice this is reading an article then I power
> the PDA off or it goes to sleep. Then a reminder wakes the device,
> and the act of that closes pRSSr. So I'm only in the main window I
> guess. Not sure if that answers your question.
A bit. I understand that you need the restoring of message reading
dialog (which is quite easy).
> > Does anyone know if the competitiors do any session restoring? Which and
> > how?
>
> Don't know.
>
> > Any further comments on session restoring? Any wishes before I start to
> > implement it?
>
> We're talking about a feature that basically should be transparent.
> It should "just work" and the user should not have to think about it.
>
In the case of "static" dialog such as message reading dialog, it is no
problem. But if you have opened dialog such as Options property sheet
and you make a lot of changes, then you switch to another application.
Then after a while low memory conditions occur and pRSSreader is killed,
all your changes are lost. Consider we are making only dialog restore,
on the next start of pRSSreader you will end in Options property sheet
but without changes you have made. Storing all changes to the
"persistent session file" might be quite hard and the code can increase
significantly. The question is: Is such kind of restoring neccesary? And
do you know about any application that does such kind of restoring?
Today, I have finished preliminary version of dialog restoring and the
code increment isn't too big. And there is no visible slowdown too. I
think that the most important thing is to restore the message reading
dialog. Other dialogs are not so important. But if I have the restoring
feature done for one dialog, making the rest of dialogs to restore is a
piece of cake. And there will be quite good restoring in the pRSSreader
for nothing.
--
David
--
pRSSreader development mailing list
prssr-devel-ml@xxxxxxxxxxxxx
//www.freelists.org/archives/prssr-devel-ml
Other related posts:
