carlosrovira commented on issue #649: Externs warning URL: https://github.com/apache/royale-asjs/issues/649#issuecomment-570555646 > If in Maven distribution build you will not add all of that - how IDE will know that something is available ? That's for me a problem for IDEs. I remember to talk with Josh about it, and determined it could be good to solve some day. Lets say I'm using Jewel in an app, and don't want to have Basic, MDL, MX, Spark, CreateJS, JQuery,...(lots of not required libs). Right now, if you write `Bu` and make code intelligence show to add the proper `Button` class you'll find with lots of button classes available, but you know that you just want the Jewel one. Then you need to read each one until you find the Jewel Button and hit enter. I think that's bad user experience for a developer. I expect to have a royale config someday for Jewel that removes CreateJS, MDL, MX and SPARK (when MXRPC will be separated from visual components). I'll not be able to do that for BASIC, since is mixed with the rest of foundation classes, so I'll have at least 2 Button options, but will remove lots of unwanted options I'll never use. And moreover, will never have the mistake of using a class in a library by mistake that could pull other unwanted dependencies. @aharui talk about this just few days ago in other thread about the danger of this (I think it was in the thread about abstraction of platform specifics patterns). I don't see any benefits on having lots of libraries we don't use to be processed by build tools or IDEs, nothing but confuse the user, make the processing times longer and make the user (many of them not as experts as others) adding classes with similar definitions to their apps and pull other unwanted definitions in doing that. just my 2.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
