Collectible Card Game Headquarters

I just felt like messing with the ManaSymbols and the Mana Pool:


Haven't done extensive tests, but it should place normal mana and snow mana into two columns x 6 rows (for each color).

It's definitely an improvements to see at a glance how much mana is stored. I don't care very much for the ordering.

Do you mean you don't care which order it's in, or you think it should be ordered differently?

Here's a more thorough test:

Resurrecting an old thread....

I have been trying to clean up the code base lately and see that there is a lot of code for the "old GUI". Does anyone still use that? Is everyone using the "new GUI". On the startup screen, does anyone uncheck the "Use new GUI" checkbox? If you use the old GUI, is there a feature that the new GUI is missing?

I hope to remove all of the old code so it will be easier to update the current GUI.

Thanks
Dave

I think there are still people that have trouble with the new GUI (GuiDisplay4.java), and use the old one (GuiDisplay3.java). I think it should be ok though to remove the ones that are even older.

I switched to the new GUI once the launchers were set up to increase the java heap space. Without the increase to the java heap space the new GUI became unplayable for me.

I have not used the old style GUI recently. I now only use the new GUI.

I also noticed that in the source, there are Look and Feel dependencies (napkin, nimrod and substance). They have not been included in the latest builds. Are these still needed?

I remember Snacko suggesting that the LAFs could provide some improvement to the spartan and basic default OS LAF. Dennis spent a couple of weeks adding the LAFs that he could find.

Some were buggy and caused error exceptions. Dennis removed the worst of them. The LAFs I imagine do not come with much by way of support from their authors.

Thanks for the feedback. I am in the process of removing the cloudgarden code. I will then start pruning down the old GUI code. I'll pay special attention to the heap and see if I can make any improvements in the new GUI. I'll keep the LAF's in mind but won't focus on those. For the time being I am not going to change any functionality. I am just trying to focus on making the current stuff more manageable.

At one point in the past some added the jl1.0.1.jar (?) for the purpose of having in-game sounds. People noticed some java heap space issues in reference to the HQ pics that had been recently added. The tapping sound that was added at that time may have caused additional heap space issues.

Dennis turned off or detached the sound code, can't remember which. He recently stated that the jl1.0.1.jar lib is primarily for music. I guess that this one can also go.

I'm not sure if we should add in-game sounds via another lib at some point. It is an interesting feature but most people would agree that heap space issues are more important.

Yes. The heap size is the priority. I will most likely remove all of the LAF and jl libs for the time being. They are probably out of date at best.

jendave wrote:. . . I will then start pruning down the old GUI code. I'll pay special attention to the heap and see if I can make any improvements in the new GUI. I'll keep the LAF's in mind but won't focus on those. For the time being I am not going to change any functionality. I am just trying to focus on making the current stuff more manageable.

what minimum size screen do we officially support or recommend? i tried on a 1024x600 netbook, but i couldn't read the stack or phase information. basically unplayable. i didn't consider choosing a different GUI . . .

Braids wrote:what minimum size screen do we officially support or recommend? i tried on a 1024x600 netbook, but i couldn't read the stack or phase information. basically unplayable. i didn't consider choosing a different GUI . . .

`
1024 x 768 is the minimum.

Braids wrote:what minimum size screen do we officially support or recommend? i tried on a 1024x600 netbook, but i couldn't read the stack or phase information. basically unplayable. i didn't consider choosing a different GUI . . .

There is an issue regarding sizes of Windows: http://code.google.com/p/cardforge/issues/detail?id=67 It may end up waiting until a new generation of UI is built for Forge.

Chris H. wrote:At one point in the past some added the jl1.0.1.jar (?) for the purpose of having in-game sounds. People noticed some java heap space issues in reference to the HQ pics that had been recently added. The tapping sound that was added at that time may have caused additional heap space issues.

Dennis turned off or detached the sound code, can't remember which. He recently stated that the jl1.0.1.jar lib is primarily for music. I guess that this one can also go.

I'm not sure if we should add in-game sounds via another lib at some point. It is an interesting feature but most people would agree that heap space issues are more important.

The reason the sounds were causing heap space errors was because it would create a new "MP3Player" object every single time a sound was played