Description of problem:
Mozilla has been deprecated and will not appear in future Cores. This will
leave the core install disks without a specific website development tool.
Formerly, Mozilla's Composer provided this functionality. I would suggest
Bluefish be moved from the repositories to the Core disks.
Version-Release number of selected component (if applicable):
Move Bluefish from "extras" repository onto core installation disks.
Webpage creation is a skill that even low-end users are capable of. It is not
a niche activity, so Bluefish should be moved to Core disks, especially if
Mozilla is removed from the installation. Using VI or Emacs is of course, an
option for website creation but is not the best-solution for low-end users and
lack the specialist features of Bluefish.
Thank you for the report.
Mozilla suite will be in the future replaced by Seamonkey which is the same code
base as the suite. Seamonkey is available as part of Fedora Extras along with
Since several other programs like Yelp and Devhelp using Mozilla suite as their
browser engine, We need to either build all these applications against Firefox
or use XULRunner which is apparently not very mature yet
More information at
Thanks for the response. I have looked at Seamonkey. So will it be moved from
Extras to the core disks? I think it is worthy of it.
Although lacking in some major features like syntax highlighting, the Composer
module does show promise.
D. Le Sage
We dont plan to move Seamonkey into Fedora Core as we already have a many
browsers and mail clients and dont want to duplicate components. If composer can
be split out as a package. it might be a good candidate for core or Nvu might be
This looks more like a comps change request. Moving to distribution.
In a post Core/Extras split world, does this matter?
Well, other than what may be in kdenetwork, we don't ship a specific HTML
editor; that being said, website development is probably left to a separate spin
that has TurboGears, RubyOnRails, PHP, and so on.