First off, I would like to say there are a few things which are paramount for me in any resizer library I would use. Please know these are only my observations and requirements.
1. Needs to be unlocked and editable my me. If not, then I won't even look at it. We all know the problems with MobGUI and the subsequent lack of support and stranded users. Simple fact is I just can't provide my clients with code I can't maintain. 2. It needs to be as simple and easy to maintain as possible. And in keeping with the simplicity theme, it needs to execute as fast as possible in the least amount of readable code. I'm not a fan of frontscripts and find they can get in the way in all sorts of ways, so I'd prefer staying with libraries and passing messages. 3. It should be easy to implement and without much fanfare. Most of my mobile projects need to be completed in weeks, not months, so trying to work with a complex framework just doesn't fit my projects. I certainly understand others have different timescales and may be more interested in more elaborate frameworks. 4. It needs to fit within my workflow. I use a Harness app for both Android and iOS phones and tablets which acts as a "player" for stacks, which are then downloaded via a Dropbox URL. So, it's more difficult to add lots of other files, like interface images in the bundle. I would rather bring files down from the Internet, or SpitOut them on the first run. 5. I think I can make a case that it's pretty much impossible in LC at this stage to identify dpi vs resolution needs if you're trying to go cross platform-- Android-iOS. Furthermore, as a designer, I can only imagine the possible nightmare involved in not having the exact right resolution images for different Android Layouts. I would suspect the carefully set margins and padding of one's design would get fairly screwed up. LC just doesn't work well with complex architectures and frameworks. Geometry Manager? Animation Manager? Ring any bells? 6. Lastly, if you tend to like to create skeuomorphic interface designs, as I do, then you pretty much know you have to work all your graphics out in Photoshop. So, for the most part there's no needing to worry about scalable *everything* in LC, as the images themselves scale quite well. So having a heavyweight library which tries to match each and every control attribute with the proper scaling algorithms, seems a bit overkill for me. Keeping things simpler, and lighter-- is better. For me. -- Chipp Walters CEO, Altuit, Inc. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
