Michael Beal wrote:
>   1) Which programming language is being used in 2.0? C, C+, C++, or
>   Python?  I'm hoping Python.  I don't know C or it's derivatives
>   and really don't want to learn it.

Python with some C parts to connect to external libs.

>   2) Where do I go to get the source for 2.0?

svn://svn.freevo.org/freevo/trunk
svn://svn.freevo.org/kaa/trunk

>   3) Would anyone care to be my mentor for learning Python and
>   Freevo?  I know I'll create some really ugly code from time to
>   time and it'll need to be cleaned up a bit.  (After all, I just
>   beginning to learn Python as my 7th programming language.)  Also,
>   I've never worked on a collaborative development project before
>   and will need some guidance.

Ignore freevo and focus on kaa for a start. Try to understand our
code, maybe write some docs and some small examples. It is very
important for any hacking in freevo/kaa to understand kaa.notifier (in
base). After that, search for a part you are willing to code stuff for
and let us know.

> Since I'm the new guy, I'd be more than happy to look over old code
> and do whatever checks would be needed to get a 1.6 or 1.7 branch
> put out there.  The revamped mixer.py code and larger format skins
> could well make it into a 1.6/1.7 release along with all of the
> prior bugfixes.  

I have no time for a 1.5.5, so if you are willing to take a look at
bugs and fix them, it would be great. But do not ask any questions
about the internal design, it has changed so much in 2.0, I don't
remeber how 1.5 works :)

> Looking over the old code will also help me get acquainted with the
> internals of Freevo and make my transition into 2.0 a LOT faster.

I don't think so, the whole core has changed.

> One other new thing I've done is reworking the INFO skin to fit a
> 1024x768 screen with a 1280x800 widescreen version planned.  I've
> found a few things about the skin subsystem that confuses the crap
> out of me but also need to be fixed.  Adjusting certain
> definitions within the xml messes with text placement quite badly.
> Why this is so, I'm not sure but I'm going to find out!

The skin subsystem will be removed for 2.0. So an update may be nice
for 1.5 users but not needed for 2.0

So to summerize: work on the 1.5 branch may be helpfull for 1.5.5 if
there are bad bugs but not helping for 2.0. Merging from 1.5 to 2.0 is
an impossible task.



Dischi

-- 
System going down at 1:45 this afternoon for disk crashing.

Attachment: pgp4p8OYkLwJh.pgp
Description: PGP signature

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Freevo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to