Re: [ANN] Nursery Framework 1.0.1 (build with Xcode 9) released
Re: [ANN] Nursery Framework 1.0.1 (build with Xcode 9) released
- Subject: Re: [ANN] Nursery Framework 1.0.1 (build with Xcode 9) released
- From: Akifumi Takata <email@hidden>
- Date: Sat, 28 Oct 2017 17:03:41 +0900
Dear Richard Charles,
Thank you for your advice.
I learned that it is necessary to refine the description of the project on
GitHub and to rethink about the name.
However, meeting with English-speaking Cocoa programmers is difficult for me.
I have pervasive developmental disorder and I can not do what a healthy person
can do.
It is a heavy burden to talk on the phone and talk with people.
The depression I currently suffer is the result of trying to behave like a
healthy person.
I will start with writing comments on classes and files.
I live in Fukuoka prefecture in Japan.
Regards,
Akifumi Takata
> 2017/10/28 5:11、Richard Charles <email@hidden>のメール:
>
>
>> On Oct 25, 2017, at 8:29 AM, Akifumi Takata <email@hidden> wrote:
>>
>> I create the repository on GitHub.
>> https://github.com/Nursery-Framework/Nursery
>
>> On Oct 26, 2017, at 5:43 PM, Akifumi Takata <email@hidden> wrote:
>>
>> I started this project in 2010 and spent five years to implement the current
>> function.
>
> Here is my advice.
>
> This is what we know about the project from GitHub. "Nursery is a persistent
> object framework (object database) for Cocoa.” Aside from reading the code
> that is all we know, which is not much.
>
> You need to compose several English paragraphs explaining what the project is
> and what problems it intends to solve. For example Apple’s Core Data is among
> other things a persistence framework. How is your project different and why
> would anyone want to use it.
>
> You also need an English paragraph describing what each file or class does.
> This description can be placed the header.
>
> Once you have done this then you need to have someone with English language
> and programming skills polish your descriptions and make sure they make sense.
>
> Then you need evaluate each routine, class, and file and make sure each name
> harmonizes with the description. Then you need to re-evaluate the project
> name. Then you need to submit this as as clean fresh project to GitHub. If it
> was my project or I was the project manager that is what I would do.
>
> For example the file NUBellBall. Really a bellBall? What in the world is a
> bellBall? If this file contained a descriptive paragraph then someone with
> English language and programming skills could help you work on the
> descriptive paragraph and make sure it makes sense. Then you could work on a
> name for the bellBall routines and file name that makes sense.
>
> You should also consider joining an English speaking Cocoa programming group.
> For example www.cocoaheads.org has two groups meeting in Japan (assuming you
> are from Japan). One meets in Tokyo and the other in Osaka. There are also
> several groups that meet in Taiwan and China. You need to talk to an English
> speaking Cocoa programmer face to face and have them help you with this.
>
> As a starting point you could compose all your descriptive paragraphs in your
> native language then use google translation services to translate into
> English. Then go to a Cocoa programming group and find a friend. Then
> convince the friend to proof read the descriptive paragraphs and make sure
> they make sense in English. Then work on renaming your routines, classes,
> files, and perhaps even the project. Then submit everything fresh to GitHub.
>
> --Richard Charles
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden