Alternatively, you could have Yi just be a library which front-end's link to. then, only the front-ends have binaries. no linking issues, no plugins, far simpler dependency checks, easier for people unrelated to the project to write new front ends..
cabal install yi-cocoa cabal install yi-vty etc etc. max On May 11, 2011, at 9:57 PM, Jean-Philippe Bernardy wrote: > On Wed, May 11, 2011 at 3:30 PM, <arenie...@gmail.com> wrote: >> Do you mean keeping UIs in the same package with core? > > No; they can be separate. > >> Or dropping the >> ability to select frontend on startup with cmd args? > > No. > > I am saying the configuration file can link to any number of UIs desired > (ff they are not installed they cannot be mentioned there), > and the user can pick any on the command line. > > > Specifically: > > * in Yi.Config.Default: remove availableFrontends; that way no > frontend is required by Core > * in Yi.Config: replace startFrondEnd by availableFrontends (defaults to > empty) > * in Yi.Main.getConfig: remove from the availableFrontends list all > that do not match the choice of the user. > * At the time of starting the UI, pick the 1st in the > availableFrontends; if not is available refuse to start. > > Cheers, > JP. > > -- > Yi development mailing list > yi-devel@googlegroups.com > http://groups.google.com/group/yi-devel -- Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/yi-devel
