Discussion:
Qt collider crash
(too old to reply)
Josh Parmenter
2011-05-09 20:03:09 UTC
Permalink
Just built with Qt, and I get a crash when I try to bring up main help. Start, apple-D and then:

Process: SuperCollider [69932]
Path: /Users/joshp/src/supercollider/buildqt/SuperCollider/SuperCollider.app/Contents/MacOS/SuperCollider
Identifier: net.sourceforge.supercollider
Version: SuperCollider version 3.1 (-Unofficial Build-)
Code Type: X86-64 (Native)
Parent Process: launchd [194]

Date/Time: 2011-05-09 13:02:17.277 -0700
OS Version: Mac OS X 10.6.7 (10J869)
Report Version: 6

Interval Since Last Report: 262863 sec
Crashes Since Last Report: 2
Per-App Interval Since Last Report: 480975 sec
Per-App Crashes Since Last Report: 2
Anonymous UUID: DFFD0287-0CBC-4EBB-BDD0-A66E144F54CD

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 QtGui 0x0000000101e7bf11 -[QCocoaWindow canBecomeMainWindow] + 17
1 com.apple.AppKit 0x00007fff8735b320 -[NSWindow _changeKeyAndMainLimitedOK:] + 251
2 com.apple.AppKit 0x00007fff8735b184 -[NSWindow _makeKeyRegardlessOfVisibility] + 111
3 com.apple.AppKit 0x00007fff8735b0ea -[NSWindow makeKeyAndOrderFront:] + 24
4 QtGui 0x0000000101e70989 QWidgetPrivate::show_sys() + 665
5 QtGui 0x0000000101f27328 QWidgetPrivate::show_helper() + 408
6 QtGui 0x0000000101f2888f QWidget::setVisible(bool) + 511
7 libQtCollider.dylib 0x00000001002dedac QWidgetProxy::customEvent(QEvent*) + 108
8 QtCore 0x000000010339a437 QObject::event(QEvent*) + 1159
9 QtGui 0x0000000101ecdddd QApplicationPrivate::notify_helper(QObject*, QEvent*) + 189
10 QtGui 0x0000000101ed4dfe QApplication::notify(QObject*, QEvent*) + 2094
11 QtCore 0x00000001032b1dec QCoreApplication::notifyInternal(QObject*, QEvent*) + 124
12 QtCore 0x000000010338d4eb QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 731
13 com.apple.CoreFoundation 0x00007fff8619a401 __CFRunLoopDoSources0 + 1361
14 com.apple.CoreFoundation 0x00007fff861985f9 __CFRunLoopRun + 873
15 com.apple.CoreFoundation 0x00007fff86197dbf CFRunLoopRunSpecific + 575
16 com.apple.HIToolbox 0x00007fff80d907ee RunCurrentEventLoopInMode + 333
17 com.apple.HIToolbox 0x00007fff80d90551 ReceiveNextEventCommon + 148
18 com.apple.HIToolbox 0x00007fff80d904ac BlockUntilNextEventMatchingListInMode + 59
19 com.apple.AppKit 0x00007fff87365e64 _DPSNextEvent + 718
20 com.apple.AppKit 0x00007fff873657a9 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155
21 com.apple.AppKit 0x00007fff8732b48b -[NSApplication run] + 395
22 com.apple.AppKit 0x00007fff873241a8 NSApplicationMain + 364
23 net.sourceforge.supercollider 0x0000000100008394 start + 52

Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x00007fff86d1d12a kevent + 10
1 libSystem.B.dylib 0x00007fff86d1effd _dispatch_mgr_invoke + 154
2 libSystem.B.dylib 0x00007fff86d1ecd4 _dispatch_queue_invoke + 185
3 libSystem.B.dylib 0x00007fff86d1e7fe _dispatch_worker_thread2 + 252
4 libSystem.B.dylib 0x00007fff86d1e128 _pthread_wqthread + 353
5 libSystem.B.dylib 0x00007fff86d1dfc5 start_wqthread + 13

Thread 2:
0 libSystem.B.dylib 0x00007fff86d1df4a __workq_kernreturn + 10
1 libSystem.B.dylib 0x00007fff86d1e35c _pthread_wqthread + 917
2 libSystem.B.dylib 0x00007fff86d1dfc5 start_wqthread + 13

Thread 3:
0 libSystem.B.dylib 0x00007fff86d1df4a __workq_kernreturn + 10
1 libSystem.B.dylib 0x00007fff86d1e35c _pthread_wqthread + 917
2 libSystem.B.dylib 0x00007fff86d1dfc5 start_wqthread + 13

Thread 4:
0 libSystem.B.dylib 0x00007fff86d47e76 recvfrom + 10
1 net.sourceforge.supercollider 0x0000000100019067 SC_UdpInPort::Run() + 87
2 libSystem.B.dylib 0x00007fff86d3d4f6 _pthread_start + 331
3 libSystem.B.dylib 0x00007fff86d3d3a9 thread_start + 13

Thread 5:
0 libSystem.B.dylib 0x00007fff86d3ef8a __semwait_signal + 10
1 libSystem.B.dylib 0x00007fff86d3ee19 nanosleep + 148
2 libSystem.B.dylib 0x00007fff86d8bdf0 sleep + 61
3 net.sourceforge.supercollider 0x000000010000a43a resyncThread(void*) + 26
4 libSystem.B.dylib 0x00007fff86d3d4f6 _pthread_start + 331
5 libSystem.B.dylib 0x00007fff86d3d3a9 thread_start + 13

Thread 6:
0 libSystem.B.dylib 0x00007fff86d3ef8a __semwait_signal + 10
1 libSystem.B.dylib 0x00007fff86d42da1 _pthread_cond_wait + 1286
2 net.sourceforge.supercollider 0x000000010000c020 TempoClock::Run() + 80
3 libSystem.B.dylib 0x00007fff86d3d4f6 _pthread_start + 331
4 libSystem.B.dylib 0x00007fff86d3d3a9 thread_start + 13

Thread 7:
0 libSystem.B.dylib 0x00007fff86d3ef8a __semwait_signal + 10
1 libSystem.B.dylib 0x00007fff86d42da1 _pthread_cond_wait + 1286
2 net.sourceforge.supercollider 0x000000010000be73 schedRunFunc(void*) + 643
3 libSystem.B.dylib 0x00007fff86d3d4f6 _pthread_start + 331
4 libSystem.B.dylib 0x00007fff86d3d3a9 thread_start + 13

Thread 8: com.apple.CFSocket.private
0 libSystem.B.dylib 0x00007fff86d47e52 select$DARWIN_EXTSN + 10
1 com.apple.CoreFoundation 0x00007fff861ba498 __CFSocketManager + 824
2 libSystem.B.dylib 0x00007fff86d3d4f6 _pthread_start + 331
3 libSystem.B.dylib 0x00007fff86d3d3a9 thread_start + 13

Thread 9:
0 libSystem.B.dylib 0x00007fff86d3ef8a __semwait_signal + 10
1 libSystem.B.dylib 0x00007fff86d42da1 _pthread_cond_wait + 1286
2 QtWebKit 0x00000001010dc5b8 WTF::TCMalloc_PageHeap::scavengerThread() + 520
3 QtWebKit 0x00000001010dc659 WTF::TCMalloc_PageHeap::runScavengerThread(void*) + 9
4 libSystem.B.dylib 0x00007fff86d3d4f6 _pthread_start + 331
5 libSystem.B.dylib 0x00007fff86d3d3a9 thread_start + 13

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x000003ffffffffff rdx: 0x0000000105150648
rdi: 0x0000000103b58760 rsi: 0x0000000103b58760 rbp: 0x00007fff5fbfdd10 rsp: 0x00007fff5fbfdd10
r8: 0x00007fff70c552a0 r9: 0x0000000000000000 r10: 0x00007fff861a1c00 r11: 0x0000000103810280
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000103947fd0 r15: 0x0000000103a42f90
rip: 0x0000000101e7bf11 rfl: 0x0000000000010246 cr2: 0x0000000000000020

