-
Content Count
5,747 -
Joined
-
Last visited
-
Days Won
335
Everything posted by EskeRahn
-
Indeed yes, important point. A Caps-lock, not a Shift-lock like old typewriters. :-)
-
e.g. like this rough sketch for the 7-key
-
actually we could get even closer if the values on the number rows also moves to SHIFT, somewhat like here from this (with the blue printed in yellow, and perhaps moved up)
-
Very good suggestion, especially a nice idea with braces and bracket (and others) close® to their usual pc-positions. A few of the ones in the second lowest row ">", ";", ":" and "_" I believe should be moved left on the keys to SHIFT position and not AltGr/YellowArrow position
-
It is, see e.g. this
-
That may go for US/UK layout, but certainly not for national keyboards. The AltGr is the way to access the stuff moved away to free the national letter keys... e.g. brackets and braces moved to AltGr 7-0, and AltGr and key left of Z to get backslash. Also access to €@£$ and the tilde as an accent are all through AltGr. But that said it of course does not matter if the key is labelled as a yellow arrow or the (odd) "AltGr"
-
Keyboard print layouts and functionality
EskeRahn replied to caymen's topic in Pro1 - Thoughts & questions
I think it is much up to the app what it reacts to. But for sure when they write their own email program optimised for landscape, I too hope they remember the various ctrl-navigation functionality. -
Keyboard print layouts and functionality
EskeRahn replied to caymen's topic in Pro1 - Thoughts & questions
Does the last part mean that the users can swap the keyboard themselves? That is that we can all safely pre-order the US model, and then later swap the keyboard if/when a layout fitting our needs better will be produced later on? If so do you have an estimate for the price of an additional keyboard? -
I guess it is a transitional problem, but could be handy yes. I opened all threads, took a few minutes, but it worked.
-
I hope for that too. I like the "Open Camera" app using the Camera2 API.
-
There are multiple app cloner apps on the market, some free, and some with millions of users. I have no idea if one will be pre installed. A very popular choice is "Parallel Space" with over 100millions downloads, and 3.6M reviews giving it a 4.6 score. might be worth a try. But if you ask if there will be a specially customized version of Android with the functionality added, I doubt it. If I understand correctly they specifically want it to be a "Pure Android experience", with a few apps added to ease the usage in Landscape compared to native Android, but none you are 'forced' to use.
-
For some apps that approach might work well, but not for others. Unless they are aware what is going on so some data can be shared between the clones.
-
Alternative OS availability, common entry
EskeRahn replied to EskeRahn's topic in Pro1 - Thoughts & questions
See new tweet. Sailfish on Pro¹ shown in short video a few hours old: -
Updates? More Consistent Interaction from Dev Team
EskeRahn replied to rubleaj's topic in General Discussion
And whenever we find it relevant to refer to the Pro¹ in other fora to do so, and perhaps with links pointing to this site. We are a small niche of users that want hardware keyboards, so the more we spread the good word the better... The more that find out the existence of this, the more potential buyers there will be, and this again will help this whole project to be profitable. And this again gives us a users a chance for better support and later updates and follow up products, including any Pro². -
Ah I see. And yes, I agree, a standardized international print, could fit many. And for those of us that prefer a national logical layout (no matter what is printed), The standard US-international could be a very good start, as the relatively few changes needed for the 'national oddities' would be all we will need to remember the placements of. (e.g. for German the Y/Z swap, and some functions moved behind a modifier key, to free the keys for ÄÖÜß) So perhaps we should recommend that they should go for * QWERTY US, Right-shifted A-Z * QWERTY US-International and then one or more of
-
I'm a bit confused now. Are you talking the FUNCTION of the keyboard, or the PRINT? I expect there to be all kinds of symbols functionally accessible by the modifier key, no matter the print. And expect that we can choose from a variety of logical national layouts (and hopefully modify them our selves). This thread was supposed to be on what should be printed on a QWERTZ keyboard, but is getting interwoven with the general thread on the keyboard layouts. (Once the QWERTZ layout is locked down in a final layout, perhaps the two threads should be merged)
-
I see this as in the department for wishes for a future Pro², as I find it extremely unlikely that we will see fundamental hardware changes at this late stage of the development of the Pro¹. I too like replaceable batteries, as I find it much easier to carry some spares, than to have a heavy device. And it also allows us to be more careless with the charging pattern (e.g. fast charge away...), as it would be no big deal how long the total lifespan of each battery would be. IF the battery is reasonably easy user replaceable on the Pro¹, I would be glad. But as I have not seen anything men
-
Interesting. Did not know that. I see that a lot of windows fonts are not yet(?) updated with the capital sharp S either, and in some the implementation looks dubious (try e.g Segoe UI Black).
-
Oh I agree with you, I just pointed out that for - I believe - many languages using Latin letters, the use of letters outside A-Z is primarily limited to a few national letters, that deserves dedicate one-stroke keys (like ÄÖÜẞ in German or ÆØÅ in Danish/Norwegian). But sure for languages heavily using accents/diacritics, that is not a possible approach, and here I too would prefer a modifier key over dead keys. But if a language uses many different accents/diacritics they will soon run out of modifier keys, so here the dead key could be a better approach....
-
Updates? More Consistent Interaction from Dev Team
EskeRahn replied to rubleaj's topic in General Discussion
Well one could argue that this forum is currently to keep us that are already aware of it interested. But catching new people would need other ways as they are unlikely to find this forum by accident. ;) I guess the forum is going to be much more alive when we all get the devices in our hands, and have all kinds of questions and wishes for what could be tweaked in software updates, or perhaps things shared user-to-user. Personally I hope there will be a way to share logical key-layouts, so the less nerdy can benefit from what the nerds among us will do for our own devices anyway. (And hopef -
I only got my S8- for half a year, but the BB Priv for three, and have seen no burn ins (yet?) on either. But could well be a matter of usage pattern. I use my phones/phablets primarily indoors, so seldom in need of high brightness. For both I have used a white theme, though after Pie switched to a black one on the S8-
-
Well in my experience it much depends on the usage. Used with a high brightness and/or some of the tempting always-on functionality, yes then OLED can burn, but if not, I do not see it as an issue. Many years ago I had a series of Samsung E870, and the exterior always-on OLED-displays, indeed did get burned out. When an update allowed to turn the always-on function off, the problem was gone, even on this early OLED.
-
Updates? More Consistent Interaction from Dev Team
EskeRahn replied to rubleaj's topic in General Discussion
I agree that more team interaction would be nice. As a volunteer, and not a staff member, I only give out already public available info. (I was "Moderator", but due to that limited me in doing something (forgot what it was) they gave me the higher role). I will forward the existence of this thread to the staff. -
All the phones I have had with FM required the use of the headphones as antenna, and this goes for the tiny portable FM-radios I have had too. As the FM lies around a wavelength of 3m, they need something comparable to 1/4 of that, that is comparable to 75cm. So even the largest phablets would struggle with FM with an internal antenna only. It might work with a strong signal under ideal conditions. So without knowing for sure, I feel quite convinced that the cable is needed.