Homebrew [Project] SoulAnger's MENUdo

[redact]

Aww

you got the beta......lucky kid.

nah, he just gives me some bits and peices on occasion

those animations were made in the scripting prog for menudo theme making (ds based)

dunt lie!! i remember you telling me on irc you get to beta test for soulanger or something!!!!
oh wait...i think you did anyway...

trust me, never happened

he just gives me some bits and peices from some old builds of menudo

 

[Hopawarty]

Least you get some...
Its like sex...

 

[fgghjjkll]

yeah..you still get updates

 

[CannonFoddr]

Please... Please... Please, can't we have at least a Beta version

Surely menudo needs to be tested on various combo's to see if it works & what bug appear

 

[redact]

Please... Please... Please, can't we have at least a Beta version

Surely menudo needs to be tested on various combo's to see if it works & what bug appear

that's what his actual beta testrs are for ;p

 

[Dwight]

I agree, beta versions shouldn't be open. Usually they're buggy as hell and will probably cause a lot of dislike for the homebrew, because a lot of people still don't know what a beta is.

 

[Skyline969]

I still wish I could have got onto the beta testing team. I asked SoulAnger if I could, but he shot me down. Oh well, at least he was nice about it.

 

[Hopawarty]

Man.
I Test everything i can my hands on, from Dphone to windows 7.
And i love it.

 

[CannonFoddr]

Please... Please... Please, can't we have at least a Beta version

Surely menudo needs to be tested on various combo's to see if it works & what bug appear
that's what his actual beta testrs are for ;pOops sorry - What I actually meant was a 'demo', it's all very well showing videos of the 'best features' but some people like to try things out (especially me), see what's 'missing', what may need improving, see if there's anything they would like added & offer suggestions.
(Personally I would like various 'plug-ins' - you start with the very basic File launcher, but if you want to play mp3 - just add a Mp3 plugin, Read PDF ? - Add the PDF plugin etc..etc)

The one thing I really hate is Programmers/Developers THINK they know what the public what's & add sooo many features - I remember someone once said QUOTE

Only 10% know how to use 90% of [Microsoft] Word, the remaining 90% only use 10% of it

 

[redact]

The one thing I really hate is Programmers/Developers THINK they know what the public wants

but you have to take into account that the project may be tailored to the dev's tastes and is released to the public because he was kind enough to share ;p

 

[Skyline969]

The best thing to do when programming is impress yourself first. From there, you can release your program to the public. If the public's not satisfied, then they don't need to use your program. Love it or shove it, I say. Then again, if you're gonna generate a little revenue from things, you need to listen to the people. But the first step is making what you want to make.

 

[CannonFoddr]

The one thing I really hate is Programmers/Developers THINK they know what the public wants

but you have to take into account that the project may be tailored to the dev's tastes and is released to the public because he was kind enough to share ;p

OK when you say it like that - then Yes I have to agree, let the developer design the program how he what's it THEN modify it for other's suggestions

I just thought that if people can try it out & suggest what they would like to see, then the dev. can use this info to develop the program with the foresight of the additional features.

Take my idea of 'plugins' - If the dev. made the program how he liked it, as an all-in-one long piece of coding - then when people say 'I don't want this', 'there's a problem with....' or 'I would like...' then dev. has to work through the listing, rewrite parts of the program to add/remove/fix 'features' - & may even create new problems

By using plugins
- If a person don't want a function - don't install the plugin (they may only want a ROM launcher or TXT reader)
- If there's a fault with 'PDF' reading - Dev. (or someone else) only has to work on a smaller piece of code to fix it
- If someone want a feature that isn't there, perhaps THEY can create a suitable addon (take Moonshell2 & nds.YSlaunch.nds as an example)

Of course without trying the program the 'public' won't know what it can or cannot do - so no suggestions can be given
(also the fact that I am desperate for this program to come out - & hate to think this may only turn out to be 'Ghostware'

)

 

[Hopawarty]

The one thing I really hate is Programmers/Developers THINK they know what the public wants

but you have to take into account that the project may be tailored to the dev's tastes and is released to the public because he was kind enough to share ;p

OK when you say it like that - then Yes I have to agree, let the developer design the program how he what's it THEN modify it for other's suggestions

I just thought that if people can try it out & suggest what they would like to see, then the dev. can use this info to develop the program with the foresight of the additional features.

Take my idea of 'plugins' - If the dev. made the program how he liked it, as an all-in-one long piece of coding - then when people say 'I don't want this', 'there's a problem with....' or 'I would like...' then dev. has to work through the listing, rewrite parts of the program to add/remove/fix 'features' - & may even create new problems

By using plugins
- If a person don't want a function - don't install the plugin (they may only want a ROM launcher or TXT reader)
- If there's a fault with 'PDF' reading - Dev. (or someone else) only has to work on a smaller piece of code to fix it
- If someone want a feature that isn't there, perhaps THEY can create a suitable addon (take Moonshell2 & nds.YSlaunch.nds as an example)

Of course without trying the program the 'public' won't know what it can or cannot do - so no suggestions can be given
(also the fact that I am desperate for this program to come out - & hate to think this may only turn out to be 'Ghostware'

)

