Permanent connection to an ArrayList

[carderne]

Say I have an ArrayList of Song objects called lib. Imagine this is my song library.

How I currently have my playlists set up, is that I have a separate Playlist object with another ArrayList of Song objects, called listSongs.
When I add songs to the playlist, it accepts an array of ints and uses this to calculate which Song objects should be duplicated in the listSongs ArrayList.

This works fine, but things get complicated when I do somethings like a delete a song form the main library, because then it has to bugger around deleting the songs from each playlist as well.

I played with keeping the playlist as an array of ints, with the ArrayList only calculated when it needs to be displayed, but this created more trouble.

Is there some way that the Playlist object can rather have a list of connections to the elements in the main lib ArrayList - shortcuts to the Song objects or something?

[xcallmejudasx]

So lib is an ArrayList of every song you have and listSongs is an ArrayList of Song objects for each Playlist object?

You could attach an ID number to to each song in lib and (as long as it's sorted) use a binary search to check if an ID in playlist exists in lib and if not remove it that way. I don't think there's any way to connect to the elements in the sense you want, and if there is, it's really only doing the same checking and deleting your doing(just behind the scenes)

[carderne]

Yes, each listSongs is an ArrayList of Song objects for each playlist.

I originally had the main lib as another listSongs ArrayList, not at all differentiated from each playlist, but although this made displaying the songs easier, it made other things more complex.

What I'm currently doing is similar to what you've said, with each song in lib having a unique ID, which is maintained when the Song object is copied into the listSongs ArrayList. Then when deleting, I check which Song objects in each ArrayList are identical to the songs that have been earmarked for deletion from lib. Your method looks more simple and efficient, so I think I'll give that a go.

I just think that it doesn't make sense to have the actual Song objecti stored in each playlist. Perhaps each Playlist could rather have an Array/ArrayList of ID numbers and then it could have a return method that would calculate, when needed, the required Song objects...

[Nicholas Jordan]

public class Loader 
{
    public static void main(String[] args)
    {
        String[] dontArgue = {"doWab","doWib","doDid","daDont","deyDo"};
        CarderneSongSampler css = new CarderneSongSampler(dontArgue);
    }
}

class CarderneSongSampler
{
    private Song_objecti[] Songs;
    public CarderneSongSampler(String[] args)
    {
        Keys = new Integer[args.length];
        int index = 0;
        for(String nextName : args)
        {
            Songs[index++] = new Song_objecti(nextName);
        }
    }
    public void main()
    {
        // ......
    }
}

class Song_objecti
{
    private String name;
    private SongData songData;
    public Song_objecti(String songName, byte[] songDataStream)
    {
        this.name = songName;
        this.songData = songDataStream;
    }
}

We can store the song data using the name of the song if the song is able to have placeholder sample data of some fashion.

[xcallmejudasx]

Yes, each listSongs is an ArrayList of Song objects for each playlist.

I originally had the main lib as another listSongs ArrayList, not at all differentiated from each playlist, but although this made displaying the songs easier, it made other things more complex.

What I'm currently doing is similar to what you've said, with each song in lib having a unique ID, which is maintained when the Song object is copied into the listSongs ArrayList. Then when deleting, I check which Song objects in each ArrayList are identical to the songs that have been earmarked for deletion from lib. Your method looks more simple and efficient, so I think I'll give that a go.

I just think that it doesn't make sense to have the actual Song objecti stored in each playlist. Perhaps each Playlist could rather have an Array/ArrayList of ID numbers and then it could have a return method that would calculate, when needed, the required Song objects...

That's correct, storing just the ID reference would speed things up a bit(search wise) and be less memory heavy, as opposed to storing the entire object.

Works the same way as Nicholas shows but instead of searching by name you search by number.

Either way a getAttribute() method of some sort will be needed because the song info should be private(so people don't change say Rick Astley - Never Gonna Give You Up ---> Francis Scott Key - The Star-Spangled Banner)

[carderne]

Thanks chaps. While I'm here, would you mind answering the followin stick question:
Is it possible to have an instance field that 'redirects' to a static field? So they are one and the same. (I will be making lots of objects of this class, but in of the objects, I want the static field and the instance field to always be the same thing...

[xcallmejudasx]

What do you mean by static field? Would that be comparable to a global variable?

instanceField = InstanceObject.getField();

say you were working with the name field.
displayName = Song.getTitle();

you can then concat things to displayName
displayName = displayName+".........";
if for some reason you wanted to do that.

Maybe I'm just not grasping what your actually asking.

[carderne]

No, this is for the List class and objects. Sorry, I don't very up to scratch with all of the nomenclature.

Here's an example of an excerpt from my List class:
private static Song[] mainSongs;
private Song[] listSongs;

Now say I make an object of this class called listFav. Then I will access the name by going:
listFav.getListSongs();
But for one object of this class, I want to access mainSongs, not listSongs. I know I can get around this with if statements, and I know what I want is quite unlikely to exist, but can I, when initializing this special object, make listSongs permanently equal to mainSongs... The static field, mainSongs, contains all of the songs in the library, and is needed for each List class to calculate which Songs it contains.

Hehe, I think I'm asking a bit much.

[xcallmejudasx]

You could set it to equal the list at the moment of initialization but it wouldn't auto update whenever mainSongs was updated unless you specifically coded it to update the other one as well.

[carderne]

Ok thanks. I thought that maybe, just maybe, there might be some sort of thingy to do it, but it doesn't matter, because I'm going to change the playlists to use an array of songIDs, rather than storing the Song objects themselves.

Rather than make another thread, I have another question which I'll ask here:
I found the javax.sound.sampled package, and I've been tying to use it, without much success so far. First off, can it play mp3 files? I don't think it can, but hopefully I'm wrong. Also, I made an AudioInputStream of a .wav file. Then I made a Clip object and used its open(
) method to open my AudioInputStream and then its loop() method to play it, and although this ran without errors, nothing played and the program terminated immediately...

How can I go about playing some music?

[xcallmejudasx]

Your probably better off starting a new thread to deal with just. Some people only read threads with headers that point to a problem they think they can help solve.

I have no idea about the sound package capabilities or AudioInputStream.

Good luck with your project

[carderne]

Point taken. SOLVED.