On 24/07/13 21:50, Hua Xiang wrote:
> 2013/7/24 Ryan Ollos <[email protected]>
>
>> On Tue, Jul 23, 2013 at 4:13 PM, Hua Xiang <[email protected]> wrote:
>>
>>> 2013/7/23 Joachim Dreimann <[email protected]>
>>>
>>>> On 23 July 2013 15:58, Hua Xiang <[email protected]> wrote:
>>>>
>>>>>
>>>>> Hi Gary,
>>>>>
>>>>>> I can't see the attachment you mentioned so it is probably removed.
>>>>>> Otherwise, that error on the svn info command at least tells us that
>>> the
>>>>>> copy of the code in /home/xiang/bep_0008_time_series_reports was
>>> checked
>>>>>> out with an older version of svn than you are attempting to svn info
>>> at
>>>>>> this point. Your previous response suggested that tortoisesvn is
>> using
>>>>>> subversion 1.7.10 so that ties together at least.
>>>>>>
>>>>> Here is the snapshot.
>>>>>
>>>>> [image: 内嵌图片 1]
>>>>>
>>>> All attachments are stripped from your email before it gets distributed
>>> to
>>>> the dev@ list, so we can't see the snapshot.
>>>>
>>>>
>>>>> If you are happy to continue using the command line (and/or you
>> want
>>> to
>>>>> upgrade your tortoisesvn to 1.8) you could follow the advice of the
>>> error
>>>>> message:
>>>>>
>>>>>> svn upgrade /home/xiang/bep_0008_time_series_reports
>>>>>>
>>>>>> I would expect the svn info command to work assuming that is
>>> successful.
>>>>> Ok. I will do upgrade.
>>>>>
>>>>>
>>>>>> Meanwhile, it is not so clear to me whether you attempted a fresh
>>>>>> checkout of the bep_0008_time_series_reports branch.. perhaps the
>>>> removed
>>>>>> attachment would have told me that though
>>>>>>
>>>>> Yes, I did a fresh checkout of the branch.
>>>>> BTW, I have created SQL statements to generate reports locally (my
>>> local
>>>>> sqlite). I would like to know how to commit my SQL statements to the
>>>>> repository so that other developer can see my change?
>>>>>
>>>> I'd be keen to hear other opinions on this again, but you can probably
>>> just
>>>> post plain SQL statements to a pastebin service, for example
>>>> http://pastebin.com/, and share links to them on this list.
>>>>
>>> I will put the SQL statements in
>>> bep_0008_time_series_reports\trac\trac\db_default.py
>>
>> That's fine for now, but please be aware that you'll need to structure your
>> code in a plugin before we can consider integrating it into Bloodhound. For
>> examples, take a look at how `bloodhound_multiproduct` ,
>> `bloodhound_relations` and the other plugins are structured. With few
>> exceptions, the code for your plugin will be entirely contained in a
>> directory with a name like `bloodhound_time_series_reports`.
>>
> Where I can find the standard procedure to create my plugin? Or, should I
> create these directory structure manually?
>
I'm afraid it is a bit of a manual process.. I tend to just create
everything required then svn add everything later but if the directories
don't already exist you can also do something like
svn mkdir bloodhound_time_series_reports/bhtsreports --parents
svn commit bloodhound_time_series_reports -m "adding basic directory
structure for bep-0008 plugin"
to get the bare minimum directories into your branch - you are free to
change either of the "bloodhound_time_series_reports" and "bhtsreports"
directory names but I will keep referring to the directories with that
name in this email.
Anyway, you will be putting a setup.py file in
/home/xiang/bep_0008_time_series_reports/bloodhound_time_series_reports
so that it will be possible to install the plugin but real code for your
project should go in
/home/xiang/bep_0008_time_series_reports/bloodhound_time_series_reports/bhtsreports.
You can use
/home/xiang/bep_0008_time_series_reports/bloodhound_relations or any of
the other bloodhound plugins to give example setup.py files but let us
know if you have any more problems.
Cheers,
Gary
