[svn:osmf:] 15094: Organizing OSMFPlayer sources in packages continued.

Revision: 15094
Revision: 15094
Author:   [email protected]
Date:     2010-03-29 05:37:23 -0700 (Mon, 29 Mar 2010)
Log Message:
Organizing OSMFPlayer sources in packages continued.
Added Paths:
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/OSMFPlayer.as
Removed Paths:
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/osmf/player/application/OSMFPlayer.a s

Similar Messages

[svn:osmf:] 15095: Organizing OSMFPlayer sources in packages continued.

Revision: 15095
Revision: 15095
Author:   [email protected]
Date:     2010-03-29 05:41:44 -0700 (Mon, 29 Mar 2010)
Log Message:
Organizing OSMFPlayer sources in packages continued.
Modified Paths:
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/OSMFPlayer.as
Removed Paths:
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/osmf/player/application/

[svn:osmf:] 15093: Organizing OSMFPlayer sources in packages.

Revision: 15093
Revision: 15093
Author:   [email protected]
Date:     2010-03-29 05:32:48 -0700 (Mon, 29 Mar 2010)
Log Message:
Organizing OSMFPlayer sources in packages.
Added Paths:
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/osmf/
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/osmf/player/
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/osmf/player/application/
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/osmf/player/application/OSMFPlayer.a s
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/osmf/player/configuration/
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/osmf/player/configuration/PlayerConf iguration.as
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/osmf/player/debug/
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/osmf/player/debug/Debugger.as
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/osmf/player/debug/DebuggerElementPro xy.as
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/osmf/player/debug/DebuggerLogger.as
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/osmf/player/debug/DebuggerLoggerFact ory.as
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/osmf/player/preloader/
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/osmf/player/preloader/Preloader.as
Removed Paths:
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/Debugger.as
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/DebuggerElementProxy.as
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/DebuggerLogger.as
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/DebuggerLoggerFactory.as
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/OSMFPlayer.as
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/PlayerConfiguration.as
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/Preloader.as

[svn:osmf:] 15934: Ensure OSMFPlayer doesn' t get stuck on preloader if configuration file is not present.

Revision: 15934
Revision: 15934
Author:   [email protected]
Date:     2010-05-06 14:18:56 -0700 (Thu, 06 May 2010)
Log Message:
Ensure OSMFPlayer doesn't get stuck on preloader if configuration file is not present.
Modified Paths:
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/org/osmf/player/preloader/Preloader.as
    osmf/trunk/libs/ChromeLibrary/org/osmf/chrome/application/ChromeApplication.as

Thank you for the replies,
unfortunately it's not the router. I usually switch on/off the router if I'm not at home. Therefore I have ruled out from the very beginning the router. And I'd rule out an upgrade of arch's packages as well. I installed->upgraded all packages after a fresh installation of arch, and then I started the configuration...
ewaller, nice "How to"
Cheers
Last edited by bradomyn (2011-09-13 10:59:39)

[svn:osmf:] 14023: Updating OSMFPlayer to the changed layout APIs, adding a comment, and fixing MediaContainer from ignoring its constructor argument.

Revision: 14023
Revision: 14023
Author:   [email protected]
Date:     2010-02-07 07:54:38 -0800 (Sun, 07 Feb 2010)
Log Message:
Updating OSMFPlayer to the changed layout APIs, adding a comment, and fixing MediaContainer from ignoring its constructor argument.
Modified Paths:
    osmf/trunk/apps/samples/framework/OSMFPlayer/src/OSMFPlayer.as
    osmf/trunk/framework/OSMF/org/osmf/containers/MediaContainer.as
    osmf/trunk/framework/OSMF/org/osmf/layout/LayoutTargetSprite.as

[svn:osmf:] 13028: Fix bug where NetStream would continue playback upon completion ( due to our not handling the new STOPPED state).

Revision: 13028
Revision: 13028
Author:   [email protected]
Date:     2009-12-16 18:10:28 -0800 (Wed, 16 Dec 2009)
Log Message:
Fix bug where NetStream would continue playback upon completion (due to our not handling the new STOPPED state). Injection from trait refactoring.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/net/NetStreamPlayTrait.as

