Re: [AD] 5.2

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


About al_get_audio_event_source, when I added those it seemed useful but I’m not sure anymore. I don’t use Allegro for audio but I don’t have to deal with any of those signals so I don’t see why Allegro can’t work without them. I think we could drop them without any harm.
 
iPhone specifics -- I’ll put it on my TODO list again.
 
DISPLAY_CONNECTED/DISCONNECTED -- I just mentioned in the Menu thread that the idea presented there for a general system event source would work for these events too (obviously not very well thought out, my bad.)
 
Trent
 
From: Peter Wang
Sent: ‎Friday‎, ‎June‎ ‎14‎, ‎2013 ‎6‎:‎55‎ ‎PM
To: Coordination of admins/developers of the game programming library Allegro
 
On Thu, 13 Jun 2013 21:31:11 -0400, SiegeLord <slabode@xxxxxxx> wrote:
> Does anybody have any roadmap in mind towards it? In the coming week or
> two I'm going to finish what I wanted to do with the vertex/index
> buffers in the primitives addon and as far as I am concerned that's
> enough features for it. I was also going to look into locked bitmaps
> (they had some really inefficient things last time I glanced at them).
>
> Are there big things to do elsewhere now? Anything partly unfinished
> that I can help with?

The big one is the build system for the Android port.  I would like
(most) of the examples to build for Android on a Linux host.  They don't
have to run especially well, but once the examples are easily runnable
on a device we will surely flush out many bugs.  And, ultimately, users
should not need to manually set up an Android-specific project to use
the port.


Going through the 5.1 additions in the docs, here are some things:

* al_get_audio_event_source, as I wrote in January:

    The aqueue driver is the only one which emits these new events.
    [...]
    I think the events can and should be generated by the driver's
    solitary voice instead of a new special purpose audio event source.

* iphone specifics changes as mentioned in January

* I don't understand the documentation for
  ALLEGRO_EVENT_DISPLAY_CONNECTED/DISCONNECTED.
  What is the relation of the "display" event source to the physical
  display?

* I think people are looking at the menu API now.

* audio recording API should be reviewed

* the video addon can be trimmed a bit I think

* (vague reservations about the auto-convert bitmap API still)

Peter

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
--
https://lists.sourceforge.net/lists/listinfo/alleg-developers


Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/