OPML Editor and Mac OS 10.9 Maverick

[Philippe BARDON]

OPML Editor cranes at launch with Mac OS 10.9 installed.

Here is the crash log :

Process:         OPML [800]

Path:            /Applications/OPML/OPML.app/Contents/MacOS/OPML

Identifier:      com.scripting.OPML

Version:         10.1a16 (10.1a16)

Code Type:       X86 (Native)

Parent Process:  launchd [171]

Responsible:     OPML [800]

User ID:         503

Date/Time:       2013-11-03 10:44:16.313 +0100

OS Version:      Mac OS X 10.9 (13A603)

Report Version:  11

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BREAKPOINT (SIGTRAP)

Exception Codes: 0x0000000000000002, 0x0000000000000000

Dyld Error Message:

  Symbol not found: _OTLIFOStealList

  Referenced from: /Applications/OPML/OPML.app/Contents/MacOS/OPML

  Expected in: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0   dyld                           0x8feac0b5 dyld_fatal_error + 1

1   dyld                           0x8feaede8 dyld::bindLazySymbol(mach_header const*, unsigned long*) + 72

2   dyld                           0x8febf34e stub_binding_helper_interface2 + 20

3   com.scripting.OPML             0x0006729a Recycle + 79

4   com.scripting.OPML             0x0006940c fwsNetEventCheckAndAcceptSocket + 57

5   com.scripting.OPML             0x000f9e5b shelleventloop + 77

6   com.scripting.OPML             0x000f9f98 shellmaineventloop + 34

7   com.scripting.OPML             0x000404c5 main + 59

8   com.scripting.OPML             0x00001c1a _start + 216

9   com.scripting.OPML             0x00001b41 start + 41

Thread 1:

0   libsystem_kernel.dylib         0x901e6046 __workq_kernreturn + 10

1   libsystem_pthread.dylib       0x99fd7dcf _pthread_wqthread + 372

2   libsystem_pthread.dylib       0x99fdbcce start_wqthread + 30

Thread 2:: Dispatch queue: com.apple.libdispatch-manager

0   libsystem_kernel.dylib         0x901e6992 kevent64 + 10

1   libdispatch.dylib             0x98b088bd _dispatch_mgr_invoke + 238

2   libdispatch.dylib             0x98b08556 _dispatch_mgr_thread + 52

Thread 3:

0   libsystem_kernel.dylib         0x901e6046 __workq_kernreturn + 10

1   libsystem_pthread.dylib       0x99fd7dcf _pthread_wqthread + 372

2   libsystem_pthread.dylib       0x99fdbcce start_wqthread + 30

Thread 4:

0   libsystem_kernel.dylib         0x901e6046 __workq_kernreturn + 10

1   libsystem_pthread.dylib       0x99fd7dcf _pthread_wqthread + 372

2   libsystem_pthread.dylib       0x99fdbcce start_wqthread + 30

Thread 5:

0   libsystem_kernel.dylib         0x901e6046 __workq_kernreturn + 10

1   libsystem_pthread.dylib       0x99fd7dcf _pthread_wqthread + 372

2   libsystem_pthread.dylib       0x99fdbcce start_wqthread + 30

Thread 0 crashed with X86 Thread State (32-bit):

  eax: 0x8fedf0f8  ebx: 0x0006725d  ecx: 0x00000000  edx: 0x8ff07084

  edi: 0x8ff07084  esi: 0x8fead1e3  ebp: 0xbffffbd8  esp: 0xbffffbbc

   ss: 0x00000023  efl: 0x00000246  eip: 0x8feac0b5   cs: 0x0000001b

   ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f

  cr2: 0x02b1b000

  

Logical CPU:     0

Error Code:      0x00000000

Trap Number:     3

[Dave Winer]

Here's what's up..

http://scripting.com/2013/11/03/frontiermacDoesntRunOnMavericks

Dave

[M. Philippe BARDON]

Thanks Dave.

Philippe BARDON

+336 8003 7438

--
You received this message because you are subscribed to a topic in the Google Groups "frontier-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/frontier-user/50pyXb7EXto/unsubscribe.
To unsubscribe from this group and all its topics, send an email to frontier-use...@googlegroups.com.
Visit this group at http://groups.google.com/group/frontier-user.
For more options, visit https://groups.google.com/groups/opt_out.

[dougla...@gmail.com]

Oh my. I've been using Frontier on my Macs for 20 years, and I'm really not interested in trying to cobble together the same functionality from other software. (Unless I'm missing something obvious that does the same thing, and to which I can easily port my UserTalk scripts.) 

Is there anyone who is both capable and willing to 'fix' Frontier on the Mac so we can keep using it for another decade or so? If so, how much work would that take, and how much would it cost? Perhaps we can all chip in. 

[Ben Greenfield]

On Nov 16, 2013, at 5:37 PM, dougla...@gmail.com wrote:

Oh my. I've been using Frontier on my Macs for 20 years, and I'm really not interested in trying to cobble together the same functionality from other software.

I know the feeling but Frontier I think now falls solidly into abandon-ware. I had the first twangs of that with Frontier 5 for mac after shelling out $2,000 for 2 licenses. I couldn't get Userland to help/fix the file.volumesize to read over 2GB. The best response I could get was they were just talking about this the otherday and they didn't know when they would fix it.

Despite that grudge I have been carrying around for years last year I started to get to work on resurrecting a good OPML/Frontier workflow. I was astounded that I could get FilemakerLIb and some other suites working but then I realized that the flow of Frontier was better at 4.2.3 and there were subtle problems that had to be bugs in basic functionality. So I dropped the notion of going back to Frontier.

Now of course I can probably run Frontier 4.2.3 in a a browser with:

http://jamesfriend.com.au/pce-js/

So emulation or perserving old hardware should be your first line of defense. It is easy as in status quo. 

If that is an unappealing long term thing the solution then look for simple ways to modify your existing dependences to other tools.

There are many OPML compatible editors start looking at those tools and see if you can replace some of your workflow with their use.

The best thing about Frontier for me was a graphic table representation of available software tools and simple command structure to string it together. 

I have not found that ever again and in fact I'm trying to make a personal one now.

(Unless I'm missing something obvious that does the same thing, and to which I can easily port my UserTalk scripts.) 

First things first I can't even imagine what your UserTalk scripts do or even what problem domain they address: )

My experience with frontier was as glue to hold together both publishing systems, public video displays, museum and tradeshow interactives.

How do you use Frontier?

If it was website management I would check out Matt Neuberg another refugee made RubyFrontier

http://www.apeth.com/RubyFrontierDocs/defaultfolder/whyrf.html

Is there anyone who is both capable and willing to 'fix' Frontier on the Mac so we can keep using it for another decade or so?

If so, how much work would that take, and how much would it cost? Perhaps we can all chip in. 

The most qualified people to do that all exist and cover many parts of the world there was is open source version I would look around and see if anyone is active and trying to get it up on Mavericks

http://frontierkernel.org/

I checked there svn logs and somebody made a change in april 2012.

That is your best bet.

Ben

--
You received this message because you are subscribed to the Google Groups "frontier-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to frontier-use...@googlegroups.com.