Image question...

Serg Koren Serg at VisualNewt.com
Wed Feb 4 23:43:27 UTC 1998


---- On Wed Feb  4 15:03:59 1998, Patrick Logan said ------

>
>    PS - FYI for anyone interested or who cares, right now I have an
>    OO structure (BeOS requires everything to be an object/class (C++)
>    pretty much...no way to write console apps or do printfs or
>    whatever.)...
>
>    All printfs and "error" statements are passed to a "printf" override 
>    method I've written that actually launches another OO standalone 
>BeApp...
>
>Really? Do you mean Code Warrior for BeOS does not already have some
>kind of library for porting console apps?

Not that I've found; or been told...CW for BeOS is still in DR3 ;-) 
and doesn't have all the goodies yet.

>
>Bash is the shell for BeOS. Does the system come with the source code?
>I wonder how Bash and all the GNU utilities are ported?

You either port the way I am (develop a GUI from it) or run it from the 
BeOS shell...

BeOS *does* have a command-line shell (Terminal); but it's not very 
user-friendly for an end-user application.  It *can* be used for posting printfs 
to but you explicitely have to launch the app from the shell.  I decided to 
forgo the shell route since an end-user probably won't be running apps from it; 
they just double-click the executable to run in GUI mode ;-)  I guess I 
*could* launch the shell on a printf but I still think a dedicated window/app 
is cleaner (yes I know these are non-Squeak topics...sorry)


>
>Is the situation like that of Win NT where you can write a Posix app
>or you can write a Win NT app, but you cannot write a mixed Posix/Win
>NT app?
>

You can write a mixed shell/GUI app in BeOS; but why would you want to?  
Most end-users just use GUI stuff now...only us hackers/developers like 
command lines ;-)

S
-------------------------------------------------
VisualNewt Software: http://www.VisualNewt.com/
Maker of Newt'sPaper(tm) the Premier Newton(R)
MessagePad(tm) News Reader.

-----------Sent by BeOS--------------------------





More information about the Squeak-dev mailing list