Binary Images:
0x100000000 - 0x100144ff7 +net.sourceforge.supercollider SuperCollider version 3.1 (-Unofficial Build-) <640B49CC-88BF-3FA8-B6B8-2B5719C07FA5> /Users/joshp/src/supercollider/buildqt/SuperCollider/SuperCollider.app/Contents/MacOS/SuperCollider
0x1001f2000 - 0x100285fff +libscsynth.1.dylib ??? (???) <D2D385E8-A6FC-3E44-82D5-DC60F56761B4> /Users/joshp/src/supercollider/buildqt/SuperCollider/SuperCollider.app/Contents/MacOS/libscsynth.1.dylib
0x1002d6000 - 0x100339fef +libQtCollider.dylib ??? (???) <AAFD515C-0287-3007-B30D-89A67E487015> /Users/joshp/src/supercollider/buildqt/SuperCollider/SuperCollider.app/Contents/MacOS/libQtCollider.dylib
0x100385000 - 0x1003d5ff7 com.apple.audio.midi.CoreMIDI 1.7.1 (42) <E7DBCE93-A637-ABA2-B623-6A76B82EE243> /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
0x1003fd000 - 0x1016b1fe7 +QtWebKit 4.7.0 (compatibility 4.7.0) <EB42430D-A00A-1D1B-F334-790BA4856799> /Users/joshp/src/supercollider/buildqt/SuperCollider/SuperCollider.app/Contents/Frameworks/QtWebKit.framework/Versions/4/QtWebKit
0x101e4c000 - 0x10281ffef +QtGui 4.7.0 (compatibility 4.7.0) <BD43BAAD-873D-45E8-3605-1E344992BB51> /Users/joshp/src/supercollider/buildqt/SuperCollider/SuperCollider.app/Contents/Frameworks/QtGui.framework/Versions/4/QtGui
0x102ac7000 - 0x102f6dfef +QtXmlPatterns 4.7.0 (compatibility 4.7.0) <F0784045-8812-A9F7-9A95-1D1FF4CCA374> /Users/joshp/src/supercollider/buildqt/SuperCollider/SuperCollider.app/Contents/Frameworks/QtXmlPatterns.framework/Versions/4/QtXmlPatterns
0x1030f0000 - 0x103208fe7 +QtNetwork 4.7.0 (compatibility 4.7.0) <DCC6577E-1F20-A97A-A583-E2BE4E3C036B> /Users/joshp/src/supercollider/buildqt/SuperCollider/SuperCollider.app/Contents/Frameworks/QtNetwork.framework/Versions/4/QtNetwork
0x103260000 - 0x1034e5fef +QtCore 4.7.0 (compatibility 4.7.0) <AEA4A1B9-46B8-7621-8D00-555040D89C56> /Users/joshp/src/supercollider/buildqt/SuperCollider/SuperCollider.app/Contents/Frameworks/QtCore.framework/Versions/4/QtCore
0x103579000 - 0x1035c1fef +phonon 4.4.0 (compatibility 4.4.0) <5305CFDF-53AD-03ED-8FE7-3E969C24774B> /Users/joshp/src/supercollider/buildqt/SuperCollider/SuperCollider.app/Contents/Frameworks/phonon.framework/Versions/4/phonon
0x1035e8000 - 0x103667fff +QtDBus 4.7.0 (compatibility 4.7.0) <C348BEAA-1135-76C6-DD71-0F5D580BF8CC> /Users/joshp/src/supercollider/buildqt/SuperCollider/SuperCollider.app/Contents/Frameworks/QtDBus.framework/Versions/4/QtDBus
0x10368b000 - 0x1036c8fef +QtXml 4.7.0 (compatibility 4.7.0) <F60B541D-A596-8964-5D2A-FD2F04781A94> /Users/joshp/src/supercollider/buildqt/SuperCollider/SuperCollider.app/Contents/Frameworks/QtXml.framework/Versions/4/QtXml
0x1184b0000 - 0x1184b4fff com.apple.audio.AudioIPCPlugIn 1.1.6 (1.1.6) <D934B45A-1406-1C78-0F55-E9C5216C269D> /System/Library/Extensions/AudioIPCDriver.kext/Contents/Resources/AudioIPCPlugIn.bundle/Contents/MacOS/AudioIPCPlugIn
0x1184bb000 - 0x1184c1fff com.apple.audio.AppleHDAHALPlugIn 1.9.9 (1.9.9f12) <E6F7EBE4-E981-DFB8-E778-EDE7580E7993> /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn
0x11d0e1000 - 0x11d10bff7 +com.grame.JackRouter JackRouter (0.9.3) <9F656F5C-CED6-0ADC-E8E4-E449DB627D3F> /Library/Audio/Plug-Ins/HAL/JackRouter.plugin/Contents/MacOS/JackRouter
0x11d122000 - 0x11d153fff +Jackmp ??? (???) <2860D1CE-3B25-8A07-CCBD-BC5F1ED0F11D> /Library/Frameworks/Jackmp.framework/Versions/A/Jackmp
0x11d1df000 - 0x11d1eafff +libqgenericbearer.dylib ??? (???) <77E42517-88E7-40A2-D92A-5B7B089FBF6C> /Developer/Applications/Qt/plugins/bearer/libqgenericbearer.dylib
0x11d1f3000 - 0x11d1f9ff7 +libqgif.dylib ??? (???) <F8CB03CC-3851-DA80-968C-1D1FC1E5197E> /Developer/Applications/Qt/plugins/imageformats/libqgif.dylib
0x11db79000 - 0x11dc91fe7 +QtNetwork 4.7.0 (compatibility 4.7.0) <DCC6577E-1F20-A97A-A583-E2BE4E3C036B> /Library/Frameworks/QtNetwork.framework/Versions/4/QtNetwork
0x11dce9000 - 0x11df6efef +QtCore 4.7.0 (compatibility 4.7.0) <AEA4A1B9-46B8-7621-8D00-555040D89C56> /Library/Frameworks/QtCore.framework/Versions/4/QtCore
0x11e002000 - 0x11e030fff +libqnmbearer.dylib ??? (???) <CFF3C625-D804-B5CD-B715-FF9FAD2D004D> /Developer/Applications/Qt/plugins/bearer/libqnmbearer.dylib
0x11e042000 - 0x11e0c1fff +QtDBus 4.7.0 (compatibility 4.7.0) <C348BEAA-1135-76C6-DD71-0F5D580BF8CC> /Library/Frameworks/QtDBus.framework/Versions/4/QtDBus
0x11e0e5000 - 0x11e122fef +QtXml 4.7.0 (compatibility 4.7.0) <F60B541D-A596-8964-5D2A-FD2F04781A94> /Library/Frameworks/QtXml.framework/Versions/4/QtXml
0x11e13c000 - 0x11e15efe7 +libqcncodecs.dylib ??? (???) <E3FAACB3-B9A7-3BB8-8B45-E3C450436E36> /Developer/Applications/Qt/plugins/codecs/libqcncodecs.dylib
0x11e163000 - 0x11e18bfe7 +libqjpcodecs.dylib ??? (???) <D64CAB9C-C91D-F3DD-4B42-C2F9482CA849> /Developer/Applications/Qt/plugins/codecs/libqjpcodecs.dylib
0x11e195000 - 0x11e1a7fe7 +libqkrcodecs.dylib ??? (???) <011B8662-24B6-5C33-1138-CD0007D3EF41> /Developer/Applications/Qt/plugins/codecs/libqkrcodecs.dylib
0x11e1ab000 - 0x11e1d0fff +libqtwcodecs.dylib ??? (???) <6FE7BE1D-B0B3-A318-16BB-3A661F4ABF60> /Developer/Applications/Qt/plugins/codecs/libqtwcodecs.dylib
0x11e5e5000 - 0x11e5ebff7 +libqico.dylib ??? (???) <429D55EC-A54C-0310-A174-522A052A7610> /Developer/Applications/Qt/plugins/imageformats/libqico.dylib
0x11e5f1000 - 0x11e5f5ff7 +libqsvg.dylib ??? (???) <5453C211-5954-7D66-78B8-303A14895612> /Developer/Applications/Qt/plugins/imageformats/libqsvg.dylib
0x11e640000 - 0x11f013fef +QtGui 4.7.0 (compatibility 4.7.0) <BD43BAAD-873D-45E8-3605-1E344992BB51> /Library/Frameworks/QtGui.framework/Versions/4/QtGui
0x11f2bb000 - 0x11f2f6fef +libqjpeg.dylib ??? (???) <C100CEBC-C6E4-7B3E-5C4B-7844CC654571> /Developer/Applications/Qt/plugins/imageformats/libqjpeg.dylib
0x11f2ff000 - 0x11f353fe7 +libqmng.dylib ??? (???) <F1A5F92E-A83B-40CA-1438-09F12FC1054B> /Developer/Applications/Qt/plugins/imageformats/libqmng.dylib
0x11f364000 - 0x11f3b3ff7 +QtSvg 4.7.0 (compatibility 4.7.0) <4627660F-3919-4F7D-C8C9-9A75243704FF> /Library/Frameworks/QtSvg.framework/Versions/4/QtSvg
0x11f3d4000 - 0x11f429fe7 +libqtiff.dylib ??? (???) <46DAD411-1D8C-2BFE-40DE-CDDF4C53B768> /Developer/Applications/Qt/plugins/imageformats/libqtiff.dylib
0x7fff5fc00000 - 0x7fff5fc3bdef dyld 132.1 (???) <486E6C61-1197-CC7C-2197-82CE505102D7> /usr/lib/dyld
0x7fff80003000 - 0x7fff8003efff com.apple.AE 496.4 (496.4) <55AAD5CA-7160-7899-1C68-562ED8160DF7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x7fff8003f000 - 0x7fff80054ff7 com.apple.LangAnalysis 1.6.6 (1.6.6) <1AE1FE8F-2204-4410-C94E-0E93B003BEDA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
0x7fff80055000 - 0x7fff80213fff libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <2C6ECACF-CD56-1714-6F63-CB6F5EE7A1E2> /usr/lib/libicucore.A.dylib
0x7fff80214000 - 0x7fff80259fff com.apple.CoreMediaIOServices 134.0 (1160) <BA22EA4A-4572-749A-4FE0-1323E0B6F6F3> /System/Library/PrivateFrameworks/CoreMediaIOServices.framework/Versions/A/CoreMediaIOServices
0x7fff8025a000 - 0x7fff80373fef libGLProgrammability.dylib ??? (???) <C4BB281B-629D-08ED-2991-3D51671B0B02> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib
0x7fff80374000 - 0x7fff8038fff7 com.apple.openscripting 1.3.1 (???) <9D50701D-54AC-405B-CC65-026FCB28258B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
0x7fff80390000 - 0x7fff803a6fff com.apple.ImageCapture 6.0.2 (6.0.2) <06E4103B-9BE4-7EAD-B532-89FC5EB06ED4> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
0x7fff803e7000 - 0x7fff803eaff7 libCoreVMClient.dylib ??? (???) <00C97B96-8D3B-45EB-F503-DB49712DC42D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
0x7fff80407000 - 0x7fff80418fff com.apple.DSObjCWrappers.Framework 10.6 (134) <3C08225D-517E-2822-6152-F6EB13A4ADF9> /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWrappers
0x7fff80419000 - 0x7fff80419ff7 com.apple.Carbon 150 (152) <191B4F4B-8D06-796B-CA0C-782F06DD7BC7> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x7fff8041a000 - 0x7fff8043dfff com.apple.opencl 12.3.6 (12.3.6) <42FA5783-EB80-1168-4015-B8C68F55842F> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
0x7fff8043e000 - 0x7fff80869fef com.apple.RawCamera.bundle 3.6.4 (561) <C4AB0054-B2C8-246E-0F17-98F4BD5BE94C> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
0x7fff8089a000 - 0x7fff80918ff7 com.apple.CoreText 3.151.8 (???) <5DCD6BD9-63FB-767E-5993-5AEBE890145B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText
0x7fff80919000 - 0x7fff80b09fef com.apple.JavaScriptCore 6533.20 (6533.20.20) <0AA8B101-C02C-0858-84BC-4E4D397E0231> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
0x7fff80b3c000 - 0x7fff80cabfe7 com.apple.QTKit 7.6.6 (1756.15) <B35EDB1D-FCB0-1D40-629E-6ACB56D57C68> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
0x7fff80d62000 - 0x7fff81060fff com.apple.HIToolbox 1.6.5 (???) <AD1C18F6-51CB-7E39-35DD-F16B1EB978A8> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x7fff81061000 - 0x7fff810e3fff com.apple.QuickLookUIFramework 2.3 (327.6) <9093682A-0E2D-7D27-5F22-C96FD00AE970> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/QuickLookUI
0x7fff810e4000 - 0x7fff81136ff7 com.apple.HIServices 1.8.2 (???) <7C91D07D-FA20-0882-632F-0CAE4FAC2B79> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
0x7fff81137000 - 0x7fff8114dfe7 com.apple.MultitouchSupport.framework 207.10 (207.10) <458F0259-6EDC-16BA-E6AA-1CEED002D188> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
0x7fff8114e000 - 0x7fff81192fe7 com.apple.ImageCaptureCore 1.0.4 (1.0.4) <F4ED3329-1A86-EB10-CFC2-999D8699B5E6> /System/Library/Frameworks/ImageCaptureCore.framework/Versions/A/ImageCaptureCore
0x7fff81193000 - 0x7fff81204ff7 com.apple.AppleVAFramework 4.10.23 (4.10.23) <3304268B-A93D-9F79-09C0-AA9081406352> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
0x7fff81205000 - 0x7fff8124cfff com.apple.QuickLookFramework 2.3 (327.6) <11DFB135-24A6-C0BC-5B97-ECE352A4B488> /System/Library/Frameworks/QuickLook.framework/Versions/A/QuickLook
0x7fff81269000 - 0x7fff812d1fff com.apple.MeshKitRuntime 1.1 (49.2) <4D3045D0-0D50-7053-3A05-0AECE86E39F8> /System/Library/PrivateFrameworks/MeshKit.framework/Versions/A/Frameworks/MeshKitRuntime.framework/Versions/A/MeshKitRuntime
0x7fff812d2000 - 0x7fff8138bfff libsqlite3.dylib 9.6.0 (compatibility 9.0.0) <2C5ED312-E646-9ADE-73A9-6199A2A43150> /usr/lib/libsqlite3.dylib
0x7fff81714000 - 0x7fff81726fe7 libsasl2.2.dylib 3.15.0 (compatibility 3.0.0) <76B83C8D-8EFE-4467-0F75-275648AFED97> /usr/lib/libsasl2.2.dylib
0x7fff81727000 - 0x7fff81748fff libresolv.9.dylib 41.0.0 (compatibility 1.0.0) <9F322F47-0584-CB7D-5B73-9EBD670851CD> /usr/lib/libresolv.9.dylib
0x7fff81749000 - 0x7fff8187eff7 com.apple.audio.toolbox.AudioToolbox 1.6.6 (1.6.6) <AFAB42A2-A3A8-83D8-D583-613625706690> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x7fff81921000 - 0x7fff81970fef libTIFF.dylib ??? (???) <F0F7F0B7-7253-F88F-9E2D-FA3770143758> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x7fff81971000 - 0x7fff81977ff7 com.apple.DiskArbitration 2.3 (2.3) <857F6E43-1EF4-7D53-351B-10DE0A8F992A> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x7fff81978000 - 0x7fff8198cff7 com.apple.speech.synthesis.framework 3.10.35 (3.10.35) <63C87CF7-56B3-4038-8136-8C26E96AD42F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x7fff8198d000 - 0x7fff81992fff libGFXShared.dylib ??? (???) <878C429B-44D4-875C-1A35-4FD8C6152695> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
0x7fff81993000 - 0x7fff819c6fff libTrueTypeScaler.dylib ??? (???) <6EFBF3B7-E4D5-E6AE-5A7D-22F37E288737> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib
0x7fff81a07000 - 0x7fff81a07ff7 com.apple.quartzframework 1.5 (1.5) <B182B579-BCCE-81BF-8DA2-9E0B7BDF8516> /System/Library/Frameworks/Quartz.framework/Versions/A/Quartz
0x7fff81a3e000 - 0x7fff81a4dfff com.apple.opengl 1.6.12 (1.6.12) <29482652-1E44-1C47-428F-1209AA65336D> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x7fff81a4e000 - 0x7fff81a53fff libGIF.dylib ??? (???) <1B9DCB7F-CD1D-B23F-8AC6-5292B94A4D0E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x7fff81a54000 - 0x7fff81a83ff7 com.apple.quartzfilters 1.6.0 (1.6.0) <9CECB4FC-1CCF-B8A2-B935-5888B21CBEEF> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzFilters.framework/Versions/A/QuartzFilters
0x7fff81ab9000 - 0x7fff81b9ffef com.apple.DesktopServices 1.5.10 (1.5.10) <B7E00D85-F971-D85B-0217-482E15E9E924> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
0x7fff81ba0000 - 0x7fff81cdefff com.apple.CoreData 102.1 (251) <9DFE798D-AA52-6A9A-924A-DA73CB94D81A> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x7fff81d47000 - 0x7fff81d47ff7 com.apple.vecLib 3.6 (vecLib 3.6) <96FB6BAD-5568-C4E0-6FA7-02791A58B584> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x7fff81dd3000 - 0x7fff81e0cfef libcups.2.dylib 2.8.0 (compatibility 2.0.0) <F8E0672F-C0B4-B161-E50D-A1405D14F21C> /usr/lib/libcups.2.dylib
0x7fff81e0d000 - 0x7fff81eeafff com.apple.vImage 4.1 (4.1) <C3F44AA9-6F71-0684-2686-D3BBC903F020> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x7fff81f83000 - 0x7fff8220bfef com.apple.security 6.1.2 (55002) <015C9A08-3D07-9462-8E91-DB1924349621> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff82212000 - 0x7fff82261ff7 com.apple.DirectoryService.PasswordServerFramework 6.1 (6.1) <01B370FB-D524-F660-3826-E85B7F0D85CD> /System/Library/PrivateFrameworks/PasswordServer.framework/Versions/A/PasswordServer
0x7fff82265000 - 0x7fff82287ff7 libexpat.1.dylib 7.2.0 (compatibility 7.0.0) <8EC31253-B585-D05E-F35D-AE3292FB790B> /usr/lib/libexpat.1.dylib
0x7fff82288000 - 0x7fff826ccfef libLAPACK.dylib 219.0.0 (compatibility 1.0.0) <E14EC4C6-B055-A4AC-B971-42AB644E4A7C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
0x7fff826cd000 - 0x7fff826cdff7 com.apple.Cocoa 6.6 (???) <68B0BE46-6E24-C96F-B341-054CF9E8F3B6> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x7fff826ce000 - 0x7fff826d4ff7 com.apple.CommerceCore 1.0 (9) <4C66D962-91B5-F25C-A6FF-DFD5F924A0DD> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCore.framework/Versions/A/CommerceCore
0x7fff826d5000 - 0x7fff826d7fff com.apple.print.framework.Print 6.1 (237.1) <CA8564FB-B366-7413-B12E-9892DA3C6157> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
0x7fff826d8000 - 0x7fff826dafff libRadiance.dylib ??? (???) <73257486-8E94-E758-1A5A-5B521F27EE12> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x7fff826db000 - 0x7fff82725ff7 com.apple.Metadata 10.6.3 (507.15) <5170FCE0-ED6C-2E3E-AB28-1DDE3F628FC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x7fff827da000 - 0x7fff827deff7 libCGXType.A.dylib 545.0.0 (compatibility 64.0.0) <49E6AF5D-AF9B-67CF-A6B8-C79F6BA8A627> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib
0x7fff827df000 - 0x7fff827f0ff7 libz.1.dylib 1.2.3 (compatibility 1.0.0) <97019C74-161A-3488-41EC-A6CA8738418C> /usr/lib/libz.1.dylib
0x7fff827f1000 - 0x7fff82919ff7 com.apple.MediaToolbox 0.484.20 (484.20) <628A7245-7ADE-AD47-3368-CF8EDCA6CC1C> /System/Library/PrivateFrameworks/MediaToolbox.framework/Versions/A/MediaToolbox
0x7fff8291a000 - 0x7fff8297cfe7 com.apple.datadetectorscore 2.0 (80.7) <5F0F865C-A80F-FE7F-7DF8-894A4A99EACA> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
0x7fff829d6000 - 0x7fff82d73fe7 com.apple.QuartzCore 1.6.3 (227.36) <6FD8E129-135E-2F89-E9F0-A3CD0C6FCEF1> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x7fff82d74000 - 0x7fff82dbdfef libGLU.dylib ??? (???) <0FCD57C5-D7AA-F2DD-D2EC-C1C8B931F65C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x7fff82dbe000 - 0x7fff82dbeff7 com.apple.Accelerate.vecLib 3.6 (vecLib 3.6) <4CCE5D69-F1B3-8FD3-1483-E0271DB2CCF3> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
0x7fff82dbf000 - 0x7fff82e3cfef libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <35ECA411-2C08-FD7D-11B1-1B7A04921A5C> /usr/lib/libstdc++.6.dylib
0x7fff82e88000 - 0x7fff82ec1ff7 com.apple.MeshKit 1.1 (49.2) <832A074D-7601-F7C9-6D3A-E1C58965C3A1> /System/Library/PrivateFrameworks/MeshKit.framework/Versions/A/MeshKit
0x7fff82ec2000 - 0x7fff82ec2ff7 com.apple.CoreServices 44 (44) <DC7400FB-851E-7B8A-5BF6-6F50094302FB> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fff82ec3000 - 0x7fff830fefef com.apple.imageKit 2.0.3 (1.0) <5D18C246-303A-6580-9DC9-79BE79467C95> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit
0x7fff830ff000 - 0x7fff8319ffff com.apple.LaunchServices 362.2 (362.2) <A8EDC37C-1D40-5ED0-49BE-90EF110A6B3A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x7fff831a0000 - 0x7fff8322cfef SecurityFoundation ??? (???) <F43FDB02-CAA5-F8FF-C8D7-6665E7403ECE> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
0x7fff8322d000 - 0x7fff83252ff7 com.apple.CoreVideo 1.6.2 (45.6) <E138C8E7-3CB6-55A9-0A2C-B73FE63EA288> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x7fff83253000 - 0x7fff8395006f com.apple.CoreGraphics 1.545.0 (???) <F0A5F62D-4C66-5B1F-4F13-322932915901> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x7fff83a5f000 - 0x7fff83a85fe7 libJPEG.dylib ??? (???) <AD42F658-7C32-EEE5-8341-A8EE6476BF46> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x7fff83a86000 - 0x7fff83aa6ff7 com.apple.DirectoryService.Framework 3.6 (621.11) <AD76C757-6701-BDB5-631E-1CB77D669586> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService
0x7fff83aa7000 - 0x7fff83d11fef com.apple.QuartzComposer 4.2 ({156.28}) <60956AE3-2B2D-A0B7-9D92-3EE33D3A7051> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzComposer.framework/Versions/A/QuartzComposer
0x7fff83f2d000 - 0x7fff83f55fff com.apple.DictionaryServices 1.1.2 (1.1.2) <E9269069-93FA-2B71-F9BA-FDDD23C4A65E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
0x7fff83fd4000 - 0x7fff840f5fe7 libcrypto.0.9.8.dylib 0.9.8 (compatibility 0.9.8) <48AEAFE1-21F4-B3C8-4199-35AD5E8D0613> /usr/lib/libcrypto.0.9.8.dylib
0x7fff840f6000 - 0x7fff841b3fff com.apple.CoreServices.OSServices 359 (359) <8F509D8D-4C94-9A1C-3A87-5B775D9F6075> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x7fff841b4000 - 0x7fff841b7ff7 com.apple.securityhi 4.0 (36638) <87868A3E-9341-1078-F00C-5E5972F01A4A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
0x7fff841b8000 - 0x7fff84218fe7 com.apple.framework.IOKit 2.0 (???) <D107CB8A-5182-3AC4-35D0-07068A695C05> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff8422f000 - 0x7fff842b4ff7 com.apple.print.framework.PrintCore 6.3 (312.7) <CDFE82DD-D811-A091-179F-6E76069B432D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
0x7fff842b7000 - 0x7fff842b8ff7 com.apple.TrustEvaluationAgent 1.1 (1) <5952A9FA-BC2B-16EF-91A7-43902A5C07B6> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent
0x7fff842e3000 - 0x7fff8432aff7 com.apple.coreui 2 (114) <923E33CC-83FC-7D35-5603-FB8F348EE34B> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x7fff8432b000 - 0x7fff84339ff7 libkxld.dylib ??? (???) <27713C39-0E51-8F5A-877B-C5539C96A520> /usr/lib/system/libkxld.dylib
0x7fff8433a000 - 0x7fff843f0fff libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <99CB3A0F-64CF-1D16-70CD-8AED2EF06C30> /usr/lib/libobjc.A.dylib
0x7fff843f1000 - 0x7fff844a1fff edu.mit.Kerberos 6.5.11 (6.5.11) <085D80F5-C9DC-E252-C21B-03295E660C91> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x7fff844a2000 - 0x7fff84563fef com.apple.ColorSync 4.6.6 (4.6.6) <EC6C8119-23F6-A96E-47A3-5CD31E462AE3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
0x7fff84564000 - 0x7fff845a5fff com.apple.SystemConfiguration 1.10.5 (1.10.2) <FB39F09C-57BB-D8CC-348D-93E00C602F7D> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x7fff847e9000 - 0x7fff84853fe7 libvMisc.dylib 268.0.1 (compatibility 1.0.0) <AF0EA96D-000F-8C12-B952-CB7E00566E08> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
0x7fff848c8000 - 0x7fff84bfcfff com.apple.CoreServices.CarbonCore 861.34 (861.34) <B5680539-CB31-6C6D-C0AD-606D4D46E7F5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x7fff84c16000 - 0x7fff84c1dfff com.apple.OpenDirectory 10.6 (10.6) <4200CFB0-DBA1-62B8-7C7C-91446D89551F> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
0x7fff84c1e000 - 0x7fff84c8aff7 com.apple.CorePDF 1.3 (1.3) <FF2F3F1B-D1D6-684C-B174-6A455E04FF91> /System/Library/PrivateFrameworks/CorePDF.framework/Versions/A/CorePDF
0x7fff84c8b000 - 0x7fff84c9afff com.apple.NetFS 3.2.2 (3.2.2) <7CCBD70E-BF31-A7A7-DB98-230687773145> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x7fff84da4000 - 0x7fff84e3eff7 com.apple.ApplicationServices.ATS 275.15.1 (???) <55B528A6-0C88-6CB8-152B-A34A440FACFE> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
0x7fff84e3f000 - 0x7fff84ef6ff7 com.apple.Bluetooth 2.4.0 (2.4.0f1) <3F3F8097-B4A7-D69E-733E-968BB1B152BA> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
0x7fff84ef7000 - 0x7fff84f86fff com.apple.PDFKit 2.5.1 (2.5.1) <38BEE9BB-3716-49BA-7E14-687FE9E066EB> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framework/Versions/A/PDFKit
0x7fff84f93000 - 0x7fff85c0efef com.apple.WebCore 6533.21 (6533.21.1) <A7433C61-B507-BDB0-9CA8-1A3A2A699B2F> /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore
0x7fff85c0f000 - 0x7fff85c50ff7 com.apple.CoreMedia 0.484.20 (484.20) <42F3B74A-F886-33A0-40EE-8399B12BD32A> /System/Library/PrivateFrameworks/CoreMedia.framework/Versions/A/CoreMedia
0x7fff85c8c000 - 0x7fff85cc9ff7 libFontRegistry.dylib ??? (???) <8C69F685-3507-1B8F-51AD-6183D5E88979> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
0x7fff85dd1000 - 0x7fff85e1dfff libauto.dylib ??? (???) <F7221B46-DC4F-3153-CE61-7F52C8C293CF> /usr/lib/libauto.dylib
0x7fff85f7f000 - 0x7fff85f80fff com.apple.MonitorPanelFramework 1.3.0 (1.3.0) <5062DACE-FCE7-8E41-F5F6-58821778629C> /System/Library/PrivateFrameworks/MonitorPanel.framework/Versions/A/MonitorPanel
0x7fff85f81000 - 0x7fff8608bff7 com.apple.MeshKitIO 1.1 (49.2) <C19D0CCD-1DCB-7EDE-76FA-BF74079AFC6A> /System/Library/PrivateFrameworks/MeshKit.framework/Versions/A/Frameworks/MeshKitIO.framework/Versions/A/MeshKitIO
0x7fff8608c000 - 0x7fff8608cff7 com.apple.ApplicationServices 38 (38) <10A0B9E9-4988-03D4-FC56-DDE231A02C63> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x7fff86096000 - 0x7fff8614bfe7 com.apple.ink.framework 1.3.3 (107) <8C36373C-5473-3A6A-4972-BC29D504250F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
0x7fff8614c000 - 0x7fff862c3fe7 com.apple.CoreFoundation 6.6.4 (550.42) <770C572A-CF70-168F-F43C-242B9114FCB5> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff862c4000 - 0x7fff863dbfef libxml2.2.dylib 10.3.0 (compatibility 10.0.0) <1B27AFDD-DF87-2009-170E-C129E1572E8B> /usr/lib/libxml2.2.dylib
0x7fff863dc000 - 0x7fff864a7fff ColorSyncDeprecated.dylib 4.6.0 (compatibility 1.0.0) <D3242F40-AA41-022C-1345-6BFC0E560460> /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ColorSync.framework/Versions/A/Resources/ColorSyncDeprecated.dylib
0x7fff8659a000 - 0x7fff86752fef com.apple.ImageIO.framework 3.0.4 (3.0.4) <EFB373AE-FE02-40C4-ABDC-09D61AFD25EA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x7fff86753000 - 0x7fff86760fe7 libCSync.A.dylib 545.0.0 (compatibility 64.0.0) <45B5B514-7CEB-38A9-F34A-1D96F010EC42> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x7fff86761000 - 0x7fff8676aff7 com.apple.DisplayServicesFW 2.3.0 (283) <5C8FEF26-FBA5-2AC6-C484-336594C637DC> /System/Library/PrivateFrameworks/DisplayServices.framework/Versions/A/DisplayServices
0x7fff8676b000 - 0x7fff867eafe7 com.apple.audio.CoreAudio 3.2.6 (3.2.6) <6D8AD3F7-409D-512C-C5BE-66C64D1B8F3E> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x7fff867eb000 - 0x7fff8682cfef com.apple.QD 3.36 (???) <5DC41E81-32C9-65B2-5528-B33E934D5BB4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
0x7fff8682d000 - 0x7fff8682efff liblangid.dylib ??? (???) <EA4D1607-2BD5-2EE2-2A3B-632EEE5A444D> /usr/lib/liblangid.dylib
0x7fff8685d000 - 0x7fff8691ffef libFontParser.dylib ??? (???) <363E2A8A-CEFE-9A74-E677-C240B27A4FC6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
0x7fff86920000 - 0x7fff86951fff libGLImage.dylib ??? (???) <6925991A-9B1B-B9FA-645A-807F9BCC3DE7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x7fff86b0f000 - 0x7fff86b3aff7 libxslt.1.dylib 3.24.0 (compatibility 3.0.0) <87A0B228-B24A-C426-C3FB-B40D7258DD49> /usr/lib/libxslt.1.dylib
0x7fff86b3b000 - 0x7fff86cb9ff7 com.apple.WebKit 6533.21 (6533.21.1) <E954BB9E-51DC-9B68-5312-E1507329A9B3> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
0x7fff86cba000 - 0x7fff86d02ff7 libvDSP.dylib 268.0.1 (compatibility 1.0.0) <98FC4457-F405-0262-00F7-56119CA107B6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
0x7fff86d03000 - 0x7fff86ec4fff libSystem.B.dylib 125.2.10 (compatibility 1.0.0) <9BAEB2F2-B485-6349-E1AB-637FE12EE770> /usr/lib/libSystem.B.dylib
0x7fff86ec5000 - 0x7fff86fbdff7 libiconv.2.dylib 7.0.0 (compatibility 7.0.0) <44AADE50-15BC-BC6B-BEF0-5029A30766AC> /usr/lib/libiconv.2.dylib
0x7fff86fbe000 - 0x7fff86fc4ff7 IOSurface ??? (???) <EAD87C9F-BADC-7116-4ADD-0B0679459D24> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
0x7fff871ac000 - 0x7fff871c9ff7 libPng.dylib ??? (???) <0C232C1E-49C8-F7A9-9634-DF2BDA1AB722> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
0x7fff871ca000 - 0x7fff8729cfe7 com.apple.CFNetwork 454.11.12 (454.11.12) <B1C9008A-4A5D-609D-5D10-C93DAD6FFB4C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x7fff8729d000 - 0x7fff872e0ff7 libRIP.A.dylib 545.0.0 (compatibility 64.0.0) <2C596A24-8B86-79D6-1A8E-5E8FFB6A1558> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x7fff872e1000 - 0x7fff872e4fff com.apple.help 1.3.1 (41) <E311A81E-9870-A430-1E16-AFF6C92CE6E5> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
0x7fff8731c000 - 0x7fff8731cff7 com.apple.Accelerate 1.6 (Accelerate 1.6) <15DF8B4A-96B2-CB4E-368D-DEC7DF6B62BB> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x7fff8731d000 - 0x7fff87321ff7 libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <95718673-FEEE-B6ED-B127-BCDBDB60D4E5> /usr/lib/system/libmathCommon.A.dylib
0x7fff87322000 - 0x7fff87d18fff com.apple.AppKit 6.6.7 (1038.35) <9F4DF818-9DB9-98DA-490C-EF29EA757A97> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff87d19000 - 0x7fff88523fe7 libBLAS.dylib 219.0.0 (compatibility 1.0.0) <EEE5CE62-9155-6559-2AEA-05CED0F5B0F1> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x7fff88524000 - 0x7fff88538fff libGL.dylib ??? (???) <0FA671EB-6FA0-BA97-C00A-C42247C22B26> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x7fff88539000 - 0x7fff8853aff7 com.apple.audio.units.AudioUnit 1.6.6 (1.6.6) <BE4E577D-87EC-8FD0-5341-AE99CE4ADC99> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x7fff8853b000 - 0x7fff887befe7 com.apple.Foundation 6.6.6 (751.53) <476E617B-B59B-53DE-991D-98C1993BCBCE> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff8886d000 - 0x7fff88d71fe7 com.apple.VideoToolbox 0.484.20 (484.20) <8B6B82D2-350B-E9D3-5433-51453CDA65B4> /System/Library/PrivateFrameworks/VideoToolbox.framework/Versions/A/VideoToolbox
0x7fff88d72000 - 0x7fff88d88fef libbsm.0.dylib ??? (???) <83676D2E-23CD-45CD-BE5C-35FCFFBBBDBB> /usr/lib/libbsm.0.dylib
0x7fff88ebd000 - 0x7fff88f4dfff com.apple.SearchKit 1.3.0 (1.3.0) <3403E658-A54E-A79A-12EB-E090E8743984> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x7fff89004000 - 0x7fff89059ff7 com.apple.framework.familycontrols 2.0.2 (2020) <F09541B6-5E28-1C01-C1AE-F6A2508670C7> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyControls
0x7fff8905a000 - 0x7fff89073fff com.apple.CFOpenDirectory 10.6 (10.6) <CCF79716-7CC6-2520-C6EB-A4F56AD0A207> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
0x7fff89216000 - 0x7fff89221ff7 com.apple.speech.recognition.framework 3.11.1 (3.11.1) <3D65E89B-FFC6-4AAF-D5CC-104F967C8131> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
0x7fff89222000 - 0x7fff89227ff7 com.apple.CommonPanels 1.2.4 (91) <4D84803B-BD06-D80E-15AE-EFBE43F93605> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
0x7fffffe00000 - 0x7fffffe01fff libSystem.B.dylib ??? (???) <9BAEB2F2-B485-6349-E1AB-637FE12EE770> /usr/lib/libSystem.B.dylib

