While BlueGriffon, tri-licensed MPL+GPL+LGPL is already on track as a pureĬomment on attachment 424017 Ĭlearing out review request, it doesn't make sense coming from Serge and at this stage.ġ) A review request should always and only come from the developer that is planning to fix all review commentsĢ) There needs to be a clear patch of where this is to land if it's reviewed.īoth are not in place here yet. Reusable, modulo a minor changes, in any gecko-based editor, of course.īut I don't really understand why you want here a SM-based standalone editor Extensions to the "core editor tool" will be
#Kompozer mac os x mac os x#
The mac os x build will look MUCH better than Nvu on macĭespite of he recent additions to Kompozer - very nice job Fabien, congrats !. That you just cannot rewrite in another way, but the very vast majority of theĬode is totally new.
I still contains a few bits from Nvu, like helper functions The only codeĪddition to the core right now is the ftp stack, that dougt r+ recently. So we willīlueGriffon is a xulrunner-based app. To give to the evolutions of such a standalone tool at this time. We can remain rather independant from the evolutions of Firefox or Seamonkey.Īnd we _must_ remain independant because we don't have enough time or money Web editor has to be a totally independant xulrunner-app. I can predict you a ratherįast divergence between the two codebases. If that's what you want, I don't recommend it. You cannot have both at the same time, can you?ĭo you want to make (a) Semonkey composer evolve along thr Kompozer path (b)Įxtract it from the Seamonley suite (c) make a standalone app out of it sharing Isolated app Seamonkey means a set of apps bundled in the same executable. I don't understand what is a 'standalone Seamonkey' composer. > as possible with SeaMonkey, so both can profit from current developments in > standalone app, possibly rebranded, i.e. What the project here is about is basically to make a SeaMonkey Composer
0 kommentar(er)
