Closed GoogleCodeExporter closed 8 years ago
Just a quick thought-
It' be seeing a precedent - once this is working, it's not much further
developement so each folder in the tree could not only have it's own coverflow,
but have it's own custom cover, background, music, buttons even?
Also, the transition between folder levels of differing coverflows could be a
new playground for 'flow animations.
Original comment by spacepim...@gmail.com
on 12 Jun 2012 at 12:50
1 last thing!!!
3d covers in a sourceflow could have a standardised back cover at a resolution
readable in coverflow.
This could contain a template of (for example)
The emulator used
in-game screengrabs
Sound, Graphic and central processors
Sound, Graphic capabilities (4 bit stereo, 8 bit 25 fps or whatever (i really
have no idea)
Years Active, units sold
Generation e.g. 8-bit
Form Format eg handheld
aka's e.g. super famicom
Manufacturer
etc.
Original comment by spacepim...@gmail.com
on 12 Jun 2012 at 1:01
Wow, you have a big imagination. It all sounds neat but I don't have the time
to do all the recoding and coding it would take to make all of that happen. And
I'm sure the other devs will agree. WiiFlow is fine the way it is. If you
really want all that then start learning c++ so you can edit wiiflow source
code to your liking.
Original comment by fledge68
on 12 Jun 2012 at 2:29
Please forgive my speculations, i do have an active imagination. I was thinking
it could be achieved relatively simply.
The code to boot dols from a 'flow already exists with brewflow, you're booting
dols from \wiiflow\plugins rather than \apps. We just call one dol homebrew and
the other dol a plugin.
The code to display 3d covers and launch specific media associated with a cover
already exists within coverflow, you're just launching a dol instead of media,
as in brewflow.
The source menu already exists.
With regard to the additional suggestion for custom 'folders', I believe i read
somewhere, and this might be wrong, that plugins would soon have custom
backgrounds, and already have custom launch sounds and coverflows.
Differing coverflows animate between configurations already, when browsing
through them. I'm merely suggesting that the direction of swipe, as it were,
could help with moving through the interface.
It seems to me a bit of imagination is what's required.:)
Obviously, i know nothing of coding, but is it really so much more complex than
other recent and ongoing developments?
Or is it just that wiiflow's fine the way it is?
Original comment by spacepim...@gmail.com
on 12 Jun 2012 at 3:24
Just a quick adjustment to the request really, and these assume that such
manipulations are already bread and butter to coverflow. Can i suggest that the
sourceflow appears from behind the user, as the coverflow disappears into this
distance. Likewise, when selecting a source via source flow, the coverflow
expands from an infinate point in the distance as the source flow disappears to
a point behind the user.
The idea is that, when used in conjunction with roulette scrolling, the user
has a sense that they are moving in a 3rd dimension, between the surfaces.
These surfaces they can then scroll in 2 dimensions.
Original comment by spacepim...@gmail.com
on 21 Jun 2012 at 2:36
[deleted comment]
[deleted comment]
keeping it simple is best and I'm only commenting on one thing at a time lol. I
like the idea of 3D icons of the consoles themselves that we scroll through
just like covers for Wii/GC games. We click on a console it takes us to the
games and we continue "Flowing" through game views, if not then a cover for the
console itself. The covers could have icons already used in WiiFlow or new
fanart w/fullcovers that have a synopsis on the back, I would be pleased, as
long as the 'Flow' is maintained it feels consistent,neat and part of a whole
experience. Even something similar to the hombrew view with console icons would
be cool.
Original comment by MassiveR...@gmail.com
on 4 Jul 2012 at 12:26
Original comment by fix94.1
on 19 Aug 2012 at 10:10
Original comment by fix94.1
on 19 Oct 2013 at 8:37
Original issue reported on code.google.com by
spacepim...@gmail.com
on 12 Jun 2012 at 12:21