How is BETA4?

beta4 seems to work ok for me... great job...
i've made a solution for this #659234: Can 1 Pixel Out be set to non-minimized? could you please take a look

is it ok for you if i try to make a clean, working onepixelout v2? i've seen the bugs concerning the 1 Pixel Out MP3 Player and now i'm working on solving a few of them...

this community helped me a lot, now it's time for me to help others, i'm not an experienced drupal developer... but i think that with a little help and a few hints i can do my job.

so should i work on this, or are you on the point of finishing them yourself?

ups... my mistake most of the features are there... i'll check and make some patches if i find anything...

thank you for the response.

added a player map in the collor section for "WordPress audio"

attached a png and patch a file

i've seen that transparentpagebg and pagebg variables for the 'wordpress audio' player don't affect the transparency/colour of the player background... regardless of what value wmode has if wmode is not set to transparent... i've tried making these variables work directly on a clean html file, but it did not work for me, probably it's a bug in the player.

i think that these hints in the admin area could be useful for those who never used this module before.

  // add hints after this section inside swftools_wpaudio_profile_form()
  // See if colorpicker 2 is loaded
  //$can_pick = function_exists('colorpicker_2_or_later');

  // Add hints
  $hints = array();

  // install colorpicker hint
  if (!$can_pick){
    $hints[] = t('Install !colorpicker module in order to have a colorpicker in the color forms.', array('!colorpicker' => l(t('Colorpicker'), 'http://drupal.org/project/colorpicker', $options = array())));
  }

  // temporary hint, until the player transparency/color is solved
  $params = variable_get('swftools_params', FALSE);
  if ($params['wmode']!='transparent'){
    $hints[] = t('You can set !wmode to transparent in order to have a transparent background for all of your swf files. Ex: use the player with a collored theme. Or you cans set !bgcolor to match your requirements.', array('!wmode' => l(t('Window mode (wmode)'), 'admin/settings/swftools/embed'), '!bgcolor' => l(t('Background color (bgcolor)'), 'admin/settings/swftools/embed')));
  }


  if ($hints){
    $form['swftools_wpaudio']['hints'] = array(
        '#type' => 'item',
        '#title' => t('Hints'),
        '#value' => theme_item_list($hints,'','ul'),
      );
  }

If it is ok for you... i would like to make some links in the $tabs area... so that it would be easier to navigate between the pages of the swftools modules. just like the links that all other useful/great modules have.

P.S. I did not add a second patch because i'm not sure how multiple patches should be made/applied.
P.S.2 thank you for the module :D

Edit: made a little modification... sorry, not a native english speaker here

here is another update, cleaned up the theme_swftools_wpaudio_accessible function

function theme_swftools_wpaudio_accessible($id, $visible) {
  $actions = array();
  
  // Note the class names - this is what lets the JavaScript determine what to attach to, and with what action
  $lClass = $visible ? '' : 'swftools-accessible-hidden';
  $pClass = 'wpaudio-accessible-open-'.$id;
  $sClass = 'wpaudio-accessible-close-'.$id;
  
  $actions[] = l(t('Play'), '', array('fragment' => ' ', 'external' => TRUE, 'attributes' => array('class' => $pClass)));
  $actions[] = l(t('Stop'), '', array('fragment' => ' ', 'external' => TRUE, 'attributes' => array('class' => $sClass)));

  // Convert the actions array to a themed list of items.
  $output = theme_item_list($actions,'','ul',array('class' => $lClass));
  
  return $output;
}

I hope i'm not only giving you more work... hope this helps.

P.S do you have certain plans, guides for the module... did you make a list somewhere? so that i can help you progress with your work?

I want to read this before I do anything else... and beside that I have some work to do, but I will study your module... and I promise to help you with it...

regards, walter

Stuart, I would like to help with the issue cue since it's a long list...

I would like to know a few things:

• are you planning a future release for the 2.x branch, and if not... do you want people switch to 3.x?
• what about drupal5...
• what about issues of 2.x that have been fixed in 3.x, do you want to mark them as closed?

I would like to start working on those... and let you do your job, developing/improving these great modules.

EDIT: just read this

Upgraded to BETA4 (on a dev computer, not production) today and cannot get it to perform correctly.

I often get this error:
The combination of flowplayer3_mediaplayer with video is not valid. Check that the player is available and that it supports the requested action.

... where sometimes the video plays(1).

Or the famous: “You are missing some Flash content that should appear here! …”.

I tried to use the same settings as SWF Tools 6.x-2.5, but still have problems.

(1) I noticed that some JS were not loading when the video was displayed. But upgrading to swftools 6.x-3.x-dev (april 24) solved that issue.

I will try to uninstall SWF Tools completely (by using the uninstall tab) and reinstall again.

So far moving to BETA4 does not work for me.

Note: I am also using Flash Node on this site.

I found out the fix for this error:

The combination of flowplayer3_mediaplayer with video is not valid. Check that the player is available and that it supports the requested action.

The old version of my [swf] tag specified a player attribute -> player="flowplayer3_mediaplayer"

Removing this attribute resolved the issue.

So upgrading would require using basic [swf] tags if not working the first time.

Beta4 should indeed be replaced by a new release as soon as possible.

I now updated a production site (oh no!!!) to 6.x-3.x-dev (april 29) without a single error messsage or hitch. I just needed to reconfigure the player and colours. Even the player="flowplayer3_mediaplayer" filter attribute does not fire any error.

As soon as a new release is made available, though, I will return the production site to releases instead of dev.

Isn't the OnePixelOut Player and WPAudio Player modules the same? Why have both?

Fair enough.

I am pointing to the showcase: http://www.dbn.ca/en/dcmontreal2009

BTW, I tested out playlist as well and I am a bit sad that we need to press play again at the end of each clip.

I had to disable autoplay because sometimes I need to display many videos in a single view, samewise, I learned that most people prefer to press Play.

OK, I'm just about to give up on this module.... 5 hours and I got just about nowhere.

The only thing i can get working is for the video file to show on a node via a CCK field, but with no play/pause button and no controls. I tried all the tricks i could find on Druapl/Flow player threads , renamed the controls swf file. nothing works!

Also, where i do print swf() i get: "You are missing some Flash content that should appear here! Perhaps your browser cannot display it, or maybe it did not initialize correctly."

I don't mean to sound ungrateful but I've just wasted half a day on this and it's been frustration all the way. what a shame :(

Hi Stuart,
Yes i did check the status page, the animation is working and everything else is marked in green.
I will try your other suggestions and report back.
I understand that this module is a complex one making use of 3rd party software etc... Hopefully, we'll be able to get it to work. I really appreciate your willingness to help me (as well as all the great work you've been doing with this module)!

I've had a couple of issues

1. If i use the default embed technique my flashnodes don't work because things like '&' and ',' which I use in my flash vars and flash var strings respectively get encoded into things flash doesn't recognise.

2. I then used SWFObject2 to place content, this time all my variables go through fine but the load fails (It spits out the you cannot view this sites flash content message) if the $scripts variable is printed at the end of page.tpl.php before $closure kind of like the other bug report from an earlier version (http://drupal.org/node/524944) ...

I'm using beta4 for SWFObject2's autoinstall which works great!