Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Openmoko Bug #1584: remove legacy openmoko boot image
(Openmoko Public Trac)
2. Re: Openmoko Bug #1583: disable blank time, keep
suspend/resume (Openmoko Public Trac)
3. Re: Openmoko Bug #1578: backstroke should delete entire
entry, not just one letter at a time (Openmoko Public Trac)
4. Re: Openmoko Bug #1579: unable to enter words that are not in
dictionary (Openmoko Public Trac)
5. Re: Openmoko Bug #1580: launch words from qtopia softmenu bar
(Openmoko Public Trac)
6. Re: Openmoko Bug #1582: create bottom bar for launcher
(Openmoko Public Trac)
7. Re: Openmoko Bug #1583: disable blank time, keep
suspend/resume (Openmoko Public Trac)
8. Re: Openmoko Bug #1584: remove legacy openmoko boot image
(Openmoko Public Trac)
9. Re: Openmoko Bug #1511: Take screen shot with gpe-scap press
"Browse" will cause Enlightment crash (Openmoko Public Trac)
--- Begin Message ---
#1584: remove legacy openmoko boot image
------------------------+---------------------------------------------------
Reporter: will | Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: normal | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Keywords: boot screen
Blocking: | Blockedby:
------------------------+---------------------------------------------------
raster, i'm still seeing the black and orange openmoko image during boot.
can we jump directly into our boot screen?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1584>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1583: disable blank time, keep suspend/resume
------------------------+---------------------------------------------------
Reporter: will | Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: high | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Comment(by marek):
Exposure already modifies the blank time only. AFAIK raster changed the
suspend time default to 1 second which will give you the desired
behaviour.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1583#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1578: backstroke should delete entire entry, not just one letter at a time
-------------------------+--------------------------------------------------
Reporter: will | Owner: [EMAIL PROTECTED]
Type: enhancement | Status: closed
Priority: normal | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution: wontfix
Keywords: keyboard | Blocking:
Blockedby: |
-------------------------+--------------------------------------------------
Changes (by raster):
* status: new => closed
* resolution: => wontfix
Comment:
This is not actually possible given standard keyboard input. as best i
know even xinput and complex input systems can't do this, so i have to
mark this as "wontfix". the ONLY way todo this is to go to every toolkit
and extend it with a "delete previous word" command that is reliably
accessible for an input system (qt, gtk, efl etc.) and that's not going to
be a happening thing any time in the near future (as i either need to
ASSUME some ctonrol-key sequence like ctl+shift+w or something, or a
special keycode mapped to a special keysym or need to look at a full input
method handler like scim/uim etc.). :(
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1578#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1579: unable to enter words that are not in dictionary
-------------------------+--------------------------------------------------
Reporter: will | Owner: [EMAIL PROTECTED]
Type: enhancement | Status: new
Priority: lowest | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution:
Keywords: keyboard | Blocking:
Blockedby: |
-------------------------+--------------------------------------------------
Changes (by raster):
* priority: high => lowest
* type: defect => enhancement
Comment:
invalid. i am happily entering those words right here now. if it's not in
the dictionary - you're going to have to type CAREFULLY and actually hit
the exact letters. it CAN be done - use your fingertip or a stylus. so not
a defect - an enahncement at best, and unfortunately i'm probably not
going to have time for it right now.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1579#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1580: launch words from qtopia softmenu bar
-------------------------+--------------------------------------------------
Reporter: will | Owner: [EMAIL PROTECTED]
Type: enhancement | Status: new
Priority: low | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution:
Keywords: keyboard | Blocking:
Blockedby: |
-------------------------+--------------------------------------------------
Changes (by raster):
* priority: normal => low
Comment:
ugh painful, but can be done. nothing to do with qtopia's softmenu (its
options/cancel thing). illume now needs special keyboard and layout policy
to hide the softmenu while typing then timeout etc. etc.... a lot of
little infra-changes
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1580#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1582: create bottom bar for launcher
------------------------+---------------------------------------------------
Reporter: will | Owner: [EMAIL PROTECTED]
Type: task | Status: new
Priority: normal | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Comment(by raster):
ugh. there goes august 8 for ASU. :(
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1582#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1583: disable blank time, keep suspend/resume
------------------------+---------------------------------------------------
Reporter: will | Owner: [EMAIL PROTECTED]
Type: defect | Status: closed
Priority: high | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution: fixed
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Changes (by raster):
* status: new => closed
* resolution: => fixed
Comment:
this is already done. been done for a week or so...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1583#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1584: remove legacy openmoko boot image
-------------------------+--------------------------------------------------
Reporter: will | Owner: [EMAIL PROTECTED]
Type: defect | Status: closed
Priority: normal | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution: wontfix
Keywords: boot screen | Blocking:
Blockedby: |
-------------------------+--------------------------------------------------
Changes (by raster):
* status: new => closed
* resolution: => wontfix
Comment:
this is not controlled by the kernel or rootfs images. it is controlled
by:
1. your uboot environment
2. another partition containing a splashimage.
at this point this is not something u can change with ASU as it's nota
direct flash of kernel or rootfs. this is definitely system-team land, and
even then unless users go and do some u-boot hacking and fun and write a
new splash in via uboot or cat it to /dev/mtdblock (something - not
sure)... you get to keep the current splash.
so it's "out of scope" imho - re-open or re-assign to system team if u
want...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1584#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1511: Take screen shot with gpe-scap press "Browse" will cause Enlightment
crash
-------------------------------+--------------------------------------------
Reporter: wendy_hung | Owner: [EMAIL PROTECTED]
Type: defect | Status: closed
Priority: normal | Milestone: ASU
Component: unknown | Version:
Severity: normal | Resolution: fixed
Keywords: Enlightment crash | Blocking:
Blockedby: |
-------------------------------+--------------------------------------------
Changes (by raster):
* status: new => closed
* resolution: => fixed
Comment:
fixed in upstream and should be in stable builds already.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1511#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
