Hey, found it, too... but thanx anyway :-)so this implies that for having a ScedDocument we need to do the same procedure (having a separate file-tree of ScedDocument source files), right?
Anyone happens to know how to control gedit from a pipe or something?Ya know, in ScelDocument, e.g. opening a new document looks like this (correct me if I'm wrong): sclang[classes: ScelDocument, Emacs, EmacsInterface] ----FIFO---> elisp interpreter ----???----> emacs
Corresponding to this we should set up a FIFO for ScedDocument/Gedit:sclang[classes: ScedDocument, PythonInterface] ----FIFO---> gedit's already running python interpreter ----???----> gedit
Honestly, I have no idea on how to do this... perhaps thor or his ixi- collegue (as python and sc specialists), or even Артём (if you're listening, it would be cool to contact me :-)
regards Till On 30.11.2007, at 11:14, Dan Stowell wrote:
It's in linux/scel/sc/extDocument.sc 2007/11/30, Till Bovermann <tboverma@xxxxxxxxxxxxxxxxxxxxxxxx>:On 30.11.2007, at 01:42, nescivi wrote:On Thursday 29 November 2007 17:00:21 Till Bovermann wrote:Hey, someone happen to implement a sced-document?you? great idea! you have my full support (though this is mostly symbolical ;) )Since Text is symbolic, I really do appreciate having your support. One question evolving from looking at the Document implementation is: where (the hell) implements the emacs mode Document.implementationClass ? I only see these files where implementationClass is mentioned:SCClassLibrary/Common/GUI/Document.sc // comment on implementationClassSCClassLibrary/Platform/linux/LinuxPlatform.sc // usage SCClassLibrary/Platform/osx/extDocument.sc // osx SCClassLibrary/Platform/osx/OSXPlatform.sc // osx ?? Till _______________________________________________ Sc-devel mailing list Sc-devel@xxxxxxxxxxxxxxx http://www.create.ucsb.edu/mailman/listinfo/sc-devel-- http://www.mcld.co.uk _______________________________________________ Sc-devel mailing list Sc-devel@xxxxxxxxxxxxxxx http://www.create.ucsb.edu/mailman/listinfo/sc-devel