EmuNewz Network

Full Version: Add-on Oriented or Non Add-on Oriented?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Personally, i would like to see this become an add-on oriented program that allows versatility in designing (such as one team can handle the base functioning works while another outside team collaborates to build an add-on meant for smoothing gameplay and graphics etc etc). so, the question is, whats your take? add-on oriented or non-add-on oriented?
(09-18-2010 06:44 PM)manafusion Wrote: [ -> ]Personally, i would like to see this become an add-on oriented program that allows versatility in designing (such as one team can handle the base functioning works while another outside team collaborates to build an add-on meant for smoothing gameplay and graphics etc etc). so, the question is, whats your take? add-on oriented or non-add-on oriented?

Just out of curiosity: What exactly did you contribute until now? Angry
nothing. and i seem to see that jpcsp is being update way more than pcsp. in fact, i noticed that pcsp havent been updated since last yr. so, i was thinking when i was at the pcsp official website (out of random curiosity) about this question. also, i actually am not really sure if it should be here or some other sub-forum.
Hi, sorry I was just flying over your text yesterday and I assumed you mean JPCSP. PCSP is a different thing, it is closed source and there are not that much devs that work on it. I think they choose this for a reason and you should accept their reasons. But if you think you can help them in any way you also could contact shadow via pm.
i only picked up the basics of c++ (which is pretty much considered nothing compared the knowledge that miniature c++ program dev have) though i might pick up on the full c++ programming some later day (im still studying and IT is not my major).
(09-18-2010 06:44 PM)manafusion Wrote: [ -> ]Personally, i would like to see this become an add-on oriented program that allows versatility in designing (such as one team can handle the base functioning works while another outside team collaborates to build an add-on meant for smoothing gameplay and graphics etc etc). so, the question is, whats your take? add-on oriented or non-add-on oriented?

Right now it is not an add-on oriented program. I think it will be hard to turn it this way because it means we need to make some part of emulator as libraries with the price of degradating compiler optimizations and so having a slower emulator. Besides, there are a lot of inline functions which means exposing the source to non pcsp dev team.
(09-19-2010 01:31 PM)hlide Wrote: [ -> ]Right now it is not an add-on oriented program. I think it will be hard to turn it this way because it means we need to make some part of emulator as libraries with the price of degradating compiler optimizations and so having a slower emulator. Besides, there are a lot of inline functions which means exposing the source to non pcsp dev team.

so basically, the team wouldnt want to sacrifice the concept of speed mainly designed around pcsp as compared to compatibility designed around jpcsp... am i right at this?
Let say PCSP is primarily designed with speed in mind and some current or future crafty technics not used or usable in JPCSP. To make it add-on oriented means redesigning and rewriting all the emulator, which is not top in our priority list.
ok. i understand now.
Reference URL's