wxperl-users — For wxPerl users

RE: [wxperl-users] Document/View Framework

[Simon F. <sim...@bb...>]

Hi Mattia,

Thanks for the detailed replies. I haven't had much chance
to work on this today. I hope to spend some time on this
over the next few days.

> > We'd need to override Wx::ClassInfo->CreateObject() or
> > wxClassInfo::m_objectConstructor.
>
> It is sufficient to override ->CreateObject.

Ok, We might still want to use Wx::ClassInfo for wx(Class)
classes. So am I right in saying, we'd have a wxPlClassInfo
class which overrides ->CreateObject. How do you see this
being used?

  my $ci_doc = Wx::PlClassInfo::FindClass("My::Doc");
  my $ci_view = Wx::PlClassInfo::FindClass("My::View");

  $doc_tmpl = Wx::DocTemplate->new($docmgr, ..., ..., ...,
                                   $ci_doc, $ci_view, flag);

or 

  $doc_tmp = Wx::DocTemplate->new($docmgr, ..., ..., ...,
                                   "My::Doc", "My::View", flag);

...and having our wxPlDocTemplate construct wxPlClassInfo objects?

If I have any other questions I'll let you know.

Thanks
Simon

-  - -- ----  ---------------------------- --- -- -   -
Simon Flack   Software Engineer   BBC, Interactive F&L  
email: sim...@bb... 
telephone: 020 8752 6436 
-  - -- ----  ----------------------------------- --- -- -   - 

> -----Original Message-----
> From: Mattia Barbon [mailto:mb...@ds...]
> Sent: 27 August 2002 19:11
> To: Simon Flack
> Cc: wxp...@li...
> Subject: Re: [wxperl-users] Document/View Framework
> 
> 
> > Hi,
> > 
> > I am working on implimenting wxWindows' doc/view framework 
> in wxPerl. I've
> > got about 95% of the XS done and it compiles ok, but I'm 
> having a problem
> WOW! This is really impressive!
> 
> > with wxDocTemplate/wxClassInfo.
> 
> > The wxDocTemplate constructor looks like this:
> > 
> >    Wx_DocTemplate *
> >    Wx_DocTemplate::new(manager, descr, filter, dir, ext, 
> docTypeName,
> >                        viewTypeName, docClassInfo, 
> viewClassInfo, flags)
> >        Wx_DocManager* manager
> >        wxString descr
> >        wxString filter
> >        wxString dir
> >        wxString ext
> >        wxString docTypeName
> >        wxString viewTypeName
> >        Wx_ClassInfo* docClassInfo
> >        Wx_ClassInfo* viewClassInfo
> >        long flags
> > 
> > The wxDocTemplate needs wxClassInfo objects for the 
> document and view
> > classes, so it can create the documents/views automatically 
> when they are
> > needed. I think this probably works ok if I use c++ classes 
> it already knows
> Yes, it should
> 
> > about such as wxDocument and wxView. Obviously wxClassInfo 
> doesn't know
> > anything about perl classes, so I can't create a classinfo 
> object for
> > "MyDocument" and "MyView".
> Yes; the alternative (as explained in wxDT::wxDT docs) is to override
> CreateDocument; to be able to do this you need a wxPlDocTemplate class
> (see below).
> 
> > At the moment, I've got this in my test script:
> > 
> >     my $ci_doc = Wx::ClassInfo::FindClass("wxDocument");
> >     my $ci_view = Wx::ClassInfo::FindClass("wxView");
> >     my $docmanager = Wx::DocManager->new( 1, 1 );
> >     my $doctemplate = Wx::DocTemplate->new($docmanager, 
> "XML", "*.xml", "",
> >                                           "xml", "MyDoc", 
> "MyView", $ci_doc,
> >                                           $ci_view, 1 );
> >     my $frame = new Wx::DocParentFrame($docmanager, undef, 
> -1, "DocView
> > Demo",
> >                                       wxDefaultPosition, 
> wxDefaultSize,
> >                                       wxDEFAULT_FRAME_STYLE);
> > 
> > 
> > So far I'm getting encouraging results for Wx::DocManager. 
> When I click on
> > File -> Open, it automatically pops up a file selector for 
> *.xml files. But
> > when I try and open one it crashes. I think this is because
> > wxView::OnCreate() isn't doing anything.
> Possibly
> 
> > What I'd like to be able to do is something like this:
> > 
> >     my $ci_doc = Wx::ClassInfo::FindClass("My::Document");
> >     my $ci_view = Wx::ClassInfo::FindClass("My::View");
> > 
> > Although we might need a different method name so we can 
> still handle c++
> > classes in the same way. My problem is that I don't know 
> how to impliment
> > this. We'd need to override Wx::ClassInfo->CreateObject() or
> > wxClassInfo::m_objectConstructor.
> It is sufficient to override ->CreateObject.
> 
> > I don't think I'm experienced enough to do this, but even 
> if I were, I'd
> > want to make sure that I did it in a way that was 
> compatible with wxPerl
> > development. 
> >
> > If I can get this working I'll submit a patch to add the 
> document/view
> > framework. If not, I'll give you what I've done so far so 
> you don't need to
> > repeat what I've already done.
> > 
> > By the way Mattia, I'm interested to know what the 
> wxPl...... classes are
> > for? Do we need something like that here? It looks like 
> there are some
> > useful functions in cpp/helpers.cpp
> The wxPlFoo classes are used when:
> 1 - you need to have a C++ virtual function overridable from Perl
>     (for example wxSizer::RecalcSizes)
> 2 - you want the C++ object to store a reference to the Perl object;
>     for example Wx::Icon does not use a wxPlIcon (just a wxIcon)
>     hence $frame->SetIcon( $icon1 ); $icon2 = $frame->GetIcon();
>     $icon1 and $icon2 will be different Perl-level objects
>     OTOH when you do $button1 = Wx::Button->new( $parent, ... );
>     $button2 = ($parent->GetChildren())[0]; $button1 and $button2
>     should be the same Perl-level object, and this is possible because
>     a wxPlButton is used
> 3 - some other utility classes are named wxPlFoo or wxPliFoo
> 
> We need these classes here, because wxDoc/View uses virtual
> functions a lot. I will post a more detailed explanation in
> another mail.
> 
> Regards
> Mattia
> 


