requirements

I've had apps denied in the past for not specifying in the plist or something that the app will ONLY run properly on devices with 3g or devices with a compass, or with texting, etc. How do I specify that my app will ONLY run properly with devices that have a front camera (like Skype would have had to do) Thanks! If you want your app to be used only on devices that have a front camera, then you can specify that by adding front-facing-camera to the app required capabilities . However, if the app has enough functionality when running on devices with no front facing camera, then it is probably

I'm trying to find the best pragmatic approach to import functions on the fly... let me explain. Say I have a directory called functions which has these files: array_select.func.php stat_mediam.func.php stat_mean.func.php ..... I would like to: load each individual file (which has a function defined inside) and use it just like an internal php function.. such as array_pop(), array_shift(), etc. Once I stumbled on a tutorial (which I can't find again now) that compiled user defined functions as part of a PHP installation.. Although that's not a very good solution because on shared/reseller

The addEventListener DOM method supports a third optional, boolean parameter (useCapture) to indicate whether the function should use event bubbling or event capturing as propagation method. In this article the difference is nicely shown (click on the examples & view code). From other questions on SO and blog posts, I concluded event bubbling was preferred mostly because IE8- didn't support it. Suppose I'm only required to support IE9+, in what situation would event capturing be necessary or preferred over event bubbling? In other words, in what situation would it be better to let the events

Is there a formal language which can be used to capture the information present in an UML sequence diagram in to a text format, which is easy understandable by humans? In our place, often times software requirements are specified in terms of complex sequence diagrams which are difficult to review, verify for correctness and make changes. Also IMHO, programmers would prefer to implement from an unambiguous text representation of the requirements, rather than from sprawling multi page diagrams. xmojmr (1) Yes , there is a proprietary almost formal text format language able to express information