[Nitro] removed working call/answer implementation?

George Moschovitis george.moschovitis at gmail.com
Tue Nov 14 03:42:34 EST 2006

Hello Fabian,

this is a total surprise for me. I haven't thought that anyone used
this! I started coding this, but left this half-finished. In fact, I
cannot understand how this works for you. This code doesnt handle
cases like multiple windows, tabbed windows and stuff like that. It is
broken,  I am very courious how you used this.

Btw,I will release version 0.41.0 next Monday (there seem to be some
bugs in 0.40.0) I will get this back in. But, If you could provide a
working implementation it would be nice. The old implementation works
with only one window openned in the application.

sorry for the inconvienience,

On 11/13/06, Fabian Buch <fabian at fabian-buch.de> wrote:
> Sun Nov 12 21:20:48 CET 2006  George Moschovitis
> <george.moschovitis at gmail.com>
>    * Removed non-working call/answer implementation.
> George:
> Why? A few seconds before release you remove working (it's not non-
> working, it works) functionality from Nitro without asking on the ML
> whether someone is using it. Why? It wouldn't've hurt to ask and not
> either to leave it in, since it's not making other stuff of Nitro
> buggy or something.
> The implementation might not be perfect, but I used it for an Auth
> system of mine and it worked quite nice (didn't use or test deep
> stack levels though). Nitro 0.40.0 is out now and I again have to
> either use my own version of Nitro or make my Auth system more
> complicated.
> George, you're the boss, you're probably also the biggest user of
> your child "Nitro". But you are not the only user and developer.
> Could you at least ask in the future whether someone else needs a
> certain functionality before you silently remove it seconds before a
> release (ok, the night before)?
> If you think some features are badly implemented they can be
> reimplemented by someone if you tell the list (something like call/
> answer isn't that difficult) and until that's done even a partly
> buggy thing can be left in till a reimplementation in a future release.
> Fabian
> --
> Nitro Q&A: http://oxyliquit.de/
> Blog: http://blog.fabian-buch.de
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general


More information about the Nitro-general mailing list