> > comments from other game developers? i have considering writing this
> > little "patch" that users install depending on what device they have
> > and we could check for it from within our programs [games].. should
> > i continue the development of it? [it would be a free patch]
>
> Just to be sure I have correctly understood : this is a proposal for
> having a way to detect the display controller, right ? And by calling
> a function, we will know which kind of controller and at which memory
> address it is located, I'm still right ?
two features.. one says "this is the controller" second says "memory base"
> That seems to be a good idea !
>
> I just don't understand the meaning of the lib id ( 'gLIB' ) you are
> proposing, as it will make the lib/patch sound like more a game library (
> appGameLibCreator ) than a display controller detection one...
well... i just chose gLIB cause it was available :) we can add to it
later maybe.. who knows *g* but, i am visioning an installable app
that users will run that does following:
- guess what device they have
- try detection
- if reset occurs, user selects another option..
can make a nice little ui program to do this.. and, give appropriate
warnings and yada yada.. brainstorming in public here :)
> I agree with Hal, this should be take care of by developers who want/need
> those informations, and should not rely on the user to choose and install
> something.
>
> But I will go further : even if I agree that one shared library is better
> than several little "patches", I think than 0 shared library is even better :
> the user will don't have to find which "patch" to choose nore he will need to
> install a shared library !
>
> We can just make a public code, available for every developer that need it,
> and then those developers will just need to include this code into their
> application.
would be best to not do this - update "patch" - update game.. why
re-release new versions (unless you want front page on PGHQ) :P heh
> We, as developers should handle all the troubles and let the users just
> install the application they want without to worry if they have to install
> some library or worse, have to choose beetwen several patches and install the
> good one.
the suggestion now (as bobby suggested) is to have a single app that
"does some tests" - it'll find the bets options for the unit - and
set them.
> To be sure it's the one you are thinking of, you just need to read to some
> registers to identify the display controler, which mean you need to know
> where in memory it is located.
>
> And to know where is located the display controler, there is an easy way :
> just look at which address is the display screen, it will give you a hint to
> where is the video RAM...
yes, thought about that, mediaQ and SED controllers have same memory
offset (just by chance - that could change) :P what about the samsung
phone? its not color, but, it has a virtual grafitti area.. and, display
is external :)
> The last problem to solve is : who will write the code, where will it be
> available and at which conditions ?
open source the sucker. GPL probably suits it best. no need for shared
library, it will just set these features.. since it is system patch,
your not linking to it - so, no issues there.. it'll provide info on
the device publically.. so, licensing shouldn't matter. if GPL is a
problem, then LGPL will suffice. or, whatever.. i hate legal crap.
basically, you dont need to be dependent on it - but, if it is there
and you can read the values.. you can write whatever you like with it.
it wont take long to write this code.. really.. i wouldn't mind hosting
it and maintaining it. its needed, should be part of the OS really.
// az
[EMAIL PROTECTED]
http://www.ardiri.com/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
