2011/1/12 jelle feringa :
> That was totally overboard and out of line.
> I'm sorry drifting from the usual nuanced and constructive tone of the list.
But it's still bad idea.
Niki
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world dom
That was totally overboard and out of line.
I'm sorry drifting from the usual nuanced and constructive tone of the list.
-jelle
On Wed, Jan 12, 2011 at 1:28 PM, jelle feringa wrote:
> What if we could add customization at load time as well, like a pluggable
>> front-end. This could be generated
>
> What if we could add customization at load time as well, like a pluggable
> front-end. This could be generated python code that dynamically create a
> parallel module namespace and renames the classes and methods.
>
If I have a veto on this, than _forget_ about renaming the OCC API. I'm
violen
Henrik Rudstrom
On 10 January 2011 11:08, Thomas Paviot wrote:
> Jelle,
>
> I agree with most of your arguments. However, there are two points that
> have to be remained:
> - OCC is about to release the version 7.0 of its technology. If we want to
> stay sync with latest OCCT version ( that's
>
> I spent dozains (hundreds?) of hours playing with SWIG/pygccxml/OCC
> headers/compiling/testing etc. This is my advice for an efficient work:
>
> STEP 1:
> - the first thing to do is to work *manually* on the SWIG files (.i).
> Choose only a few basic modules (for instance Standard, gp, Geom)
Hey Thomas and Jelle,
Good to hear your opinions Jelle, and I see that code breakage is a major
issue.
Still i think there are ways to deal with that. One of course is to allow
customized wrapper generation, but i fear that would create a separation in
the community, and i wouldn't want to be the
Jelle,
I agree with most of your arguments. However, there are two points that have
to be remained:
- OCC is about to release the version 7.0 of its technology. If we want to
stay sync with latest OCCT version ( that's something that must be
discussed, but I think we should), this will introduce a
Thomas, Henrik,
Please do not be overly prudent with the SWIG operations.
I'm speaking here with regard to the semantic implications of some if what
you've been discussing
The *worst* thing a reasonably mature project can do is to dramatically
change its API ( from CamelCamps to pep_8 is dramati
2011/1/9 Henrik Rudstrom
>
> On 7 January 2011 23:20, Thomas Paviot wrote:
>
>> A follow up of Henrik's post dealing with pygccxml, forked from the so
>> long but fundamental 'Anyone seen this?' thread! And comply with Henrik's
>> wish to be 'clear what the purpose of the discussion actually i
On 7 January 2011 23:20, Thomas Paviot wrote:
> A follow up of Henrik's post dealing with pygccxml, forked from the so long
> but fundamental 'Anyone seen this?' thread! And comply with Henrik's wish
> to be 'clear what the purpose of the discussion actually is' . Hope this
> posit is clear eno
2011/1/7 Thomas Paviot
> A follow up of Henrik's post dealing with pygccxml, forked from the so long
> but fundamental 'Anyone seen this?' thread! And comply with Henrik's wish
> to be 'clear what the purpose of the discussion actually is' . Hope this
> posit is clear enough ;)
>
> Inserted my
11 matches
Mail list logo
