SOC2008 FloatCanvas2 merge?

[Nitro]

Hello Robin,

I'd like to release floatcanvas2, so it finally gets a bit more testing.
If you are ok with that, I've got a few questions left:

1) What do I have to do so the SOC2008_FloatCanvas branch in 3rdparty can
be merged into trunk?

2) Is it you or me who has to do the merging?

3) How do you/I go about writing the build/packaging scripts which pull
the neccessary stuff from 3rdparty into wx.lib?

4) For the wxPython demo, does it suffice to just spawn the FC2 demo from
the wxPython demo?

-Matthias

[Christopher Barker]

Nitro wrote:
> I'd like to release floatcanvas2, so it finally gets a bit more testing.

cool!

I do think a first step is to make sure it works on wxMac and wxGTK --
IIRC, it didn't work on GTK a while back.

Sorry, I'm not set up for testing GTK at this point :-(

as for the Mac:

There seems to be a sign error somewhere in the rendering code -- up and
down seem to be switched. If I switch to "pan" mode, when I move the
mouse up, the image moves down.


-Chris



--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

Chris....@noaa.gov

[Nitro]

Am 30.11.2009, 20:15 Uhr, schrieb Christopher Barker
<Chris....@noaa.gov>:

> Nitro wrote:
>> I'd like to release floatcanvas2, so it finally gets a bit more testing.
>
> cool!
>
> I do think a first step is to make sure it works on wxMac and wxGTK --
> IIRC, it didn't work on GTK a while back.
>
> Sorry, I'm not set up for testing GTK at this point :-(

I can only test on windows at this point :-/

> as for the Mac:
>
> There seems to be a sign error somewhere in the rendering code -- up and
> down seem to be switched. If I switch to "pan" mode, when I move the
> mouse up, the image moves down.

That's strange, it all works here for me. Does the Mac use a different
coordinate system somehow? Have you noticed any differences in the
GraphicsContext stuff between Mac and other platform?
The coordinates are mostly handled via numpy until they're finally fed
into the GraphicsContext. Does the lion in the svg importer demo show
upside down, too? Or is this problem specific to panning?

-Matthias

[Christopher Barker]

Nitro wrote:
> Am 30.11.2009, 20:15 Uhr, schrieb Christopher Barker

>> as for the Mac:
>>
>> There seems to be a sign error somewhere in the rendering code -- up and
>> down seem to be switched. If I switch to "pan" mode, when I move the
>> mouse up, the image moves down.
>
> That's strange, it all works here for me. Does the Mac use a different
> coordinate system somehow?

not that I know of, but...

> Have you noticed any differences in the
> GraphicsContext stuff between Mac and other platform?

I've hardly used GraphicsContext -- so I'm not the one to ask. I can
tell you that the few demos that are in the wxPython demo work the same
way on my Windows and Mac boxen.

> The coordinates are mostly handled via numpy until they're finally fed
> into the GraphicsContext. Does the lion in the svg importer demo show
> upside down, too?

yes -- it is upside-down, so it's apparently not a panning issue.

It was doing to right at some point way back when, but I can't tell you
when it broke -- so I have no idea of FC2 changed, or wxPython changed...

-CHB

[Mike Driscoll]

On Mon, Nov 30, 2009 at 2:32 PM, Nitro <nitro...@googlemail.com> wrote:

Am 30.11.2009, 20:15 Uhr, schrieb Christopher Barker
<Chris....@noaa.gov>:

> Nitro wrote:
>> I'd like to release floatcanvas2, so it finally gets a bit more testing.
>
> cool!
>
> I do think a first step is to make sure it works on wxMac and wxGTK --
> IIRC, it didn't work on GTK a while back.
>
> Sorry, I'm not set up for testing GTK at this point :-(

I can only test on windows at this point :-/

