Re: [Poopmup-public] List of proposed changes in poopmup

[Sherif Z. <sza...@gm...>]

Andreas,
To be honest, the bird has been hibernating for about a year.
And I thing that you have woken up it's spirit.

Ok, I shouldn't try to be mistical. My last step before I stoped was
doing code clean up. And I think that there is need for a code clean
up.

Rename files as much as you see fit. I think it would be alot better.

As for the world objects Stephen is the guy that coded that part. It
was about 2 years ago, I you can try him out, I think he is still on
the list.

I think that what you are doing with this project is amazing, and this
is why I wanted to gpl poopmup.

I encourage you to tweak, modify, rework it.

1 part that I always wanted to redo was the texture loader. I really
didn't like that code.


Sherif Zaroubi.



On Sat, 16 Oct 2004 01:51:37 +0200, Andreas Pokorny <die...@gm...> wrote:
> Hi Sherif and all the others,
> I managed to look at the newest source now. So here is the list
> things i would like to do first:
> 
> 1) Move source files into src/
>    src/base3d/    <all math cam bbox stuff>
>    src/gui        <contents of osd and osd/formElem and the font stuff>
>    src/world      <contents of theWorld>
>    src/objects    <contents of movableObjects mapObject derivedGeom and
>                    bird>
>    src/media      <image and sound file loader>
>                    + further 3dmodel, and world file loader
>    src/           <everything else, the main file myObjectives(<-or in
>                    World?), and the config file loader>
> 
>    There are still many files i am not aware about, especially with the
>    world and object stuff, so most of that is based on the file names.
>    Maybe a different structure makes more sense?
> 
> 2) Rename files, remove 'my' prefix, and enforce a fixed naming policy
> 
> 3) Gui cleanup:
>    * use of std::list, and std::string instead of arrays
>    * use of templates for some of the widgets
> 
> 4) Singleton config file loader
> 
> 5) Rework math objects:
>    I think the point and vector classes could be enhanced, and
>    simplified by using overloded operators.
> 
> 6) Add time based movement, instead of fixed time steps
>    Before I can start that, I will need to learn the current way of doing
>    things, but I guess that will be the first new thing to implement.
> 
> 7) Fix all current problems with sound and texture loading
>    (i had problems here, but i havent looked into that)
> 
> --- Release of version 1.3 ---
> 
> 8) 3D model import
> 9) Start adding scripting support by using boost::python
> 
> Is that ok so far?
> May I use the boost libraries?
> I might need smart pointer templates, or boost::function, and signals
> might be helpful for the gui classes. But from the current point of view
> boost is a post-1.3 thing.
> 
> I might have more time tomorrow.
> 
> Best Regards
> Andreas Pokorny
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Poopmup-public mailing list
> Poo...@li...
> https://lists.sourceforge.net/lists/listinfo/poopmup-public
> 


-- 
Sherif Zaroubi