It's not a "must have". I have yet to use it in any of my projects.
It can be very handy, and I am glad someone is maintaining it, but it's not required. > On 14 Nov 2015, at 06:29, Jesse <purplecabb...@gmail.com> wrote: > > Okay. I'll back down then. I thought it was a 'must have' which to me > dictates that we 'must have' a fork. > > > >> On Nov 13, 2015, at 10:46 AM, Shazron <shaz...@gmail.com> wrote: >> >> I don't agree with keyboard being in core. It's not "required" on ios, >> it's just a cosmetic change, and its pretty hacky to get right. With >> iPad and iPad Pro's new enhanced keyboards, this will be a bigger >> nightmare to maintain thus I am strongly against this. >> >> With iOS 7 and greater's flat UI, the toolbar doesn't look that bad anyway. >> >> As an example, Gmail iOS doesn't even bother trying to hide the >> toolbar. Try to do a Search on it to see the keyboard. It uses a >> WebView I believe for most of its UI. >> >> >>> On Thu, Nov 12, 2015 at 9:52 PM, Jesse <purplecabb...@gmail.com> wrote: >>> The reason I think the keyboard should be core is that it is required on >>> ios, and we are completely dependent on ionic to maintain it. The license >>> is Apache 2.0 so I think it would make the most sense for use to depend on >>> a fork of our own and ask Ionic to continue to contribute to it. >>> ( or review their future changes and pull into our branch when appropriate. >>> ) >>> >>> >>> >>> >>> >>> @purplecabbage >>> risingj.com >>> >>> On Tue, Nov 10, 2015 at 12:12 PM, Kerri Shotts <kerrisho...@gmail.com> >>> wrote: >>> >>>> Yay, the audit happened! :-) So very cool. Not sure I agree with a couple >>>> of the choices, but haven’t had the brain power to think through everything >>>> yet. >>>> >>>> If the keyboard plugin is going to remain managed by ionic, then I’d keep >>>> it out of core, honestly. To me, “core” implies Apache-managed. Installed >>>> by default, OTH, wouldn’t be a bad idea. >>>> >>>> As for native dialogs, well… personally, I’m all for doing them in >>>> HTML/CSS/JS. On the flip side, native dialogs can be a quick way to display >>>> messages or get input. That said, I don’t think it needs to be a core >>>> plugin. Perhaps spin it off into a third-party plugin and let the community >>>> step up if they see the need. >>>> >>>> @Parashuram: I have a native controls plugin for iOS. It needs some love, >>>> though, which I plan on getting to once my book is done (almost!). I know >>>> there are others out there too, but I’m not sure how many support Android. >>>> >>>> >>>> >>>> Kerri Shotts , photoKandy Studios LLC • (312) 380–1035 • (618) 435–0823 >>>> (mobile) >>>> >>>> http://www.photokandy.com/ • @photokandy • Github • CoderWall >>>> >>>> → CONFIDENTIAL ← >>>> >>>> This email and any attachments may be confidential. If you are not the >>>> intended recipient, please let us know by replying to this message, and >>>> then remove the message and its attachments from your system. You should >>>> not disseminate, distribute, or otherwise copy or release the information >>>> contained herein, nor can we accept any liability for any loss or damages >>>> resulting from the use, abuse, or mis-use of the information contained >>>> herein. >>>> >>>> → SECURITY ← >>>> >>>> Computer viruses can be distributed via email. It is the recipient’s >>>> responsibility to check this email and any attachments for viruses. Email >>>> transmission cannot be guaranteed to be secure or error-free as the email >>>> could have been intercepted, corrupted, delayed, and/or re-transmitted. The >>>> sender does not accept any liability for errors or omissions within this >>>> message or its attachments, nor for any viruses which may be present. >>>> >>>> Note: We do our very best to ensure that nothing we send contains viruses. >>>> However, because of the nature of email and the way it is sent, we can’t >>>> promise that some other party hasn’t intercepted our email and added >>>> malicious content. Due to the nature of email, we can’t accept any >>>> liability for any damage or loss arising from the use, abuse, or mis-use of >>>> this email and any of its attachments. >>>> >>>> → PRIVACY ← >>>> >>>> Email is not a secure communications medium. When replying to this or any >>>> message, you should not include any information that you do not want the >>>> entire world to be capable of seeing. In other words, don’t send financial >>>> accounts (CC#s, Bank Account #s, etc.), passwords, social security numbers, >>>> or the like, even when asked directly. photoKandy Studios LLC >>>> will never ask you for this information. >>>> >>>> Information transmitted via email may be intercepted and retransmitted by >>>> any number of other entities. This is the nature of email, and as such, we >>>> can’t be held liable for any loss or damage incurred by replying to this >>>> message with compromising information. Review your message prior to sending >>>> it, and ensure that there is no information you wouldn’t be comfortable >>>> with the entire world knowing. >>>> >>>> >>>> From: Parashuram N <panar...@microsoft.com> >>>> Reply: dev@cordova.apache.org <dev@cordova.apache.org> >>>> Date: November 10, 2015 at 11:23:17 AM >>>> To: dev@cordova.apache.org <dev@cordova.apache.org> >>>> Subject: Re: Plugin Audit 2015 >>>> >>>> I agree with Raymond on the ability to use native dialogs. I think I would >>>> like to extend it beyond dialogs, and see if it is possible to use other >>>> native controls too - like Sidebar, etc. I think they may not make sense as >>>> core plugins though. Supporting them for multiple platforms is hard. Maybe >>>> someone could come up with a list of plugins that enable native controls in >>>> Cordova apps ? >>>> >>>> >>>> >>>>> On 11/10/15, 6:25 AM, "Raymond Camden" <raymondcam...@gmail.com> wrote: >>>>> >>>>> "Globalization (make sync" >>>>> >>>>> YES, YES, YES! >>>>> >>>>> (Sorry, but that makes me *very* happy to hear!) >>>>> >>>>> "Dialogs (Should use HTML/CS/JS dialogs instead)" >>>>> >>>>> Strongly no, but I'm assuming there is a good reason for this beyond >>>>> just what is listed in the parenthesis. Yes, UI frameworks normally >>>>> have their own dialog widgets, but the fact that I can use a device >>>>> standard dialog is a big plus for me. I'll even use it over Ionic's >>>>> even when inside an Ionic app. >>>>> >>>>> >>>>> On Fri, Nov 6, 2015 at 4:53 PM, Steven Gill <stevengil...@gmail.com> >>>> wrote: >>>>>> Jesse, Simon and I spent sometime doing a plugin audit. Our >>>> recommendations >>>>>> can be found at https://github.com/cordova/cordova-discuss/pull/28 >>>>>> >>>>>> Overview: >>>> https://github.com/stevengill/cordova-discuss/blob/master/proposals/PluginsAudit2015/overview.md >>>>>> >>>>>> Please give us feedback! >>>>>> >>>>>> -Steve >>>>> >>>>> >>>>> >>>>> -- >>>> >>>>> =========================================================================== >>>>> Raymond Camden, Developer Advocate for MobileFirst at IBM >>>>> >>>>> Email : raymondcam...@gmail.com >>>>> Blog : >>>> https://na01.safelinks.protection.outlook.com/?url=www.raymondcamden.com&data=01%7c01%7cpanarasi%40microsoft.com%7cce0374c4640a4c22e3c808d2e9dad25f%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iro%2bUZtcOYBhVNRxnsRb1UXvxB%2b7NGSqQYMJXd6IdgI%3d >>>>> Twitter: raymondcamden >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org >>>>> For additional commands, e-mail: dev-h...@cordova.apache.org >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org >> For additional commands, e-mail: dev-h...@cordova.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
