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?
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???
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.
Cheers,
Don
Show replies by thread