Hi, It would nice to see Rebel reacquired and turned into a UCI, Android and iOS compatible program. The ELO does not have to be improved, just allow people to download and add it to their collection.
Thank you,
Sean
Rebel to be reacquired by Ed
Moderators: hgm, Rebel, chrisw
-
- Posts: 1777
- Joined: Thu Jun 05, 2008 10:58 pm
- Location: Canada
-
- Posts: 27810
- Joined: Fri Mar 10, 2006 10:06 am
- Location: Amsterdam
- Full name: H G Muller
Re: Rebel to be reacquired by Ed
The whole concept of an engine is incompatible with iOS, isn't it?
-
- Posts: 6340
- Joined: Mon Mar 13, 2006 2:34 pm
- Location: Acworth, GA
Re: Rebel to be reacquired by Ed
Seems so.hgm wrote:The whole concept of an engine is incompatible with iOS, isn't it?
"Good decisions come from experience, and experience comes from bad decisions."
__________________________________________________________________
Ted Summers
__________________________________________________________________
Ted Summers
-
- Posts: 1777
- Joined: Thu Jun 05, 2008 10:58 pm
- Location: Canada
Re: Rebel to be reacquired by Ed
hgm wrote:The whole concept of an engine is incompatible with iOS, isn't it?
Why?
-
- Posts: 27810
- Joined: Fri Mar 10, 2006 10:06 am
- Location: Amsterdam
- Full name: H G Muller
Re: Rebel to be reacquired by Ed
iOS does not allow one process to launch another process. So it is impossible for a GUI to fire up an engine. Both the GUI and the engine would have to be the same executable. And if you want to play engine A against engine B then A, B and the GUI would all have to be in a single executable.
-
- Posts: 144
- Joined: Fri Sep 12, 2014 4:57 am
- Location: Randwick Australia
-
- Posts: 536
- Joined: Thu Mar 09, 2006 12:53 am
Re: Rebel to be reacquired by Ed
That makes me wonder why IOS has this restriction. Is it simply a matter of policy that they don't allow this? In which case, rooting the device might allow it? Or is it matter of design that Apple deliberately chose? If that is the case, it begs the question of why they designed it that way?hgm wrote:iOS does not allow one process to launch another process. So it is impossible for a GUI to fire up an engine. Both the GUI and the engine would have to be the same executable. And if you want to play engine A against engine B then A, B and the GUI would all have to be in a single executable.
-
- Posts: 20943
- Joined: Mon Feb 27, 2006 7:30 pm
- Location: Birmingham, AL
Re: Rebel to be reacquired by Ed
Main reason, it keeps their thumb on everything. It is incredibly useful to be able to spawn a process, send it input, receive output from it, etc... And it has only been available in Unix since the 1970 time frame.royb wrote:That makes me wonder why IOS has this restriction. Is it simply a matter of policy that they don't allow this? In which case, rooting the device might allow it? Or is it matter of design that Apple deliberately chose? If that is the case, it begs the question of why they designed it that way?hgm wrote:iOS does not allow one process to launch another process. So it is impossible for a GUI to fire up an engine. Both the GUI and the engine would have to be the same executable. And if you want to play engine A against engine B then A, B and the GUI would all have to be in a single executable.
-
- Posts: 454
- Joined: Mon Nov 01, 2010 6:55 am
- Full name: Ted Wong
Re: Rebel to be reacquired by Ed
Roy, that's because there's no reason to spawn multiple processes in a mobile application. It's doggy and insecure. The kernel would need more resources to track the processes. Multi-threading works well. Rooting the device won't help because all the functions for spawning a process in the SDK have empty implementation. We can still call those functions, but they will return immediately and do nothing.royb wrote:That makes me wonder why IOS has this restriction. Is it simply a matter of policy that they don't allow this? In which case, rooting the device might allow it? Or is it matter of design that Apple deliberately chose? If that is the case, it begs the question of why they designed it that way?hgm wrote:iOS does not allow one process to launch another process. So it is impossible for a GUI to fire up an engine. Both the GUI and the engine would have to be the same executable. And if you want to play engine A against engine B then A, B and the GUI would all have to be in a single executable.
Therefore, all the unix functions able to spawn a process gets implemented in iOS like this:
void fork()
{
#ifdef IOS
// Empty implementation
#else // Eg: Mac OS-X
.... implementation code ...
#endif
}
Windows Phone is the same.
-
- Posts: 6340
- Joined: Mon Mar 13, 2006 2:34 pm
- Location: Acworth, GA
Re: Rebel to be reacquired by Ed
Now that I did not know. Been many years ago when I last used one.kinderchocolate wrote:royb wrote:That makes me wonder why IOS has this restriction. Is it simply a matter of policy that they don't allow this? In which case, rooting the device might allow it? Or is it matter of design that Apple deliberately chose? If that is the case, it begs the question of why they designed it that way?hgm wrote:iOS does not allow one process to launch another process. So it is impossible for a GUI to fire up an engine. Both the GUI and the engine would have to be the same executable. And if you want to play engine A against engine B then A, B and the GUI would all have to be in a single executable.
Windows Phone is the same.
"Good decisions come from experience, and experience comes from bad decisions."
__________________________________________________________________
Ted Summers
__________________________________________________________________
Ted Summers