New Gideros Book

ar2rsawseen

@OZApps that is exactly how it happens, and even after so many people rereading and rechecking, something always slips by

ArtLeeApps

I really hope you dont mind me posting them when i find them, if you do go on to do a second edition that could be useful...

As ive said its well worded and easy to follow... and i am a fairly fresh newbie compared to most in this forum...... i am learning many things i didnt know, working through it slowly, and playing with variations. i can see short cuts i could have used to build my app better and cleaner too.

I could see how auto correct would do weird stuff. the publisher could just run a spell checker but things like Grammar could be missed like the "No" or "Now".
With the technical stuff, even if you were an experienced coder, just reading the code and not running the code, its easy to miss things like "." or ":". Even in my "day job" id could spend an hour coding then compile only to find many typos causing it to not run.

Im happy to review anyones books, but keep in mind i only have limited time after to work to play

OZApps

"OZApps : I was one of the tech reviewers. I spotted a few spelling errors, but was told by the publishers not to report them as they would sort them out. They said to check for consistancy and if something was missing, etc... overall though, I think it's a great book - especially since it's his first.

Please do not get me wrong, I just meant that another set of eyes are always welcome. With Packt, I have been a tech reviewer on quite a few books and wel there is a way they work. When I tech review, I either change the words or add a comment to consider rephrasing or using alternatives. I think this book is a marvellous effort.

And my comment was trying to explain to @ArtLeeApps about the process. Plus the fact that many of the errors creep in due to Auocorrect, computers, accidental keystrokes and the worst of them all, when your brain like your computer gets laggy (at odd hours of the night)

OZApps

@OZApps that is exactly how it happens, and even after so many people rereading and rechecking, something always slips by

I know, when I look at my own book, I look at it and go, Geee how did that get past? That's how it is or depending on you look at it and take it. The book is quite nice.

Mells

Was a reviewer.
Doing spell check would have been a terrible use of my time (someone else can do it better and cheaper).
Basically if you pay someone to do something, you want to put "experts" in their field (expert is too strong but you get the idea. Someone who knows a little more on the topic than others) and tell them not to care about anything else.
As you can tell I was not contacted for my english speaking abilities
That's the editor's work to have someone look at this.

But I agree with @OZApps that it's important to have someone go through every code sample. The publisher has to coordinate all reviewer's abilities.

On my side, I stated right from the start that I didn't have time to test the code but would focus on other areas to provide feedback.

loucsam

I can't recall if it was mentioned, but it would be nice to have an errata web page somewhere.

ar2rsawseen

@loucsam, sorry I don't understand
you mean you want to see errata for book on a website?

loucsam

Correct I would like to see a web page with the errors.
There can a link from here somewhere, and also on the download page on packt.

ar2rsawseen

@loucsam hmm, that actually makes sense.
As it is my first book, I currently have no idea how it is handled, especially as it might differ from publisher to publisher, but let me contact them and check

ar2rsawseen

Aha, so here is how it goes:

Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us.

By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the errata submission formlink, and entering the details of your errata.

Once your errata are verified, your submission will be accepted and the errata will be uploaded on our website, or added to any list of existing errata, under the Errata section of that title.

Any existing errata can be viewed by selecting your title from http://www.packtpub.com/support.

@ArtLeeApps will you do the honor of being the first to errata my book

ArtLeeApps

Hi @ar2rsawseen,

Thanks for the open door to post away... Im posting at the errata submission site now.
It will save me annoying yous posting them here :-bd

speeder_kidoteca

ar2rsaween you approached Pakt or they approached you?


They wanted me to make the definitive Corona SDK book, and I ended refusing, first because they are messy (they sent me e-mails in seemly random times, forgot to reply e-mails, different workers tried to contact me without talking between themselves...), and second because the contract terms were just outright terrible (and badly written, I mean, monies, seriously?)

I wonder if you somehow figured how to convince them to make a good contract or something.

ar2rsawseen

They approached me, on this forum by pm, and it was a mini book so the contract was quite negotiable and did not contain anything I was not able to agree to

MikeHart

@speeder_kidoteca: Tell me, been there, done that, survied.

"Monkey Game Development: Beginners guide" is the title I wrote for them. I had a similar experience with them, but went through it. At first I had a nice project editor from England. After they moved everything to India, the process went downhill. Constantly changing editors, broken chapter files, rude editors, etc etc. Their technical editors screwed up formating and didn't check for grammar and spelling whatsoever, which I thought would be the case.

After the book was published, they didn't do any marketing besides a one time mentioning in their own newsletter. I was asked to do it all myself. I constanly have to remind them for the quarterly sales stats but I doubt I will see anymore money besides the advance I got.

If they ever want me to write for them again, then they have to pay much much more. :-)

The good thing is, I send them some corrections of the code files as an errata and I got a free ebook for it. I am not sure if they do that with everyone who sends erratas to them.

My technical reviewer experience with APress was awesome. Very friendly, understanding and supporting. To bad, I had to quit after a while but it still was a great experience. They also pay for technical reviewing too. Packt just offers you a copy of the book.

ArtLeeApps

@MikeHart ive sent about 6 errata to them now on this book and have 2 free eBooks so far.

im enjoying those of the train trips to/from work

ar2rsawseen

I don't know I actually had quite great experience with Packt.
Their dead lines really helped me keep moving forward, the editing was not painful at all, and I had really great technical editor, with whom we still are in contact and chatting from time to time.

About marketing, now there is a marketing specialist assigned to the book, and we are discussing marketing strategies and communities which can be approached.

Of course there are a lot of work I need to do myself, which Packt does not offer, as for example, creating a website for a book:
http://giderosgamedevelopment.com

Or writing guest blog posts, etc. But it is the marketing specialist, who is consulting and coming up with ideas, and arranging reviews and blog posts.

Maybe Packt came a great way after that time, don't know

ar2rsawseen

And first give away started:
http://appcodingeasy.com/Gideros-Mobile/Chance-to-win-a-copy-of-Gideros-Mobile-Game-Development

WauloK

My book review :

http://bluebilby.com/2013/12/04/book-review-gideros-mobile-game-development/

ar2rsawseen

Awesome, thank you.
And added it on the book's website:
http://giderosgamedevelopment.com/news/Book-review-on-BlueBilbycom

WauloK

B-)

paul_k_clark

Totally awesome, congrats and kongorats

ar2rsawseen

Just a reminder, that you guys still can win a free copy of e-book here:
http://appcodingeasy.com/Gideros-Mobile/Chance-to-win-a-copy-of-Gideros-Mobile-Game-Development

OZApps

Here is a review of the book,

Learning to make apps with Gideros http://reviewme.oz-apps.com/2013/12/learning-to-make-apps-with-gideros.html

ar2rsawseen

Thank you
http://giderosgamedevelopment.com/news/Book-review-on-OZAppscom