Re: [sqlite] OSX path
Hello John, > As for "top-posting," In the corporate culture I come from, it is > considered the only way to do things (or at least one faction who > has the ear of the ops boss, believes this). Yes, I noticed that too. I can think of two reasons for doing things in this terribly inefficient way: a) people got started mailing with Outlook, which for several years didn't support threading and therefore no easy reference to earlier material was available (mind you, pretty much any other mailtool did threading years before MS actually came up with Outlook, so I wonder what their excuse is). In fact, the MS Exchange server even implements a specific protocol extension to support to-posting (only the new text needs to be send to the server, which copies the old text straight from the referenced mail). b) people think that their time (spend editing) is much more important that the readers time. But in truth it's probably just plain ignorance that started it. Or maybe in your company conversations really go like this: Well, it's just easier that way. > So what do you like about B? > > Well, personally I would prefer B... > > > Do you think A is a good idea? but personally I believe it's easier to read: > > > Do you think A is a good idea? > > Well, personally I would prefer B... > So what do you like about B? Well, it's just easier that way. Sven -- __ _ _ __ __ __ / _` || ' \ \ \ / http://www.svenutcke.de/ \__, ||_|_|_|/_\_\http://www.dr-utcke.de/ |___/ Key fingerprint = 6F F8 55 1C F9 E3 A8 F7 09 DF F7 2C 25 0C 54 53 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] OSX path
Thanks for your kind words, Simon. As for myself, I really do strive for civility, though I don't always get there. I'll keep working at it if you promise to be patient with me. As for "top-posting," In the corporate culture I come from, it is considered the only way to do things (or at least one faction who has the ear of the ops boss, believes this). I actually got counseled for cutting out a goodly chunk of what I thought was unnecessary old message. It was a gentle admonishment, nevertheless, I got the message. In fact, I shudder as I read your message and find out I am *expected* to cut out the stuff that is no longer needed (grin). > -Original Message- > From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] > > Yep. Adobe totally explains why you're still thinking in terms of colon > paths. > InDesigns is a terrific program (I've never developed for it) but Adobe hasn't > ported it to more recent API layers. Adobe's habit of lagging several years > behind > Apple in this way is a terrible handicap and hits it each time Apple stops > supporting > old (in this case 11 years old) sets of API. It's going to happen again in > OS X 10.7 > because OS X 10.7 does not support the PowerPC compatibility layer. Gulp. Another sleepless three months for us InDesign Plugin programmers as we figure out how to cope... Take care. R, John ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] OSX path
On 17 Jun 2011, at 11:50pm, john darnell wrote: > Say what you will about Adobe and InDesign, but their tools for writing > Apple, ah, supplemental code, are not insubstantial or trivial. IMHO, it is > understandable when that is my major environment for writing code that I > might not know the more current practice. Yep. Adobe totally explains why you're still thinking in terms of colon paths. InDesigns is a terrific program (I've never developed for it) but Adobe hasn't ported it to more recent API layers. Adobe's habit of lagging several years behind Apple in this way is a terrible handicap and hits it each time Apple stops supporting old (in this case 11 years old) sets of API. It's going to happen again in OS X 10.7 because OS X 10.7 does not support the PowerPC compatibility layer. Sorry about the tone of my earlier post. I wasn't trying to condemn you, merely show that neither side of the SQLite programming community would have written a note about colon paths because neither side of the Mac SQLite programming community would have thought it was a problem. On 18 Jun 2011, at 1:06am, john darnell wrote: > Um, what's top-posting? Adding your new text at the top of a post, then including the whole earlier post you're replying to. We've already read the earlier post. We don't need to see it again. If you think you need it for context when we read your post, it has to be /above/ your new text, so we read it first. And we don't need the whole thing, just the bit you're replying to. Take a look at the post you're reading now, and you'll see a more efficient way to do things. Don't worry: you're just going through a little stage all new posters go through. Simon. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] OSX path
Um, what's top-posting? And of course I always strive to be wise. Simon (or for that matter, the rest of the list), if you thought I was being a wiseass, then again, my apologies. R, John > -Original Message- > From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] > On Behalf Of Warren Young > Sent: Friday, June 17, 2011 7:00 PM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] OSX path > > On 6/17/2011 4:50 PM, john darnell wrote: > > > > I am essentially a Windows programmer > > Is that also your excuse for top-posting? :) > > > I will have to take your > > word on the use of HFS-style paths vs posix/Unix style paths on Mac > > platforms. > > That would be wise, because Simon is correct. > > > I will have to say, however, that at least the InDesign SDK, which is > > my chief habitat when it comes to writing Mac code, encourages the > > use of colon-laden paths--or at least does not greatly discourage it, > > That's because all Adobe software created before about 2006[*] was built > on top of the Carbon SDK, which interprets colon-delimited paths for > backwards compatibility with Classic Mac OS. OS X's native > POSIX/Mach/Cocoa APIs understand only slash-based paths. > > SQLite is built on top of the POSIX layer of OS X, so it only > understands POSIX paths. > > As more Mac programs move to 64-bit, they must move from Carbon to > Cocoa, and thus will require POSIX paths, unless they've built in their > own portability layer. I can see Adobe doing that, to preserve legacy > compatibility. > > [*] Lightroom was the first Cocoa-based Adobe app. Its first public > beta came out in 2006. > ___ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] OSX path
On 6/17/2011 4:50 PM, john darnell wrote: > > I am essentially a Windows programmer Is that also your excuse for top-posting? :) > I will have to take your > word on the use of HFS-style paths vs posix/Unix style paths on Mac > platforms. That would be wise, because Simon is correct. > I will have to say, however, that at least the InDesign SDK, which is > my chief habitat when it comes to writing Mac code, encourages the > use of colon-laden paths--or at least does not greatly discourage it, That's because all Adobe software created before about 2006[*] was built on top of the Carbon SDK, which interprets colon-delimited paths for backwards compatibility with Classic Mac OS. OS X's native POSIX/Mach/Cocoa APIs understand only slash-based paths. SQLite is built on top of the POSIX layer of OS X, so it only understands POSIX paths. As more Mac programs move to 64-bit, they must move from Carbon to Cocoa, and thus will require POSIX paths, unless they've built in their own portability layer. I can see Adobe doing that, to preserve legacy compatibility. [*] Lightroom was the first Cocoa-based Adobe app. Its first public beta came out in 2006. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] OSX path
Simon: First of all, let me apologize for my whine. We all have our bumps in the road and if we don't then we're probably not doing our jobs (as one venerable Navy Chief once pointed out to a hapless, naïve ensign many years ago). I should have just shut up and moved on. I am essentially a Windows programmer so I will have to take your word on the use of HFS-style paths vs posix/Unix style paths on Mac platforms. I will have to say, however, that at least the InDesign SDK, which is my chief habitat when it comes to writing Mac code, encourages the use of colon-laden paths--or at least does not greatly discourage it, while not encouraging at all the use of the posix/Unix style of path presentation. They have a few functions scattered here and there for HFS-to-URL/Posix conversion, but rarely are they mentioned in their docs, or used not at all in their examples. Say what you will about Adobe and InDesign, but their tools for writing Apple, ah, supplemental code, are not insubstantial or trivial. IMHO, it is understandable when that is my major environment for writing code that I might not know the more current practice. Okay, it's an excuse (grin), but it's all I've got. Take care, and honest, thanks! John > -Original Message- > From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] > On Behalf Of Simon Slavin > Sent: Friday, June 17, 2011 5:18 PM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] OSX path > > > On 17 Jun 2011, at 10:09pm, john darnell wrote: > > > I checked two references and neither one of them mentioned this teensy > > little > requirement. I guess they must've thought it wasn't important. > > The use of colons for file paths is purely an old-fashioned Mac thing and > never > worked cross-platform. So from the SQLite and sides, the programmers would > never think to mention the colon format and might never have known about it > (although as it happens DRH is a Mac user and doubtless does). > > From the Mac side, since OS X began (twelve years ago) you've been able to use > standard Unix slash format for file paths, and the colon format has > pretty-much > diminished into misuse. So only pre-OS X Mac programmers like us would know > about it. > > Sorry about that. But I'm keeping my copy of _Inside Mac_ because I'm > convinced > it's a classic. > > Simon. > > > ___ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] OSX path
On 17 Jun 2011, at 10:09pm, john darnell wrote: > I checked two references and neither one of them mentioned this teensy > little requirement. I guess they must've thought it wasn't important. The use of colons for file paths is purely an old-fashioned Mac thing and never worked cross-platform. So from the SQLite and sides, the programmers would never think to mention the colon format and might never have known about it (although as it happens DRH is a Mac user and doubtless does). >From the Mac side, since OS X began (twelve years ago) you've been able to use >standard Unix slash format for file paths, and the colon format has >pretty-much diminished into misuse. So only pre-OS X Mac programmers like us >would know about it. Sorry about that. But I'm keeping my copy of _Inside Mac_ because I'm convinced it's a classic. Simon. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] OSX path
Thanks Doug. I appreciate you pointing this out to me. I checked two references and neither one of them mentioned this teensy little requirement. I guess they must've thought it wasn't important. R, John > -Original Message- > From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] > On Behalf Of Doug Currie > Sent: Friday, June 17, 2011 4:07 PM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] OSX path > > > On Jun 17, 2011, at 2:56 PM, john darnell wrote: > > > I am attempting to open an SQLite database on the Mac (OSX Snow Leopard) > and am getting an error. This is the code I am using: > > > > char DBEnginePath[1000]; > > > > strcpy(DBEnginePath, "Macintosh HD:Applications:Adobe InDesign CS5:Plug- > Ins:WPC_ID:IndexData.db"); > > fprintf(stderr, "%s\n", DBEnginePath); > > // Sends > correct path to stderr for verification. > > Result = sqlite3_open_v2(DBEnginePath, _ptr, > SQLITE_OPEN_READONLY, NULL); // Errors out here. > > Your path has colons instead of slashes for separators. > > Open a Terminal window, and drag the database file into the window. The > terminal.app will display the path name on the command line. You can copy and > paste from there. It's probably something like: > > /Applications/Adobe\ InDesign\ CS5/Plug-Ins/WPC_ID/IndexData.db > > e > > ___ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] OSX path
On Jun 17, 2011, at 2:56 PM, john darnell wrote: > I am attempting to open an SQLite database on the Mac (OSX Snow Leopard) and > am getting an error. This is the code I am using: > > char DBEnginePath[1000]; > > strcpy(DBEnginePath, "Macintosh HD:Applications:Adobe InDesign > CS5:Plug-Ins:WPC_ID:IndexData.db"); > fprintf(stderr, "%s\n", DBEnginePath); > // Sends correct path to stderr for verification. > Result = sqlite3_open_v2(DBEnginePath, _ptr, SQLITE_OPEN_READONLY, > NULL); // Errors out here. Your path has colons instead of slashes for separators. Open a Terminal window, and drag the database file into the window. The terminal.app will display the path name on the command line. You can copy and paste from there. It's probably something like: /Applications/Adobe\ InDesign\ CS5/Plug-Ins/WPC_ID/IndexData.db e ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
