Excerpts from Don Zickus's message of 2017-05-22 17:08 -04:00: > Hi Dan, > > A recurring theme we seem to encounter when working through various features > we want to implement in beaker, is the challenges the front-end poses to add > code. It isn't just a straight-forward add code (once you understand the > technology), but there is an added bonus of understanding the strange quirks > the legacy code is laying upon the current code. :-) But you already know > that. :-) > > > I wanted to reach out and understand what the initial thoughts were to > migrate away from the legacy stuff. Obviously your team made an initial > effort and stopped. And there is still plenty of work to be done. Was a > process to move forward ever documented?
Well, we never stopped (up until this year I mean). About 75% of the TurboGears code has been ported to Flask + Backbone. Our process was that whenever we needed to add a new feature or make substantial changes in a TG widget, we would first port it to Flask + Backbone and then fix/improve it. But you are right there are plenty of pieces unported (systems grid is the last problematic one). Beaker's UI is huge. > Granted things are a little bit better now that we understand how to > run the > server in developer mode better and have the corresponding lengthy > dependencies installed. But I still struggle just to convert one page to > strictly flask and still involves using kid files to pass back to > cherrypy??? Well once a whole page is ported over there will be no CherryPy stuff left. Just a shell of a Kid template to emit JSON and a Backbone widget (and those can go away once master.kid is not needed). But you are probably thinking of the system page, which is still a mixture of TG and Backbone widgets. Bear in mind it is by far the biggest single page, containing I think 10 independent tabs and many widgets. Of those only 3 are not yet ported. So long as there are TG widgets left on it, the outermost rendering for that page is still done in CherryPy. > With all the changing technology out there, it would be nice to have > beaker > be updated easily to match our needs. So I was trying to wrap my head > around an easy process to migrate things to a better place. It would be nice... There is no easy process except to start rewriting. Now you can probably appreciate when people said "why does it take you guys so long to churn out Beaker features? why haven't you done mine yet?" it's not because the three of us were just sitting around twiddling our thumbs. :-) -- Dan Callaghan <dcall...@redhat.com> Senior Software Engineer, Products & Technologies Operations Red Hat
signature.asc
Description: PGP signature
_______________________________________________ Beaker-devel mailing list -- beaker-devel@lists.fedorahosted.org To unsubscribe send an email to beaker-devel-le...@lists.fedorahosted.org