I recommend VirtualBox or VMWare Server if you can't build your own Linux box (and you have extra hard drive space). I use VMWare Server (free) at work with a couple of Ubuntu versions and XP. At home, I've been using VirtualBox as VMWare didn't get along with my Vista laptop too well and it's too slow on my old machine.

-------------------

Mike Driscoll

Blog:   http://blog.pythonlibrary.org

[Nitro]

Am 30.11.2009, 21:46 Uhr, schrieb Christopher Barker
<Chris....@noaa.gov>:

> Nitro wrote:
>> Am 30.11.2009, 20:15 Uhr, schrieb Christopher Barker
>
>>> as for the Mac:
>>>
>>> There seems to be a sign error somewhere in the rendering code -- up
>>> and
>>> down seem to be switched. If I switch to "pan" mode, when I move the
>>> mouse up, the image moves down.
>>
>> That's strange, it all works here for me. Does the Mac use a different
>> coordinate system somehow?
>
> not that I know of, but...
>
>> Have you noticed any differences in the
>> GraphicsContext stuff between Mac and other platform?
>
> I've hardly used GraphicsContext -- so I'm not the one to ask. I can
> tell you that the few demos that are in the wxPython demo work the same
> way on my Windows and Mac boxen.
>
>> The coordinates are mostly handled via numpy until they're finally fed
>> into the GraphicsContext. Does the lion in the svg importer demo show
>> upside down, too?
>
> yes -- it is upside-down, so it's apparently not a panning issue.
>
> It was doing to right at some point way back when, but I can't tell you
> when it broke -- so I have no idea of FC2 changed, or wxPython changed...

Thanks for testing!

I got myself a virtual Mac and have committed some fixes. Could you please
update SVN and try again?

Some teasers:

http://www.dr-code.org/nitro/shots/floatcanvas2-1.jpg (not an image,
polygons rendered)

http://www.dr-code.org/nitro/shots/floatcanvas2-2.jpg (with effects)

http://www.dr-code.org/nitro/shots/floatcanvas2-3.jpg (animated)

-Matthias

[Nitro]

Thanks for the tip. I might try getting a virtual (k)ubuntu later, too.

-Matthias

[niki]

Nitro wrote:
>
> I got myself a virtual Mac and have committed some fixes. Could you please
> update SVN and try again?

What is this virtual Mac? Apparently is's suitable for testing wxPython
code.

regards,
Niki

[Christopher Barker]

Nitro wrote:
> I got myself a virtual Mac and have committed some fixes. Could you please
> update SVN and try again?

Bingo! -- with some quick testing, it seems to be be working right now.

Nice work.

[Christopher Barker]

niki wrote:
> What is this virtual Mac?

I'm curious about that too -- OS-X running under VirtualBox or VM-Ware
or ???


-Chris

[Nitro]

Am 03.12.2009, 18:30 Uhr, schrieb Christopher Barker
<Chris....@noaa.gov>:

> niki wrote:
>> What is this virtual Mac?
>
> I'm curious about that too -- OS-X running under VirtualBox or VM-Ware
> or ???

Yes.

-Matthias

[Robin Dunn]

Hi Nitro,

Sorry for the delay in responding, I've been busy with other things for
a while and am now trying to get caught up on everything.

On 11/30/09 10:52 AM, Nitro wrote:
> Hello Robin,
>
> I'd like to release floatcanvas2, so it finally gets a bit more testing.
> If you are ok with that, I've got a few questions left:

Before I answer the questions, I have one of my own, as it will affect
my answers. Is it intended that FC2 will replace FC, or will both
continue to exist for a while? For my answers below I'll assume both
will continue to exist.

>
> 1) What do I have to do so the SOC2008_FloatCanvas branch in 3rdparty can
> be merged into trunk?

We'll want to keep it in the 3rdParty folder and then use svn:external
properties to hook it into the main wxPython SVN tree at the right
places. If you take a look at wxPython/3rdParty/AGW you'll see a good
way to organize it for library packages. In that folder there are just
2 sub folders. One will become a sub folder of wx/lib folder in the
wxPython source tree(s) using svn:external and the other will become a
sub folder of main demo folder. I'd like you to follow this same
pattern. You can have other sub folders there if needed, but they
probably won't be linked into the main source tree anywhere.