BBCi at http://www.bbc.co.uk

This e-mail (and any attachments) is confidential and may contain 
personal views which are not the views of the BBC unless specifically 
stated.
If you have received it in error, please delete it from your system, do 
not use, copy or disclose the information in any way nor act in 
reliance on it and notify the sender immediately. Please note that the 
BBC monitors e-mails sent or received. Further communication will 
signify your consent to this.

[wxperl-users] wxPerl Wiki

[Jouke V. <jo...@pv...>]

The wxPerl Wiki I mentioned before has more or less been set up. The 
current url is http://213.84.151.206/cgi-wxperl/view.pl/FrontPage , 
which will become http://wxperl.pvoice.org/cgi-wxperl/view.pl/FrontPage 
in a few days (after the dns change has been propagated throughout the 
world).

Of course the Wiki is empty right now, but I'll be starting to put 
things on it, and hope a lot of you will do the same.

Jouke

[wxperl-users] Re: wxIE success

[Graciliano M. P. \(V. Sites\) <gm...@vi...>]

> >Yes, you can get every thing, since this is enabled from the internal
> functions of the Internet Explorer activex (.ocx). In the demo for
wxWindows
> >you can ask to the user if the page can open another window, etc...
>
> Excellent. Where is it documented?
No, thi class are not documented yet!
http://members.optusnet.com.au/~blackpaw/

>
> Let me know when you have a new demo, this is VERY interesting :-)
Ok

>
> On Linux you want to add Konqueror or Mozilla, or both?
Well, both. But I think that Konqueror will be bets, 1th because it comes
with KDE, 2th because it's more fast to load and run. The Konqueror peoples
are doing something like IE on Windows, including the resources to embed it.
But this will use other interfaces, since we don't have ActiveX on Linux,
and I think that for each we need to make a different interface to link to
wxWindows! Will be hard!

>
> Btw, I finally bought a new graphics card and now I can use XFree 4.
Debian is quite good now, it has both KDE and Gnome.

Yes! I got an old computer (Pent166) and put a new card, well, not new,
better, to run Red Hat and test wxPerl on Linux too. And it works fine,
1024px!


Graciliano M. P.

[wxperl-users] Re: wxIE success

[Graciliano M. P. \(V. Sites\) <gm...@vi...>]

> Okay, got it. Great stuff :-)
>
> I can place it in my current app once it's advanced. Actually I only need
one function. Will it be possible to get the link a user clicks on?
> Like OnLinkClicked() in wxHTML?

Yes, you can get every thing, since this is enabled from the internal
functions of the Internet Explorer activex (.ocx). In the demo for wxWindows
you can ask to the user if the page can open another window, etc...

Graciliano M. P.

Re: [wxperl-users] Default background colour

[Mattia B. <mb...@ds...>]

