[Greasemonkey] Re: Output possibilities?

[Philip Friedman - Auto Europe]

Thanks for the ideas.

Data uri's would be straightforward, but aren't there length limits? I'm at
about 3k in size now and need this to scale.

I get saving the data and retrieving it on a linked "blank" page for
display. But...

1) Are there length limits to GM_setValue/GM_getValue values? I would need
to segment the data. Easy enough to do.

2) Another problem with greasemonkeying the data onto a "blank" page is that
it's also greasemonkeyed just like the original data, so doesn't show when
you print or save the page.

Another Idea: is there a way to push things onto the clipboard? The
troublesome part is actually just selecting all the data. Is there a
programmatic way to select DOM elements? The user could then Ctrl-C. 

Or save Specific DOM elements to a file? I could provide buttons to do
either of these.

--
Regards, Phil Friedman - Auto Europe 

|-----Original Message-----
|From: greasemonkey-bounces at mozdev.org 
|[mailto:greasemonkey-bounces at mozdev.org] On Behalf Of Andre
|Sent: Friday, May 12, 2006 6:33 AM
|To: greasemonkey at mozdev.org
|Subject: [Greasemonkey] Re: Output possibilities?
|
|
|
|Dave Land wrote:
|> 
|> I really had to think about what Jeremy meant here...
|> 
|
|thanks for writing up your thoughts. it helped me get 
|something similar started.
|
|> Maybe it's something like this:
|> ...
| > ...
|> Of course, you could have two separate scripts, one for the target 
|> page that /writes/ the data, and one for the fake about: page that 
|> /reads/ and /renders/ the data, but maybe one is better. I 
|don't know 
|> and it's past midnight.
|
|I guess the usual restriction applies that one script cannot 
|read the SetValues of another ...
|
|Cheers, Andre
|
|_______________________________________________
|Greasemonkey mailing list
|Greasemonkey at mozdev.org
|http://mozdev.org/mailman/listinfo/greasemonkey
|