My daughter has had her Razr for about 9 months now. About two weeks ago she picked up her phone in the morning on her way to school when she noticed two cracks, both starting at the camera lens. One goes completely to the bottom and the other goes sharply to the side. She has never dropped it and me and my husband went over it with a fine tooth comb. We looked under a magnifying glass and could no find any reason for the glass to crack. Not one ding, scratch or bang. Our daughter really takes good care of her stuff, but we still wanted to make sure before we sent it in for repairs. Well we did and we got a reply from Motorola with a picture of the cracks saying this was customer abuse and that it is not covered under warranty. Even though they did not find any physical damage to back it up. Well I e-mailed them back and told them I did a little research and found pages of people having the same problems. Well I did not hear from them until I received a notice from Fed Ex that they were sending the phone back. NOT FIXED!!! I went to look up why and guess what there is no case open any more for the phone. It has been wiped clean. I put in the RMA # it comes back not found, I put in the ID #, the SN# and all comes back not found. Yet a day earlier all the info was there. I know there is a lot more people like me and all of you, but they just don't want to be bothered so they pay to have it fix, just to have it do it again. Unless they have found the problem and only fixing it on a customer pay only set up. I am furious and will not be recommending this phone to anyone. And to think I was considering this phone for my next up grade! NOT!!!!

[svn:bz-trunk] 21277: Added ds-console source to package-oem and removed copy command for datavisualization .swc which doesn't exist in the specified location.

Revision: 21277
Revision: 21277
Author:   [email protected]
Date:     2011-05-18 11:35:28 -0700 (Wed, 18 May 2011)
Log Message:
Added ds-console source to package-oem and removed copy command for datavisualization.swc which doesn't exist in the specified location. I do not find it in the most recent package-oem.zip neither
Modified Paths:
    blazeds/trunk/build.xml

Gusar wrote:No, it's not. I have actually seen cases where software rendering gave a higher glxgears score than hardware rendering (and no, it wasn't about vsync). Of course, with *actual* apps on the same machine, software rendering sucked compared to hardware rendering.
Please do not jump to conclusions and make assumptions here like 'when will people finally get it??'. I never said it was a benchmark. I have also seen many examples of where it's results do not go with conventional performance. I have a Radeon 9000 that goes faster on glxgears than a Geforce FX 5600 running Nouveau. Which is the faster card? The FX by miles. It is not a benchmark as it can not be compared between configurations. What I know is that on this individual system, from prior experience over many years when 3D acceleration is working glxgears gets between 300 and 400 fps. When it is not working it gets less than 10. That is a fact but does not mean it is benchmarkable. Yes, a Quake 3 timedemo (I have these numbers too and they very much correlate to glxgears performance for this system given just how slow it is) would be a benchmark but when it runs less than 0.1fps and even the 2D rendering means that navigating the menu is impossible, there just isn't the time to find out. Hence if playing around with drivers on this system I would use glxgears to check that 3D acceleration is working but not to benchmark. Glxinfo does not give you all this evidence.
But to clarify, I wouldn't use glxgears as a benchmark, benchmarking is different and I do a lot of that too.

Since 1.5: Multiple sources of package comments found for package

SInce I upgraded to JDK 1.5, I get these warnings
Multiple sources of package comments found for package "x.y.z"
for my package comments. Did something change for package.html content?

I already have them in the sources ...Ok, but are you sure that the Javadoc classpath option does not also point to directories with package html files?
It works without warnings, when using 1.4 ... these warnings appear since using 1.5.Yep. The Doclet interface of the Doclet API specifies a method void setRawCommentText(String text) prior to 1.5 this method did exactly what its name implies. With 1.5 the implementation was changed to generate a warning and do nothing if it was attempted to set the comment text multiple times.
What happens is this:
Javadoc sees the package.html files in the sources, creates an appropriate Doc (PackageDoc) instance and sets the comment text. Then for some reason Javadoc encounters package.html files for already existing Doc instances and tries to set the comment text a second (third, fourth, ...) time.
So, all you need to do is to ensure that Javadoc parses the package.html file for a given package only once, i.e. ensure that only sourcepath points to the package.html files but not classpath.

Javadoc: warning - Multiple sources of package comments found for package

