pnotepad.org forums

Programmer's Notepad Forums

1. 

   sven
   Member

   Hi,

   I tried to get the python scripting extension running using:
   - Python 2.5
   - boost 1.33.1
   - vc8
   - PN2 2.0.654-devel

   What happens:
   (1) I press a key (well, one that corresponds to a letter) within a document in PN
   (2) eventually DocSink::OnCharAdded(char c) is called
   (3) OnCharAdded calls onCharAdded in glue.py and passes the character + a reference to the current document

   But for some reason it throws an error message when the python script (glue.py) accesses a method of IDocumentPtr in function "onCharAdded".

   > Python error: <type 'exceptions.AttributeError'>: 'IDocument' object has no attribute 'GetCurrentScheme'

   I checked the document object: From within DocSink::OnCharAdded the method is accessible. This exception is also fired in case of any other method call of IDocument in python.

   Printing the other parameter passed, char c, on the debug output window works fine. Does anyone know how boost does the "object conversion" and where I can dig further to find out what's wrong?

   Why is boost necessary at all? Isn't there an another way to call python functions from within C++ without linking that massive (and IMMO not very elegantly written) library (even though we are only using the python relevant dll)?

   Cheers,
   Sven

   Posted 4 years ago #
2. 

   sven
   Member

   Okay, I found the mistake.

   glue.py and my vesion of PN2 (in particular pnpy) don't fit together. In mod_pn.cpp some cpp-functions are mapped to different names under python

   
.add_property("FileName", &IDocument::GetFileName)
.add_property("CurrentScheme", &IDocument::GetCurrentScheme)
.add_property("Modified", &IDocument::GetModified)
.add_property("CanSave", &IDocument::GetCanSave)


   Furthermore, some cpp-functions are mapped to properties, and thus have to be called differently under Python (e.g. in python: doc.CurrentScheme rather than doc.GetCurrentScheme()).

   Anyway, PN is a nice, little program and I'm looking forward to contribute some features.
   Good on you, Simon.

   Posted 4 years ago #
3. 

   simon
   PN Developer

   Yup, I've just fixed this in the source - good catch. I'm trying to gradually make anything that makes sense as a property a property, this makes sense to me but does cause a little breakage. User scripts causing errors like this will show the errors in the output pane. I should probably do this for built-ins too.

   Posted 4 years ago #
4. 

   simon
   PN Developer

   As for boost::python, it was one of the quickest ways to get up and running and expose objects in a nice way to python. I am still interested in experimenting with using swig instead (it would certainly reduce the build times) but at the moment I'd rather spend time on adding features and improving the extensions interface than on replacing a working implementation.

   If you're interested then I'd certainly welcome improvements.

   Posted 4 years ago #
5. 

   sven
   Member

   Well, now that I have accomplished to run the python script, I am not that keen on change the python object passing any more (if I bump into any better way to expose objects to python I'd certainly give it a go).

   My initial intention was to implement the Emacs indentation into PN2. I have it sort of running for .py files, but need to fine tune more in order to do it as smart as Emacs. Another interesting side-effect is that it also indents entire documents in one go...

   Posted 4 years ago #
6. 

   simon
   PN Developer

   Cool, please let use see the results!

   Posted 4 years ago #

RSS feed for this topic

Reply

You must log in to post.