From bender at footard.com  Fri May  4 02:56:28 2007
From: bender at footard.com (MandyB)
Date: Fri, 4 May 2007 02:56:28 -0700 (PDT)
Subject: [Sage] memory usage
In-Reply-To: <15028.67721.qm@web31013.mail.mud.yahoo.com>
References: <15028.67721.qm@web31013.mail.mud.yahoo.com>
Message-ID: <10319943.post@talk.nabble.com>


I think the developers have abandoned Sage. They don't seem to care anymore
:(

James, I moved from Sage to Wizz RSS News Reader about 6 months ago. Wizz is
also a Firefox add-on and is similar to Sage, but it is far richer in
features. I tested the Atom feed you posted with Wizz and it works
perfectly. No memory problems that I noticed and Wizz processed the feed
very quickly.
-- 
View this message in context: http://www.nabble.com/memory-usage-tf3502385.html#a10319943
Sent from the MozDev - sage mailing list archive at Nabble.com.


From bender at footard.com  Fri May  4 08:37:41 2007
From: bender at footard.com (MandyB)
Date: Fri, 4 May 2007 08:37:41 -0700 (PDT)
Subject: [Sage] Three or More Columns in Sage
In-Reply-To: <5284356.1173469778879.JavaMail.root@elwamui-little.atl.sa.earthlink.net>
References: <9418726.1173422431210.JavaMail.root@elwamui-chisos.atl.sa.earthlink.net>
	<5284356.1173469778879.JavaMail.root@elwamui-little.atl.sa.earthlink.net>
Message-ID: <10323650.post@talk.nabble.com>


Andres,

You should address the "widely promoted" issue with the guys who run
addons.mozilla.org. They are the ones who are responsible for promoting Sage
on https://addons.mozilla.org/en-US/firefox/recommended

There are better feed reading add-ons, yet they continue to promote Sage?


I am just a high power RSS reader and I don't code. I figured since Sage is
so widely promoted that feature should be there and not necessitate a user
to code for a feature like that. There was a Sage CSS style sheet created
called I believe "widescreenstyle" that somehow has been pulled and no
longer available. If a product is to have wider use, it should be there.
Yahoo is already making steps to have a 4 column Ajaxed version of their MY
Yahoo pages soon complete with RSS, and the trend is to go wider.
-- 
View this message in context: http://www.nabble.com/Three-or-More-Columns-in-Sage-tf3374105.html#a10323650
Sent from the MozDev - sage mailing list archive at Nabble.com.


From bender at footard.com  Fri May  4 02:56:28 2007
From: bender at footard.com (MandyB)
Date: Fri, 4 May 2007 02:56:28 -0700 (PDT)
Subject: [Sage] memory usage
In-Reply-To: <15028.67721.qm@web31013.mail.mud.yahoo.com>
References: <15028.67721.qm@web31013.mail.mud.yahoo.com>
Message-ID: <10319943.post@talk.nabble.com>


I think the developers have abandoned Sage. They don't seem to care anymore
:(

James, I moved from Sage to Wizz RSS News Reader about 6 months ago. Wizz is
also a Firefox add-on and is similar to Sage, but it is far richer in
features. I tested the Atom feed you posted with Wizz and it works
perfectly. No memory problems that I noticed and Wizz processed the feed
very quickly.
-- 
View this message in context: http://www.nabble.com/memory-usage-tf3502385.html#a10319943
Sent from the MozDev - sage mailing list archive at Nabble.com.


From k-marken at online.no  Sat May  5 07:55:20 2007
From: k-marken at online.no (kenneth marken)
Date: Sat, 05 May 2007 16:55:20 +0200
Subject: [Sage] [Fwd: Re:  memory usage]
Message-ID: <463C9AD8.3050500@online.no>



-------- Original Message --------
From: - Sat May 05 16:54:20 2007
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00800000
Message-ID: <463C9A94.309 at online.no>
Date: Sat, 05 May 2007 16:54:12 +0200
From: kenneth marken <k-marken at online.no>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: MandyB <bender at footard.com>
Subject: Re: [Sage] memory usage
References: <15028.67721.qm at web31013.mail.mud.yahoo.com> 
<10319943.post at talk.nabble.com>
In-Reply-To: <10319943.post at talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

MandyB wrote:
> I think the developers have abandoned Sage. They don't seem to care anymore
> :(
> 
> James, I moved from Sage to Wizz RSS News Reader about 6 months ago. Wizz is
> also a Firefox add-on and is similar to Sage, but it is far richer in
> features. I tested the Atom feed you posted with Wizz and it works
> perfectly. No memory problems that I noticed and Wizz processed the feed
> very quickly.

hmm, wizz. tested it. found it to bothersome. i kinda liked how sage
could display new entries of a RSS feed in the main area. i cant see
that wizz is able to do that.

only problem i have with sage is that it walks all over the currently
active tab. there was one version on bugzilla that fixed this, mostly.
but it never made it over into the main source.


From ksfiles at gmail.com  Wed May  9 09:24:01 2007
From: ksfiles at gmail.com (Kirby Files)
Date: Wed, 09 May 2007 12:24:01 -0400
Subject: [Sage] Bug parsing <link>?
Message-ID: <4641F5A1.1060503@gmail.com>

Folks,
   A number of feeds use relative URIs in the href for a <link> (see, 
e.g., http://www.intertwingly.net/blog/index.atom, where an example 
href is "2007/05/09/JavaFX-Script", which should be treated as 
relative to http://intertwingly.net/blog/).
   While these are valid URIs, Sage seems to interpret them as 
fully-qualified URIs; the resulting links are of the form: 
http://2007/05/09/JavaFX-Script.
   Could we please have this behavior changed, so that any relative 
URI  (or absolute path) is interpreted in relation to the base URI of 
the feed?

Thanks,
   --kirby

From one at phoenixchange.com  Thu May 17 00:26:03 2007
From: one at phoenixchange.com (Robin (UK))
Date: Thu, 17 May 2007 08:26:03 +0100
Subject: [Sage] Sage doesn't update "properly"
Message-ID: <003b01c79854$a3da8370$daba1b52@phoenix>

Hi

First thanks for Sage.  I really couldn't figure out how to get RSS working in Firefox before!

However, Sage still seems to have a key weakness compared to the IE7 functionality.  This is the failure of the feed reader to update feed titles automatically.

In Options>Settings the "Automatically update feed titles" option is checked.  However the list does not update automatically, ever, but needs to be manually updated.  This is made worse because even then there seems to be a delay.  IE7 updates almost immediately but Sage takes a while and I have to wait a few minutes after posting entries to my blog to see that the changes have been registered in the reader (I'm just checking through the functionality of my site.)

I don't understand why there is an option for Automatic updating if it doesn't work so I must have something wrong somewhere.

Secondly, even when marked as read, all the "feeds" (the changes made since the site or "feed" was last visited)  remain listed rather than just new ones.

Any help gratefully received.

Kind regards

~ Robin

p.s. Any help with nomenclature would be appreciated.  In order to be able to communicate less clumsily about all this I need to have different labels for: 
  1.. the code that generates the "feed"
  2.. the information contained in the "feed"
  3.. the display of the "feed" in the feed reader
  4.. the individual elements of the "feed", the separate items that are new or have been modified
I "know" that the feed is the information delivered by a site to a feed reader but that seems a clumsy definition as the four discrete parts of this information transmission process are listed above. For instance: consider the sentence: "I had to delete feed: from the feed so that the feed can now be read by the feed reader and the feed titles updated by the feed along with the individual feed titles. However the feed still doesn't update the feed reader so that feed titles and the titles of the feeds are shown as updated".  There must be a better way!!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mozdev.org/pipermail/sage/attachments/20070517/37bb3169/attachment.html 

From k-marken at online.no  Thu May 17 09:23:53 2007
From: k-marken at online.no (kenneth marken)
Date: Thu, 17 May 2007 18:23:53 +0200
Subject: [Sage] Sage doesn't update "properly"
In-Reply-To: <003b01c79854$a3da8370$daba1b52@phoenix>
References: <003b01c79854$a3da8370$daba1b52@phoenix>
Message-ID: <464C8199.8020702@online.no>

Robin (UK) wrote:
>  
> However, Sage still seems to have a key weakness compared to the IE7 
> functionality.  This is the failure of the feed reader to update feed 
> titles automatically.
>  
> In Options>Settings the "Automatically update feed titles" option is 
> checked.  However the list does not update automatically, ever, but 
> needs to be manually updated.  This is made worse because even then 
> there seems to be a delay.  IE7 updates almost immediately but Sage 
> takes a while and I have to wait a few minutes after posting entries to 
> my blog to see that the changes have been registered in the reader (I'm 
> just checking through the functionality of my site.)
>  

i think the option points towards changing the "name" of the feed in the 
list to match the title of the feed if its ever changed (basically a 
automatic version of right clicking on a feed in the list and selecting 
"get feed title"). not to be confused with a timed check for when feeds 
update.

hmm, that is unless i have miss understood your question.

From one at phoenixchange.com  Thu May 17 15:28:41 2007
From: one at phoenixchange.com (Robin (UK))
Date: Thu, 17 May 2007 23:28:41 +0100
Subject: [Sage] Sage doesn't update "properly"
References: <003b01c79854$a3da8370$daba1b52@phoenix>
	<464C8199.8020702@online.no>
Message-ID: <001301c798d2$ba6788d0$daba1b52@phoenix>

Thanks for replying Kenneth.  Surely that can't be?!  Are you saying that 
the Option provided ONLY relates to when the actual "title" of the feed is 
changed, from "BBC News" to "B.B.C. News", for example, and not to actually 
updating the feeds automatically and showing that new information is 
available by emboldening the feed title shown in the side panel . . . 
:((  If I'd have found that something like Scribefire was available for IE7 
I think I would be giving up on Firefox etc by now ;)  Surely a primary 
advantage of RSS is to be automatically updated with new information and not 
to have to keep checking by clicking manually all the time??

Oh well . . .  maybe Sage will think of adding the functionality ion their 
next issue . . . ??  Pretty please :))


----- Original Message ----- 
From: kenneth marken
To: Robin (UK)
Cc: sage at mozdev.org
Sent: Thursday, May 17, 2007 5:23 PM
Subject: Re: [Sage] Sage doesn't update "properly"


Robin (UK) wrote:
>  However, Sage still seems to have a key weakness compared to the IE7 
> functionality.  This is the failure of the feed reader to update feed 
> titles automatically.
>  In Options>Settings the "Automatically update feed titles" option is 
> checked.  However the list does not update automatically, ever, but needs 
> to be manually updated.  This is made worse because even then there seems 
> to be a delay.  IE7 updates almost immediately but Sage takes a while and 
> I have to wait a few minutes after posting entries to my blog to see that 
> the changes have been registered in the reader (I'm just checking through 
> the functionality of my site.)
>

i think the option points towards changing the "name" of the feed in the
list to match the title of the feed if its ever changed (basically a
automatic version of right clicking on a feed in the list and selecting
"get feed title"). not to be confused with a timed check for when feeds
update.

hmm, that is unless i have miss understood your question.


-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.467 / Virus Database: 269.7.1/807 - Release Date: 16/05/2007 
18:05 


From k-marken at online.no  Thu May 17 15:45:51 2007
From: k-marken at online.no (kenneth marken)
Date: Fri, 18 May 2007 00:45:51 +0200
Subject: [Sage] Sage doesn't update "properly"
In-Reply-To: <001301c798d2$ba6788d0$daba1b52@phoenix>
References: <003b01c79854$a3da8370$daba1b52@phoenix>
	<464C8199.8020702@online.no> <001301c798d2$ba6788d0$daba1b52@phoenix>
Message-ID: <464CDB1F.90805@online.no>

Robin (UK) wrote:
> Thanks for replying Kenneth.  Surely that can't be?!  Are you saying 
> that the Option provided ONLY relates to when the actual "title" of the 
> feed is changed, from "BBC News" to "B.B.C. News", for example, and not 
> to actually updating the feeds automatically and showing that new 
> information is available by emboldening the feed title shown in the side 
> panel . . . :((  If I'd have found that something like Scribefire was 
> available for IE7 I think I would be giving up on Firefox etc by now ;)  
> Surely a primary advantage of RSS is to be automatically updated with 
> new information and not to have to keep checking by clicking manually 
> all the time??
> 

not that i have understood at least. to check if a feed have new entries 
you have to hit the top left button. and then it will check every feed 
in turn. if you only want to see if one of them have new stuff, click it.

thats my experience.

this makes sage a usable (imo) but very bare bones feed reader.

From green408 at gmail.com  Thu May 17 21:40:05 2007
From: green408 at gmail.com (ox ox)
Date: Fri, 18 May 2007 12:40:05 +0800
Subject: [Sage] [help] high cpu usage when opening a big rss feed
Message-ID: <b0eb0a0a0705172140i30953883j979a81c64bc0e36c@mail.gmail.com>

Hi

I suffering a performance trouble when opening a RSS feed
http://blogs.msdn.com/fyuan/rss.xml ( a big-size rss feed). It will
continually stick with high CPU utilization.  I ensure it is the Javascript
performance issues when I have use VTune to get following result:

Address   Size  Function   Class        Full Name        Module     Source
File       Timer Samples  Resolved Module Path        Timer events     Timer
%

302700    8175        js_SearchScope               js_SearchScope
js3250.dll          516  C:\firefox\Mozilla Firefox\js3250.dll     516000
12.98113208

34113      3777        js_AtomToPrintableString
js_AtomToPrintableString js3250.dll          636  C:\firefox\Mozilla
Firefox\js3250.dll     636000    16

107718    25393      js_GetSrcNoteOffset
js_GetSrcNoteOffset
js3250.dll          1179        C:\firefox\Mozilla Firefox\js3250.dll
1179000  29.66037736



After that, I try to profile with Venkman but get following understandable
results of the time consumed

:



enkman Profile Report Created .......... Fri May 18 2007 01:01:03 GMT+0800
User Agent ....... Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:
1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 Debugger Version . Venkman
0.9.87[Mozilla rv:
1.8.1.3/2] Sorted By ........ total
=================================================================================
0 XStringBundle: 5000 - 0 milliseconds Function Name: getString (Lines 14 -
22) Total Calls: 6 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time
(ex. calls): 0 (min/max/avg 0/0/0) Function Name: get_stringBundle (Lines 44
- 58) Total Calls: 6 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time
(ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
1 XStringBundle: 5000 - 0 milliseconds Function Name: getString (Lines 14 -
22) Total Calls: 31 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time
(ex. calls): 0 (min/max/avg 0/0/0) Function Name: get_stringBundle (Lines 44
- 58) Total Calls: 31 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time
(ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
2 browser.xml: 5000 - 0 milliseconds Function Name: onxblmousedown (Lines
897 - 916) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0)
Time (ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
3 browser.xml: 5000 - 0 milliseconds Function Name: onxblmouseup (Lines 889
- 895) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time
(ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
4 browser.xml: 5000 - 0 milliseconds Function Name: onxblmousedown (Lines
897 - 916) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0)
Time (ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
5 browser.xml: 5000 - 0 milliseconds Function Name: onxblmouseup (Lines 889
- 895) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time
(ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
6 button.xml: 5000 - 0 milliseconds Function Name: onxblcommand (Lines 127 -
134) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time
(ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
7 button.xml: 5000 - 0 milliseconds Function Name: onxblcommand (Lines 127 -
134) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time
(ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
8 dialog.xml: 7.5 - 25 milliseconds Function Name: __toplevel__ (Lines 130 -
142) Total Calls: 1 (max recurse 0) Total Time: 15.63 (min/max/avg
15.63/15.63/15.63)
Time (ex. calls): 15.63 (min/max/avg 15.63/15.63/15.63)
-------------------------------------------------------------------------------
=================================================================================
9 popup.xml: 5000 - 0 milliseconds Function Name: onxblpopupshowing (Lines
231 - 239) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0)
Time (ex. calls): 0 (min/max/avg 0/0/0) Function Name: onxblpopupshowing
(Lines 146 - 162) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg
0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
10 popup.xml: 5000 - 0 milliseconds Function Name: onxblpopupshowing (Lines
231 - 239) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0)
Time (ex. calls): 0 (min/max/avg 0/0/0) Function Name: onxblpopupshowing
(Lines 146 - 162) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg
0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
11 popup.xml: 5000 - 0 milliseconds Function Name: onxblpopupshowing (Lines
231 - 239) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0)
Time (ex. calls): 0 (min/max/avg 0/0/0) Function Name: onxblpopupshowing
(Lines 146 - 162) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg
0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
12 popup.xml: 5000 - 0 milliseconds Function Name: onxblpopupshowing (Lines
146 - 162) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0)
Time (ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
13 toolbar.xml: 5000 - 0 milliseconds Function Name: onxblDOMMenuItemActive
(Lines 317 - 318) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg
0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
14 toolbar.xml: 5000 - 0 milliseconds Function Name:
onxblDOMMenuItemInactive (Lines 318 - 319) Total Calls: 1 (max recurse 0)
Total Time: 0 (min/max/avg 0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
15 toolbar.xml: 5000 - 0 milliseconds Function Name: onxblDOMMenuBarActive
(Lines 299 - 307) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg
0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
16 toolbar.xml: 5000 - 0 milliseconds Function Name: onxblDOMMenuItemActive
(Lines 317 - 318) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg
0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0) Function Name:
onxblDOMMenuBarInactive (Lines 309 - 315) Total Calls: 1 (max recurse 0)
Total Time: 0 (min/max/avg 0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0)
Function Name: onxblDOMMenuItemInactive (Lines 318 - 319) Total Calls: 1
(max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time (ex. calls): 0
(min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
17 tree.xml: 5000 - 0 milliseconds Function Name: onxblmousedown (Lines 606
- 639) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time
(ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
18 tree.xml: 5000 - 0 milliseconds Function Name: onxblclick (Lines 647 -
700) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time
(ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
19 tree.xml: 5000 - 0 milliseconds Function Name: onxblfocus (Lines 292 -
297) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time
(ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
20 tree.xml: 5000 - 0 milliseconds Function Name: onxblblur (Lines 300 -
301) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time
(ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
21 tree.xml: 5000 - 0 milliseconds Function Name: onxblfocus (Lines 292 -
297) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time
(ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
22 commonDialog.js: 5000 - 0 milliseconds Function Name: __toplevel__ (Lines
1 - 331) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0)
Time (ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
23 commonDialog.xul: 5000 - 0 milliseconds Function Name: __toplevel__
(Lines 62 - 63) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg
0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
24 venkman.xul: 7.5 - 25 milliseconds Function Name: oncommand (Lines 1 - 2)
Total Calls: 1 (max recurse 0) Total Time: 15.63 (min/max/avg
15.63/15.63/15.63)
Time (ex. calls): 15.63 (min/max/avg 15.63/15.63/15.63)
-------------------------------------------------------------------------------
=================================================================================
25 venkman.xul: 1000 - 5000 milliseconds Function Name: oncommand (Lines 1 -
2) Total Calls: 1 (max recurse 0) Total Time: 4250 (min/max/avg
4250/4250/4250) Time (ex. calls): 4250 (min/max/avg 4250/4250/4250)
-------------------------------------------------------------------------------
=================================================================================
26 venkman-service.js: 5000 - 0 milliseconds Function Name: jsdph_newuri
(Lines 284 - 289) Total Calls: 2 (max recurse 0) Total Time: 0 (min/max/avg
0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
27 firebug-service.js: 5000 - 0 milliseconds Function Name: anonymous (Lines
142 - 147) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0)
Time (ex. calls): 0 (min/max/avg 0/0/0) Function Name: anonymous (Lines 160
- 175) Total Calls: 2 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time
(ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
28 nsBookmarkTransactionManager.js: 5000 - 0 milliseconds Function Name:
bkTxnMgrQI (Lines 260 - 270) Total Calls: 29 (max recurse 0) Total Time: 0
(min/max/avg 0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0) Function Name:
bkmkTxnMgrCanUndo (Lines 321 - 323) Total Calls: 12 (max recurse 0) Total
Time: 0 (min/max/avg 0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0) Function
Name: bkmkTxnMgrCanRedo (Lines 325 - 327) Total Calls: 12 (max recurse 0)
Total Time: 0 (min/max/avg 0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
29 nsMicrosummaryService.js: 5000 - 0 milliseconds Function Name:
MSS__resource (Lines 134 - 136) Total Calls: 6 (max recurse 0) Total Time: 0
(min/max/avg 0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0) Function Name:
anonymous (Lines 84 - 88) Total Calls: 3 (max recurse 0) Total Time: 0
(min/max/avg 0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0) Function Name:
anonymous (Lines 159 - 164) Total Calls: 3 (max recurse 0) Total Time: 0
(min/max/avg 0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0) Function Name:
anonymous (Lines 205 - 206) Total Calls: 3 (max recurse 0) Total Time: 0
(min/max/avg 0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0) Function Name:
MSS__updateMicrosummaries (Lines 219 - 244) Total Calls: 3 (max recurse 0)
Total Time: 0 (min/max/avg 0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0)
Function Name: MSS__getBookmarks (Lines 606 - 626) Total Calls: 3 (max
recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time (ex. calls): 0
(min/max/avg 0/0/0) Function Name: anonymous (Lines 75 - 80) Total Calls: 6
(max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time (ex. calls): 0
(min/max/avg 0/0/0) Function Name: getPref (Lines 2233 - 2247) Total Calls:
3 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0) Time (ex. calls): 0
(min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
30 nsSafebrowsingApplication.js: 5000 - 0 milliseconds Function Name:
anonymous (Lines 1833 - 1835) Total Calls: 48 (max recurse 0) Total Time: 0
(min/max/avg 0/0/0) Time (ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
31 nsUpdateService.js: 5000 - 0 milliseconds Function Name: getPref (Lines
537 - 544) Total Calls: 4 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0)
Time (ex. calls): 0 (min/max/avg 0/0/0) Function Name: anonymous (Lines 2679
- 2699) Total Calls: 1 (max recurse 0) Total Time: 0 (min/max/avg 0/0/0)
Time (ex. calls): 0 (min/max/avg 0/0/0)
-------------------------------------------------------------------------------
=================================================================================
Thanks for using Venkman, the Mozilla JavaScript Debugger.



Can anyone help with this problem(high cpu utilization )?



Thanks in advance!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mozdev.org/pipermail/sage/attachments/20070518/7159e05a/attachment-0001.html 

From bender at footard.com  Fri May 18 22:51:34 2007
From: bender at footard.com (MandyB)
Date: Fri, 18 May 2007 22:51:34 -0700 (PDT)
Subject: [Sage] Sage doesn't update "properly"
In-Reply-To: <001301c798d2$ba6788d0$daba1b52@phoenix>
References: <003b01c79854$a3da8370$daba1b52@phoenix>
	<464C8199.8020702@online.no>
	<001301c798d2$ba6788d0$daba1b52@phoenix>
Message-ID: <10694052.post@talk.nabble.com>


May I suggest that, before giving up on Firefox, you try Wizz RSS News
Reader?

Wizz RSS News Reader already offers the functionality to periodically check
feeds for new content. It also has many features that Sage doesn't have,
which makes it a far more useful reader.

Mandy



googlerefugee wrote:
> 
> Thanks for replying Kenneth.  Surely that can't be?!  Are you saying that 
> the Option provided ONLY relates to when the actual "title" of the feed is 
> changed, from "BBC News" to "B.B.C. News", for example, and not to
> actually 
> updating the feeds automatically and showing that new information is 
> available by emboldening the feed title shown in the side panel . . . 
> :((  If I'd have found that something like Scribefire was available for
> IE7 
> I think I would be giving up on Firefox etc by now ;)  Surely a primary 
> advantage of RSS is to be automatically updated with new information and
> not 
> to have to keep checking by clicking manually all the time??
> 
> Oh well . . .  maybe Sage will think of adding the functionality ion their 
> next issue . . . ??  Pretty please :))
> 

-- 
View this message in context: http://www.nabble.com/Sage-doesn%27t-update-%22properly%22-tf3770361.html#a10694052
Sent from the MozDev - sage mailing list archive at Nabble.com.


From k-marken at online.no  Sat May 19 06:00:03 2007
From: k-marken at online.no (kenneth marken)
Date: Sat, 19 May 2007 15:00:03 +0200
Subject: [Sage] Sage doesn't update "properly"
In-Reply-To: <10694052.post@talk.nabble.com>
References: <003b01c79854$a3da8370$daba1b52@phoenix>
	<464C8199.8020702@online.no> <001301c798d2$ba6788d0$daba1b52@phoenix>
	<10694052.post@talk.nabble.com>
Message-ID: <464EF4D3.6060108@online.no>

MandyB wrote:
> May I suggest that, before giving up on Firefox, you try Wizz RSS News
> Reader?
> 
> Wizz RSS News Reader already offers the functionality to periodically check
> feeds for new content. It also has many features that Sage doesn't have,
> which makes it a far more useful reader.
> 

is there a option to have wizz list the content of a rss feed in the 
main area? so far i have only gotten it to show the pages...

From bender at footard.com  Sat May 19 23:04:57 2007
From: bender at footard.com (MandyB)
Date: Sat, 19 May 2007 23:04:57 -0700 (PDT)
Subject: [Sage] Sage doesn't update "properly"
In-Reply-To: <464EF4D3.6060108@online.no>
References: <003b01c79854$a3da8370$daba1b52@phoenix>
	<464C8199.8020702@online.no>
	<001301c798d2$ba6788d0$daba1b52@phoenix>
	<10694052.post@talk.nabble.com> <464EF4D3.6060108@online.no>
Message-ID: <10703163.post@talk.nabble.com>


As far as I know, you can only get Wizz RSS to display the content of a feed
by using Preview All (Right click on the listed items and click on Preview
All). It doesn't show the feed content in the main browser window, but
rather in a separate window.

Mandy



kenneth marken wrote:
> 
> is there a option to have wizz list the content of a rss feed in the 
> main area? so far i have only gotten it to show the pages...
> 

-- 
View this message in context: http://www.nabble.com/Sage-doesn%27t-update-%22properly%22-tf3770361.html#a10703163
Sent from the MozDev - sage mailing list archive at Nabble.com.


From bender at footard.com  Mon May 21 05:40:49 2007
From: bender at footard.com (MandyB)
Date: Mon, 21 May 2007 05:40:49 -0700 (PDT)
Subject: [Sage] Bug parsing <link>?
In-Reply-To: <4641F5A1.1060503@gmail.com>
References: <4641F5A1.1060503@gmail.com>
Message-ID: <10717958.post@talk.nabble.com>


Forgive me for constantly plugging the "opposition" :)

I tested Sam Ruby's feed ( http://www.intertwingly.net/blog/index.atom )
with Wizz and it works perfectly.

Mandy


Kirby Files-2 wrote:
> 
> Folks,
>    A number of feeds use relative URIs in the href for a <link> (see, 
> e.g., http://www.intertwingly.net/blog/index.atom, where an example 
> href is "2007/05/09/JavaFX-Script", which should be treated as 
> relative to http://intertwingly.net/blog/).
>    While these are valid URIs, Sage seems to interpret them as 
> fully-qualified URIs; the resulting links are of the form: 
> http://2007/05/09/JavaFX-Script.
>    Could we please have this behavior changed, so that any relative 
> URI  (or absolute path) is interpreted in relation to the base URI of 
> the feed?
> 
> Thanks,
>    --kirby
> _______________________________________________
> Sage mailing list
> Sage at mozdev.org
> http://mozdev.org/mailman/listinfo/sage
> 
> 

-- 
View this message in context: http://www.nabble.com/Bug-parsing-%3Clink%3E--tf3717658.html#a10717958
Sent from the MozDev - sage mailing list archive at Nabble.com.


From green408 at gmail.com  Fri May 25 09:56:35 2007
From: green408 at gmail.com (ox ox)
Date: Sat, 26 May 2007 00:56:35 +0800
Subject: [Sage] [help] high cpu usage when opening a big rss feed
In-Reply-To: <b0eb0a0a0705172140i30953883j979a81c64bc0e36c@mail.gmail.com>
References: <b0eb0a0a0705172140i30953883j979a81c64bc0e36c@mail.gmail.com>
Message-ID: <b0eb0a0a0705250956h4f4208cdke5eb35434a2938bd@mail.gmail.com>

I eat my funny question. It caused by convert from html  character entities
to unicode strings (It sounds like the problem fall into mozilla). It can be
fix temporarily by turning off html rendering options.

2007/5/18, ox ox <green408 at gmail.com>:
>
> Hi
>
> I suffering a performance trouble when opening a RSS feed
> http://blogs.msdn.com/fyuan/rss.xml ( a big-size rss feed). It will
> continually stick with high CPU utilization.  I ensure it is the Javascript
> performance issues when I have use VTune to get following result:
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mozdev.org/pipermail/sage/attachments/20070526/968f510f/attachment.html 

From phorst at speakeasy.net  Tue May 29 22:33:11 2007
From: phorst at speakeasy.net (Peter Horst)
Date: Wed, 30 May 2007 00:33:11 -0500
Subject: [Sage] how to move to next item in sidebar?
Message-ID: <465D0C97.1030306@speakeasy.net>

I must be missing something - what's the keybinding to move to the next 
(unread) feed in the Sage sidebar?  Can't find it anywhere.  
Clicky-clicky gets awfully tiresome when you check as many feeds as I do...

Thanks!