Model: MacBookPro6,2, BootROM MBP61.0057.B0C, 2 processors, Intel Core i7, 2.66 GHz, 8 GB, SMC 1.58f16
Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 512 MB
Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.10.131.36.9)
Bluetooth: Version 2.4.0f1, 2 service, 12 devices, 1 incoming serial ports
Network Service: Built-in Ethernet, Ethernet, en0
Serial ATA Device: ST9500420ASG, 465.76 GB
Serial ATA Device: MATSHITADVD-R UJ-898
USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfd100000
USB Device: Hub, 0x05ac (Apple Inc.), 0x9122, 0xfd130000
USB Device: Keyboard Hub, 0x05ac (Apple Inc.), 0x1006, 0xfd131000
USB Device: USB Optical Mouse, 0x046d (Logitech Inc.), 0xc018, 0xfd131100
USB Device: Apple Keyboard, 0x05ac (Apple Inc.), 0x0220, 0xfd131200
USB Device: Apple Cinema HD Display, 0x05ac (Apple Inc.), 0x921e, 0xfd132000
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0xfd120000
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8507, 0xfd110000
USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfa100000
USB Device: iPad, 0x05ac (Apple Inc.), 0x129f, 0xfa140000
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0236, 0xfa120000
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8218, 0xfa113000
USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403, 0xfa130000
FireWire Device: Vendor 0x1F2 Device 0x101800, 0x1F2, Up to 400 Mb/sec

