How to use Firebug Lite on iOS (iPad, iPhone, etc.):

http://martinkool.com/post/13629963755/firebug-on-ipad-and-iphone

If you have tried out the new iTunes Match service from Apple, you may be disappointed that these playlists are not synced to iCloud (you see a little cloud icon next to your playlist name with a slash through it that clicked tells you it is ineligible for iCloud):

The playlist needs to be refactored so that it doesn’t depend on other playlists.

Unfortunately iTunes does not let you construct a single playlist that matches exactly to what was created in my old post (you can’t set a “limit to” number of songs for a single matching subsection–only to entire playlists). However, as a next-best thing, you can take advantage of the “Last Skipped” clause to help minimize the occurrence of poorly-rated music. The following is a single stand-alone playlist that corresponds to the “Good Mix” playlist from the old post (hold down the Option/Alt key when clicking the “+” button to create one of the indented “All”/”Any” subsections):

Here’s another single stand-alone playlist that corresponds to the “Christmas Mix” playlist from my old post:

Adjust the time values to your preferences.  The reason why the no-star ratings are given equal weight as the 5-star songs is that it is likely that it is music that you just purchased and thus want to hear it frequently until you make a decision on what other rating you want to give it or it will help encourage you to rate all of your music.  If you have a ton of unrated music simply make a zero-star-rated playlist and work your way through it.

1. If you use af:region and the jsff page fragment files have more than 1 root component, optimize it by arranging these components with a single root component. For example, if you want your region contents to stretch, you might have one visible content component and a series of popup components, put the visible content component inside of a “center” facet of an af:panelStretchLayout and put all of those popups in the “bottom” facet but also make sure to assign bottomHeight=”0px”. If you don’t want the contents to stretch, simply wrap these components with an af:panelGroupLayout layout=”vertical”.
2. Avoid using a af:panelStretchLayout where topHeight, bottomHeight, startWidth, or endWidth is set to “auto”.
3. Minimize uses of af:panelAccordion in discloseMany=”true” mode if possible.
4. Minimize use of components that provide overflow popups, e.g. af:panelAccordion, af:panelTabbed, af:toolbar, af:breadCrumbs, af:menuBar. If you have to use these components, make sure that your target screen size can accommodate the content without having to invoke overflow.
5. Minimize use of components that provide custom title text truncation, e.g. af:panelHeader and af:showDetailHeader. If you have to use these components, make sure that your target screen size can accommodate the title text without having to truncate.
6. Minimize use of af:carousel, af:table, af:tree, af:treeTable.
7. Avoid complex user interfaces. Users will struggle to process complex application structures. Legacy browsers will struggle with processing of complex content. Keep the number of tabs simple (use less than 10). Keep the number of columns in a table small (use less than 10).
8. Finally, don’t ignore the warnings that JDeveloper gives you.

Here’s an example assigning a padding for the “start” side of 10px:

inlineStyle="padding-#{adfFacesContext.rightToLeft?'right':'left'}:10px;"

See oracle.adf.view.rich.context.AdfFacesContext for other properties.

Step 1 – Select your shape with the selection tool.

Step 2 – Open the gradient palette and select the color stop whose color you wish to change (notice the triangle above the color has a black fill).

Step 3 – Change to the eye dropper tool (or press “i”)

Step 4 – It is very important that you hold down the shift key when you click to pick up a color or else the gradient will be replaced with a solid color but now the color stop is using your newly-chosen color!

Step 1 – Draw the shape.

Step 2 – Add a stroke to the shape by choosing Effect – Path – Outline Stroke.

Step 3 – The stroke appears with a solid color.

Step 4 – Convert the solid stroke into a separate object by choosing Object – Path – Outline Stroke.

Step 5 – You now have separate objects so you can select the stroke separately to make changes.

Step 6 – Finally, you can apply a gradient style on the separated stroke object and can apply other effects like a drop shadow.  Rearrange the order of the 2 objects so that the drop shadow of the stroke does not cover up the inner shape.

I found a solution that brings the icons back (this could just be a temporary fix):

1. Right-click the icon and choose Options – Show In Finder so that you can easily locate it in a future step.
2. Drag the transparent icon away from the dock so that it turns into a puff of smoke.
3. Open Applications – Utilities – Terminal then type “killall Dock” to restart the Dock
4. From the window opened in step 1, drag the icon back into the dock where it was before

These UIInstructions components are likely due to the presence of an HTML DOCTYPE (or other content) appearing in one or more of your JSF fragment files. These fragment files are likely missing a ui:composition wrapper.

More info on why you might want the HTML DOCTYPE (or other content):
http://download.oracle.com/javaee/6/javaserverfaces/2.0/docs/pdldocs/facelets/ui/composition.html

As browsers evolve, changes have been made with how the HTML “accessKey” attribute works. There are differences across platforms for the same browser version as well as differences across browser versions on the same platform.  There are even some cases where the exact same browser treats accessKey differently for button elements vs. anchor elements!  This post shows some examples of how to invoke the accessKey and what the behavior is.

Sample button and anchor HTML using the “accessKey” attribute

<html>
<body>
<button onclick="javascript:alert('hi button with onclick')"
        accessKey="r">Button t<u style="color:red">r</u>y me</button>
<a href="javascript:;" onclick="alert('hi anchor with onclick');return false;"
        accessKey="o">Anchor with <b style="color:red">o</b>nclick</a>
</body>
</html>

How different browsers handle the above accessKey letters for button and anchor elements

• Red = Different behavior for buttons and anchors
• Comment 1 = To just set focus on the button/anchor, change your about:config setting for the “accessibility.accesskeycausesactivation” user preference.
• Comment 2 = Press Enter to click the button/anchor
• Comment 3 = There appears to be no built-in mechanism to just set focus on the button/anchor.  The component handling the click event would be responsible for setting focus while handling the click.

<attribute-class>java.lang.String</attribute-class>

but what if you needed an array of Strings? That has a bit stranger syntax:

<attribute-class>[[Ljava.lang.String;</attribute-class>

Why is this not just "java.lang.String[]"? These attribute-class entries are the result of calling Class.forName.  The Class.forName on an array of objects looks like "[[Lsome.package.SomeClass;".