On Thu, Oct 22, 2009 at 12:06 PM, Francesco Montorsi
<f18m_cpp217...@yahoo.it> wrote:
> [sorry for not reading the rest of the thread; I may have missed something
> important]
>
> Hi John, Klaas,
>
> Klaas Holwerda ha scritto:
>> John Labenski wrote:
>>> The Python stuff looks easy to skip and we may have to write our own
>>> @beginWxLuaOnly sections.
> indeed. I think it's ok (for wx developers) to have the wx interface files
> patched upstream (in wx repo) with @beginWxLuaOnly sections since there are
> already wxPerl and wxPython equivalents.
Ok, we'll see. I was thinking that I would only patch them locally,
but if the wxWidgets people don't mind it would be nicer to have them
built in.
>> That is what i meant. I don't know how wxWidgets parses those
>> tags/things from the headers using Doxygen, and even if they do.
> if you want a simple C++ parser of the Doxygen (XML) output, please look in
> wxWidgets/utils/ifacecheck.
I've looked at that, it's nice, but I think it would be best to stick
to an all Lua solution. Lua tables are very powerful, easy to use, and
I will need to make a variety of structures.
I have started a parser in Lua and it loads the XML just fine, now it
is just a "simple" matter of converting the loaded table into tables
of classes, functions, enums, etc...
> The @beginWxPythonOnly sections are used only in the HTML output (and with the
> XML output they are not needed by ifacecheck: it only checks the consistency
> of
> the docs against the wx C++ headers, it knows nothing about python).
>
>> Without
>> adding something extra to the doxygen setup files, they don't show up as
>> extra tags in XML.
>> But if possible that solves most problems i think. Maybe just ask
>> Francesco, he knows.
> yes, adding in wx/docs/doxygen/Doxyfile_inc some stuff it should be possible
> to
> have those tags appear also in the XML output.
>
>> still need %rename for overloaded
>>> functions that take int/double/enum values since Lua treats them all
>>> as double so we can't tell what function the user wanted to call. How
>>> can we stick that into the interface file so it ends up in the doxygen
>>> XML? I'm sure there's a way...
I tried to get rid of as many of the %rename functions as possible, it
looks like they are mostly used to distinguish between functions that
return a wxSize or wxPoint and identically named functions that take
int* values and set them. For example:
For wxWindow
%rename GetClientSizeWH virtual void GetClientSize() const // C++
func GetClientSize(int* w, int* h)
wxSize GetClientSize() const
> can you make an example of which info would you like to stuff inside e.g. the
> following doxygen XML snippet:
>
> <memberdef kind="function"
> id="classwx_about_dialog_info_1a2bde3b28eb55f653e8229ea534775c24"
> prot="public"
> static="no" const="no" explicit="no" inline="no" virt="non-virtual">
> <type>void</type>
> <definition>void wxAboutDialogInfo::SetDevelopers</definition>
> <argsstring>(const wxArrayString &developers)</argsstring>
> <name>SetDevelopers</name>
Something like this, which is not necessary for this function, see
above where it would be used.
<rename>SetDevelopersForLua</rename>
Thanks,
John
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
wxlua-users mailing list
wxlua-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxlua-users