******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/

“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono
*/


_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
Josh Parmenter
2011-05-09 20:06:57 UTC
Permalink
Also - I did another build and turned off the library fixup. Then I get this with the main help (screenshot attached).

Josh
Jakob Leben
2011-05-09 20:18:44 UTC
Permalink
Post by Josh Parmenter
Also - I did another build and turned off the library fixup. Then I get
this with the main help (screenshot attached).
Hmm, interesting. Either text is not rendered or text color is transparent.
Do you see any text if you click-drag over the help page so as to select
text? And if you try copy-pasting selection somewhere else?
Josh Parmenter
2011-05-09 20:22:37 UTC
Permalink
looks like copy / paste works.

Josh
Post by Josh Parmenter
Also - I did another build and turned off the library fixup. Then I get this with the main help (screenshot attached).
Hmm, interesting. Either text is not rendered or text color is transparent. Do you see any text if you click-drag over the help page so as to select text? And if you try copy-pasting selection somewhere else?
******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/

“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono
*/
Jonatan Liljedahl
2011-05-09 21:02:18 UTC
Permalink
Could you try this:

- make sure the bundle fixup is turned off
- in your build folder:
make clean
rm -rf SuperCollider
make && make install

then open SuperCollider/SuperCollider.app and try again.

did it help? (I've noticed that the build/SuperCollider folder is
sometimes not updated when files and/or build-options changed)

/Jonatan
Post by Josh Parmenter
looks like copy / paste works.
Josh
Post by Josh Parmenter
Also - I did another build and turned off the library fixup. Then I get
this with the main help (screenshot attached).
Hmm, interesting. Either text is not rendered or text color is transparent. Do
you see any text if you click-drag over the help page so as to select text?
And if you try copy-pasting selection somewhere else?
******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/
“Every composer – at all times and in all cases – gives his own interpretation
of how modern society is structured: whether actively or passively, consciously
or unconsciously, he makes choices in this regard. He may be conservative or he
may subject himself to continual renewal; or he may strive for a revolutionary,
historical or social palingenesis." - Luigi Nono
*/
_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
Josh Parmenter
2011-05-09 21:13:58 UTC
Permalink
nope - same problem :(

Josh
Post by Jonatan Liljedahl
- make sure the bundle fixup is turned off
make clean
rm -rf SuperCollider
make && make install
then open SuperCollider/SuperCollider.app and try again.
did it help? (I've noticed that the build/SuperCollider folder is sometimes not updated when files and/or build-options changed)
/Jonatan
Post by Josh Parmenter
looks like copy / paste works.
Josh
Post by Josh Parmenter
Also - I did another build and turned off the library fixup. Then I get
this with the main help (screenshot attached).
Hmm, interesting. Either text is not rendered or text color is transparent. Do
you see any text if you click-drag over the help page so as to select text?
And if you try copy-pasting selection somewhere else?
******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/
“Every composer – at all times and in all cases – gives his own interpretation
of how modern society is structured: whether actively or passively, consciously
or unconsciously, he makes choices in this regard. He may be conservative or he
may subject himself to continual renewal; or he may strive for a revolutionary,
historical or social palingenesis." - Luigi Nono
*/
_______________________________________________
sc-dev mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/

“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono
*/


_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
Jonatan Liljedahl
2011-05-09 21:20:20 UTC
Permalink
You could try and tweak the font in your local Help/scdoc.css and see if
it is related. As Jakob said, it seems either the text is hidden or
transparent.. very strange. You could also try to rename scdoc.css
temporarily and see if the text is visible then.

/Jonatan
Post by Josh Parmenter
nope - same problem :(
Josh
Post by Jonatan Liljedahl
- make sure the bundle fixup is turned off
make clean
rm -rf SuperCollider
make&& make install
then open SuperCollider/SuperCollider.app and try again.
did it help? (I've noticed that the build/SuperCollider folder is sometimes not updated when files and/or build-options changed)
/Jonatan
Post by Josh Parmenter
looks like copy / paste works.
Josh
Post by Josh Parmenter
Also - I did another build and turned off the library fixup. Then I get
this with the main help (screenshot attached).
Hmm, interesting. Either text is not rendered or text color is transparent. Do
you see any text if you click-drag over the help page so as to select text?
And if you try copy-pasting selection somewhere else?
******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/
“Every composer – at all times and in all cases – gives his own interpretation
of how modern society is structured: whether actively or passively, consciously
or unconsciously, he makes choices in this regard. He may be conservative or he
may subject himself to continual renewal; or he may strive for a revolutionary,
historical or social palingenesis." - Luigi Nono
*/
_______________________________________________
sc-dev mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/
“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono
*/
_______________________________________________
sc-dev mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
Tim Blechmann
2011-05-09 21:20:36 UTC
Permalink
Post by Josh Parmenter
nope - same problem :(
btw, has anyone tried with the qt packages from macport?
Post by Josh Parmenter
Post by Jonatan Liljedahl
- make sure the bundle fixup is turned off
make clean
rm -rf SuperCollider
make && make install
--
tim-xpEK/MU0Hawdnm+***@public.gmane.org
http://tim.klingt.org

Your mind will answer most questions if you learn to relax and wait
for the answer.
William S. Burroughs
Dan Stowell
2011-05-10 10:10:26 UTC
Permalink
Post by Tim Blechmann
Post by Josh Parmenter
nope - same problem :(
btw, has anyone tried with the qt packages from macport?
it's what I've always been using.

Dan

_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
Lucas Samaruga
2011-05-09 23:07:35 UTC
Permalink
Post by Josh Parmenter
(screenshot attached).
But why your server windows has a dark gray background?
Josh Parmenter
2011-05-09 23:52:11 UTC
Permalink
I set the background color of my windows in startup.rtf

Josh
Post by Josh Parmenter
(screenshot attached).
But why your server windows has a dark gray background?
******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/

“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono
*/
Lucas Samaruga
2011-05-10 02:21:35 UTC
Permalink
Post by Josh Parmenter
I set the background color of my windows in startup.rtf
and how do you did it? I want to try it to see if the problem is related.
Josh Parmenter
2011-05-10 03:04:14 UTC
Permalink
{
Server.local.window.view.background_(Color.grey(0.1, 0.9));
Server.local.window.view.children.do({arg me, i;
(me.isKindOf(SCStaticText)).if({
(me.background != Color.white).if({
me.stringColor_(Color.white)
})
})
});
Server.local.window.bounds_(Rect(654, 14, 288, 98));
Server.internal.window.view.background_(Color.grey(0.1, 0.9));
Server.internal.window.view.children.do({arg me, i;
(me.isKindOf(SCStaticText)).if({
(me.background != Color.white).if({
me.stringColor_(Color.white)
})
})
});

Server.internal.window.bounds_(Rect(948, 14, 288, 98));
}.defer(0.1);

I just commented those lines out, and Help still doesn't show up correctly. I actually commented out all my customization, and there wasn't any difference.

And with fixing up the path, it still crashes. But it really only seems to be Help related. My other GUI things all pop open just fine.

Josh
Post by Josh Parmenter
I set the background color of my windows in startup.rtf
and how do you did it? I want to try it to see if the problem is related.
******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/

“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono
*/
Jakob Leben
2011-05-09 20:16:11 UTC
Permalink
Post by Josh Parmenter
Just built with Qt, and I get a crash when I try to bring up main help
Yes, the library fixup messes with Qt libs, you have been warned :)
Josh Parmenter
2011-05-09 20:21:06 UTC
Permalink
So there is no way to pass around a Qt build at all? ack.

Josh
Post by Josh Parmenter
Just built with Qt, and I get a crash when I try to bring up main help
Yes, the library fixup messes with Qt libs, you have been warned :)
******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/

“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono
*/
Jakob Leben
2011-05-09 20:32:30 UTC
Permalink
Post by Josh Parmenter
So there is no way to pass around a Qt build at all? ack.
I already suggested to read [1] and try out the macdeployqt tool distributed
with Qt SDK. I can't try it myself since I don't have a Mac.

[1] http://doc.qt.nokia.com/latest/deployment-mac.html
Jonatan Liljedahl
2011-05-09 21:00:20 UTC
Permalink
It's quite easy to install Qt, it's just a download and click. So if you
want to provide binaries to friends/students, I'd suggest that approach.

Even if I know that people expect apps on OS X to have no dependencies,
I would prefer if we can at least provide an SC.app without Qt bundled
as a download alternative for people who already have Qt installed.

/Jonatan
Post by Josh Parmenter
So there is no way to pass around a Qt build at all? ack.
Josh
Post by Josh Parmenter
Just built with Qt, and I get a crash when I try to bring up main help
Yes, the library fixup messes with Qt libs, you have been warned :)
******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/
“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono
*/
_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
Josh Parmenter
2011-05-10 15:02:07 UTC
Permalink
As for telling users to install dependencies, the reason (I would suggest) to avoid this is that as each new version of Qt comes out, there may be things that break. Then, you guys, the Qt knowledgeable among us, get tasked with maintaining SC for various versions of Qt. But let's say you can't, and someone downloads a new version of Qt that breaks SC, then we tell them 'Oh - don't download the new Qt, you need to get this Qt', well, this starts getting tedious and at some point, someone coming to a new program will just say 'why bother'. I can understand why you might see this as a weakness of Mac users, etc., but keeping a version of Qt that we know works with SC bundled in with SC, while there are headaches on OUR end at the moment, will really keep headaches for new users from happening later (or, at least, it will let them have headaches about learning a new language, not just getting the thing to start up).

No - as I mentioned yesterday, it seemed that most of my regular GUI stuff worked fine for path-fixed-up Qt stuff, it was just Help that seemed to be bonked. Could this be a bug in how Help is using the GUI?

Josh
It's quite easy to install Qt, it's just a download and click. So if you want to provide binaries to friends/students, I'd suggest that approach.
Even if I know that people expect apps on OS X to have no dependencies, I would prefer if we can at least provide an SC.app without Qt bundled as a download alternative for people who already have Qt installed.
/Jonatan
Post by Josh Parmenter
So there is no way to pass around a Qt build at all? ack.
Josh
Post by Josh Parmenter
Just built with Qt, and I get a crash when I try to bring up main help
Yes, the library fixup messes with Qt libs, you have been warned :)
******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/
“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono
*/
_______________________________________________
sc-dev mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/

“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono
*/


_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
Jonatan Liljedahl
2011-05-10 16:05:46 UTC
Permalink
Post by Josh Parmenter
As for telling users to install dependencies, the reason (I would suggest) to avoid this is that as each new version of Qt comes out, there may be things that break. Then, you guys, the Qt knowledgeable among us, get tasked with maintaining SC for various versions of Qt. But let's say you can't, and someone downloads a new version of Qt that breaks SC, then we tell them 'Oh - don't download the new Qt, you need to get this Qt', well, this starts getting tedious and at some point, someone coming to a new program will just say 'why bother'. I can understand why you might see this as a weakness of Mac users, etc., but keeping a version of Qt that we know works with SC bundled in with SC, while there are headaches on OUR end at the moment, will really keep headaches for new users from happen
ing later (or, at least, it will let them have headaches about learning a new language, not just getting the thing to start up).

Yes, I totally see the point with bundling Qt. But I think there might
be users who prefer to download SC.app without Qt, if they have Qt
already installed.
Post by Josh Parmenter
No - as I mentioned yesterday, it seemed that most of my regular GUI stuff worked fine for path-fixed-up Qt stuff, it was just Help that seemed to be bonked. Could this be a bug in how Help is using the GUI?
If I remember correctly, there were other bugs as well introduced by the
fixup bundle. HelpBrowser doesn't do anything strange or special as far
as I can see. In any case, since the behaviour changes when using fixup
bundle, it clearly shows that fixup bundle does more than fixing the
link paths - it breaks something.

Also, there are other problems with Qt + SC.app, for example Dialog not
working and hanging some thread. I guess we have to choose if we should
try to fix this or get rid of cocoa and rewrite SC.app in Qt - which
means we would have a true cross platform SC app.

Jakob, any news regarding the Qt + cocoa problems?

But, whatever we choose - the fixup bundle thing must be fixed, since Qt
would be bundled also in a non-cocoa-only-Qt SC.app.

/Jonatan
Post by Josh Parmenter
Josh
It's quite easy to install Qt, it's just a download and click. So if you want to provide binaries to friends/students, I'd suggest that approach.
Even if I know that people expect apps on OS X to have no dependencies, I would prefer if we can at least provide an SC.app without Qt bundled as a download alternative for people who already have Qt installed.
/Jonatan
Post by Josh Parmenter
So there is no way to pass around a Qt build at all? ack.
Josh
Post by Josh Parmenter
Just built with Qt, and I get a crash when I try to bring up main help
Yes, the library fixup messes with Qt libs, you have been warned :)
******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/
“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono
*/
_______________________________________________
sc-dev mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/
“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono
*/
_______________________________________________
sc-dev mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
Dan Stowell
2011-05-10 16:09:26 UTC
Permalink
Post by Josh Parmenter
As for telling users to install dependencies, the reason (I would suggest)
to avoid this is that as each new version of Qt comes out, there may be
things that break. Then, you guys, the Qt knowledgeable among us, get tasked
with maintaining SC for various versions of Qt. But let's say you can't, and
someone downloads a new version of Qt that breaks SC, then we tell them 'Oh
- don't download the new Qt, you need to get this Qt', well, this starts
getting tedious and at some point, someone coming to a new program will just
say 'why bother'. I can understand why you might see this as a weakness of
Mac users, etc., but keeping a version of Qt that we know works with SC
bundled in with SC, while there are headaches on OUR end at the moment, will
really keep headaches for new users from happening later (or, at least, it
will let them have headaches about learning a new language, not just getting
the thing to start up).
Yes, I totally see the point with bundling Qt. But I think there might be
users who prefer to download SC.app without Qt, if they have Qt already
installed.
Yes. But you agree, I hope, that these will be a small minority of
users, that they're probably relatively tech-savvy already if they're
worrying about that sort of thing, and therefore it's OK to leave them
till last and put our efforts into trying to help the others?
Post by Josh Parmenter
No - as I mentioned yesterday, it seemed that most of my regular GUI stuff
worked fine for path-fixed-up Qt stuff, it was just Help that seemed to be
bonked. Could this be a bug in how Help is using the GUI?
If I remember correctly, there were other bugs as well introduced by the
fixup bundle. HelpBrowser doesn't do anything strange or special as far as I
can see. In any case, since the behaviour changes when using fixup bundle,
it clearly shows that fixup bundle does more than fixing the link paths - it
breaks something.
Also, there are other problems with Qt + SC.app, for example Dialog not
working and hanging some thread. I guess we have to choose if we should try
to fix this or get rid of cocoa and rewrite SC.app in Qt - which means we
would have a true cross platform SC app.
Jakob, any news regarding the Qt + cocoa problems?
But, whatever we choose - the fixup bundle thing must be fixed, since Qt
would be bundled also in a non-cocoa-only-Qt SC.app.
/Jonatan
Post by Josh Parmenter
Josh
Post by Jonatan Liljedahl
It's quite easy to install Qt, it's just a download and click. So if you
want to provide binaries to friends/students, I'd suggest that approach.
Even if I know that people expect apps on OS X to have no dependencies, I
would prefer if we can at least provide an SC.app without Qt bundled as a
download alternative for people who already have Qt installed.
/Jonatan
Post by Josh Parmenter
So there is no way to pass around a Qt build at all? ack.
Josh
Post by Josh Parmenter
Just built with Qt, and I get a crash when I try to bring up main help
Yes, the library fixup messes with Qt libs, you have been warned :)
******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/
“Every composer – at all times and in all cases – gives his own
interpretation of how modern society is structured: whether actively or
passively, consciously or unconsciously, he makes choices in this regard. He
may be conservative or he may subject himself to continual renewal; or he
may strive for a revolutionary, historical or social palingenesis." - Luigi
Nono
*/
_______________________________________________
sc-dev mailing list
http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/
“Every composer – at all times and in all cases – gives his own
interpretation of how modern society is structured: whether actively or
passively, consciously or unconsciously, he makes choices in this regard. He
may be conservative or he may subject himself to continual renewal; or he
may strive for a revolutionary, historical or social palingenesis." - Luigi
Nono
*/
_______________________________________________
sc-dev mailing list
http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
_______________________________________________
sc-dev mailing list
http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
--
http://www.mcld.co.uk

