DocBookCSS is a mostly-pure-CSS2 implementation of the DocBook standard.
Unlike DocBookXSL which relies on transforming the XML, it utilizes the
XML-styling features of modern web browsers to display the DocBook.
Its appearance still is a long way from the Haiku Book and Userguide, but
it looks (mostly) the same as the old DocBookXSL so we can stop using that.
Eventually we just need to make DocBookCSS use our styling.
Written by DarkWyrm, this user guide has been long since superseded by
the new HTML-based User Guide, which has everything this did and then
some, with the exception of the "History" section. That section
does seem like it could be useful somewhere, so I've moved it to
its own file in the "docs/misc" directory.
"BToolBar" matches the current convention ("BStatusBar", "BMenuBar", etc.)
I've no idea what I was thinking when I renamed this before...
Also adjust all users of BToolBar (Tracker and ShowImage).
* It no longer has consistent naming across architectures, as it's
now GCC4-only.
* It hasn't been in the default images for that reason since that change
was made a few months ago, and nobody has missed it.
* Only a few pieces of software use it at this point, so those who need
it can simply run "pkgman install cmd:cmake".
All of the other .dox files here list authors at the top of the file
in a standard (non-Doxygen) comment, so do the same here.
I've listed the file as copyright 2011, as (according to Git) that's
the last time it was functionally changed. I also added a few people
in as being authors of the file who seem to have made significant
changes to it.
* Remove references to outdated stuff (OsDrawer, old OpenGrok)
* Removed GitHub as a code search option (not nearly as flexible
as OpenGrok, and updated bi-monthly or so instead of daily.)
* General reorganization.
Fixes#11842.
I didn't add the gdb package to the bundled packages because AFAIK,
most users / developers of Haiku use our built-in Debugger instead,
because it's so much more awesome (thanks, Ingo & Rene!).
If I'm somehow mistaken about that, please don't hesitate to speak
up and I'll add it.
The "header" in this case is just the MIME type and content size, but we
must still send the notification when these are available. It will be
used for example in WebKit next release.
* Put getlimits and kill back in the image, the former is not provided
by coreutils, Haiku provides an updated version of the latter.
* frcode is not provided by either coreutils or Haiku and has been
removed, do we need it?
* Since coreutils is now a mandatory package, add it to the REQUIRES
of all the Haiku packages, otherwise system updates will be broken.
* Adapt the other (arm, m68k, ppc) package_infos as well.
Signed-off-by: John Scipione <jscipione@gmail.com>
* NeedsToRebuild() didn't actually do anything, as this
returns whether it needs to be rebuilt or not.
* Replaced RemoveItems() with ForceRebuild(), which should
already delete the menu items, whilst additionally
letting the leaf menu know that it needs to rebuild itself.
This bug was reproducible 100%; however, with this fix, there
is now a rare race condition where clicking between an app menu
and the leaf menu will result in both menus showing concurrently.
* this is a mandatory package.
* removed related commands from the minimum image definition.
* removed related commands from the Haiku package PROVIDES.
* the su command is deprecated in 8.22. Use the 8.4 in-tree version.
* the packages contain and provide the df command, to be removed.
This reverts commit 31ea76548a.
Adrien, please try again without clobbering the otherwise nice
BNetworkInterface API!
Conflicts:
src/kits/network/getifaddrs.cpp