2 replies to this topic

[ViroMan]

I been thinking about how to display the available information without taking up so much space and I came up with this... tell me which you prefer.

New Concept:




Current Display:




In the second picture you can see all the available data at the same time although the price is all the space that it uses. In the first picture the data to the right it refreshed each time you click on a release. Trade of is you need to click it to see its information. Use the poll above to tell me which you like better.

Edit: I know the first picture clearly shows that the selected release is not English i just threw the longest text I could find in there when making that mockup.

[Joseph King]

It really doesn't take up that much real-estate as it is. Considering how useful this app is, I couldn't care less if it used the whole blasted screen. If I can minimise it to the Taskbar, what does the size matter.

Would changing the size make it simpler to code?

Think KISS.

Edited by Joseph King, 20 November 2011 - 11:28 PM.

[ViroMan]

Actually changing the size would take a little bit of coding. Making a GUI only takes a min or two... adding code to support gui takes a bit longer.

hmm describing the way apup2 works might be better then the long text I had. This will be equally long but should describe things better.
APUP2 is written modular:
There is the UI functions, then there is the APUP2 Engine which does all the work and is also modular, then there is the download DLL which does all the downloading.
The UI functions only tell the engine what you selected and what options you have. This is a one way transference of data to the engine. I created the UI to be separate from the engine so that a change to either will not break the other one.
The engine has links to the UI so the engine can display things if needed like with the release.list and miscellaneous text.
The engine stores data about the list and scripts in a structured nature(I will not go into detail would take a lot of text). The data is not accessable in any way to the UI at the moment due to it being kept several layers below accesability to the UI. I have to create a few functions to access that data. <-- this in itself is not so hard but, like any change needs testing.

In short... keeping it is the way it is now would be no work... making it smaller takes work. I don't mind the work though... its up to you guys if you want to change it... just remember it takes time away from me doing other things.