> > Wx::SystemSetting::GetColour; I think the colour you want is
> > wxSYS_COLOUR_WINDOW.
> 
> Ehhh....where in the world is Wx::SystemSetting documented? I have the 
> documentation here, did a search for SystemSetting which returned 'no 
> topics found'...
Try searching for "wxSystemSettings"... (yes, it is suboptimal, I know)

Regards
Mattia

Re: [wxperl-users] A few things + questions ..

[Jouke V. <jo...@pv...>]

> GetPlData, documented under GetItemData
My version of the documentation contains a wxPython note that they have 
GetPyData, but no wxPerl note for GetPlData...

> The problem is that this is a big task; in addition it does not require
> XS/C++/wxWindows knowledge, so if someone writes a TeX -> POD converter
> that works for wxWindows docs, I'll probably include it in the distribution;
> but *I* won't write it.
I know, I know....it's just one of the many thoughts...


> It would be nice to have a way to write (in a perl-programmer-friendly way)
> which type each argument is, and which arguments are optional/have a default
> value; but I can't think of something that is both compact and
> perl-programmer-friendly
Hmm...maybe something for the Wiki....


Jouke

Re: [wxperl-users] Default background colour

[Jouke V. <jo...@pv...>]

> Wx::SystemSetting::GetColour; I think the colour you want is
> wxSYS_COLOUR_WINDOW.

Ehhh....where in the world is Wx::SystemSetting documented? I have the 
documentation here, did a search for SystemSetting which returned 'no 
topics found'...

But thanks anyway...sounds like this class could be very handy at times...

Jouke

Re: [wxperl-users] wxIE & wxActiveX Test 1

[Mattia B. <mb...@ds...>]

> >
> >
> >Other thing, how will be the structure for this, because wxIE & wxFlash (in
> >the future) need wxActiveX, and this is only for Win32. We can put:
> >Wx::Win32::IE , Wx::ActiveX::IE or Wx::IE. The class now is: Wx::IEHtmlWin.
> >Since this 2 classes aren't in the wxWindows/contrib and are very basics, we
> >can't follow wxWindows yet. For wxFlash I wnat to make something portable,
> >for Win32 ActiveX, and Linux using the Netscape Plig-in.
> >
> I would vote for Wx::ActiveX::IE, and Wx::ActiveX::Flash and so on...
Me too.

Regards
Mattia

Re: [wxperl-users] printing

[Mattia B. <mb...@ds...>]

> hello
> 
> i tried to change the printing demo to take the data from a textctrl.
> but i was unable to do it because i don't understand what the demo is exactly
> doing...
> can someone give a small example how to print the text in a textctrl?
This example uses Wx::HtmlEasyPrinting to do the job. It is IMHO the
easiest way to do what you want. You can see how the wxHtmlWindow demo
uses it. An extract is below.

# construct a Wx::HtmlEasyPrinting and keep it around
# you will probably store that in $this->{PRINTER}, but
# $printer is shorter...
$printer = Wx::HtmlEasyPrinting->new( 'wxPerl demo' );

# Page Setup (needs to be done only once)
$printer->PageSetup;
# likewise for Printer Setup
$printer->PrinterSetup;
# get the text
my $text = $textctrl->GetValue;
my $html = "<html><head></head><body>$text</body></html>";
# preview it
$printer->PreviewText;
# or print it
$printer->PrintText;
# you should be able to save/restore Page/Printer setup
# using
my $data1 = $printer->GetPageSetupData;
my $data2 = $printer->GetPrintData;
# and calling the Get/Set methods on $data1 and $data2
# but I haven't tried if this works

HTH
Mattia

Re: [wxperl-users] wxIE & wxActiveX Test 1

[Mattia B. <mb...@ds...>]

> Mattia,
> 
>   I have a gift for you! :-P
>   I have sucess with the XS for wxActiveX and wxIE.
Excellent!

>   You can get the source and binary at:
>   http://wxperl.virtuasites.com.br/wxie-0.1.zip (1Mb)
>   I put the basics of ./blib just for the peoples see the demo.
Me and my 33.600 modem would appreciate if sources were available
separately...

Regards
Mattia

[wxperl-users] wxPlFoo classes & virtual methods

[Mattia B. <mb...@ds...>]

This is mainly intended for Simon, who is working on doc/view.
How to make virtual C++ methods overridable from perl.
I did not test the code. You can find working code in various places.

