Dear all,

I am new to Yi and like the Haskell extensibility very much! I have
been using xmonad for a while and Yi looks like an editor *of the same
kind*. However one thing bothers me a little bit: It seems that Yi
heavily uses Data.Prototype in various places (for example color
themes), but I haven't seen the part of the code in Yi that we really
need the full power of Prototype. That is, I feel the existing usage
of Prototype can be replaced by records and typeclasses together. I
saw the blog post at
http://yi-editor.blogspot.com/2008/12/prototypes-encoding-oo-style.html
but that particular example can be achieved by typeclasses too.

To me, typeclass seems more Haskell-ish and I would like to stick to
that if possible. Two technical downsides of Prototype are that we
need to define all kinds of accessors, and that I am afraid it will be
slightly less efficient. I would like to understand if there are
reasons that we need Prototype. To clarify: I am fine with Prototype
as long as there's a usage for which typeclasses and records are
simply too awkward. It's very likely that I, as a beginner, overlooked
some important code in Yi. :-)

Thanks,
Favonia

-- 
Yi development mailing list
[email protected]
http://groups.google.com/group/yi-devel

Reply via email to