There won't be any 64-bit Carbon framework anymore in Leopard. It looks like Apple won't push it any further in the future (that's a guess, I admit).
Moreover the new Interface of Sente 5 shows what modern Cocoa interfaces can look like. Although there's still a lot of space for improvements, espacially with CoreAnimation.
I know that you, Jon, are the only developer of Bookends, but, would you perhaps consider creating Bookends Cocoa in the near future, or at least rebuild the interface in IB3. I'm pretty sure that you loyal community will help you even in alpha/beta phase.
Again: Cocoa version of Bookends?
Sorry, Jon, I didn't want to sound rude. Bookends 10 was a big step in the right direction. I really appreciate you changes. Thanks a lot. My comment is not about the interface in general, but more about the question Carbon vs. Cocoa.Jon wrote:I won't comment on future plans for Bookends. But I will say that interface just got a pretty big facelift with Bookends 10, and so far the feedback has been very positive. Now I'm focusing (as usual) on functionality.
Sorry, I didn't mean to seem offended, and I'm certianly not. I was just pointing out that we did a lot of work to update the UI in Bookends 10, and the feedback has been positive. I should also mention that Cocoa is a framework, not a UI, and most of the interface elements are shared with Carbon. Of course we'll keep looking at ways to improve it, and once Leopard is out we'll see what things we might take advantage of. I imagine Bookends' UI will continue to evolve for the foreseeable future...
Jon
Sonny Software
Jon
Sonny Software
Couldn't agree more on the previous post about the commitment to support by Jon. I guess, what the question is really trying to get at is less the issue of UI (discussed in GREAT length in various threads here...) but rather an issue of legacy (will users be able to run BE in future versions of the Mac OS?) but also functionality, that is, can BE take full advantage of the the new features (better PDF handling, sharing of information, spell-checking, etc.) that the Mac OS provides?Jon wrote:Sorry, I didn't mean to seem offended, and I'm certianly not. I was just pointing out that we did a lot of work to update the UI in Bookends 10, and the feedback has been positive. I should also mention that Cocoa is a framework, not a UI, and most of the interface elements are shared with Carbon. Of course we'll keep looking at ways to improve it, and once Leopard is out we'll see what things we might take advantage of. I imagine Bookends' UI will continue to evolve for the foreseeable future...
Yes, of course Bookends will run on future versions of Mac OS X (certainly it does on Leopard). As for employing cool Mac OS X technologies, we're always looking for ways to integrate them (viz the drag and drop of pdfs to get the full citation info from PubMed, and the pdf viewer added in Bookends 10, both of which employ pdfkit). That's not going to stop.
Jon
Sonny Software
Jon
Sonny Software
-
happymac
I'm a new to this forum, and new to Bookends! I'm very dependent on Word for my work, and am concerned about how Bookends will work with the new version of Office. Will Bookends work with the new Word?Jon wrote:Yes, of course Bookends will run on future versions of Mac OS X (certainly it does on Leopard). As for employing cool Mac OS X technologies, we're always looking for ways to integrate them (viz the drag and drop of pdfs to get the full citation info from PubMed, and the pdf viewer added in Bookends 10, both of which employ pdfkit). That's not going to stop.