On Fri, Jun 11, 2021 at 10:13 PM Félix <[email protected]> wrote:
> Hi Edward, Hi Thomas! > > Thanks for [sumarizing] the whole of what we agreed orally on here in > this post :) > I'm glad you agree. I'll merge ekr-server-imports into devel in a few minutes. *EkR > again imo, that server should be called leoserver.py, and it should > live in leo/core.* > yes indeed, that is the plan. > This morning I was wondering why I prefer the name leoserver.py to leobridgeserver.py. The reason, I think, is that there is only ever going to be one server, so the name need not (should not?) refer to implementation strategy. Similarly, in another branch I'll probably want to change the name of the LeoBridgeIntegController class back to LeoServer. That name change should have no effect on either leoInteg or Leo itself. *EkR > I definitely want to use `@'file. * > Haha! yeah me too! I just recently realized why @file is much better when > trying to collaborate with other people in 'gitted' project! omg! (I'll > probably switch most files in leointeg to @files too pretty soon!) > Good. All future Leo devs will be using Leo, so @file much more convenient than @clean. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS2y%3DcnCm4Fo1X-47cdME%3Dh8aJbZjWdyb8ued-qwnFg%2BdA%40mail.gmail.com.
