Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Nicolas Pouillard <nicolas.pouillard@gmail.com>
To: William Morgan <wmorgan-sup@masanjin.net>,
	sup-talk@rubyforge.org, sup-devel@rubyforge.org
Subject: Re: [sup-devel] sup v2 progress report
Date: Mon, 28 Mar 2011 05:52:52 -0700 (PDT)	[thread overview]
Message-ID: <4d9084a4.cc7e0e0a.6404.ffff8fad@mx.google.com> (raw)
In-Reply-To: <1301257195-sup-9486@masanjin.net>

On Sun, 27 Mar 2011 20:41:59 +0000, William Morgan <wmorgan-sup@masanjin.net> wrote:
> Hello all,
> 
> I'm happy to report that Sup version 2 is well underway!
> 
> Sup version 2 features:
> - a client/server model that works over HTTP, allowing
>     a) development of other clients, e.g. web-based and phone-based
>     b) simultaneous access from multiple clients
>     c) IMAP emulation, aka no more lock-in!
> - an improved console-based client
> 
> Heliotrope, the server component, is close to ready for a version 1 release.
> You can find it at https://github.com/wmorgan/heliotrope/.
> 
> The client, which I'm calling Turnsole, is coming along swimmingly. I hope to
> release a pre-alpha some-stuff-actually-works version within the next few days.
> Much of the UI code has been borrowed from Sup, but the internals are quite
> different:
> - it's event-based, rather than thread-based, which streamlines a lot of the
>   code and avoids a whole big class of bugs.
> - all the index and email threading code is ripped out
> - most of the email parsing code is gone
> - it handles Ruby 1.9 string encoding stuff correctly, rather than having
>   random checks scattered around
> 
> I think you're going to like it, since:
> - the threads are pre-computed on the server side, so it's much, much faster
> - you can finally view attachments locally!
> 
> Stay tuned for more. We're still a ways off before it's a drop-in replacement,
> but I'm excited about how everything is coming together.

While mass importing an mbox I got this:

$ ... heliotrope-add ...
; forced to decode html. running html2text on 868b mime part...
end offset is 237534473
.../heliotrope/lib/heliotrope/decoder.rb:109:in `gsub': incompatible character encodings: UTF-8 and ASCII-8BIT (Encoding::CompatibilityError)
  from .../heliotrope/lib/heliotrope/decoder.rb:109:in `decode_rfc2047'
  from .../heliotrope/lib/heliotrope/message.rb:208:in `decode_header'
  from .../heliotrope/lib/heliotrope/message.rb:30:in `parse!'
  from bin/heliotrope-add:105:in `<main>'

Best regards,

-- 
Nicolas Pouillard
http://nicolaspouillard.fr
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  parent reply	other threads:[~2011-03-28 13:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-27 20:41 William Morgan
2011-03-28  4:14 ` [sup-talk] " Matthieu Rakotojaona
2011-03-28 14:57   ` David J. Hamilton
2011-03-28 22:57   ` William Morgan
2011-03-28 12:52 ` Nicolas Pouillard [this message]
2011-03-29  3:11   ` [sup-talk] [sup-devel] " William Morgan
2011-03-29  4:00   ` William Morgan
2011-03-29 21:19     ` [sup-talk] " Nicolas Pouillard
2011-03-29 21:31       ` William Morgan
2011-03-28 14:21 ` [sup-talk] " Lincoln de Sousa
2011-03-29  3:12   ` William Morgan
2011-04-14  7:39 ` [sup-talk] [sup-devel] " Ico Doornekamp
2011-04-14  7:51 ` Ico Doornekamp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4d9084a4.cc7e0e0a.6404.ffff8fad@mx.google.com \
    --to=nicolas.pouillard@gmail.com \
    --cc=sup-devel@rubyforge.org \
    --cc=sup-talk@rubyforge.org \
    --cc=wmorgan-sup@masanjin.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox