Follow-up: New kbd layout for e17 wm (beta2 release)

As a follow-up post to the Demo build of Enlightenment 17, I have made a new keyboard layout specifically designed for the Archos 5/7’s screen resolution.  I have also addressed a few troubling issues in regards to the illume kbd itself.

List of improvements:

  • The dimensions are now 800×220 so there is more viewing area above the keyboard.
  • Decreased the size of the keys a touch (not a problem since the interpretive skills of illumes kbd are amazing), and increased the font size on the keys themselves
  • Moved the placement/size of the “popup” keys (when a key is initially pressed –the popup display that grows from the current key pressed) to compensate for the new container size.
  • Moved some bottom row buttons around to center the space-bar for easier use with both thumbs.
  • Removed the “Terminal” kbd layout, since it is no longer compatible with the new 800×220 container.
  • Added a keyboard icon to the top shelf (replacing the “qwerty” text).

Some Screenshots:

custom e17 kbd container (800×220)

e17 topshelf keyboard icon

Since I had to recode the illume bits to make changes to the top shelf and the letter sizing/placement, it is necessary to download the new beta version, as opposed to just releasing a .kbd file.  Props go out to raster from #e for some advice on edje  :)

You can download the image  >>>HERE<<<

**note:  I’ll be updating the parent post with the new beta2 build as well.

Note::

[ If you wish to run this along side your current build, rename image to "illume.img" and make the appropriate entry in "menu.lst" Otherwise just overwrite your "rootfs.img" and your good to go.]

As always, input and suggestions are welcome.

~Cheers

Spz0


Tags: , , , , , , , , ,

13 Responses to “Follow-up: New kbd layout for e17 wm (beta2 release)”

  1. SynK says:

    sorry to be a bother, but will this work with gen 7? ive been trying to find out for ages, but im gessing both gen 6 and 7 support this, idk. Sorry to bother but I have looked around the forums and here for an answer, but came to find out that I am terrible at searching things!

    Thanks!

    • tbr says:

      It should sort-of-work.
      There still is no official gen7 angstrom image although I’ve heard that making things work with at least some of the gen7 specific fixes isn’t that hard. Archos helper will be mostly useless though as we have different wireless chipsets etc.

  2. Kearney says:

    I would like to give you kudos for a very sweet set up… I now really like my Archos. Had a question though. Every time I upgrade everything I seem to break the Archos; as in I get the Angstrom start up screen but then it just hangs there at the very last bit. Any ideas? No worries if not, I just won’t upgrade. Thanks again for a sweet set up.

    • tbr says:

      If you mean opkg upgrade – that can break things. Especially depending on which image you run it might use up all the inodes. For now I would – if at all – only upgrade single packages that I know need upgrading.

      In the long run this problem should disappear with better angstrom/openaos integration.

      • Kearney says:

        Cool thanks for telling me. Another noob question…how do I know which packages need upgrading and how do I do it?Thanks

  3. kyle says:

    i can never get this to boot. it always hangs on the black screen with the little “x” how can i fix this?

    • Spz0 says:

      Try renaming your “home.img” to something else. The image will re-create your home.img and add all necessary mods to it.
      Also, I have never tested running multiple e17 images in succession, so if you have had y older build installed, and are upgrading, consider starting with a fresh home.img.

      Good luck. :)

      • kyle says:

        yea, that didnt work either i am just going to give up

        • Spz0 says:

          Im not sure then m8, it’s been tested around the ringer, and works 100% or it wouldn’t be released.
          Stop by #openpma , perhaps others may have more insight as to your particular problem.

          ~Cheers :)

          • kyle says:

            what you said works!! i dont know why it didnt work the first 5 times but i did it a sixth time and then all of a sudden the x went away and the other screen popped up. thank you for your help!!!

  4. greg says:

    I can’t thank you enough, this has finally turned my A7 into a viable pdf reader, the loading times of the standard reader drove me nuts. Is there anything that can be done for the epdfreader so that it functions even in full screen mode?

    • Spz0 says:

      to be honest, Im not sure m8. I haven’t played around with it enough. I find that it works great for me in normal mode. Something to note though. I’ll have to check into it.

      Thanks :)

      ~Spz0

  5. [...] **updated to beta2 build as described HERE [...]

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>