[interfacekit] Re: App Server Startup procedures and question

Wow, this is great stuff.  The Layer stuff you posted the other night
was really good as well.

Regarding the linker problem, you're not going to be linking to
control_graphics_card at build time -- you'll load the symbol at run
time.  So whatever code you have that's trying to link at build time
will need revision.  Check out the docs on loading symbols from addons
in the Kernel Kit docs.  If any of it isn't clear let me know, and I can
whip up an example; my main BeOS project is an addon *festival*, so I've
done it plenty! =P

e

DarkWyrm wrote:
> 
> I've been working hard on figuring out a base for the app_server using the
> BWindowScreen class this weekend and I seem to have somewhat of a step-by-
> step for startup. Let me know if there is something else we need to add to
> this process.
> 
> App Server Startup procedures
> -------------------------------
> 1) Load and make use of global settings
> 2) Initialize graphics driver
> 3) Initialize desktop (defined as the collection of workspaces)
> 
> Graphics Driver Initialization (calls to control_graphics_card())
> -------------------------------
> 1) open graphics driver
>     A) look in current path. If empty and last path, halt system. If merely
> empty, repeat with next path.
>         a)Write to serial port "Attempting to load <name> as graphics driver"
>         b)call with B_OPEN_GRAPHICS_CARD. If return B_ERROR, call with
> B_CLOSE_GRAPHICS_CARD and read next entry in path.
>     B) write to serial port "Using <name> as graphics driver"
> 2) Generate system palette
> 3) call B_CONFIG_GRAPHICS_CARD
> 4) call B_GET_GRAPHICS_CARD_HOOKS
> 5) call B_GET_GRAPHICS_CARD_INFO
> 
> Driver search path list
> -------------------------
> 1) /fd/beos/system/add-ons/app_server
> 2) /boot/home/config/add-ons/app_server
> 3) /boot/beos/system/add-ons/app_server
> 
> Desktop Initialization
> ---------------------------
> 1) Create number of workspaces according to user settings (or defaults)
> 2) Set workspace settings to what has been loaded in preferences
> 3) activate_workspace(0)
> 
> One question: I attempted playing around with the graphics driver stuff and
> ran into one slight snag - the linker can't find control_graphics_card.
> Anyone know how to get around this?
> 
> --DW

Other related posts: