Очередная реплика Глазмана:
Since the future of Nvu is Mozilla Composer that will be the basis of
Nvu 2.0, I definitely recommend irc://irc.mozilla.org#composer as the
best spot for discussion on Nvu.
Итак, Nvu не умер и даже будет 2.0... Гм...
Отсутствует
Еще цитата:
I have spent a few cycles on number 2 user feedback about Nvu and Composer : xulrunner-based Mozilla Composer will allow to switch between two documents' source without forcing to go back to normal view :-)
Дожить бы...
Отсутствует
Почитайте вот это - http://www.glazman.org/weblog/dotclear/index.php?2006/09/15/2074-kompozer
Весьма познавательное чтиво.
Глазман забросил Nvu, но ему не нравится что кто-то им теперь занимается... Мда...
Отсутствует
Glazman чего-то изредка говорил и обещал с момента выхода NVU 1.0, но ни одного бага не исправил и другим не давал. Теперь когда чувак Kaze хорошо ли плохо ли, но чего то стал делать - проснулась жаба. А KompoZer - вещь достойная - пару багов только исправить - люди пользуются и радуются.
Отсутствует
Nvu - Glazblog
http://glazman.org/weblog/dotclear/index.php?Nvu
Thursday 7 December 2006
How active is the Composer project?
Well, it's active ; I spend most of my days on it, a colleague here at Disruptive Innovations is also implementing new features for it, and a few companies have knocked on our door to sponsor it (note to sponsor candidates : please contact us directly, phone is best). A few other people are already working on features or even extensions to Composer. The Mozilla Foundations (Frank Hecker to name him) is actively helping us in our quest for a new name for the project. It is alive and well alive.
What language(s) is Composer implemented in? Is it all C/C++, or is there a higher-level scripting interface also available? I don't suppose there's a Python wrapper?
It's based on trunk's xulrunner. I think our code additions to the core will represent roughly 20% of the new code, 80% being chrome (xul, js, xbl, css, ...). No, no python wrapper at this time butr that's a neat suggestion.
Is there a home page for the Composer project, separate from SeaMonkey?
Not yet.
Do I need to check out all of the SeaMonkey source to compile and program Composer, or can it be checked out as a more self-contained project?
the latter.
What's the best way to start learning the internals? Just check out the source, is there a better way?
for the time being, yes, the source... I'll document later, I prefer focusing on the code for the time being. Sorry, we're only humans and have limited resources ; in that case, doc is always the part of the project that suffers, unfortunately...
Отсутствует
Отсутствует
Почитайте вот это - http://www.glazman.org/weblog/dotclear/index.php?2006/09/15/2074-kompozer
Весьма познавательное чтиво.
Глазман забросил Nvu, но ему не нравится что кто-то им теперь занимается... Мда...
Нет чтобы скооперироваться с этим человеком, нет, лучше его критиковать и еще намекать про копирайты
Свобода только тут - mozilla@conference.jabber.ru
Отсутствует