[forms-devel] Review Announcement: SE-0002: Additional EventArgs On PoppedToRoot
jason.smith at xamarin.com
Fri Jun 3 19:30:16 UTC 2016
If by EOD today there are no objections, I will approve the spec and you
can move onto implementation :)
Though now that you mention it, PoppedToRootEventArgs is both more concise
and equally descriptive... Something we can catch in code pull review
anyway since that changes nothing about the implementation which is what we
are primarily concerned with here.
On Fri, Jun 3, 2016 at 11:09 AM, <johan.kson at gmail.com> wrote:
> Good news to me! Do you want me to prep a pull request or do you want to
> implement it yourself? Is the naming of the event args class satisfactory
> for example?
> // Johan
> Skickat från min iPhone
> 3 juni 2016 kl. 19:17 skrev Jason Smith <jason.smith at xamarin.com>:
> I find no particular issue for this change other than it being a
> completely hidden API. Users who know about it can use it, but there is
> nothing which would enable a new user to find it. In the future, if we ever
> can (currently not looking likely), we could then change the event
> signature to expose the new event args.
> Unless objections are raised, I am going to approve this review.
> On Wed, Jun 1, 2016 at 10:42 AM, Jason Smith <jason.smith at xamarin.com>
>> Hello Xamarin community,
>> The review of "Additional EventArgs On PoppedToRoot" begins now and runs
>> through June 3, 2016. The proposal is available here:
>> Reviews are an important part of the Xamarin evolution process. All
>> reviews should be sent to the xamarin-evolution mailing list at
>> or, if you would like to keep your feedback private, directly to the
>> review manager. When replying, please try to keep the proposal link at the
>> top of the message:
>> Proposal link:
>> Reply text
>> Other replies
>> What goes into a review?
>> The goal of the review process is to improve the proposal under review
>> through constructive criticism and, eventually, determine the direction of
>> Xamarin. When writing your review, here are some questions you might want
>> to answer in your review:
>> - What is your evaluation of the proposal?
>> - Is the problem being addressed significant enough to warrant a
>> change to Xamarin?
>> - Does this proposal fit well with the feel and direction of Xamarin?
>> - If you have used other languages or libraries with a similar
>> feature, how do you feel that this proposal compares to those?
>> - How much effort did you put into your review? A glance, a quick
>> reading, or an in-depth study?
>> More information about the Xamarin evolution process is available at
>> Thank you,
>> -Jason Smith
>> Review Manager
> forms-devel mailing list
> forms-devel at lists.xamarin.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the forms-devel