IMHO, if you are going to be creating a GUI, then use a PR that is specifically designed to give good X-platform GUI's. APR is not that project. If you had a non-GUI project, then APR would be a much better fit for you.
Ryan On Tue, 27 Aug 2002, TC wrote: > >> Beyond the portability are there other benefits you have noticed > >> using APR in the last few years on the Apache Web server > > > >I would be happy to answer this. But first, let me comment on a few of > >the options above, and some of what we have learned. I want to be clear > >that I am not bad-mouthing ANY of those projects, they are all good, but > >we have some knowledge in this area, so I am trying to help. > So what types of projects are more suited to APR. > right now with asterisk for example they are trying to get the functions > for a basic phone up on win32, these are running in linux OS now > it includes these types of functions > > the IAX VoIP protocol layer... > & phonecore which actually implements a phone, with controls for driving > various > aspects of its operation (i.e. adding new calls, switching between active > calls, changing audio devices, conferencing, etc) > > so these are not like a "server" based process like the core asterisk PBX > but more like a personal productivity app, most of this port once the > "phonecore" > is up will be about the GUI portion... getting this UI over gnophone.com/ > so does it still make sense > to use APR as the portability of the core then yet another portability layer > for > the GUI say like wxWindows or is there a better strategy .. > > -- _______________________________________________________________________________ Ryan Bloom [EMAIL PROTECTED] 550 Jean St Oakland CA 94610 -------------------------------------------------------------------------------