_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
Jonatan Liljedahl
2011-05-10 16:11:55 UTC
Permalink
Post by Dan Stowell
Yes, I totally see the point with bundling Qt. But I think there might be
users who prefer to download SC.app without Qt, if they have Qt already
installed.
Yes. But you agree, I hope, that these will be a small minority of
users, that they're probably relatively tech-savvy already if they're
worrying about that sort of thing, and therefore it's OK to leave them
till last and put our efforts into trying to help the others?
Absolutely. These users might even build their SC from source in most
cases, where they simply can disable the Qt bundling.

/Jonatan

_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
Josh Parmenter
2011-05-10 16:10:53 UTC
Permalink
Yes, I totally see the point with bundling Qt. But I think there might be users who prefer to download SC.app without Qt, if they have Qt already installed.
True - tricky...
Post by Josh Parmenter
No - as I mentioned yesterday, it seemed that most of my regular GUI stuff worked fine for path-fixed-up Qt stuff, it was just Help that seemed to be bonked. Could this be a bug in how Help is using the GUI?
If I remember correctly, there were other bugs as well introduced by the fixup bundle. HelpBrowser doesn't do anything strange or special as far as I can see. In any case, since the behaviour changes when using fixup bundle, it clearly shows that fixup bundle does more than fixing the link paths - it breaks something.
Good point.
Also, there are other problems with Qt + SC.app, for example Dialog not working and hanging some thread. I guess we have to choose if we should try to fix this or get rid of cocoa and rewrite SC.app in Qt - which means we would have a true cross platform SC app.
Yes... THAT would be rad.
Jakob, any news regarding the Qt + cocoa problems?
But, whatever we choose - the fixup bundle thing must be fixed, since Qt would be bundled also in a non-cocoa-only-Qt SC.app.
I might have time later to try and run install_name_tool by hand and see if the problems are still there (so - I'll try fixing up the bundle by hand and if that is OK, perhaps we can just do it as a script ourselves).

More later.

Josh
_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
Jonatan Liljedahl
2011-05-10 16:22:20 UTC
Permalink
Post by Josh Parmenter
Also, there are other problems with Qt + SC.app, for example Dialog not working and hanging some thread. I guess we have to choose if we should try to fix this or get rid of cocoa and rewrite SC.app in Qt - which means we would have a true cross platform SC app.
Yes... THAT would be rad.
I think it wouldn't be too much work. The important thing is the
Document class implementation, then a main menu and a postwindow. I
would have a go but my Qt and C++ skills are not very high (coming from
a lot of developing-hours with GTK and C), so I leave this task to Jakob :)
Post by Josh Parmenter
Jakob, any news regarding the Qt + cocoa problems?
But, whatever we choose - the fixup bundle thing must be fixed, since Qt would be bundled also in a non-cocoa-only-Qt SC.app.
I might have time later to try and run install_name_tool by hand and see if the problems are still there (so - I'll try fixing up the bundle by hand and if that is OK, perhaps we can just do it as a script ourselves).
More later.
Ok, good! That will give us a hint on what's happening.

Btw, I remember now that when bundling Qt, it seems like it sometimes
tries to load both the bundled Qt and the system-wide installed one.
(shows up in Console.app) This might very well be part of the problem..
No idea why it happens, though..

/Jonatan

_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
Miguel Negrao
2011-05-10 17:01:47 UTC
Permalink
Post by Josh Parmenter
Yes, I totally see the point with bundling Qt. But I think there might be users who prefer to download SC.app without Qt, if they have Qt already installed.
True - tricky...
Post by Josh Parmenter
No - as I mentioned yesterday, it seemed that most of my regular GUI stuff worked fine for path-fixed-up Qt stuff, it was just Help that seemed to be bonked. Could this be a bug in how Help is using the GUI?
If I remember correctly, there were other bugs as well introduced by the fixup bundle. HelpBrowser doesn't do anything strange or special as far as I can see. In any case, since the behaviour changes when using fixup bundle, it clearly shows that fixup bundle does more than fixing the link paths - it breaks something.
Good point.
Also, there are other problems with Qt + SC.app, for example Dialog not working and hanging some thread. I guess we have to choose if we should try to fix this or get rid of cocoa and rewrite SC.app in Qt - which means we would have a true cross platform SC app.
Yes... THAT would be rad.
I’m curious, besides Jakob does anyone else have knowledge of Qt inner workings or has capability and willingness to learn ? I suspect Jakob will not have time for a full Qt app soon, and it’s not such good policy to have only one developer who know what is going on inside.

best,
---
Miguel Negrão // ZLB
http://www.friendlyvirus.org/artists/zlb/
Jonatan Liljedahl
2011-05-10 19:17:40 UTC
Permalink
Post by Josh Parmenter
Yes, I totally see the point with bundling Qt. But I think there might be users who prefer to download SC.app without Qt, if they have Qt already installed.
True - tricky...
Post by Josh Parmenter
No - as I mentioned yesterday, it seemed that most of my regular GUI stuff worked fine for path-fixed-up Qt stuff, it was just Help that seemed to be bonked. Could this be a bug in how Help is using the GUI?
If I remember correctly, there were other bugs as well introduced by the fixup bundle. HelpBrowser doesn't do anything strange or special as far as I can see. In any case, since the behaviour changes when using fixup bundle, it clearly shows that fixup bundle does more than fixing the link paths - it breaks something.
Good point.
Also, there are other problems with Qt + SC.app, for example Dialog not working and hanging some thread. I guess we have to choose if we should try to fix this or get rid of cocoa and rewrite SC.app in Qt - which means we would have a true cross platform SC app.
Yes... THAT would be rad.
I’m curious, besides Jakob does anyone else have knowledge of Qt inner workings or has capability and willingness to learn ? I suspect Jakob will not have time for a full Qt app soon, and it’s not such good policy to have only one developer who know what is going on inside.
Good points. Perhaps Jakob could write a readme for devs describing the
basics of QtCollider?

/Jonatan

_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
Lucas Samaruga
2011-05-10 19:59:34 UTC
Permalink
Post by Jonatan Liljedahl
Post by Jonatan Liljedahl
Good points. Perhaps Jakob could write a readme for devs describing the
basics of QtCollider?
he already made that two times, I don't know if that is in the main sc repo
now.
Tim Blechmann
2011-05-10 20:02:38 UTC
Permalink
Post by Josh Parmenter
Post by Jonatan Liljedahl
Also, there are other problems with Qt + SC.app, for example Dialog not
working and hanging some thread. I guess we have to choose if we should
try to fix this or get rid of cocoa and rewrite SC.app in Qt - which
means we would have a true cross platform SC app.
Yes... THAT would be rad.
I’m curious, besides Jakob does anyone else have knowledge of Qt inner
workings or has capability and willingness to learn ? I suspect Jakob will
not have time for a full Qt app soon, and it’s not such good policy to
have only one developer who know what is going on inside.
i do have a rough understanding of jakob's code base and the code is very
readable. however i cannot spare too much time at the moment ... but if we want
to try to reimplement the scapp in qt, i will definitely try to help!

tim
--
tim-xpEK/MU0Hawdnm+***@public.gmane.org
http://tim.klingt.org

Every word is like an unnecessary stain on silence and nothingness
Samuel Beckett
Jakob Leben
2011-05-10 20:12:27 UTC
Permalink
I’m curious, besides Jakob does anyone else have knowledge of Qt inner
Post by Miguel Negrao
workings or has capability and willingness to learn ? I suspect Jakob
will
Post by Miguel Negrao
not have time for a full Qt app soon, and it’s not such good policy to
have only one developer who know what is going on inside.
i do have a rough understanding of jakob's code base and the code is very
readable. however i cannot spare too much time at the moment ... but if we want
to try to reimplement the scapp in qt, i will definitely try to help!
Actually, it is still to decide whether Qt app will be the same process as
sclang or a separate one (in that case we'd need to decide on an appropriate
interprocess communication protocol). If it is a different process, then no
knowledge of QtCollider internals are needed to implement it.
Lucas Samaruga
2011-05-10 20:16:54 UTC
Permalink
2011/5/10 Jakob Leben
On Tue, May 10, 2011 at 10:02 PM, Tim Blechmann
Post by Miguel Negrao
I’m curious, besides Jakob does anyone else have knowledge of Qt inner
Post by Miguel Negrao
workings or has capability and willingness to learn ? I suspect Jakob
will
Post by Miguel Negrao
not have time for a full Qt app soon, and it’s not such good policy to
have only one developer who know what is going on inside.
i do have a rough understanding of jakob's code base and the code is very
readable. however i cannot spare too much time at the moment ... but if we want
to try to reimplement the scapp in qt, i will definitely try to help!
Actually, it is still to decide whether Qt app will be the same process as
sclang or a separate one (in that case we'd need to decide on an appropriate
interprocess communication protocol). If it is a different process, then no
knowledge of QtCollider internals are needed to implement it.
If it is in the same process could the editor will be customizable by
sclang?
If not, a separated application could be easy to make with the basic qt
blueprints, I guess.
Jakob Leben
2011-05-10 20:20:19 UTC
Permalink
Post by Lucas Samaruga
2011/5/10 Jakob Leben
Post by Jakob Leben
Actually, it is still to decide whether Qt app will be the same process as
sclang or a separate one (in that case we'd need to decide on an appropriate
interprocess communication protocol). If it is a different process, then no
knowledge of QtCollider internals are needed to implement it.
If it is in the same process could the editor will be customizable by
sclang?
If not, a separated application could be easy to make with the basic qt
blueprints, I guess.
Even if it is a separate process, the two-way interaction between sclang and
IDE would be possible, given an appropriate interprocess communication
protocol.
Jonatan Liljedahl
2011-05-10 20:50:26 UTC
Permalink
Post by Jakob Leben
Post by Lucas Samaruga
2011/5/10 Jakob Leben
Post by Jakob Leben
Actually, it is still to decide whether Qt app will be the same process as
sclang or a separate one (in that case we'd need to decide on an appropriate
interprocess communication protocol). If it is a different process, then no
knowledge of QtCollider internals are needed to implement it.
If it is in the same process could the editor will be customizable by
sclang?
If not, a separated application could be easy to make with the basic qt
blueprints, I guess.
Even if it is a separate process, the two-way interaction between sclang and
IDE would be possible, given an appropriate interprocess communication
protocol.
I like the modular approach of using a separate process. It could
benefit also the development of other frontends which already uses a
separate sclang process. With a well defined IPC protocol it would be
easier to implement Document support and stuff like that, and it could
hopefully be made more frontend-agnostic and cross-platform.

So, the new app would start sclang, using its stdin/out to evaluate code
and get back the post output. An sclang class would manage the IPC
through a pair of pipes, for Document support and Menubar customization
and stuff like that. On the qt app side, some kind of commands are read
from, and results sent to, these pipes.

Perhaps we can find a nice and slim Qt editor library instead of
re-inventing the wheel regarding the common editor-features? But I'm
afraid it needs to support rich text, which internally would be HTML
(and then we need some code to read RTF and translate it to html).

/Jonatan

_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
Jakob Leben
2011-05-10 20:54:52 UTC
Permalink
Post by Jonatan Liljedahl
Perhaps we can find a nice and slim Qt editor library instead of
re-inventing the wheel regarding the common editor-features?
I was thinking of that, but after all, the common stuff we need is quite
simple to implement, and the advanced stuff will be very much SC specific so
will need custom implementation anyway...
Post by Jonatan Liljedahl
But I'm afraid it needs to support rich text, which internally would be
HTML (and then we need some code to read RTF and translate it to html).
...and this is the first example of such advanced thing.
Jonatan Liljedahl
2011-05-10 21:22:16 UTC
Permalink
Post by Jakob Leben
Post by Jonatan Liljedahl
Perhaps we can find a nice and slim Qt editor library instead of
re-inventing the wheel regarding the common editor-features?
I was thinking of that, but after all, the common stuff we need is quite
simple to implement, and the advanced stuff will be very much SC specific so
will need custom implementation anyway...
Post by Jonatan Liljedahl
But I'm afraid it needs to support rich text, which internally would be
HTML (and then we need some code to read RTF and translate it to html).
...and this is the first example of such advanced thing.
Yes, you're right. And QTextEdit seems to handle all the basics already.
Some stuff that needs to be added to replicate the cocoa SC.app:

- evaluate selection or current line
- double click parentheses (or press shortcut) to select
- the other selection-based stuff, like finding implementations of a
method or jumping to a class source file. I guess there is already code
for this on the sclang side, so we can just call it and interpret the
results.
- syntax coloring
- font family, style and size stuff
- read RTF files

stuff that we might want to add:

- line numbering
- word wrap on/off
- tab use spaces on/off
- tab width
- goto line number
- bookmarks
- autocompletion/suggestion
- a project/session manager (list of files)

also, I would like a "plaintext" mode where rich text is stripped to
plain, and syntax coloring is automatic and instant. i.e. just like any
other code editor.

/Jonatan

_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
Miguel Negrao
2011-05-10 21:55:29 UTC
Permalink
Post by Jonatan Liljedahl
Post by Jakob Leben
Post by Jonatan Liljedahl
Perhaps we can find a nice and slim Qt editor library instead of
re-inventing the wheel regarding the common editor-features?
I was thinking of that, but after all, the common stuff we need is quite
simple to implement, and the advanced stuff will be very much SC specific so
will need custom implementation anyway...
Post by Jonatan Liljedahl
But I'm afraid it needs to support rich text, which internally would be
HTML (and then we need some code to read RTF and translate it to html).
...and this is the first example of such advanced thing.
- evaluate selection or current line
- double click parentheses (or press shortcut) to select
- the other selection-based stuff, like finding implementations of a method or jumping to a class source file. I guess there is already code for this on the sclang side, so we can just call it and interpret the results.
- syntax coloring
- font family, style and size stuff
- read RTF files
- line numbering
- word wrap on/off
- tab use spaces on/off
- tab width
- goto line number
- bookmarks
- autocompletion/suggestion
- a project/session manager (list of files)
most are features I like in intellij IDEA:
- all documents in just one window with tabs.
- place the cursor anywhere and write, the editor then adds the right amount of spaces internally. This means also automatically there is no unneded whitespace or tabs. This is a great one !!!!
- documentation pop ups. hit ctrl-j and a small window hovers with documentation for the method, focus continues to be on the document and hit esc to dismiss. These are also usable with the code completion. Type classname, hit . a pop up appears with method names hit down a couple of times until you find a method. If you are wondering what it does it ctl-j and a pop up apears with the description of the method.
- definition pop ups (show source of method in a popup)
- If quarks were rewritten to allow versions, then projects/sessions could have a mode where instead of importing everything in extensions, they would only import selected quarks at some specific version. This would allow to make breaking code more difficult, and would allow to better keep projects separated.
- reformat -> select the whole code and hit reformat would make all the code me pretty with the right indentation, spaces, etc.
- re-align -> selected code is put at the correct indentation
- typing { “ ( ‘ will automatically type the corresponding closing one ‘ ) “ }
- shortcut to join lines. i.e.
method{
something
with the cursor in “something” hit the shortcut and it becomes
method{ something
- collapse method and class implementations (the implementation disappears).
- show class hierarchy (in another window).

This is what I can think off now... Seems a bit silly to implement all this stuff from scratch though... I hope there is already code out there that can be used.

best,
--
Miguel Negrão // ZLB
http://www.friendlyvirus.org/artists/zlb/
Lucas Samaruga
2011-05-10 22:28:13 UTC
Permalink
2011/5/10 Miguel Negrao
Post by Miguel Negrao
- all documents in just one window with tabs.
I think is better a dual interface, SDI and TDI to switch between if you
want! I think the implementation shouldn't be very different and is just a
matter of grouping SDIs in a container...
And for historical reasons, sc was always SDI, also the Document interface
is designed that way.
Miguel Negrao
2011-05-10 22:43:38 UTC
Permalink
Post by Lucas Samaruga
2011/5/10 Miguel Negrao
- all documents in just one window with tabs.
I think is better a dual interface, SDI and TDI to switch between if you want! I think the implementation shouldn't be very different and is just a matter of grouping SDIs in a container...
And for historical reasons, sc was always SDI, also the Document interface is designed that way.
Sure, it should be possible to detach a window if you really want to. Coding always requires a lot of documents/files open at the same time, it’s not good for organization to keep them hanging around. Just look at almost any IDE in the planet, or at processing, for instance.

Just because sc for historical reasons made a wrong ui decision doesn’t mean we should perpetuate it ad infinitum... at least it’s something that should be very well discussed.

best,
--
Miguel Negrão // ZLB
http://www.friendlyvirus.org/artists/zlb/
Lucas Samaruga
2011-05-11 00:33:57 UTC
Permalink
Yes that's totally right, but I really prefer the simple documents hanging
around some times (and to be able to group other in tabs) for better
organization on desktop, and in relation to other app windows too. My
thought was that is better to not be attached to only one mode and the sdi
is the most basic of the two. But I'm fine with any.

2011/5/10 Miguel Negrao
Post by Lucas Samaruga
2011/5/10 Miguel Negrao
Post by Miguel Negrao
- all documents in just one window with tabs.
I think is better a dual interface, SDI and TDI to switch between if you
want! I think the implementation shouldn't be very different and is just a
matter of grouping SDIs in a container...
And for historical reasons, sc was always SDI, also the Document interface
is designed that way.
Sure, it should be possible to detach a window if you really want to.
Coding always requires a lot of documents/files open at the same time, it’s
not good for organization to keep them hanging around. Just look at almost
any IDE in the planet, or at processing, for instance.
Just because sc for historical reasons made a wrong ui decision doesn’t
mean we should perpetuate it ad infinitum... at least it’s something that
should be very well discussed.
best,
--
Miguel Negrão // ZLB
http://www.friendlyvirus.org/artists/zlb/
Jonatan Liljedahl
2011-05-10 20:56:06 UTC
Permalink
Post by Jonatan Liljedahl
Perhaps we can find a nice and slim Qt editor library instead of
re-inventing the wheel regarding the common editor-features? But I'm
afraid it needs to support rich text, which internally would be HTML
(and then we need some code to read RTF and translate it to html).
Maybe this one?
http://www.riverbankcomputing.co.uk/software/qscintilla/intro

/Jonatan

_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
James Harkins
2011-05-11 01:36:31 UTC
Permalink
At Tue, 10 May 2011 22:50:26 +0200,
Post by Jonatan Liljedahl
I like the modular approach of using a separate process. It could
benefit also the development of other frontends which already uses a
separate sclang process. With a well defined IPC protocol it would be
easier to implement Document support and stuff like that, and it could
hopefully be made more frontend-agnostic and cross-platform.
Would sclang <--> editor interaction be synchronous or asynchronous? Mac users are accustomed to Document methods running synchronously.

hjh


--
James Harkins /// dewdrop world
jamshark70-***@public.gmane.org
http://www.dewdrop-world.net

"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal." -- Whitman

blog: http://www.dewdrop-world.net/words
audio clips: http://www.dewdrop-world.net/audio
more audio: http://soundcloud.com/dewdrop_world/tracks

_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
Jakob Leben
2011-05-11 09:30:35 UTC
Permalink
Post by James Harkins
Post by Jonatan Liljedahl
I like the modular approach of using a separate process. It could
benefit also the development of other frontends which already uses a
separate sclang process. With a well defined IPC protocol it would be
easier to implement Document support and stuff like that, and it could
hopefully be made more frontend-agnostic and cross-platform.
Would sclang <--> editor interaction be synchronous or asynchronous? Mac
users are accustomed to Document methods running synchronously.
Depends on the IPS protocol. Synchronous seems more difficult but at the
moment I couldn't say impossible.
Jonatan Liljedahl
2011-05-11 11:20:46 UTC
Permalink
Post by Jakob Leben
Post by Jonatan Liljedahl
I like the modular approach of using a separate process. It could
benefit also the development of other frontends which already uses a
separate sclang process. With a well defined IPC protocol it would be
easier to implement Document support and stuff like that, and it could
hopefully be made more frontend-agnostic and cross-platform.
Would sclang<--> editor interaction be synchronous or asynchronous? Mac
users are accustomed to Document methods running synchronously.
Depends on the IPS protocol. Synchronous seems more difficult but at the
moment I couldn't say impossible.
Asynchronous methods could be made synchronous by blocking until the
result is received from the editor? It's only for methods that return a
result (like "get current selection") that needs to be synchronous.
sclang->editor one-way interaction would just be queued in the correct
order so that any future editor->sclang interaction would happen after
the other stuff has been done.

/Jonatan

_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/

Jakob Leben
2011-05-10 17:29:44 UTC
Permalink
Post by Jonatan Liljedahl
Also, there are other problems with Qt + SC.app, for example Dialog not
working and hanging some thread. I guess we have to choose if we should try
to fix this or get rid of cocoa and rewrite SC.app in Qt - which means we
would have a true cross platform SC app.
As for the choice: I already tried to fix those bugs and it was not in my
capability. I believe the true problem is hidden in the depths of the Qt
framework, and I couldn't find any plausible workaround either. I posted
about it on various Qt forums and no reply either. The way we use Qt in
Cocoa app is not documented anywhere, so I believe Qt's support for that is
rather on the bottom of priorities for authors of Qt.

So we are left to either wait for newer versions of Qt and hope that they
fix those problems, or make a whole Qt SC app. I think the latter option has
already turned out to be the only viable one.
Continue reading on narkive:
Loading...