1 - create a new .h file, say docview.h
2 - put this in the file
class wxPlDocument : public wxDocument
{
    WXPLI_DECLARE_DYNAMIC_CLASS( wxPlDocument );
    WXPLI_DECLARE_V_CBACK();
public:
    wxPlDocument( const char* package )
        :m_callback( "Wx::PlSizer" )
    {
        m_callback.SetSelf( wxPli_make_object( this, package ), TRUE );
    }

    // overridable methods
    // there are various handy macros in cpp/v_cback.h; in this case you can't
    // use DEC/DEF_V_CBACK_BOOL__VOID because it uses a non-const method
    virtual bool IsModified() const;
};

bool wxPlDocument::IsModified() const
{
    if( wxPliVirtualCallback_FindCallback( aTHX_ &m_callback, "IsModified" ) )
    {
        // you can use _CallCallback( ...., G_SCALAR, "ii", 1, 1 );
        // to pass arguments to the callback; I will document the valid
        // flag letters ASAP
        SV* ret = wxPliVirtualCallback_CallCallback( aTHX_ &m_callback,
                                                     G_SCALAR );
        bool val = SvTRUE( ret );
        SvREFCNT_dec( ret );
        return val;
    }

    return wxDocument::IsModified();
}

WXPLI_IMPLEMENT_DYNAMIC_CLASS( wxPlDocument, wxDocument );