h1. The Problem
By creating the Maven Site for our software we receive the following error messages:
javadoc: warning - Multiple sources of package comments found for package*
We use maven with maven projects containing multiple maven modules.
We have the same package names used in different modules (e.g. util-api with package util.text and util-impl with package util.text)
Package Info are created using package-info.java files.
We use maven-javadoc-plugin
A search pointed to the following old links:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5095714
http://forums.sun.com/thread.jspa?forumID=41&threadID=713300
Does anyone experience the same problem? How can it be solved?
h1. Our configuration
$ mvn -version
Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200)
Java version: 1.6.0_14
Default locale: de_CH, platform encoding: UTF-8
OS name: "linux" version: "2.6.18-92.1.1.el5" arch: "amd64" Family: "unix"
maven-javadoc-plugin version=2.6.1
no special configuration

h1. The Problem
By creating the Maven Site for our software we receive the following error messages:
javadoc: warning - Multiple sources of package comments found for package*
We use maven with maven projects containing multiple maven modules.
We have the same package names used in different modules (e.g. util-api with package util.text and util-impl with package util.text)
Package Info are created using package-info.java files.
We use maven-javadoc-plugin
A search pointed to the following old links:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5095714
http://forums.sun.com/thread.jspa?forumID=41&threadID=713300
Does anyone experience the same problem? How can it be solved?
h1. Our configuration
$ mvn -version
Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200)
Java version: 1.6.0_14
Default locale: de_CH, platform encoding: UTF-8
OS name: "linux" version: "2.6.18-92.1.1.el5" arch: "amd64" Family: "unix"
maven-javadoc-plugin version=2.6.1
no special configuration

[svn:osmf:] 15952: Attempting to fix server build ( missing source path to sample plug-in), take 2.

Revision: 15952
Revision: 15952
Author:   [email protected]
Date:     2010-05-07 10:07:24 -0700 (Fri, 07 May 2010)
Log Message:
Attempting to fix server build (missing source path to sample plug-in), take 2.
Modified Paths:
    osmf/trunk/apps/samples/framework/OSMFPlayer/OSMFPlayer-build-config.xml

Joey,
Try removing the com.apple.iCal.plist file from your Macintosh HD/Users/yourusername/Library/Preferences Folder. To find that Library folder, use Finder>Go Menu>Depress the "Option" key>Library. Drag the .plist file to your desktop.
Next, go to your Macintosh HD/Users/yourusername/Library/Calendars Folder and remove any files with "Cache" as a part of the file name. Use the same method as described above to get to the correct Library Folder.
Restart using a Safe Boot, and after the Safe Boot is complete startup normally and test Calendar for functionality.

[svn:osmf:] 15951: Attempting to fix server build ( missing source path to sample plug-in).

Revision: 15951
Revision: 15951
Author:   [email protected]
Date:     2010-05-07 09:57:57 -0700 (Fri, 07 May 2010)
Log Message:
Attempting to fix server build (missing source path to sample plug-in).
Modified Paths:
    osmf/trunk/apps/samples/framework/OSMFPlayer/OSMFPlayer-build-config.xml

Joey,
Try removing the com.apple.iCal.plist file from your Macintosh HD/Users/yourusername/Library/Preferences Folder. To find that Library folder, use Finder>Go Menu>Depress the "Option" key>Library. Drag the .plist file to your desktop.
Next, go to your Macintosh HD/Users/yourusername/Library/Calendars Folder and remove any files with "Cache" as a part of the file name. Use the same method as described above to get to the correct Library Folder.
Restart using a Safe Boot, and after the Safe Boot is complete startup normally and test Calendar for functionality.

[svn:osmf:] 14180: PARB changes: Move BinarySearch to layout package, it doesn't need to be part of the public API.

Revision: 14180
Revision: 14180
Author:   [email protected]
Date:     2010-02-15 21:52:51 -0800 (Mon, 15 Feb 2010)
Log Message:
PARB changes: Move BinarySearch to layout package, it doesn't need to be part of the public API.
Modified Paths:
    osmf/trunk/framework/OSMF/.flexLibProperties
    osmf/trunk/framework/OSMF/org/osmf/layout/LayoutRendererBase.as
Added Paths:
    osmf/trunk/framework/OSMF/org/osmf/layout/BinarySearch.as
    osmf/trunk/framework/OSMFTest/org/osmf/layout/TestBinarySearch.as
Removed Paths:
    osmf/trunk/framework/OSMF/org/osmf/utils/BinarySearch.as
    osmf/trunk/framework/OSMFTest/org/osmf/utils/TestBinarySearch.as

