Re: [AD] thoughts on a release

["Miquel 'Fire' Burns" <miquelfire@xxxxxxxxxx>]

There is one feature I would like to see (but never got to actually
for, thought about it a few days ago) is a way to get how big I can
make a windowed display in which the window decoration and other
always on top stuff will not be cut off.

This could wait until 5.2 however. Actually, I'm not aware if such a
feature exists outside of Windows.

On Wed, Jan 20, 2010 at 7:33 AM, Peter Wang <novalazy@xxxxxxxxxx> wrote:
> On 2010-01-19, Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx> wrote:
>> On Tue January 19 2010, Thomas Fjellstrom wrote:
>> > On Tue January 19 2010, Peter Wang wrote:
>> > > On 2010-01-19, Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx> wrote:
>> > > > > Another thing that's arguably as important as those, is a
>> > > > > "capabilities" framework, so people can query what they can, and
>> > > > > can't do on a given computer.
>> > >
>> > > Was there a proposal somewhere?  What kind of capabilities did you have
>> > > in mind?
>> >
>> > I think there might have been a proper proposal, but at any rate its been
>> > mentioned on IRC and the list a few times in the past.
>> >
>> > What I think (and others seem to agree, SiegeLord, Elias, etc) is that
>> >  there should be a list of common capabilities exported via an allegro
>> >  API. So you can detect if there really is FAST hw acceleration (just
>> >  having GL work is no indication), things like NPOT textures, FBO's, and
>> >  other useful (but not always available) features should be advertised in
>> >  a cross platform manner (yes, I'm aware "FBO" is a GL term, but D3D
>> >  should have a corresponding feature).
>> >
>> > This way people can detect what features are available, and provide
>> > different code paths, before objects are even created.
>
> I would think that many of the graphical capabilities would not be known
> until OpenGL is initialised, which means you'd want to query it on a
> specific display.  Maybe like:
>
>    enum { ALLEGRO_CAPABILITY_NPOT_TEXTURES = 1, ... };
>    bool al_get_display_capability(ALLEGRO_DISPLAY *dpy, int cap);
>
> Perhaps some capabilities are not boolean values, e.g. maximum texture
> size, so maybe we need multiple functions with different return types.
>
>> I'm not the one to work on the capabilities stuff, but I do have some
>> experience working with both Xinerama and XRandR, so I will volunteer to
>> work on that should no one else want to (as a last resort).
>
> As usual I can't find any documentation for Xrandr.h.  Do you know where
> it is, or of a good example?
>
> Peter
>
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for Conference
> attendees to learn about information security's most important issues through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers
>



-- 
Note: No trees were killed in the sending of this message, but a large
number of electrons were terribly inconvenienced.