On 6/22/06, Dan Shechter <[EMAIL PROTECTED]> wrote: > I can verify that :) > I was able to change beta7 <-> IronPythonTextBox to work together, but it's > not working on beta8 again....
Just fyi, I updated the project and .dll so it supports beta8. http://www.codeproject.com/useritems/irontextbox/irontextbox_src.zip http://www.codeproject.com/useritems/irontextbox/irontextbox_dll.zip On 6/22/06, Dino Viehland <[EMAIL PROTECTED]> wrote: > The good news here is that we're almost done w/ the breaking changes... If > you depend on the AST namespace we'll probably break you a little bit more in > the next release (all the public fields have become properties), but that > should be it. > This is good to know because I'll wait until then to actually schedule time to code a project I have been debating with myself to code or not (a more complete C# library of ConceptNet) just to save me some headaches in the long run. I am still undecided on how to handling this speed dilemma of mine but it just seems easier to use a mixture of IronPython, .Net, and script files instead of using just the .Net library for what I am doing. Someone today told me they are using XML-RPC.NET to communicate with ConceptNetXMLRPCServer.py but it sounded like the loading of the predicate files (which I have mention onlist previously) and creating the huge semantic map (Python List instances) was a hurdle for him also. I also need to look at this but I have not looked at XML-RPC.NET yet. He wasn't sure on how to handle the return values from some ConceptNet methods because he wasn't familiar with ConceptNet's methods and logic, I advised him that IronPython would probably help get those returning values from the server. -- Later, Joe _______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
