Reformatted by me:
I would say no. an the reason why is.
it would take up more space in the memory.
an while it could take 1-2 hours to write a code for. those one or two hours could be to have wiiflow have it's own internet browser.( not just a plug in, but a full blown wiiflow browser).
or make it more stable, find the memory leak that's been plaguing wiiflow.
i can keep going. not to knock what your wanting to do,it does sound cool/nice. but even by your own admission, not a lot of us use source.so in my mind this would be a waste of time, that could be spent doing the other things i mentioned.
If the past developer that said "it would only take a good coder 1-2 hrs to write." . well get to coding, or is this coder saying," hey i'm not as good as i thought i was, an i can't do it."
i like the source menu with it's homebrew channel look, they might be icons,an not covers. but in all reality how long do you think people sit an watch/look at the source menu. (me when i use it, it's like 2-3 mill seconds, just long enough to get to were i'm going.) besides wiiflow already starts at a coverflow.( the last area/game you played.).
For me, i would like to see no buttons in coverflow.(i.e. settings/fav..ect.) well my be just the one, an get rid of the source menu all together. most of the other buttons can be found on other pagers. the one button i would keep is the switch button,( gc/nand/plug in.) just use that one button.
Thanks for your input, I just have a couple of corrections to make there
I have made no admission that 'not a lot of use source', on the contrary, I think the
majority of users do - just not everyone. In fact,
you use it, if only for 2-3 milliseconds(!)
I should say that the unnamed developer is a current member of the team, just isn't working on wiiflow at the moment, i'll quote directly: - "There is plenty of room for more code, the space required has nothing to do with the memory issues".
Can i ask, in reality, how long do you look at the coverflow for? If you're just picking games, why not use postloader- it's quicker? I suspect you use Wiiflow because of the visual environment it provides - that environment is not used in the 2D source menu.
I find that your assertion that a whole new browser could be programmed in 1-2 hours unlikely at best - and why would wiiflow even need one? - There's a plugin in development based on Wiibrowser, btw.
I understand that there are always going to be priorities that have to be decided upon, and people are always going to have different priorities but I would point out that I have been pushing for this for
over a year, and a lot of wiiflow development has passed in that time. This is not about an extra paint job, a cherry on the top - this is about the source menu catching up with the rest of wiiflow and finally, seamlesly fitting in.
