Create a plan to move KendoUI from alpha to beta

[adriatic]

Assuming that the currently defined selection of KendoUI controls we want to aureliaize is complete, we still have 32 controls to do.

Then given Rob's most recent assessment:

combined with our common vision we are doing it to help aurelia become what we all expect it to be (apology if it sounds too corny), we should re-verify our current plan and revise it if necessary to get to the Beta quickly maintaining the quality level.

Folks with most experience in writing wrappers (I am on the bottom of the totem pole) should pick some of the most impressive remaining controls (Spreadsheet, Diagram, Calendar, Scheduler, Gantt) and get them going.

Please state your preferences

[adriatic]

There is a different approach possible as the alternative to "each grab a KendoUI control and turn it into the matching Aurelia component". We could create a serial "production line" which starts with the definition of all bindables for a given KendoUI control and ends with implementation of a catalog page for the resulting Aurelia component -- and then "loop" over all remaining KendoUI controls.

This approach takes in account the "specific knowledge" of team members and might easily result with better productivity and higher quality.

[JeroenVinke]

Instead of doing a big-bang update with all the wrappers, I favor a more incremental approach. I propose we finish the 0.2.0 milestone and then work from there. Features (such as #269, #268, #263) are just as important as new wrappers IMO and we should release those rather sooner than later.

[Thanood]

I guess as a non-kendo person I can't do very much here. But what about the catalog app itself?

For instance the project-status - which, as @adriatic mentioned, could be used as an overview in the future.

I changed it into a repeated list of cards (is there a kendo equivalent? Bootstrap has cards anyway), getting its contents from a js object - which may also be enhanced in the future if it makes sense.

I could "backport" that if you want me to. I know it's not much but the app is already good as it is, so there's that. :smile:

Of course, I could also test the current catalog app.

[adriatic]

@JeroenVinke writes:

I propose we finish the 0.2.0 milestone and then work from there

Starting this issue [Create a plan to move KendoUI from alpha to beta] was a bad idea as I was not aware of 0.2.0 milestone being defined (shame on me :-)).

Since @JeroenVinke has the best understanding of the KendoUI bridge status, let's just follow his lead

[adriatic]

@Thanood writes

For instance the project-status - which, as @adriatic mentioned, could be used as an overview in the future.

I propose to put more focus on "wrapping" than presenting the wrapped things - it seems that we did more than good enough job packaging KendoUI bridge in a nice dress (based on some comments to Rob's blog on Aurelia KendoUI)

[JeroenVinke]

Just to explain, we now have 2 branches: master and 0.2.0. The master branch contains the code for the 0.1.2 version. We're developing everything of the 0.2.0 milestone in the 0.2.0 branch.

That way, when we need to quickly create a patch for the "0.1.x" version, we can just create that from master. When the milestone is finished, we merge the 0.2.0 branch into the master branch.

[adriatic]

Thank you for the explanation. Good plan.