There are more complex examples of this in various cpp/*.h files.

Feel free to ask if this is not clear enough/need more information.

Regards
Mattia

Re: [wxperl-users] Document/View Framework

[Mattia B. <mb...@ds...>]

> Hi,
> 
> I am working on implimenting wxWindows' doc/view framework in wxPerl. I've
> got about 95% of the XS done and it compiles ok, but I'm having a problem
WOW! This is really impressive!

> with wxDocTemplate/wxClassInfo.

> The wxDocTemplate constructor looks like this:
> 
>    Wx_DocTemplate *
>    Wx_DocTemplate::new(manager, descr, filter, dir, ext, docTypeName,
>                        viewTypeName, docClassInfo, viewClassInfo, flags)
>        Wx_DocManager* manager
>        wxString descr
>        wxString filter
>        wxString dir
>        wxString ext
>        wxString docTypeName
>        wxString viewTypeName
>        Wx_ClassInfo* docClassInfo
>        Wx_ClassInfo* viewClassInfo
>        long flags
> 
> The wxDocTemplate needs wxClassInfo objects for the document and view
> classes, so it can create the documents/views automatically when they are
> needed. I think this probably works ok if I use c++ classes it already knows
Yes, it should

> about such as wxDocument and wxView. Obviously wxClassInfo doesn't know
> anything about perl classes, so I can't create a classinfo object for
> "MyDocument" and "MyView".
Yes; the alternative (as explained in wxDT::wxDT docs) is to override
CreateDocument; to be able to do this you need a wxPlDocTemplate class
(see below).

> At the moment, I've got this in my test script:
> 
>     my $ci_doc = Wx::ClassInfo::FindClass("wxDocument");
>     my $ci_view = Wx::ClassInfo::FindClass("wxView");
>     my $docmanager = Wx::DocManager->new( 1, 1 );
>     my $doctemplate = Wx::DocTemplate->new($docmanager, "XML", "*.xml", "",
>                                           "xml", "MyDoc", "MyView", $ci_doc,
>                                           $ci_view, 1 );
>     my $frame = new Wx::DocParentFrame($docmanager, undef, -1, "DocView
> Demo",
>                                       wxDefaultPosition, wxDefaultSize,
>                                       wxDEFAULT_FRAME_STYLE);
> 
> 
> So far I'm getting encouraging results for Wx::DocManager. When I click on
> File -> Open, it automatically pops up a file selector for *.xml files. But
> when I try and open one it crashes. I think this is because
> wxView::OnCreate() isn't doing anything.
Possibly

> What I'd like to be able to do is something like this:
> 
>     my $ci_doc = Wx::ClassInfo::FindClass("My::Document");
>     my $ci_view = Wx::ClassInfo::FindClass("My::View");
> 
> Although we might need a different method name so we can still handle c++
> classes in the same way. My problem is that I don't know how to impliment
> this. We'd need to override Wx::ClassInfo->CreateObject() or
> wxClassInfo::m_objectConstructor.
It is sufficient to override ->CreateObject.

> I don't think I'm experienced enough to do this, but even if I were, I'd
> want to make sure that I did it in a way that was compatible with wxPerl
> development. 
>
> If I can get this working I'll submit a patch to add the document/view
> framework. If not, I'll give you what I've done so far so you don't need to
> repeat what I've already done.
> 
> By the way Mattia, I'm interested to know what the wxPl...... classes are
> for? Do we need something like that here? It looks like there are some
> useful functions in cpp/helpers.cpp
The wxPlFoo classes are used when:
1 - you need to have a C++ virtual function overridable from Perl
    (for example wxSizer::RecalcSizes)
2 - you want the C++ object to store a reference to the Perl object;
    for example Wx::Icon does not use a wxPlIcon (just a wxIcon)
    hence $frame->SetIcon( $icon1 ); $icon2 = $frame->GetIcon();
    $icon1 and $icon2 will be different Perl-level objects
    OTOH when you do $button1 = Wx::Button->new( $parent, ... );
    $button2 = ($parent->GetChildren())[0]; $button1 and $button2
    should be the same Perl-level object, and this is possible because
    a wxPlButton is used
3 - some other utility classes are named wxPlFoo or wxPliFoo

We need these classes here, because wxDoc/View uses virtual
functions a lot. I will post a more detailed explanation in
another mail.

Regards
Mattia

Re: [wxperl-users] A few things + questions ..

[Mattia B. <mb...@ds...>]

> Mattia Barbon wrote:
> 
> >>I'll make a start for this soon and would like to invite everyone to 
> >>contribute. My experience is that the wxWindows docs themselves are not 
> >>quite what you're looking for while building a wxPerl application, 
> >>because it's not always clear wether a function or class is implemented 
> >>
> >The "implemented class" part is not that difficult; the "implemented function"
> >part should be doable (automatically); which way should implemented/not
> >implemented classes/dunctions be marked?
> >
> Well, a simple remark like 'wxPerl note: this function is not 
> implemented'  under a function that is not implemented would do for me. 
Ok

> And for the Validators: how they are implemented in wxPerl, and for 
Hmm, yes, I forgot that

> something I stumbled into (from the top of my head, I don't have the 
> code here): GetPlItemData (or something) for the Tree control, for which 
> I can't find any documentation.
GetPlData, documented under GetItemData

> These are just things I can think of right now, but I'm sure there are 
> more things that should be documented.
> 
> Another thing that wouldn't be a bad idea I personally think, is to have 
> the possibility of having the documentation available in POD format. I 
> don't have a problem with the HTML documentation, but I know there are a 
> *lot* of Perl programmers who *love* POD , and would appreciate the 
> availability of the docs in this format.
The problem is that this is a big task; in addition it does not require
XS/C++/wxWindows knowledge, so if someone writes a TeX -> POD converter
that works for wxWindows docs, I'll probably include it in the distribution;
but *I* won't write it.

> >>in wxPerl or not, what parameters wxPerl expects and so on.
> >>
> >If you could sketch some way to make parameter wxPerl expects,
> >or whatever, clearer, *and* if this can be made automatically
> >(i.e. by a script), I could incorporate this in the docs.
> >
> I have to think about this. I think of something like simply showing how 
> you would call it from Perl, like:
> 
> $button = Wx::Button->new($parentid, etc etc)
Yes
 
> Which is significantly different from how you would call the constructor 
> in C++. It's all considered as common knowledge, but a starter would not 
> always understand how to read the C++ docs.
It would be nice to have a way to write (in a perl-programmer-friendly way)
which type each argument is, and which arguments are optional/have a default
value; but I can't think of something that is both compact and
perl-programmer-friendly

Regards
Mattia

Re: [wxperl-users] Default background colour

[Mattia B. <mb...@ds...>]

> Is there a name for the default background colour of a frame, a panel or 
> whatever Wx::Window derrivate? I tried to set the background colour of a 
> selected button, and tried to reset it back to its original value, and 
> thought that would be wxLIGHT_GREY, but that seems to be a bit darker 
> than the default backgroundcolour.
Wx::SystemSetting::GetColour; I think the colour you want is
wxSYS_COLOUR_WINDOW.

HTH
Mattia

Re: [wxperl-users] wxActiveX & Perl5.8-win32 binary

[Graciliano M. P. \(V. Sites\) <gm...@vi...>]

> Many, Many kudos Graciliano!
>
> Is it possible to publish a binary for Perl 5.6 (that is, the current
> Activestate Perl distro I'm using)? I'd *love* to go and use this!

Yes, and this will be done. But now the wxActiveX class was not fully
ported, in other words is not functional yet! When all be done I, or Mattia,
will publish the binarys, since this is not a easy class to compile.

Graciliano M. P.

Re: [wxperl-users] wxIE & wxActiveX Test 1

[Graciliano M. P. \(V. Sites\) <gm...@vi...>]

> >Other thing, how will be the structure for this, because wxIE & wxFlash
(in
> >the future) need wxActiveX, and this is only for Win32. We can put:
> >Wx::Win32::IE , Wx::ActiveX::IE or Wx::IE. The class now is:
Wx::IEHtmlWin.
> >Since this 2 classes aren't in the wxWindows/contrib and are very basics,
we
> >can't follow wxWindows yet. For wxFlash I wnat to make something
portable,
> >for Win32 ActiveX, and Linux using the Netscape Plig-in.
> >
> I would vote for Wx::ActiveX::IE, and Wx::ActiveX::Flash and so on...

OK! But about Flash, the class wont be inside ActiveX, because ActiveX is
only for Win32, and I want to enable it on linux too. For Flash I think
Wx::Flash better.

Graciliano M. P.

[wxperl-users] Document/View Framework

[Simon F. <sim...@bb...>]

Hi,

I am working on implimenting wxWindows' doc/view framework in wxPerl. I've
got about 95% of the XS done and it compiles ok, but I'm having a problem
with wxDocTemplate/wxClassInfo.

The wxDocTemplate constructor looks like this:

   Wx_DocTemplate *
   Wx_DocTemplate::new(manager, descr, filter, dir, ext, docTypeName,
                       viewTypeName, docClassInfo, viewClassInfo, flags)
       Wx_DocManager* manager
       wxString descr
       wxString filter
       wxString dir
       wxString ext
       wxString docTypeName
       wxString viewTypeName
       Wx_ClassInfo* docClassInfo
       Wx_ClassInfo* viewClassInfo
       long flags

The wxDocTemplate needs wxClassInfo objects for the document and view
classes, so it can create the documents/views automatically when they are
needed. I think this probably works ok if I use c++ classes it already knows
about such as wxDocument and wxView. Obviously wxClassInfo doesn't know
anything about perl classes, so I can't create a classinfo object for
"MyDocument" and "MyView".

At the moment, I've got this in my test script:

    my $ci_doc = Wx::ClassInfo::FindClass("wxDocument");
    my $ci_view = Wx::ClassInfo::FindClass("wxView");
    my $docmanager = Wx::DocManager->new( 1, 1 );
    my $doctemplate = Wx::DocTemplate->new($docmanager, "XML", "*.xml", "",
                                          "xml", "MyDoc", "MyView", $ci_doc,
                                          $ci_view, 1 );
    my $frame = new Wx::DocParentFrame($docmanager, undef, -1, "DocView
Demo",
                                      wxDefaultPosition, wxDefaultSize,
                                      wxDEFAULT_FRAME_STYLE);


So far I'm getting encouraging results for Wx::DocManager. When I click on
File -> Open, it automatically pops up a file selector for *.xml files. But
when I try and open one it crashes. I think this is because
wxView::OnCreate() isn't doing anything.

What I'd like to be able to do is something like this:

    my $ci_doc = Wx::ClassInfo::FindClass("My::Document");
    my $ci_view = Wx::ClassInfo::FindClass("My::View");

Although we might need a different method name so we can still handle c++
classes in the same way. My problem is that I don't know how to impliment
this. We'd need to override Wx::ClassInfo->CreateObject() or
wxClassInfo::m_objectConstructor.

I don't think I'm experienced enough to do this, but even if I were, I'd
want to make sure that I did it in a way that was compatible with wxPerl
development. 

If I can get this working I'll submit a patch to add the document/view
framework. If not, I'll give you what I've done so far so you don't need to
repeat what I've already done.

By the way Mattia, I'm interested to know what the wxPl...... classes are
for? Do we need something like that here? It looks like there are some
useful functions in cpp/helpers.cpp

Let me know if you want me to send you what I've got so far.

Thanks
Simon









BBCi at http://www.bbc.co.uk

This e-mail (and any attachments) is confidential and may contain 
personal views which are not the views of the BBC unless specifically 
stated.
If you have received it in error, please delete it from your system, do 
not use, copy or disclose the information in any way nor act in 
reliance on it and notify the sender immediately. Please note that the 
BBC monitors e-mails sent or received. Further communication will 
signify your consent to this.

[wxperl-users] Default background colour

[Jouke V. <jo...@pv...>]

Is there a name for the default background colour of a frame, a panel or 
whatever Wx::Window derrivate? I tried to set the background colour of a 
selected button, and tried to reset it back to its original value, and 
thought that would be wxLIGHT_GREY, but that seems to be a bit darker 
than the default backgroundcolour.

Jouke

Re: [wxperl-users] A few things + questions ..

[Jouke V. <jo...@pv...>]

Mattia Barbon wrote:

>>I'll make a start for this soon and would like to invite everyone to 
>>contribute. My experience is that the wxWindows docs themselves are not 
>>quite what you're looking for while building a wxPerl application, 
>>because it's not always clear wether a function or class is implemented 
>>
>The "implemented class" part is not that difficult; the "implemented function"
>part should be doable (automatically); which way should implemented/not
>implemented classes/dunctions be marked?
>
Well, a simple remark like 'wxPerl note: this function is not 
implemented'  under a function that is not implemented would do for me. 
And for the Validators: how they are implemented in wxPerl, and for 
something I stumbled into (from the top of my head, I don't have the 
code here): GetPlItemData (or something) for the Tree control, for which 
I can't find any documentation.
These are just things I can think of right now, but I'm sure there are 
more things that should be documented.

Another thing that wouldn't be a bad idea I personally think, is to have 
the possibility of having the documentation available in POD format. I 
don't have a problem with the HTML documentation, but I know there are a 
*lot* of Perl programmers who *love* POD , and would appreciate the 
availability of the docs in this format.

>>in wxPerl or not, what parameters wxPerl expects and so on.
>>
>If you could sketch some way to make parameter wxPerl expects,
>or whatever, clearer, *and* if this can be made automatically
>(i.e. by a script), I could incorporate this in the docs.
>
I have to think about this. I think of something like simply showing how 
you would call it from Perl, like:

$button = Wx::Button->new($parentid, etc etc)

Which is significantly different from how you would call the constructor 
in C++. It's all considered as common knowledge, but a starter would not 
always understand how to read the C++ docs.

Jouke

Re: [wxperl-users] GridSizer methods

[Jouke V. <jo...@pv...>]

 >
 >
 >C:\>perl -MWx -e "print Wx::wxVERSION_STRING(), qq{\n};$s
 >                  = Wx::GridSizer->new( 1, 2 ); $s->FitInside( )"
 >wxWindows 2.3.3
 >Usage: Wx::Sizer::FitInside(THIS, window) at -e line 1.
 >
 >What does this print for you?
 >
This prints the same for me. Weird. I must have tested it on my other
(Linux) box which has 2.2.9 on it...Sorry to bother you :/

Jouke

Re: [wxperl-users] wxIE & wxActiveX Test 1

[Jouke V. <jo...@pv...>]

>
>
>Other thing, how will be the structure for this, because wxIE & wxFlash (in
>the future) need wxActiveX, and this is only for Win32. We can put:
>Wx::Win32::IE , Wx::ActiveX::IE or Wx::IE. The class now is: Wx::IEHtmlWin.
>Since this 2 classes aren't in the wxWindows/contrib and are very basics, we
>can't follow wxWindows yet. For wxFlash I wnat to make something portable,
>for Win32 ActiveX, and Linux using the Netscape Plig-in.
>
I would vote for Wx::ActiveX::IE, and Wx::ActiveX::Flash and so on...

Jouke

Re: [wxperl-users] wxActiveX & Perl5.8-win32 binary

[Jouke V. <jo...@pv...>]

Many, Many kudos Graciliano!

Is it possible to publish a binary for Perl 5.6 (that is, the current
Activestate Perl distro I'm using)? I'd *love* to go and use this!

Jouke

Graciliano M. P. (Virtua Sites) wrote:

 >Hi,
 >
 >   To see the wxIE and wxActiveX demo you need Perl 5.8.0. You can 
donwload
 >the binary here:
 >http://wxperl.virtuasites.com.br/perl-5.8.0-win32.zip
 >
 >In the demo, inside wxActiveX.pm, I put only the command for wxIE. If you
 >want to play more do this:
 >
 >Change the line:
 >    my $activex = Wx::IEHtmlWin->new( $this , -1 , wxDefaultPosition ,
 >wxDefaultSize );
 >to:
 >  my $activex = Wx::ActiveX->new( $this , 
"ShockwaveFlash.ShockwaveFlash" ,
 >101 , wxDefaultPosition , wxDefaultSize );
 >
 >This will show the Shockwave Flash plug-in (press the right button of the
 >mouse to see).
 >
 >Here are other ProgID for ActiveX:
 >
 >QuickTime.QuickTime
 >WMPlayer.OCX
 >MediaPlayer.MediaPlayer.1
 >PDF.PdfCtrl
 >ShockwaveFlash.ShockwaveFlash
 >rmocx.RealPlayer G2 Control
 >MSCAL.Calendar
 >
 >Enjoy. :-P
 >Graciliano M. P.
 >
 >
 >
 >
 >
 >-------------------------------------------------------
 >This sf.net email is sponsored by: OSDN - Tired of that same old
 >cell phone?  Get a new here for FREE!
 >https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
 >_______________________________________________
 >wxperl-users mailing list
 >wxp...@li...
 >https://lists.sourceforge.net/lists/listinfo/wxperl-users
 >

[wxperl-users] wxActiveX & Perl5.8-win32 binary

[Graciliano M. P. \(V. Sites\) <gm...@vi...>]

Hi,

   To see the wxIE and wxActiveX demo you need Perl 5.8.0. You can donwload
the binary here:
http://wxperl.virtuasites.com.br/perl-5.8.0-win32.zip

In the demo, inside wxActiveX.pm, I put only the command for wxIE. If you
want to play more do this:

Change the line:
    my $activex = Wx::IEHtmlWin->new( $this , -1 , wxDefaultPosition ,
wxDefaultSize );
to:
  my $activex = Wx::ActiveX->new( $this , "ShockwaveFlash.ShockwaveFlash" ,
101 , wxDefaultPosition , wxDefaultSize );

This will show the Shockwave Flash plug-in (press the right button of the
mouse to see).

Here are other ProgID for ActiveX:

QuickTime.QuickTime
WMPlayer.OCX
MediaPlayer.MediaPlayer.1
PDF.PdfCtrl
ShockwaveFlash.ShockwaveFlash
rmocx.RealPlayer G2 Control
MSCAL.Calendar

Enjoy. :-P
Graciliano M. P.

[wxperl-users] wxIE & wxActiveX Test 1

[Graciliano M. P. \(V. Sites\) <gm...@vi...>]

Mattia,

  I have a gift for you! :-P
  I have sucess with the XS for wxActiveX and wxIE.

  You can get the source and binary at:
  http://wxperl.virtuasites.com.br/wxie-0.1.zip (1Mb)
  I put the basics of ./blib just for the peoples see the demo.

  I have ported only the Class creator for wxActiveX and wxIE, the other
commands I still have to do. I'm having some problems with the other cmds,
because the compiler crash. For example, if I add this in the XS (after)
Wx_IEHtmlWin::new:

bool
Wx_IEHtmlWin::LoadString( html )
  wxString html

  Compiler says "unexpected void" or something like that! I don't know what
I have to change in the .cpp or headers of the class to can port the other
functions.

After finish all the XS I will try to port Flash!... Another long way...

About the compiler, I used the VC6, too many changes to do this with MinGW.

Other thing, how will be the structure for this, because wxIE & wxFlash (in
the future) need wxActiveX, and this is only for Win32. We can put:
Wx::Win32::IE , Wx::ActiveX::IE or Wx::IE. The class now is: Wx::IEHtmlWin.
Since this 2 classes aren't in the wxWindows/contrib and are very basics, we
can't follow wxWindows yet. For wxFlash I wnat to make something portable,
for Win32 ActiveX, and Linux using the Netscape Plig-in.

If wxActiveX can be fully ported, we don't need to compile wxIE, we can make
a PM, just using Wx::ActiveX. Of course that the compiled way will be more
fast to run, but we need to try this to port and test all the ActiveX
resource. Now wxIE was inside the ActiveX.xs, but I think that we don't need
to split this in other ./ext, just in other XS.


Graciliano M. P.

Re: [wxperl-users] Wx::ListCtrl, sorting

[Mattia B. <mb...@ds...>]

> hello
> i whish to sort my ListCtrlItems.
> the ListCtrl is in report mode.
> 
> i noticed the SortItems function, but it only sorts the items after the
> ItemData, not after the labels.
> is there a function/a way to sort the items after the text?
Not directly, see below

> if not, what would be a good/fast way do do this myself?
> think that's a very mathematically problem.
I don't kno how fast is what I am proposing, but here is goes:
(this is pseudo-code, I think is enough to get you started,
 I'll provide real-code if you so wish)

when inserting, construct an hash to map between item data and
the item index

my $data = 0; # this needs to be unique!
my %map;

foreach ( ... things to insert ... ) {
   my $item = INSERT_ITEM;

   # this provides at least 2 * 10^9 unique data identifiers,
   # should be enough
   $list->SetItemData( $item, ++$data );
   $map{$data} = $item;
}

When sorting, use the hash to map from the data to the index:
sub callback {
	my( $f, $s ) = @_;
    my( $i1, $i2 ) = ( $map{$f}, $map{$s} );

    # now you can use $i1, $i2 to retrieve the labels
    # and compare them
}

HTH
Mattia