>
> 2) Is it you or me who has to do the merging?

You can copy from the SOC branch to the wxPython/3rdParty/FloatCanvas2
folder (or whatever you want to name it) with floatcanvas2 and demo
subfolders. Be sure to use svn copy so the history is maintained
between the old location and the new.

I'll add the svn:external properties in the main source tree once you've
got things set up in their new location.

>
> 3) How do you/I go about writing the build/packaging scripts which pull
> the neccessary stuff from 3rdparty into wx.lib?

There are a few files that will need to be edited and made aware of the
new folders and files to be included in the builds. Be sure to do it in
both the wxPython trunk and the WX_2_8_BRANCH since the 2.8 branch is
not fully closed yet.

1. setup.py (in the root of the wxPython source tree): At least the
WX_PKGLIST will need edited, adding the new package dirs that need to be
installed. If there are any files in those dirs that are not *.py files
that also need to be installed then they will need to be mentioned in
the DATA_FILES list.

2. distrib/DIRLIST: This file contains a list of all folders, relative
to the wxPython root, that need to be copied into the source tarball.
Anything that is needed for the build or install needs to go into this list.

3. distrib/make_installer.py: This script is used to build and run the
InnoSetup installer script for the Windows installers. You'll need to
mention all the files, again relative to the wxPython root, that need to
be installed on Windows in the [Files] section. (To make it easier you
can just specify the files by wildcard for each folder, but don't use
something like *.* because then all the .pyc files that happen to be in
the build dir would be included too.) You'll also need to add entries
to the [UninstallDelete] section for files that should be deleted on
uninstall that may not have been installed by the installer, like the
*.pyc files. Also note that there are two templates in this file, one
for the main installer and one for the docs/demos.

>
> 4) For the wxPython demo, does it suffice to just spawn the FC2 demo from
> the wxPython demo?

That would be okay to start with, but eventually I'd like for it to be
integrated into the main demo like AGW is. To do that you can put a
__demo__.py file in your main demo directory that provides info for the
main demo to be able to build up its tree of samples and to know what
modules to run. See AGW/demo/__demo__.py.

Since you have lots and lots of items in the FC2 demo then perhaps you
could choose some of them to integrate into the wxPython demo using the
__demo__.py mechanism, and then have the last item in the list be
something like See More Samples that launches your demo application.

--
Robin Dunn
Software Craftsman
http://wxPython.org

[Christopher Barker]

Robin Dunn wrote:
> Before I answer the questions, I have one of my own, as it will affect
> my answers. Is it intended that FC2 will replace FC, or will both
> continue to exist for a while? For my answers below I'll assume both
> will continue to exist.

I think so -- FC2 ended up being perhaps inspired by FloatCanvas, but
it's quite a different beast. I don't know how may FloatCanvas users
there are, but it's at least a few. I'll do my best to keep the tech
support up for FloatCanvas.

I suppose the may be an opportunity to give FC2 a better name!

[Robin Dunn]

On 12/10/09 4:56 PM, Christopher Barker wrote:
> Robin Dunn wrote:
>> Before I answer the questions, I have one of my own, as it will affect
>> my answers. Is it intended that FC2 will replace FC, or will both
>> continue to exist for a while? For my answers below I'll assume both
>> will continue to exist.
>
> I think so -- FC2 ended up being perhaps inspired by FloatCanvas, but
> it's quite a different beast. I don't know how may FloatCanvas users
> there are, but it's at least a few. I'll do my best to keep the tech
> support up for FloatCanvas.

Ok, makes sense to me. Thanks for confirming this.

>
> I suppose the may be an opportunity to give FC2 a better name!

Anybody have any suggestions?