lukechannings / vibe Goto Github PK

Bug in the persistence module but only reproducible in IE. Steps:

1. Drag two items from the collection to the playlist.
2. Clear the playlist.
3. Drag another item from the collection to the playlist.
4. Reload the browser.

The playlist should be redrawn with only the n playlist branch, instead it is drawn with n and n-1 branches.

Dragging the same item into the playlist multiple times causes the duration of the playlist to be incremented, but the item is not duplicated in the playlist. This is caused by the caching of the playlist items in the UIPlaylist.

There are a few issues with the playlist model and UI synchronisation, for example items to the playlist using "play next" does not work in some circumstances.

Removing items from the playlist when sparsely selected results in an error being thrown, this may be a result of not caching the elements, or referring to them by their numerical indexes rather than their object references.

A more extensive bug hunt needs to be performed for v0.1.2.

After the client is configured to connect to a Vibe Server it should load the UI. A bug prevents this from happening and a reload must occur before this can happen.

FireFox stops playing music when the settings pane is opened. Probably something to do with Flash and the embedded object having to be visible.

Need a better way of managing the linking of stylesheets that works with the following:

• requirejs loaded callback
• r.js optimisations (preferably essential stylesheets should inject <style>)

This may not be technically viable or may perhaps be hard to implement because
browsers do not emit events when a stylesheet is loaded. Try to adapt util.registerStylesheet
to be a requirejs module, optional dependencies are a higher concern.

The ModalDialogue module does not render at all in Opera 12. The ModalDialogueOverlay does not get appended to the body, further investigation necessary, the guess would be that document.body was not available at the point at which the overlay is appended. However, no error is thrown, which makes that theory unlikely.

When an item is moved in a RearrangeableList, the change event should be handled and the change should be reflected in the UndoManager instance. The change will be committed in the UndoManager instance without creating more than one new version.

In certain circumstances the Playlist Info has the incorrect duration time for the playlist. See: http://cl.ly/I6Hv. Needs to be fixed and a unit test should be created for the expandTime method.

The UIPlayerVolume module will implement an interface for controlling the currentSound's volume property. The interface will be in the form of a slider, and will use the DragDealer dependency, the same as UIPlayerSlider uses.

Add context menus for the collection and playlist allowing a right-click
context menu to appear and the following options be presented:

Collection:

• Add to collection
• Play next

Playlist:

• Remove

Grey out undo and redo buttons when there is no respective operation to perform.
Apply the disabled CSS class to each button when there is no possibility to undo or redo, this helps to avoid confusion. Also, perhaps an icon redesign is needed?

On Firefox, Drag and Drop doesnt work on the playlist. So if you try to rearrange the list items (songs) on the Playlist, by dragging your favourite to the top for example, it doesnt work. However it does work on Google Chrome, but NOT on Firefox.

Drag and Drop does not function in Opera. The elements are draggable, but the Playlist is not a valid drop area, further investigation needed. Suggest a rewrite of Drag and Drop usage with reworked drop zone support.

Keyboard controls can be useful, I was thinking:

• space : play / pause the current track
• up / down arrows : playlist selection up and down
• enter : play selected playlist item
• alt up / alt down : volume up and down
• left / right : seek to new position

This will probably make it before the VibeServer rewrite, probably for v0.1.2.

Refactor and reimplement updateInfo method of the ModelPlaylist Object Prototype. The updateInfo triggers proved to be unreliable in built versions of Vibe, indicating further issues with EventEmitter. All triggers for updateInfo have been stripped out in the latest branch until this issue is solved.

In a playlist, the natural progression of the track playing causes the playing info element to be hidden.