Opera

MEB you have some True POINT here!
no need to Reply!

"MEB" wrote in message
...
On 04/30/2010 09:17 AM, glee wrote:
"MEB" wrote in message
...
On 04/29/2010 11:44 PM, glee wrote:
Geez....you've missed the entire point. There was, for many builds and
versions of Opera, a simple checkbox to enable or disable Java on a
global or per site basis, readily available through the Preferences
menu
for all users, without having to resort to buried modifications. The
option was removed, making it much more difficult, if not impossible,
for said users to adjust the setting. The links you keep referring to
apply to earlier versions of Opera, when there was still an option to
enable or disable Java on a per site basis. They do not work with the
current version. Again, since you are insisting this can be done on
Opera 10.5x, show me how. The links you have supplied either discuss
disabling JavaScript but not Java, or describe how to do it on earlier
versions of Opera.

NO, I USED Opera, so I'm not ignoring the checkbox missing issue... and
LOOK on the Opera forums and for the other informational
sites/blogs/etc.

BTW No, 10.5* was being discussed in THAT prior linked discussion AND
you will find the other v10 being discussed in other linked or
referenced materials... ON OPERA..


The reason they do not work, and the checkbox was removed, is that the
devs have changed the way Opera handles Java....it is now handled via a
plug-in. The only user-friendly way to disable Java is to disable ALL
plug-ins. Disabling Java without disabling other plug-ins can only be
done GLOBALLY now, through the plugin-ignore.ini. It turns out that
even the option to disable Java globally via opera:config is ignored in
version 10.5x. There is no way to disable only Java on a PER SITE
basis, in Opera 10.5x. THAT is the point being made. Apparently you
are not using Opera 10.5x and are not aware of the changes that have
been made.

Jackson stated the inability to control Java on a per site basis was a
show stopper for him. I reiterated his position. You have gone on and
on about how it can be done...prove it.


Man,, you have become awful whiny Windows user... WHERE are your links
to the discussions/information you are stating/referencing??? You do
know I have TRIED to put some actual info into this discussion..
Yeah I noted the plug in issue researching YOUR issues, so WHERE would
the modification be made... think it might be the controlling plug in...
or another plug in or user script.. or STILL available via other
methods...

Come on man, just HOW do you think your browser receives its java
orders, oh wait I DID direct you to SUN "Beginners" pages so you could
look at the elements, page inclusions and other that would be the
identifiers/page elements to BLOCK... AND even provided a couple...
and DID note the user.css - that's CSS3 BTW, might want to look at what
can be done with that...

ALSO please post *YOUR* personal contacts with the *developers* of
Opera pursuant this issue. I see ZERO links in your posts...
Have ALL of you forgotten the PRIOR issues such as disablement of other
"features" for a couple *SUB* versions that were later corrected...and
generally due to input on *OPERA'S forums*...

