| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10
Comments:
<0> Well, access keys - without visual popups - are enabled in all other browsers, I think: Firefox, Opera, IE ...
<1> I meant the Ctrl turning them on
<1> the next key will act
<2> Sho_: I think not in Firefox... some people have been asking for this feature...
<0> Yes, it would need to be a combo of pressing Ctrl+key simultaneously, as it is everywhere else
<2> I think it's only available through an extension
<0> Unless the popup thingie is on
<2> but Ctrl+Key simultaneously would be mapped to other shortcut keys...
<1> ctrl+keys are already taken
<1> we can't do that
<0> Jucato: Firefox definitely has access keys - and had so since Netscape 1.0 probably ;)
<2> Sho_: how to activate them? let me check...
<0> Jucato: Ctrl+key, how else
<2> Sho_: must be something that needs to be enabled first
<2> :(
<0> Jucato: accessibility.accesskeycausesactivation is 'true' by default in my copy of Firefox
<2> about:config?
<0> yup
<2> it's true here too... but can't seem to activate it...
<2> nothing appears...
<0> Jucato: What would appear?
<2> nothing...
<2> bah nvm...
<0> Jucato: You're confusing access keys and popups for them again :)
<2> are they different really? or just how Konqueror/KHTML defines/implements them... how do I use Access Keys in Fx?
<0> It's true however that the Firefox implementation has its pitfalls as well ... iirc when 2.0.0 came out one of its official keyboard shortcuts shadowed a common access key used in some popular webforum software and everybody got angry
<0> There's an about:config option somewhere where you can change the precedence of access keys over app shortcuts which became popular due to that
<2> ok, here's my problem... I didn't implement all these Access Keys features... until a few days ago, I didn't even know where they are defined... I'm just making a GUI control for people to be able to turn them on/off, because they've been complaining, because it's a hidden setting...
<2> :(
<0> Jucato: Well, as I said above, what it comes down to is that in HTML, you can add an 'accesskey' attribute to elements. E.g. <input accesskey="p" />. The thought behind that feature of the spec is to give document authors the ability to ***ign keyboard accelerators/shortcuts to UI elements.
<1> KHTML goes one step further and ***igns them to elements even when authors don't
<1> which is what annoys people
<1> having them on the few webpages where authors did add access keys wouldn't be a problem
<2> yes, most of the ***ignments are random and inconsistent
<1> having them everywhere does
<0> Jucato: The browsers differ in how these accelerators/shortcuts are exposed to users. Most browsers other than Konqueror treat them as regular accelerators, giving app shortcuts that happen to be the same precedence, I guess. In Konqueror, you press Ctrl and popups appear showing the access key alongside the element it was ***igned to, and then you press the key.
<1> they are not random nor inconsistent
<1> they are ***igned first to form elements, preferring first letters in words
<2> ok they just "seem" random...
<0> Jucato: Since it's different in every other browser, I ***umed the popups were an optional visualization of what works the same as in other browsers when the popups are disabled
<1> then they are ***igned to links
<0> Jucato: Which apparently isn't the case, so I was wrong
<1> if no letter is available, it goes alphabetical
<1> if you have a link "Click Here" and a button "Click Here", the access keys will be, respectively, H and C
<0> Jucato: So your label text would appear to be fine save for the "/disable"
<2> last try... "Enable Access Ke&ys - Ticking this checkbox enables KDE's Access Keys, which are activiated by pressing the Ctrl Key. Konqueror needs to be restarted for changes to take effect."
<2> that one?
<2> because it really does disable them when disabled. no popups, no access keys...
<0> Not sure how I feel about "KDE's Access Keys" .)
<1> Konqueror's
<0> But KHTML's Access Keys would be geeky
<2> KHTML's Access Keys
<0> Perhaps just say "Access Keys"
<2> thiago: it doesn't affect KOnqueror only
<1> true
<2> ok, removing "KDE's"
<1> but most people don't notice them in KMail
<0> thiago: The popups happen in other apps that embed KHTML as well, e.g. Amarok ... and apparently that preference does disable them as well
<2> actually, I could make it affect Konqi only, but that would make it inconsistent...
<0> so Konqueror's would be not-quite-right, too
<0> But KDE's invites confusion with normal accelerators
<1> yeah...
<2> kmail, akregator, amarok, ktorrent, anything that uses KHTML...
<2> ok.. plain Access Keys it is
<1> which is why I think for KDE4 we need to KParts around KHTML
<1> one for the web browser and another for embedded HTML
<1> s/to/two/
<2> um... any more corrections before I svn diff and re-send the patch?
<0> Yeah, that's needed for other reasons as well
<0> E.g. the DPI calculation ****up
<1> true, but I fear that lies deeper down
<1> the parts are just shells around KHTML
<1> the difference between the two would be the turning on and off of features, as well as some browser integration
<1> embedded HTML most definitely don't want non-local references being loaded, JS being run, etc.
<0> I remember talking to Maksim about the DPI thing and he briefly considered adding some API to the part to set the DPI mode depening on what the engine was used for
<0> If there were two parts, that could be done there :)
<0> (It's funny how we tend to have more serious devel discussion here than in #kde-devel these days ..)
<2> maybe I should bring these stuff into #k-d...
<0> You'd distract them from talking about Freeciv
<0> ;)
<2> oh yeah... nvm...
<2> i don't want to butt in... :)
<3> quiero el repositorio para
<3> debian de kde 3.5.5
<4> hi all
<5> uranos: english please
<5> hello elvirolo
<4> what package should i install in order to get the "extract here" (ark) entry in the action menu ?
<2> um.. Ark
<0> elvirolo: Ark -- have a look in its preferences, there's an option to enable/disable Konq integration
<4> Sho_: ok thanks
<0> elvirolo: If it's enabled already, try disabling it and enabling it again
<2> hm.. maybe I should have mentioned the patch to #khtml and sent it there rather than kfm-devel?
<4> it says i have to install kdeaddons
<4> hum
<0> Jucato: kfm-devel is the right venue
<5> elvirolo: yup, you have to install that
<2> ok...
<0> Isn't ark in kdeutils?
<5> for the action menus of ark in konqueror
<0> ah
<5> Sho_: yes, but its actionmenus are provided as addons in kdeaddons
<2> it's separate?
<2> oh
<5> arkplugin it's called, iirc
<6> What does it take to get on the KDE site?
<2> ?
<6> canllaith: How goes?
<5> ?
<7> lol
<6> Are there requirements fora project for it to be hosted as a sub section of kde.org?
<8> it should be a kde app
<8> obviously
<2> :)
<8> what app do you hgave in mind DaSkreech ?
<2> wb annma
<8> I git cut off
<8> got
<2> aw... :(
<2> ditto...
<8> ;)
<6> sometimes in stead of alt-tabbing you have to halt-tabbing
<6> annma: Katapult
<6> They are a tad disroganized but the rooler coaster website they have really hurths them
<8> do you have a svn account?
<2> currently, Mez's host kinda took down their site (afaik)
<8> DaSkreech: will yo be webmaster?
<6> Yeah and before that it was hacked and before that it was kind of randomly renamed
<6> annma: I'm not sure I'll have to ask the current webmaster I guess
<2> that'll be Mez
<9> DaSkreech: are you talking about getting a new katapult page up?
<2> is katapult in kde svn already?
<8> DaSkreech: you'll have to ask sysadmin for hosting
<8> note that the website will be KDE style
<8> (probably)
<9> katapult had a number of branches on launchpad, most are abandoned
<6> Oh also. how would wiki work?
<8> no wiki
<6> Blast :-(
<8> you can't have your own wiki in that case
<8> yes
Return to
#kde
or
Go to some related
logs:
ubuntu invalid compressed format
CS_DESCRIBE_INPUT returned 0
#php
#lgp
#debian
ubuntu lib6c audio
install wolfenstein on dapper
megahal little endian
centos could not allocate partitions as primary partitions
debian stuck in prompt
|
|