* Moved setting the default cursor from ServerScreen to Desktop
* Getting the default cursor is now done using the CursorManager
* Removed outdated setcursor from SysCursor.cpp (we have a new implementation by now)
* Renamed SysCursor.cpp to CursorSet.cpp as that's what it is
* Moved headers/private/app/SysCursor.h to headers/private/servers/app/CursorSet.h
* Removed some unneeded header includes along the way
There remains {set|get}_syscursor now in CursorSet.cpp. Serverside for these are not implemented
and they are obvious hacks. Do we need to keep them?
Also this commit _would_ break Appearance, but 1) all the related code is currently commented out
with the comment "cursor set management belongs in another app" and 2) it is already broken
because of ColorSet.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@13726 a95241bf-73f2-0310-859d-f6bbb57e9c96
specified via options -l and -s. An arbitrary program can be run in the
terminal instead of a shell.
* Console::fState was never initialized which could cause the terminal to
not print anything.
* stdin, -out, and -err were set in MiniView::Start() and in
MiniView::ExecuteShell(). Thus resetting them in the latter method after
executing the shell had no effect. Removed it in the former method and
now reset them after loading, but before resuming the shell.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@13676 a95241bf-73f2-0310-859d-f6bbb57e9c96
did not work anymore, and thus, the safemode with the current Bootscript
did not work.
It now does again.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@13192 a95241bf-73f2-0310-859d-f6bbb57e9c96
to LinkReceiver, LinkMsgSender to LinkSender, and put everything into the
BPrivate namespace.
Made AppServerLink a cheap object - it will use the applications receiver/sender
and not create its own buffers.
Fixed broken communication stuff here and there (mostly Font.cpp).
Put the newly introduced set|get_system_colors() into the BPrivate namespace -
please don't introduce private functions into the public namespace!!!
Also fixed their broken communication use, as Darkwyrm obviously forgot about
it again: the sequence Flush(); GetNextMessage() without error checking is
purely wrong and can make the app hang and/or crash! :-)
Other minor cleanup.
The input_server used some test mode with the haiku build target which is
probably wrong.
Hopefully I did not forget anything this time.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@13128 a95241bf-73f2-0310-859d-f6bbb57e9c96
to compile our libbe.so with RUN_WIHTOUT_APP_SERVER for the image.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@12190 a95241bf-73f2-0310-859d-f6bbb57e9c96
with coordinates specified as arguments, but this somehow
(and why ever) does hinder /bin/sh from execution (under R5
at least). If someone could point me to the problem I'd be greatful.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@12105 a95241bf-73f2-0310-859d-f6bbb57e9c96
We use Setenv instead of the native setenv to stay binary compatible with
BeOS, as R5 does not have setenv.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@12079 a95241bf-73f2-0310-859d-f6bbb57e9c96
This doesn't work under Haiku yet though.
Also made the thread functions into members of MiniView so that we
can have correct private members.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@12078 a95241bf-73f2-0310-859d-f6bbb57e9c96
It can be run under R5 and Haiku (binary compatible) and should work
with the Haiku app_server and input_server.
It gives access to a /bin/sh like a normal terminal, but has no fancy features
like different text encoding support and it cannot even redraw itself when
something else overdraws it.
But it's pretty impressiv that it works so well under Haiku.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@12068 a95241bf-73f2-0310-859d-f6bbb57e9c96
Ingo Weinhold