List,
Apologies for moving off-topic.
The discussion is now moved to be on PM.
Thank you.
On Wed, Oct 24, 2012 at 3:39 AM, Simon Slavin wrote:
>
> On 24 Oct 2012, at 5:29am, Igor Korot wrote:
>
>> It looks like you are "Apple person" that I got suggeted to talk to. ;-)
>> The situation is as fo
On 24 Oct 2012, at 5:29am, Igor Korot wrote:
> It looks like you are "Apple person" that I got suggeted to talk to. ;-)
> The situation is as follows: I am developing an application that will
> utilize not just SQLite but some other library.
> According to the "development standards" on *nix-lik
Igor Korot wrote:
Darren,
On Tue, Oct 23, 2012 at 8:53 PM, Darren Duncan wrote:
You should not have an application installer, at all. Instead, you can ask
the question on where to store the database when the user opens your
program. Or better yet, your application should have menu commands l
Darren,
On Tue, Oct 23, 2012 at 8:53 PM, Darren Duncan wrote:
> Igor Korot wrote:
>>
>> Well, that the closest definition of the data I'm about to put into
>> this database.
>> I am making a sport related application and need to store the data
>> about the teams, players etc.
>> User should be ab
Simon,
On Tue, Oct 23, 2012 at 5:24 PM, Simon Slavin wrote:
>
> On 23 Oct 2012, at 11:41pm, Igor Korot wrote:
>
>> On Tue, Oct 23, 2012 at 3:10 PM, Simon Slavin wrote:
>>
>>> If your user considers these SQLite databases to be their own documents
>>> (i.e. like a word processor saves text docu
Igor Korot wrote:
Well, that the closest definition of the data I'm about to put into
this database.
I am making a sport related application and need to store the data
about the teams, players etc.
User should be able to add/edit/delete this information and this
information will be presented
in t
On 23 Oct 2012, at 11:41pm, Igor Korot wrote:
> On Tue, Oct 23, 2012 at 3:10 PM, Simon Slavin wrote:
>
>> If your user considers these SQLite databases to be their own documents
>> (i.e. like a word processor saves text documents, your application saves
>> SQLite databases) then you must use
Hi,
On Tue, Oct 23, 2012 at 3:10 PM, Simon Slavin wrote:
>
> On 23 Oct 2012, at 10:35pm, Igor Korot wrote:
>
>> On Tue, Oct 23, 2012 at 2:26 PM, Doug Currie wrote:
>>>
>>> On Oct 23, 2012, at 4:58 PM, Igor Korot wrote:
>>>
1. I know on Mac I need to build an application bundle. Where do I
On 23 Oct 2012, at 10:35pm, Igor Korot wrote:
> On Tue, Oct 23, 2012 at 2:26 PM, Doug Currie wrote:
>>
>> On Oct 23, 2012, at 4:58 PM, Igor Korot wrote:
>>
>>> 1. I know on Mac I need to build an application bundle. Where do I
>>> store the .db file relative to the bundle?
>>> Inside it? Hom
On Oct 23, 2012, at 11:35 PM, Igor Korot wrote:
> So then user home directory (~) should be fine, right?
No. Don't. Lookup NSApplicationSupportDirectory and check the documentation.
Apple has clear APIs and guidelines about where to put what. Learn them.
__
Hi, Doug,
On Tue, Oct 23, 2012 at 2:26 PM, Doug Currie wrote:
>
> On Oct 23, 2012, at 4:58 PM, Igor Korot wrote:
>
>> 1. I know on Mac I need to build an application bundle. Where do I
>> store the .db file relative to the bundle?
>> Inside it? Home directory? Somewhere on the hard drive? What i
On Oct 23, 2012, at 4:58 PM, Igor Korot wrote:
> 1. I know on Mac I need to build an application bundle. Where do I
> store the .db file relative to the bundle?
> Inside it? Home directory? Somewhere on the hard drive? What is the
> usual place for it?
If the database is read-only, you can sore
Hi, ALL,
I'm developing a program that will be cross-platform and utilize
SQLite database.
My main development platform is Windows and when I finish I will move to Mac.
My question is:
1. I know on Mac I need to build an application bundle. Where do I
store the .db file relative to the bundle?
I
13 matches
Mail list logo