Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>What you plan looks doable. Can't give much links because don't recall any that could help on stuff like you're doing. Actually, most useful link for you will probably be MIDP (<a href="http://download.oracle.com/javame/config/cldc/ref-impl/midp2.0/jsr118/index.html" rel="nofollow">JSR 118</a>) API reference - your part is going to be mostly <code>lcdui</code> package, and especially <code>Graphics</code> API.</p> <p>As for advice, no problem. First thing to note is that there will be more coding and more (much more) testing/debugging than it was in your prior experiment with <em>implicit list</em>. If you can think of some possible deadline / timing requirements that may become a problem - just keep in mind that prior design with implicit list as a fallback. It won't look as fancy but it'll work work safe and correct.</p> <p>Another important thing is to decide what kind devices you are going to target. For menu like one you are going to develop, it may be rather difficult to get consistent look and feel both at 160x200 basic phone with <a href="http://en.wikipedia.org/wiki/Telephone_keypad" rel="nofollow">ITU-T keypad</a> and on 400x600 touchscreen smartphone. Below I am going to assume you'll try to target as wide variety of devices as possible - note the narrower you can get it, the easier it will be to code and test.</p> <p>When targeting lots of different devices it is helpful to use an emulator that can be configured to simulate various display sizes and resolution, presense or absence of touchscreen input etc. Keep in mind though that emulator alone won't fully simulate real device. To keep your feets on the ground, consider also some regular <a href="http://en.wikipedia.org/wiki/Smoke_testing" rel="nofollow">smoke testing</a> of your application with real device, preferable using over-the-air (OTA) installation.</p> <p>Here are some particular API tips that I can think of now.</p> <ul> <li>Use <code>Canvas.getGameAction</code> to handle pressed key code - that is likely the most reliable/portable way to figure up/down and select actions for menu. </li> <li>Use <code>Canvas.hasPointerEvents</code> to figure if there's touch screen support. Users with touch screen devices may get disappointed if it turns out that your fancy menu can't react when they tap on screen. </li> <li>Use <code>Font.getHeight</code> and <code>Font.stringWidth</code> to figure how much space is occupied by menu item text. </li> <li>Use <code>Image.getGraphics</code> if you want to draw something over the image object.</li> </ul> <p>As I mentioned, you most likely will do a lot of stuff using <code>lcdui.Graphics</code> API. It's mostly rather simple, but you will probably need to understand somewhat tricky stuff about clipping. Good luck.</p>
    singulars
    1. This table or related slice is empty.
    1. POJ2ME app menu develop
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USgnat
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POJ2ME app menu develop
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COmany thanks, i'll try to do it
      singulars
      1. PO
      1. USMRM
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload