Hi Eric, IUP is extremely healthy the way it is now, so protecting IUP's health is the more important of all things to consider. Please, IUP developers, do not let IUP go the way of Microsoft or GTK+ or Firefox. They had thee winning formula; a product that worked great and everybody loved, and then they went out and threw it all away for something "new" and "better" and "more healthy", but in reality they ruined their products. The moral of the story here is, don't let the dream anyone speaks of turn IUP into a nightmare. Let's keep it realistic, practical, readable, maintainable, and modular -- like it is now -- and drop the dream if it would affect the health of IUP in any of those regards. I am perfectly happy with IUP not being available on iOS or Android. That would never affect my choice of IUP because IUP is still the best portable user interface out there for Windows and Linux.
Talking about the different specific event loops is like talking about apples and oranges. iOS and IUP work on two completely different event paradigms. It would require a rework of IUP base code to handle or convert two completely different methods of handling events, and by definition that would make it a kludge. Could you get a beginner programmer to understand any of that song and dance routine? If you take an orange and try to turn it into an orange-apple hybrid, all you are going to get is a Frankenstein monster. You cannot port a desktop app to a iOS app. They don't remotely look or act the same. Desktops have just one main screen, whereas iOS has tiny little multiple main screens you switch between. That means you would need multiple GUIs yet only use only one IupMainLoop. I smell another kludge in the making with that one. IUP has no variable constraint functions that I know of or have seen. You set the size of a control and you're done. Unlike a desktop app, your mobile app must fill the entire screen. Modifying IUP so it would *elegantly* be resizable on-the-fly just doesn't seem to be there. This isn't something that iOS does automatically for you, it sends you a notification of the screen size at start up, and it notifies you when orientation changes, it is then up to your program to accommodate those changes with your many different GUIs screen sizes. What a horrible coding mess that would be to try and do with IUP as it is now. Most iOS programmers do not understand the difference between nil and null (and certainly no one outside of iOS would understand this at all). In iOS, a string can be null terminated but it cannot be nil terminated. The variable that defines a string can be nil or a value. If you don't handle the nil case by implicitly unwrapping or binding your optionals, your app will crash or not function. Without nil, you can make unsafe pointers and get absolutely no feedback from IUP that they are unsafe. Have fun debugging that issue within IUP. Nil is an entirely new concept from Apple that IUP and the C language does not even come close to handling natively. Like I said, make this a separate project from IUP and call it something else. Best Regards, Andrew ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Iup-users mailing list Iup-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/iup-users