Revision: 14180
Revision: 14180
Author:   [email protected]
Date:     2010-02-15 21:52:51 -0800 (Mon, 15 Feb 2010)
Log Message:
PARB changes: Move BinarySearch to layout package, it doesn't need to be part of the public API.
Modified Paths:
    osmf/trunk/framework/OSMF/.flexLibProperties
    osmf/trunk/framework/OSMF/org/osmf/layout/LayoutRendererBase.as
Added Paths:
    osmf/trunk/framework/OSMF/org/osmf/layout/BinarySearch.as
    osmf/trunk/framework/OSMFTest/org/osmf/layout/TestBinarySearch.as
Removed Paths:
    osmf/trunk/framework/OSMF/org/osmf/utils/BinarySearch.as
    osmf/trunk/framework/OSMFTest/org/osmf/utils/TestBinarySearch.as

[svn:osmf:] 15867: asdocs: Update to accomodate generating OSMF for Flex 4. 0 asdocs from OSMF 1.0 source with as few changes as possible.

Revision: 15867
Revision: 15867
Author:   [email protected]
Date:     2010-05-02 19:36:51 -0700 (Sun, 02 May 2010)
Log Message:
asdocs: Update to accomodate generating OSMF for Flex 4.0 asdocs from OSMF 1.0 source with as few changes as possible.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/display/ScaleMode.as

bringrags wrote:
We do indeed recommend replacing the osmf.swc from a Flex 4 project if you're going to use OSMF in Flex 4, but you may (will?) run into issues if you attempt to use Flex's VideoPlayer within that project. Note also that you'll need to replace osmf.swc for each individual project (or edit your flex-config.xml file to point to the updated SWC).
In terms of future plans, we are working closely with the Flex team to ensure that their next release ships with the latest OSMF version. No ETA on that though.
I have followed the recommendations and removed the old version of swc and replaced it with the release version. And so far the video and audio players work fine without errors.
But looking at the flex-config.xml I see that it still points to the old version.

    <runtime-shared-library-path>
<path-element>libs/osmf.swc</path-element>
<rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.0.0.14159/osmf_flex.4.0.0.13495.swz</rsl-url>
<policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
<rsl-url>osmf_flex.4.0.0.13495.swz</rsl-url>
<policy-file-url></policy-file-url>
</runtime-shared-library-path>
Could you elaborate a little bit more on editing this part of flex-config.xml?
Thanks,
FTQuest

[svn:osmf:] 13851: OSMFPlayer: adding a nicer sample image.

Revision: 13851
Revision: 13851
Author:   [email protected]
Date:     2010-01-28 04:18:13 -0800 (Thu, 28 Jan 2010)
Log Message:
OSMFPlayer: adding a nicer sample image.
Modified Paths:
    osmf/trunk/apps/samples/framework/OSMFPlayer/html-template/index.template.html
Added Paths:
    osmf/trunk/apps/samples/framework/OSMFPlayer/html-template/images/vegetation.jpg

Hi,
You are the first person I have read so far on this forum who does not use Flex or Flash builder. I will check out FlashDevelop. It is good information to know. Thanks a lot!
-Wei Zhang
Senior Computer Scientist
Adobe Systems, Inc.
[email protected]

[svn:osmf:] 11341: Added some unit tests to get the metadata package above 80%

Revision: 11341
Author:   [email protected]
Date:     2009-10-30 16:24:35 -0700 (Fri, 30 Oct 2009)
Log Message:
Added some unit tests to get the metadata package above 80%
Modified Paths:
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/metadata/TestTemporalFacet.as

The nature of the Media class is that it accesses it asynchronously. This means that when you create an instance of it, and then immediately query it, the data you want may not be available yet. This is all in the Javadoc, see the doc for Media:
The media information is obtained asynchronously and so not necessarily available immediately after instantiation of the class. All information should however be available if the instance has been associated with a MediaPlayer and that player has transitioned to MediaPlayer.Status.READY statusSo you could associate the Media with a MediaPlayer, and then wait until it goes to the Status READY, and then read the length of the Media.
As for your 2nd question, getMetadata() returns a Map. You can just loop through it:
for(Map.Entry<String, Object> entry : media.getMetadata()) {
    // etc
}However, the same restrictions apply as with Media -- you will probably need to wait before the information is available -- that's why the Listener approach works, because it will notify you as soon as the information is added to the map.

[svn:osmf:] 15094: Organizing OSMFPlayer sources in packages continued.

Similar Messages

Maybe you are looking for