And BTW I SPECIFICALLY stated I wasn't using Opera at the moment, and
my installation ISN'T going to help a Windows user, nor would any code
modifications FOR LINUX unless via a plug in or something like Blockit
[a plug in using Opera's built-in support]... did you even bother to
contact that creator/coder or any of the others on Opera's forums, or
others offering coding/plug-ins for work-arounds?
Yes?, links and/or personal contact indications please.
No?, then...

You could actually read the complete thread in one of the links that YOU
supplied earlier:
http://groups.google.com/group/opera...561d324362c6b8


If you read the entire thread, including the info supplied by Rijk van
Geijtenbeek from Opera Software ASA, you will see there is no longer any
option to disable one plug-in alone on a PER SITE basis, and that Java
is now handled as a plug-in, which was not the case in earlier
versions....but then you should already know that since you profess to
be so versed in the workings of Opera.

Yeah, AS SUPPLIED BY OPERA presently; I read that discussion and
several dozen others ON Opera and elsewhere; searched several dozen
sites for HAS been done to modify Opera and JAVA; refreshed my knowledge
on "java script" and JAVA; re-looked at the actual FF plug-in coding,
and I can see the areas which could potentially be used when compared
against Opera and its coding.
You want to whine, instead, why don't YOU write the new plug-in that
DOES allow JAVA disablement or work with the coders that are addressing
these and other issues, that seems far more productive.
I'm not professing anything like what you are attempting to infer
and/or stating; I AM indicating that if you rely upon many programmers
you will NEVER get what you want or what was/is needed to correct or
modify THEIR programs, nor information on HOW to control their
programs/applications - like Windows, or FireFox, or now Opera. If
enough Opera users complain or work on/with the Opera developers I would
bet you can get that checkbox "per site" function back.

BTW: the "disable one plug-in alone on per site basis" ISN'T what we
are supposedly addressing in this discussion beyond noting it was
removed, we are supposedly looking for ways to deal with these supposed
issues and applicable methods regarding JAVA and its usage and blockage.


Yet still you go on, with no specifics whatsoever, about CSS tweaking
and other "methods" to do this, even after I've repeatedly explained the
point we are making here.....that the majority of users do not do that
type of tweaking, and the previously available GUI options are no longer
available.

Oh wow, there's another duuuuhhhh moment... that WAS what we were
discussing wasn't it... glad you reminded me...

I have directed to the parties actually working on modifications and
plug-ins; files that potentially can/could be used; methodologies and
actual coding examples;, and several other necessary parts for both an
understanding of WHAT needs addressed and WHERE the potentials lay; now
point to ANYTHING you have posted which shows anything of value for
actually dealing with/addressing the purported issue.

AND MY POINT: you can sit there and whine and complain or you can make
an effort to do something about it or change it, or modify it; just like
everything else on this planet or in your life.

It was great that this was brought here for discussion to point out
this issue, its quite another when all YOU do is whine... and make
comments to me like *I'M* responsible for creating something YOU want
for YOUR OS, and in the childish "prove it" nonsense. I now use an OS in
which *I* have the ability to define/control just about any activity and
to what extent *I* allow it via the myriad of config and other settings
or direct code modifications available. If I choose, I can/could limit
just about anything or its access and/or abilities.

How about YOU PROVE beyond any modification or script, that it is
impossible to disable JAVA, I dare you [see how that's pretty childish
and stupid as there are ways to do so].

--
MEB
http://peoplescounsel.org/ref/windows-main.htm
Windows Info, Diagnostics, Security, Networking
http://peoplescounsel.org
The "real world" of Law, Justice, and Government
___---

MEB you have some True POINT here!
no need to Reply!

"MEB" wrote in message
...
On 04/30/2010 09:17 AM, glee wrote:
"MEB" wrote in message
...
On 04/29/2010 11:44 PM, glee wrote:
Geez....you've missed the entire point. There was, for many builds and
versions of Opera, a simple checkbox to enable or disable Java on a
global or per site basis, readily available through the Preferences
menu
for all users, without having to resort to buried modifications. The
option was removed, making it much more difficult, if not impossible,
for said users to adjust the setting. The links you keep referring to
apply to earlier versions of Opera, when there was still an option to
enable or disable Java on a per site basis. They do not work with the
current version. Again, since you are insisting this can be done on
Opera 10.5x, show me how. The links you have supplied either discuss
disabling JavaScript but not Java, or describe how to do it on earlier
versions of Opera.

NO, I USED Opera, so I'm not ignoring the checkbox missing issue... and
LOOK on the Opera forums and for the other informational
sites/blogs/etc.

BTW No, 10.5* was being discussed in THAT prior linked discussion AND
you will find the other v10 being discussed in other linked or
referenced materials... ON OPERA..


The reason they do not work, and the checkbox was removed, is that the
devs have changed the way Opera handles Java....it is now handled via a
plug-in. The only user-friendly way to disable Java is to disable ALL
plug-ins. Disabling Java without disabling other plug-ins can only be
done GLOBALLY now, through the plugin-ignore.ini. It turns out that
even the option to disable Java globally via opera:config is ignored in
version 10.5x. There is no way to disable only Java on a PER SITE
basis, in Opera 10.5x. THAT is the point being made. Apparently you
are not using Opera 10.5x and are not aware of the changes that have
been made.

Jackson stated the inability to control Java on a per site basis was a
show stopper for him. I reiterated his position. You have gone on and
on about how it can be done...prove it.


Man,, you have become awful whiny Windows user... WHERE are your links
to the discussions/information you are stating/referencing??? You do
know I have TRIED to put some actual info into this discussion..
Yeah I noted the plug in issue researching YOUR issues, so WHERE would
the modification be made... think it might be the controlling plug in...
or another plug in or user script.. or STILL available via other
methods...

Come on man, just HOW do you think your browser receives its java
orders, oh wait I DID direct you to SUN "Beginners" pages so you could
look at the elements, page inclusions and other that would be the
identifiers/page elements to BLOCK... AND even provided a couple...
and DID note the user.css - that's CSS3 BTW, might want to look at what
can be done with that...

ALSO please post *YOUR* personal contacts with the *developers* of
Opera pursuant this issue. I see ZERO links in your posts...
Have ALL of you forgotten the PRIOR issues such as disablement of other
"features" for a couple *SUB* versions that were later corrected...and
generally due to input on *OPERA'S forums*...

And BTW I SPECIFICALLY stated I wasn't using Opera at the moment, and
my installation ISN'T going to help a Windows user, nor would any code
modifications FOR LINUX unless via a plug in or something like Blockit
[a plug in using Opera's built-in support]... did you even bother to
contact that creator/coder or any of the others on Opera's forums, or
others offering coding/plug-ins for work-arounds?
Yes?, links and/or personal contact indications please.
No?, then...

You could actually read the complete thread in one of the links that YOU
supplied earlier:
http://groups.google.com/group/opera...561d324362c6b8


If you read the entire thread, including the info supplied by Rijk van
Geijtenbeek from Opera Software ASA, you will see there is no longer any
option to disable one plug-in alone on a PER SITE basis, and that Java
is now handled as a plug-in, which was not the case in earlier
versions....but then you should already know that since you profess to
be so versed in the workings of Opera.

Yeah, AS SUPPLIED BY OPERA presently; I read that discussion and
several dozen others ON Opera and elsewhere; searched several dozen
sites for HAS been done to modify Opera and JAVA; refreshed my knowledge
on "java script" and JAVA; re-looked at the actual FF plug-in coding,
and I can see the areas which could potentially be used when compared
against Opera and its coding.
You want to whine, instead, why don't YOU write the new plug-in that
DOES allow JAVA disablement or work with the coders that are addressing
these and other issues, that seems far more productive.
I'm not professing anything like what you are attempting to infer
and/or stating; I AM indicating that if you rely upon many programmers
you will NEVER get what you want or what was/is needed to correct or
modify THEIR programs, nor information on HOW to control their
programs/applications - like Windows, or FireFox, or now Opera. If
enough Opera users complain or work on/with the Opera developers I would
bet you can get that checkbox "per site" function back.

BTW: the "disable one plug-in alone on per site basis" ISN'T what we
are supposedly addressing in this discussion beyond noting it was
removed, we are supposedly looking for ways to deal with these supposed
issues and applicable methods regarding JAVA and its usage and blockage.


Yet still you go on, with no specifics whatsoever, about CSS tweaking
and other "methods" to do this, even after I've repeatedly explained the
point we are making here.....that the majority of users do not do that
type of tweaking, and the previously available GUI options are no longer
available.

Oh wow, there's another duuuuhhhh moment... that WAS what we were
discussing wasn't it... glad you reminded me...

I have directed to the parties actually working on modifications and
plug-ins; files that potentially can/could be used; methodologies and
actual coding examples;, and several other necessary parts for both an
understanding of WHAT needs addressed and WHERE the potentials lay; now
point to ANYTHING you have posted which shows anything of value for
actually dealing with/addressing the purported issue.

AND MY POINT: you can sit there and whine and complain or you can make
an effort to do something about it or change it, or modify it; just like
everything else on this planet or in your life.

It was great that this was brought here for discussion to point out
this issue, its quite another when all YOU do is whine... and make
comments to me like *I'M* responsible for creating something YOU want
for YOUR OS, and in the childish "prove it" nonsense. I now use an OS in
which *I* have the ability to define/control just about any activity and
to what extent *I* allow it via the myriad of config and other settings
or direct code modifications available. If I choose, I can/could limit
just about anything or its access and/or abilities.

How about YOU PROVE beyond any modification or script, that it is
impossible to disable JAVA, I dare you [see how that's pretty childish
and stupid as there are ways to do so].

--
MEB
http://peoplescounsel.org/ref/windows-main.htm
Windows Info, Diagnostics, Security, Networking
http://peoplescounsel.org
The "real world" of Law, Justice, and Government
___---

Have you read
Opera way to disable only Java. you give know reply to it, Why, Because
it Works.
if so you you keep play here!
You can not have your Cake and eat it too.
But you like to have it your way and it will not always work.



"glee" wrote in message
...
"MEB" wrote in message
...
On 04/30/2010 09:17 AM, glee wrote:
"MEB" wrote in message
...
On 04/29/2010 11:44 PM, glee wrote:
Geez....you've missed the entire point. There was, for many builds
and
versions of Opera, a simple checkbox to enable or disable Java on a
global or per site basis, readily available through the Preferences
menu
for all users, without having to resort to buried modifications. The
option was removed, making it much more difficult, if not impossible,
for said users to adjust the setting. The links you keep referring to
apply to earlier versions of Opera, when there was still an option to
enable or disable Java on a per site basis. They do not work with the
current version. Again, since you are insisting this can be done on
Opera 10.5x, show me how. The links you have supplied either discuss
disabling JavaScript but not Java, or describe how to do it on earlier
versions of Opera.

NO, I USED Opera, so I'm not ignoring the checkbox missing issue... and
LOOK on the Opera forums and for the other informational
sites/blogs/etc.

BTW No, 10.5* was being discussed in THAT prior linked discussion AND
you will find the other v10 being discussed in other linked or
referenced materials... ON OPERA..


The reason they do not work, and the checkbox was removed, is that the
devs have changed the way Opera handles Java....it is now handled via
a
plug-in. The only user-friendly way to disable Java is to disable ALL
plug-ins. Disabling Java without disabling other plug-ins can only be
done GLOBALLY now, through the plugin-ignore.ini. It turns out that
even the option to disable Java globally via opera:config is ignored
in
version 10.5x. There is no way to disable only Java on a PER SITE
basis, in Opera 10.5x. THAT is the point being made. Apparently you
are not using Opera 10.5x and are not aware of the changes that have
been made.

Jackson stated the inability to control Java on a per site basis was a
show stopper for him. I reiterated his position. You have gone on
and
on about how it can be done...prove it.


Man,, you have become awful whiny Windows user... WHERE are your links
to the discussions/information you are stating/referencing??? You do
know I have TRIED to put some actual info into this discussion..
Yeah I noted the plug in issue researching YOUR issues, so WHERE would
the modification be made... think it might be the controlling plug
in...
or another plug in or user script.. or STILL available via other
methods...

Come on man, just HOW do you think your browser receives its java
orders, oh wait I DID direct you to SUN "Beginners" pages so you could
look at the elements, page inclusions and other that would be the
identifiers/page elements to BLOCK... AND even provided a couple...
and DID note the user.css - that's CSS3 BTW, might want to look at what
can be done with that...

ALSO please post *YOUR* personal contacts with the *developers* of
Opera pursuant this issue. I see ZERO links in your posts...
Have ALL of you forgotten the PRIOR issues such as disablement of other
"features" for a couple *SUB* versions that were later corrected...and
generally due to input on *OPERA'S forums*...

And BTW I SPECIFICALLY stated I wasn't using Opera at the moment, and
my installation ISN'T going to help a Windows user, nor would any code
modifications FOR LINUX unless via a plug in or something like Blockit
[a plug in using Opera's built-in support]... did you even bother to
contact that creator/coder or any of the others on Opera's forums, or
others offering coding/plug-ins for work-arounds?
Yes?, links and/or personal contact indications please.
No?, then...

You could actually read the complete thread in one of the links that YOU
supplied earlier:
http://groups.google.com/group/opera...561d324362c6b8


If you read the entire thread, including the info supplied by Rijk van
Geijtenbeek from Opera Software ASA, you will see there is no longer any
option to disable one plug-in alone on a PER SITE basis, and that Java
is now handled as a plug-in, which was not the case in earlier
versions....but then you should already know that since you profess to
be so versed in the workings of Opera.

Yeah, AS SUPPLIED BY OPERA presently; I read that discussion and
several dozen others ON Opera and elsewhere; searched several dozen
sites for HAS been done to modify Opera and JAVA; refreshed my knowledge
on "java script" and JAVA; re-looked at the actual FF plug-in coding,
and I can see the areas which could potentially be used when compared
against Opera and its coding.
You want to whine, instead, why don't YOU write the new plug-in that
DOES allow JAVA disablement or work with the coders that are addressing
these and other issues, that seems far more productive.
I'm not professing anything like what you are attempting to infer
and/or stating; I AM indicating that if you rely upon many programmers
you will NEVER get what you want or what was/is needed to correct or
modify THEIR programs, nor information on HOW to control their
programs/applications - like Windows, or FireFox, or now Opera. If
enough Opera users complain or work on/with the Opera developers I would
bet you can get that checkbox "per site" function back.

BTW: the "disable one plug-in alone on per site basis" ISN'T what we
are supposedly addressing in this discussion beyond noting it was
removed, we are supposedly looking for ways to deal with these supposed
issues and applicable methods regarding JAVA and its usage and blockage.


Yet still you go on, with no specifics whatsoever, about CSS tweaking
and other "methods" to do this, even after I've repeatedly explained the
point we are making here.....that the majority of users do not do that
type of tweaking, and the previously available GUI options are no longer
available.

Oh wow, there's another duuuuhhhh moment... that WAS what we were
discussing wasn't it... glad you reminded me...

I have directed to the parties actually working on modifications and
plug-ins; files that potentially can/could be used; methodologies and
actual coding examples;, and several other necessary parts for both an
understanding of WHAT needs addressed and WHERE the potentials lay; now
point to ANYTHING you have posted which shows anything of value for
actually dealing with/addressing the purported issue.

AND MY POINT: you can sit there and whine and complain or you can make
an effort to do something about it or change it, or modify it; just like
everything else on this planet or in your life.

It was great that this was brought here for discussion to point out
this issue, its quite another when all YOU do is whine... and make
comments to me like *I'M* responsible for creating something YOU want
for YOUR OS, and in the childish "prove it" nonsense. I now use an OS in
which *I* have the ability to define/control just about any activity and
to what extent *I* allow it via the myriad of config and other settings
or direct code modifications available. If I choose, I can/could limit
just about anything or its access and/or abilities.

How about YOU PROVE beyond any modification or script, that it is
impossible to disable JAVA, I dare you [see how that's pretty childish
and stupid as there are ways to do so].


LOL...the only person being childish in this thread is you, MEB. Your
rude and condescending responses to Bill Blanton and myself, you refusal
to show one concrete example where Java can be disabled "per site" while
continuing to insist it can be done, your current frothing and
ranting......

Every time someone has asked you for clarification and to show a working
example, you run around the question, attacking the questioner's
intelligence or abilities, instead of giving any concrete useful answer or
working example.

Have you even tried BlockIt, the script you recommended, with Opera 10.5x?
I've added it, and it blocks images and some scripts.....but it does
nothing to block Java. Applets load and run unfettered.
--
Glen Ventura, MS MVP Oct. 2002 - Sept. 2009
A+
http://dts-l.net/

Have you read
Opera way to disable only Java. you give know reply to it, Why, Because
it Works.
if so you you keep play here!
You can not have your Cake and eat it too.
But you like to have it your way and it will not always work.



"glee" wrote in message
...
"MEB" wrote in message
...
On 04/30/2010 09:17 AM, glee wrote:
"MEB" wrote in message
...
On 04/29/2010 11:44 PM, glee wrote:
Geez....you've missed the entire point. There was, for many builds
and
versions of Opera, a simple checkbox to enable or disable Java on a
global or per site basis, readily available through the Preferences
menu
for all users, without having to resort to buried modifications. The
option was removed, making it much more difficult, if not impossible,
for said users to adjust the setting. The links you keep referring to
apply to earlier versions of Opera, when there was still an option to
enable or disable Java on a per site basis. They do not work with the
current version. Again, since you are insisting this can be done on
Opera 10.5x, show me how. The links you have supplied either discuss
disabling JavaScript but not Java, or describe how to do it on earlier
versions of Opera.

NO, I USED Opera, so I'm not ignoring the checkbox missing issue... and
LOOK on the Opera forums and for the other informational
sites/blogs/etc.

BTW No, 10.5* was being discussed in THAT prior linked discussion AND
you will find the other v10 being discussed in other linked or
referenced materials... ON OPERA..


The reason they do not work, and the checkbox was removed, is that the
devs have changed the way Opera handles Java....it is now handled via
a
plug-in. The only user-friendly way to disable Java is to disable ALL
plug-ins. Disabling Java without disabling other plug-ins can only be
done GLOBALLY now, through the plugin-ignore.ini. It turns out that
even the option to disable Java globally via opera:config is ignored
in
version 10.5x. There is no way to disable only Java on a PER SITE
basis, in Opera 10.5x. THAT is the point being made. Apparently you
are not using Opera 10.5x and are not aware of the changes that have
been made.

Jackson stated the inability to control Java on a per site basis was a
show stopper for him. I reiterated his position. You have gone on
and
on about how it can be done...prove it.


Man,, you have become awful whiny Windows user... WHERE are your links
to the discussions/information you are stating/referencing??? You do
know I have TRIED to put some actual info into this discussion..
Yeah I noted the plug in issue researching YOUR issues, so WHERE would
the modification be made... think it might be the controlling plug
in...
or another plug in or user script.. or STILL available via other
methods...

Come on man, just HOW do you think your browser receives its java
orders, oh wait I DID direct you to SUN "Beginners" pages so you could
look at the elements, page inclusions and other that would be the
identifiers/page elements to BLOCK... AND even provided a couple...
and DID note the user.css - that's CSS3 BTW, might want to look at what
can be done with that...

ALSO please post *YOUR* personal contacts with the *developers* of
Opera pursuant this issue. I see ZERO links in your posts...
Have ALL of you forgotten the PRIOR issues such as disablement of other
"features" for a couple *SUB* versions that were later corrected...and
generally due to input on *OPERA'S forums*...

And BTW I SPECIFICALLY stated I wasn't using Opera at the moment, and
my installation ISN'T going to help a Windows user, nor would any code
modifications FOR LINUX unless via a plug in or something like Blockit
[a plug in using Opera's built-in support]... did you even bother to
contact that creator/coder or any of the others on Opera's forums, or
others offering coding/plug-ins for work-arounds?
Yes?, links and/or personal contact indications please.
No?, then...

You could actually read the complete thread in one of the links that YOU
supplied earlier:
http://groups.google.com/group/opera...561d324362c6b8


If you read the entire thread, including the info supplied by Rijk van
Geijtenbeek from Opera Software ASA, you will see there is no longer any
option to disable one plug-in alone on a PER SITE basis, and that Java
is now handled as a plug-in, which was not the case in earlier
versions....but then you should already know that since you profess to
be so versed in the workings of Opera.

Yeah, AS SUPPLIED BY OPERA presently; I read that discussion and
several dozen others ON Opera and elsewhere; searched several dozen
sites for HAS been done to modify Opera and JAVA; refreshed my knowledge
on "java script" and JAVA; re-looked at the actual FF plug-in coding,
and I can see the areas which could potentially be used when compared
against Opera and its coding.
You want to whine, instead, why don't YOU write the new plug-in that
DOES allow JAVA disablement or work with the coders that are addressing
these and other issues, that seems far more productive.
I'm not professing anything like what you are attempting to infer
and/or stating; I AM indicating that if you rely upon many programmers
you will NEVER get what you want or what was/is needed to correct or
modify THEIR programs, nor information on HOW to control their
programs/applications - like Windows, or FireFox, or now Opera. If
enough Opera users complain or work on/with the Opera developers I would
bet you can get that checkbox "per site" function back.

BTW: the "disable one plug-in alone on per site basis" ISN'T what we
are supposedly addressing in this discussion beyond noting it was
removed, we are supposedly looking for ways to deal with these supposed
issues and applicable methods regarding JAVA and its usage and blockage.


Yet still you go on, with no specifics whatsoever, about CSS tweaking
and other "methods" to do this, even after I've repeatedly explained the
point we are making here.....that the majority of users do not do that
type of tweaking, and the previously available GUI options are no longer
available.

Oh wow, there's another duuuuhhhh moment... that WAS what we were
discussing wasn't it... glad you reminded me...

I have directed to the parties actually working on modifications and
plug-ins; files that potentially can/could be used; methodologies and
actual coding examples;, and several other necessary parts for both an
understanding of WHAT needs addressed and WHERE the potentials lay; now
point to ANYTHING you have posted which shows anything of value for
actually dealing with/addressing the purported issue.

AND MY POINT: you can sit there and whine and complain or you can make
an effort to do something about it or change it, or modify it; just like
everything else on this planet or in your life.

It was great that this was brought here for discussion to point out
this issue, its quite another when all YOU do is whine... and make
comments to me like *I'M* responsible for creating something YOU want
for YOUR OS, and in the childish "prove it" nonsense. I now use an OS in
which *I* have the ability to define/control just about any activity and
to what extent *I* allow it via the myriad of config and other settings
or direct code modifications available. If I choose, I can/could limit
just about anything or its access and/or abilities.

How about YOU PROVE beyond any modification or script, that it is
impossible to disable JAVA, I dare you [see how that's pretty childish
and stupid as there are ways to do so].


LOL...the only person being childish in this thread is you, MEB. Your
rude and condescending responses to Bill Blanton and myself, you refusal
to show one concrete example where Java can be disabled "per site" while
continuing to insist it can be done, your current frothing and
ranting......

Every time someone has asked you for clarification and to show a working
example, you run around the question, attacking the questioner's
intelligence or abilities, instead of giving any concrete useful answer or
working example.

Have you even tried BlockIt, the script you recommended, with Opera 10.5x?
I've added it, and it blocks images and some scripts.....but it does
nothing to block Java. Applets load and run unfettered.
--
Glen Ventura, MS MVP Oct. 2002 - Sept. 2009
A+
http://dts-l.net/

Risky is the Game on the micro world, with out a little risky you or know
one will be able to write Pug-in and Un-Pug!
In writing Un-Pug for a Browse a unwanted Errors came up and till you get
in right!
It's good to see MEB trying to write a Un-Pug Java for Opera Browse.

So do you have a Un-Pug Java Code in the Work for Opera,
If so can we see it, if not it's time to move on to a new SUBJECT do you
thank Bill Blanton!

No Need To Reply
if you not work on a Un-Pug Java Code for Opera Browse.



"Bill Blanton" wrote in message
...
On 4/30/2010 09:17, glee wrote:
"MEB" wrote in message
...
On 04/29/2010 11:44 PM, glee wrote:
Geez....you've missed the entire point. There was, for many builds and
versions of Opera, a simple checkbox to enable or disable Java on a
global or per site basis, readily available through the Preferences
menu
for all users, without having to resort to buried modifications. The
option was removed, making it much more difficult, if not impossible,
for said users to adjust the setting. The links you keep referring to
apply to earlier versions of Opera, when there was still an option to
enable or disable Java on a per site basis. They do not work with the
current version. Again, since you are insisting this can be done on
Opera 10.5x, show me how. The links you have supplied either discuss
disabling JavaScript but not Java, or describe how to do it on earlier
versions of Opera.

NO, I USED Opera, so I'm not ignoring the checkbox missing issue... and
LOOK on the Opera forums and for the other informational
sites/blogs/etc.

BTW No, 10.5* was being discussed in THAT prior linked discussion AND
you will find the other v10 being discussed in other linked or
referenced materials... ON OPERA..


The reason they do not work, and the checkbox was removed, is that the
devs have changed the way Opera handles Java....it is now handled via a
plug-in. The only user-friendly way to disable Java is to disable ALL
plug-ins. Disabling Java without disabling other plug-ins can only be
done GLOBALLY now, through the plugin-ignore.ini. It turns out that
even the option to disable Java globally via opera:config is ignored in
version 10.5x. There is no way to disable only Java on a PER SITE
basis, in Opera 10.5x. THAT is the point being made. Apparently you
are not using Opera 10.5x and are not aware of the changes that have
been made.

Jackson stated the inability to control Java on a per site basis was a
show stopper for him. I reiterated his position. You have gone on and
on about how it can be done...prove it.


Man,, you have become awful whiny Windows user... WHERE are your links
to the discussions/information you are stating/referencing??? You do
know I have TRIED to put some actual info into this discussion..
Yeah I noted the plug in issue researching YOUR issues, so WHERE would
the modification be made... think it might be the controlling plug in...
or another plug in or user script.. or STILL available via other
methods...

Come on man, just HOW do you think your browser receives its java
orders, oh wait I DID direct you to SUN "Beginners" pages so you could
look at the elements, page inclusions and other that would be the
identifiers/page elements to BLOCK... AND even provided a couple...
and DID note the user.css - that's CSS3 BTW, might want to look at what
can be done with that...

ALSO please post *YOUR* personal contacts with the *developers* of
Opera pursuant this issue. I see ZERO links in your posts...
Have ALL of you forgotten the PRIOR issues such as disablement of other
"features" for a couple *SUB* versions that were later corrected...and
generally due to input on *OPERA'S forums*...

And BTW I SPECIFICALLY stated I wasn't using Opera at the moment, and
my installation ISN'T going to help a Windows user, nor would any code
modifications FOR LINUX unless via a plug in or something like Blockit
[a plug in using Opera's built-in support]... did you even bother to
contact that creator/coder or any of the others on Opera's forums, or
others offering coding/plug-ins for work-arounds?
Yes?, links and/or personal contact indications please.
No?, then...

You could actually read the complete thread in one of the links that YOU
supplied earlier:
http://groups.google.com/group/opera...561d324362c6b8


If you read the entire thread, including the info supplied by Rijk van
Geijtenbeek from Opera Software ASA, you will see there is no longer any
option to disable one plug-in alone on a PER SITE basis, and that Java
is now handled as a plug-in, which was not the case in earlier
versions....but then you should already know that since you profess to
be so versed in the workings of Opera.

Yet still you go on, with no specifics whatsoever, about CSS tweaking
and other "methods" to do this,

MEB is never specific.. It's too risky to the argument.

even after I've repeatedly explained the
point we are making here.....that the majority of users do not do that
type of tweaking, and the previously available GUI options are no longer
available.

Risky is the Game on the micro world, with out a little risky you or know
one will be able to write Pug-in and Un-Pug!
In writing Un-Pug for a Browse a unwanted Errors came up and till you get
in right!
It's good to see MEB trying to write a Un-Pug Java for Opera Browse.

So do you have a Un-Pug Java Code in the Work for Opera,
If so can we see it, if not it's time to move on to a new SUBJECT do you
thank Bill Blanton!

No Need To Reply
if you not work on a Un-Pug Java Code for Opera Browse.



"Bill Blanton" wrote in message
...
On 4/30/2010 09:17, glee wrote:
"MEB" wrote in message
...
On 04/29/2010 11:44 PM, glee wrote:
Geez....you've missed the entire point. There was, for many builds and
versions of Opera, a simple checkbox to enable or disable Java on a
global or per site basis, readily available through the Preferences
menu
for all users, without having to resort to buried modifications. The
option was removed, making it much more difficult, if not impossible,
for said users to adjust the setting. The links you keep referring to
apply to earlier versions of Opera, when there was still an option to
enable or disable Java on a per site basis. They do not work with the
current version. Again, since you are insisting this can be done on
Opera 10.5x, show me how. The links you have supplied either discuss
disabling JavaScript but not Java, or describe how to do it on earlier
versions of Opera.

NO, I USED Opera, so I'm not ignoring the checkbox missing issue... and
LOOK on the Opera forums and for the other informational
sites/blogs/etc.

BTW No, 10.5* was being discussed in THAT prior linked discussion AND
you will find the other v10 being discussed in other linked or
referenced materials... ON OPERA..


The reason they do not work, and the checkbox was removed, is that the
devs have changed the way Opera handles Java....it is now handled via a
plug-in. The only user-friendly way to disable Java is to disable ALL
plug-ins. Disabling Java without disabling other plug-ins can only be
done GLOBALLY now, through the plugin-ignore.ini. It turns out that
even the option to disable Java globally via opera:config is ignored in
version 10.5x. There is no way to disable only Java on a PER SITE
basis, in Opera 10.5x. THAT is the point being made. Apparently you
are not using Opera 10.5x and are not aware of the changes that have
been made.

Jackson stated the inability to control Java on a per site basis was a
show stopper for him. I reiterated his position. You have gone on and
on about how it can be done...prove it.


Man,, you have become awful whiny Windows user... WHERE are your links
to the discussions/information you are stating/referencing??? You do
know I have TRIED to put some actual info into this discussion..
Yeah I noted the plug in issue researching YOUR issues, so WHERE would
the modification be made... think it might be the controlling plug in...
or another plug in or user script.. or STILL available via other
methods...

Come on man, just HOW do you think your browser receives its java
orders, oh wait I DID direct you to SUN "Beginners" pages so you could
look at the elements, page inclusions and other that would be the
identifiers/page elements to BLOCK... AND even provided a couple...
and DID note the user.css - that's CSS3 BTW, might want to look at what
can be done with that...

ALSO please post *YOUR* personal contacts with the *developers* of
Opera pursuant this issue. I see ZERO links in your posts...
Have ALL of you forgotten the PRIOR issues such as disablement of other
"features" for a couple *SUB* versions that were later corrected...and
generally due to input on *OPERA'S forums*...

And BTW I SPECIFICALLY stated I wasn't using Opera at the moment, and
my installation ISN'T going to help a Windows user, nor would any code
modifications FOR LINUX unless via a plug in or something like Blockit
[a plug in using Opera's built-in support]... did you even bother to
contact that creator/coder or any of the others on Opera's forums, or
others offering coding/plug-ins for work-arounds?
Yes?, links and/or personal contact indications please.
No?, then...

You could actually read the complete thread in one of the links that YOU
supplied earlier:
http://groups.google.com/group/opera...561d324362c6b8


If you read the entire thread, including the info supplied by Rijk van
Geijtenbeek from Opera Software ASA, you will see there is no longer any
option to disable one plug-in alone on a PER SITE basis, and that Java
is now handled as a plug-in, which was not the case in earlier
versions....but then you should already know that since you profess to
be so versed in the workings of Opera.

Yet still you go on, with no specifics whatsoever, about CSS tweaking
and other "methods" to do this,

MEB is never specific.. It's too risky to the argument.

even after I've repeatedly explained the
point we are making here.....that the majority of users do not do that
type of tweaking, and the previously available GUI options are no longer
available.