Yeah.
But it all comes down to what the dev thinks.
I Mean i love those developers that listen to the public, because on the iPhone App Store i've requested a function and they included it in the next release, Which makes me one happy customer.
But devs that don't listen should just quit if you ask me.

I Never know what you can get out of the public, they have some good ideas waiting to be coded.
I Made a iPod Touch 2G 'Jailbreak' Tool.
Im still coding it, with help from the public.
Help = Ideas.

Me and some guys then take it into note, i put it in the windows version, he puts in into the mac version.
And im thinking of putting in onto linux once i can compile it, i don't know python yet.
Should be easy as xPwn was compiled for linux, thats another story though.

Sharing thoughts.

 

[Matt140]

Only problem is, when your a developer public suggestions can always become either too large too be implemented, or, too hard to be added at such a late stage.

I remember one project I was working on, a newsgroup was set-up, and just before the release we had quite a few requests that were way too large.

However, I quite like the plugin idea, just might be too hard to add, probably in a next major release, Soul may add something along the lines of it.
Speaking of Soul, has something happened? Haven't seen a post in ages...
Perhaps a sign of a close, upcoming, surprise launch??

Regards,
Matt.

 

[spinal_cord]

hey
tell dem i got an injury
uhmm
his in the hospital
he got jacked up
sliced and diced
:-j

Just kidding... Soulanger is still working on MENUdo, don't worry people. Also, I recently tried another build, still very smooth, very clean. I'm not saying anything more than that.

 

[CannonFoddr]

However, I quite like the plugin idea, just might be too hard to add, probably in a next major release, Soul may add something along the lines of it.

Considering that on the DS 'plug-ins' would actually be seperate nds files - all that would be needed (in theory) would be something like :-

> Browse & Select file in 'Menudo'
> Menudo 'sees' what type of file it is (e.g. *.nds[Homebrew] / *.nds[Comercial] / *.mp3 / *.dpg etc)
> Menudo 'passes' name of file to appropiate 'Plug-in' (or *.nds file)
> 'Plug-in' starts up & runs/shows the file as needed

Seeing that no-one (other than the BETA testers & Developer) knows how Menudo actually works - we may even find out that it already works this way (or something similar)

 

[Skyline969]

However, I quite like the plugin idea, just might be too hard to add, probably in a next major release, Soul may add something along the lines of it.

Considering that on the DS 'plug-ins' would actually be seperate nds files - all that would be needed (in theory) would be something like :-

> Browse & Select file in 'Menudo'
> Menudo 'sees' what type of file it is (e.g. *.nds[Homebrew] / *.nds[Comercial] / *.mp3 / *.dpg etc)
> Menudo 'passes' name of file to appropiate 'Plug-in' (or *.nds file)
> 'Plug-in' starts up & runs/shows the file as needed

Seeing that no-one (other than the BETA testers & Developer) knows how Menudo actually works - we may even find out that it already works this way (or something similar)

Of course, if they were separate NDS files, we could use them by themselves. I had something different in mind - .dll files or something in which MENUdo reads from and executes their code. Then everything's still integrated into MENUdo itself and not other NDS files. That's more like how plugins work.

 

[ShadowEO]

0_0 My post is gone... >_>
Anyway, Great to hear that he's still working spinal_cord. Hope he keeps up the good work

Can't wait to try it when it comes out!!!

 

[CannonFoddr]

Of course, if they were separate NDS files, we could use them by themselves. I had something different in mind - .dll files or something in which MENUdo reads from and executes their code. Then everything's still integrated into MENUdo itself and not other NDS files. That's more like how plugins work.

It's depends on your point of view of how plugins work.

My POV is based on how Moonshell use/used plugins:-
> In Moonshell1 - the plugins were ordinary nds files with a slight modification to autoload a 'passed on' filename (from moonshell) - I found this out as I actually managed to get Moonshell to start up a 'plugin' for a file type that wasn't in the original moonshell setup (the only problem was that it didn't autoload the selected file)
> In Moonshell2 - the 'resetmse' files are actually nothing more than renamed 'firmware' files (e.g. renamed 'ttmenu.dat' to 'TTIO.nds') - which in themselves are nothing more than *.NDS files set up to autorun on startup anyway

Your POV seems to be based on something like 'Windows' use of DLL's - which, as you know, is a library of code that can be executed by Windows (or any other program). Usually what happens is Windows passes info to the DLL in a particular format - the DLL then runs & then 'returns' the result back to Windows, which then acts on the result

It really all boils down to SoulAnger's POV & how he thinks plug-ins should work

 

[Matt140]

Those Beta testers sure are lucky

...

Anyways, one implementation of a plug-in system would be a scripting system, choosing that option would make it easier for the public to create plug-ins without having to download a compiler, learn C, have enough skill to debug it etc. Plus, i'm guessing that, if such an option was integrated into menudo, it would need to have access to menudo's system, which could cause a hole lot of controversy in the debugging part.
But, i'm not that experienced in DS dev-ing, all i've managed to do is fill the top screen with a blue gradient

,

Regards,
Matt.