Re: [Rosegarden-user] Fwd: [Rosegarden-devel] Rosegarden's Future

2012-05-14 Thread David Tisdell
I have posted requests for Mac developers to 3 Apple lists:
*Coreaudio-api* https://lists.apple.com/mailman/listinfo/coreaudio-api A
mailing list for developers using Core Audio and MIDI APIs (C or Java) on
MacOS X
*Unix-porting* 
https://lists.apple.com/mailman/listinfo/unix-portingDiscussions
about porting UNIX-based software to Mac OS X
*X11-users* https://lists.apple.com/mailman/listinfo/x11-users X11 for
Mac OS X discussion list

We'll see if we garner any interest. I'll also see if I can find out who
tried to do the port in the fink project before the change to the qt
codebase and see if he is interested.

Dave

On Mon, May 14, 2012 at 6:04 AM, David Tisdell david.tisd...@gmail.comwrote:

 Claudio,

 I can't guarantee anything on recruiting developers but I can put it out
 there on Apple developer lists. I am not a developer myself but I can
 test some builds. I have all three platforms running at home (Linux, Mac
 and Windows). I have installed the Windows alpha and it is very
 promising (Thanks Richard).

 Dave

 On 5/13/12 6:56 PM, Cláudio Pinheiro wrote:
  I'm interested in a Mac port, and I may help with coding.
  Most of my coding experience involves portable code between Linux,
  Windows, ARM and microcontrollers, and I develop for Mac as a hobby.
  Having said that, I believe the biggest problem I see today in
  Rosegarden is the following mentality:
  I'm a Linux user and I want a tool to help me making music on
  Linux.. So Rosegarden is chosen because it's the most comprehensive
  DAW for the Linux platform, making the choice to use it subordinated
  to the choice of which operating system one wants to use. As the
  Linux-using musicians demographics is a tiny one is somewhat natural
  to expect that Rosegarden's visibility is minimal. And as Linux-using
  musicians programmers with free time and interest are even rarer,
  things pile up on the TODO queue (111 open bugs and 144 open feature
  requests).
  Let's take the opposite example: Mixxx. Multiplatform, Qt-based,
  low-latency DJ mixing program, runs on Linux, Windows and Mac OS X,
  GPL-licensed, free in App Store, has 800+ reviews (4.5 stars) and a
  thriving community.
  What's the main difference between Mixxx and Rosegarden as end-user
  products? When somebody wants to go into DJ'ing he/she can choose
  Mixxx to do the job as a (better) alternative to the commercial ones.
  When somebody wants to write music with a DAW he/she'll try to use a
  program that fulfills its needs. If he/she uses Linux Rosegarden is a
  choice. Had Rosegarden be multiplatform, the mentality would be I
  want a tool to help me making music instead of I'm a Linux user and
  I want a tool to help me making music on Linux.. When we remove the
  platform from the equation we broaden Rosegarden's target audience
  tenfold? Thirtyfold? If we were able to have iOS and Android ports, oh
 my.
  Rosegarden needs broad visibility by potential users, so it can
  generate a critical mass that would attract developers that would
  maintain a sustained growth and (even) better codebase and
  documentation. To achieve it Rosegarden must walk the multiplatform
  path. It must be the top priority now for the future's greater good.
  With this in mind, somebody said that would be able to recruit coders
  to work on a Mac port, please do so and ask them to do it in a
  multiplatform way. Somebody said that could help with the homepage.
  Please step up and do something seksy, atractive. Let's have
  commitment. Let's make Rosegarden reach what no other DAW I'm aware of
  has reached and Mixxx, LibreOffice and others had reached in their
  respective niches. We have lots of success examples all around us, so
  it's time to act upon.
 
  On Sat, May 12, 2012 at 10:34 AM, Ian Gardner ilgard...@yahoo.co.uk
  mailto:ilgard...@yahoo.co.uk wrote:
 
 
 
   For what it's worth, I think it's evident that the test framework
   Rosegarden should be using is the Qt one. (As least, if it's any
   good -- which it is; it's pretty nice.)
  
  
   Chris
  
 
  *raises hand* yes I'm potentially interested in looking at stuff
  around testing. I'll need to bone up on the Qt test stuff though,
  never having used it before.
 
  I'm much more interested in the macro top level testing I was
  talking about earlier (scripting out composition building by
  capturing the commands issued) rather than the gnarly micro unit
  testing of writing tests inside every single class and function in
  RG. I exaggerate there of course, but hopefully you catch my drift!
 
  Cheers,
 
  Ian.
 
 
 
 --
  Live Security Virtual Conference
  Exclusive live event will cover all the ways today's security and
  threat landscape has changed and how IT managers can respond.
  Discussions
  will include endpoint security, mobile security and the latest in
  

Re: [Rosegarden-user] Fwd: [Rosegarden-devel] Rosegarden's Future

2012-05-14 Thread David Tisdell
Perhaps I need to move this information to the developers list. I got this
reply from a guy on one of the Apple developer lists.

I had a brief go at rosegarden with other packages installed using fink
(fink needs the --prefix=/sw) on Mac OS X 10.6.8. However, I found issues
with configure tests for X11, dssi.h and sha1sum. Make finally failed
because i had no alsa installed and there was no quick resolution for that.

(He had all the compile errors in here which I will leave out of this post)

Unfortunately, I do not really have the skills/time to dig deeper into all
these issues, but maybe someone can pick it up. Once rosegarden builds on
macosx, i could contribute and maintain a package discription for fink.

He seems interested in moving forward. with help from others.

Dave


On Mon, May 14, 2012 at 8:04 AM, David Tisdell david.tisd...@gmail.comwrote:

 I have posted requests for Mac developers to 3 Apple lists:
 *Coreaudio-api* https://lists.apple.com/mailman/listinfo/coreaudio-apiA 
 mailing list for developers using Core Audio and MIDI APIs (C or Java) on
 MacOS X
 *Unix-porting* 
 https://lists.apple.com/mailman/listinfo/unix-portingDiscussions about 
 porting UNIX-based software to Mac OS X
 *X11-users* https://lists.apple.com/mailman/listinfo/x11-users X11 for
 Mac OS X discussion list

 We'll see if we garner any interest. I'll also see if I can find out who
 tried to do the port in the fink project before the change to the qt
 codebase and see if he is interested.

 Dave


 On Mon, May 14, 2012 at 6:04 AM, David Tisdell david.tisd...@gmail.comwrote:

 Claudio,

 I can't guarantee anything on recruiting developers but I can put it out
 there on Apple developer lists. I am not a developer myself but I can
 test some builds. I have all three platforms running at home (Linux, Mac
 and Windows). I have installed the Windows alpha and it is very
 promising (Thanks Richard).

 Dave

 On 5/13/12 6:56 PM, Cláudio Pinheiro wrote:
  I'm interested in a Mac port, and I may help with coding.
  Most of my coding experience involves portable code between Linux,
  Windows, ARM and microcontrollers, and I develop for Mac as a hobby.
  Having said that, I believe the biggest problem I see today in
  Rosegarden is the following mentality:
  I'm a Linux user and I want a tool to help me making music on
  Linux.. So Rosegarden is chosen because it's the most comprehensive
  DAW for the Linux platform, making the choice to use it subordinated
  to the choice of which operating system one wants to use. As the
  Linux-using musicians demographics is a tiny one is somewhat natural
  to expect that Rosegarden's visibility is minimal. And as Linux-using
  musicians programmers with free time and interest are even rarer,
  things pile up on the TODO queue (111 open bugs and 144 open feature
  requests).
  Let's take the opposite example: Mixxx. Multiplatform, Qt-based,
  low-latency DJ mixing program, runs on Linux, Windows and Mac OS X,
  GPL-licensed, free in App Store, has 800+ reviews (4.5 stars) and a
  thriving community.
  What's the main difference between Mixxx and Rosegarden as end-user
  products? When somebody wants to go into DJ'ing he/she can choose
  Mixxx to do the job as a (better) alternative to the commercial ones.
  When somebody wants to write music with a DAW he/she'll try to use a
  program that fulfills its needs. If he/she uses Linux Rosegarden is a
  choice. Had Rosegarden be multiplatform, the mentality would be I
  want a tool to help me making music instead of I'm a Linux user and
  I want a tool to help me making music on Linux.. When we remove the
  platform from the equation we broaden Rosegarden's target audience
  tenfold? Thirtyfold? If we were able to have iOS and Android ports, oh
 my.
  Rosegarden needs broad visibility by potential users, so it can
  generate a critical mass that would attract developers that would
  maintain a sustained growth and (even) better codebase and
  documentation. To achieve it Rosegarden must walk the multiplatform
  path. It must be the top priority now for the future's greater good.
  With this in mind, somebody said that would be able to recruit coders
  to work on a Mac port, please do so and ask them to do it in a
  multiplatform way. Somebody said that could help with the homepage.
  Please step up and do something seksy, atractive. Let's have
  commitment. Let's make Rosegarden reach what no other DAW I'm aware of
  has reached and Mixxx, LibreOffice and others had reached in their
  respective niches. We have lots of success examples all around us, so
  it's time to act upon.
 
  On Sat, May 12, 2012 at 10:34 AM, Ian Gardner ilgard...@yahoo.co.uk
  mailto:ilgard...@yahoo.co.uk wrote:
 
 
 
   For what it's worth, I think it's evident that the test framework
   Rosegarden should be using is the Qt one. (As least, if it's any
   good -- which it is; it's pretty nice.)
  
  
   Chris
  
 
  *raises hand* yes I'm