Re: [pygccxml-development] Another status report...

[Allen B. <al...@vr...>]

Matthias Baas wrote:

> Hi,
>
> unless I find some bugs I'm currently done with the selection stuff in 
> the experimental folder. With the current version I can now almost 
> create the same bindings as before with only slight adjustments to my 
> script. By default, the selection is similar to Allen's initial 
> version  but you can "activate" more flexible queries if desired to 
> get something that rather resembles my initial version.
> The next thing I need to get the same bindings as before is the 
> ability to add custom methods, I haven't checked yet if Allen's 
> addMethod() method still works or not, I'll try to do that tomorrow....
>
> I have also done some updates in the wiki:
>
> - There's one more goal I added and I even dared adding it to the top 
> of the list as I would consider that this is the "ultimate" goal for 
> me: pyplusplus  (and its API) should minimize the time it takes to 
> create the final bindings for a C++ library. Do you agree on that?

Yes, I agree with the condition that we mean minimize the time to create 
the final bindings assuming you already know something about 
boost.python and pyplusplus.  If the user doesn't know either tool yet 
then it may take a while to understand the basics.

>
> - To most of the issues I added an "Experimental version" section that 
> provides a short outline how the current code in the experimental 
> folder handles the respective issue. Of course, as this code is still 
> "experimental" this doesn't mean that this is how the issue will 
> definitely be resolved, but it's rather one proposal that exists in 
> code so that it can be tried out to see how well it works in practice.

Good idea.

>
> - I've removed my comments from the "What operations does the 
> selection interface provide?" topic as there is no general 
> disagreement on my part. But I added a new "open issue" about the 
> overloaded methods.

>
>
> How should we proceed now to resolve the issues in the wiki? There 
> still seems to be some disagreement, but I don't always see how an 
> alternative proposal would look like. So should we schedule another 
> chat session and go over those issues trying to find a resolution? Or 
> do you already have some comments about my latest changes? Could you 
> try them out? Do you need more documentation about the usage? Does the 
> selection work for you or were you confused when you tried using it? 
> (for me, it's still the overloaded methods that can lead to some 
> "surprises")

I really need to get some time to test the new interface.  I have gotten 
swamped by a couple of big projects and have not had time to devote to 
this in about a week. :(

>
> So what are your plans for the next couple of days? What does our next 
> "milestone" look like? I'd like to see the basic principles of 
> selection/decoration to be resolved so that we can move on with 
> thinking about features that have only been touched so far but that are no

I think a good milestone would be an API that would allow the 
capabilities that my original simple prototype allowed.  In other words, 
basic selection, exposing, renaming, and policy.  In a way this will 
really be the core capabilities that most users will need.

-Allen

> t yet implemented at all.
>
> - Matthias -
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting 
> language
> that extends applications into web and mobile media. Attend the live 
> webcast
> and join the prime developer group breaking into this new coding 
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> pygccxml-development mailing list
> pyg...@li...
> https://lists.sourceforge.net/lists/listinfo/pygccxml-development
>