Here’s a quick update about the progress of this project. It’s about 12% complete. That’s slower than expected, but the project should move more swiftly now. (About four work days were diverted to get Apparatuses online.) Also, I’m moving a little bit slower because I want the book to look nice.
Oh yeah, and I think I might be going a little crazy.
(Shooting Stars started playing on my playlist while animating the fish. Heh, felt like the perfect background music.)
I got up to the “Rotation follows motion” part. I started wondering if I should add a graphic to better explain the effect. Next thing I know, I’m drawing a fish. HA HA!
I’m not sure if I’ll use it. What do you think?
- I like the fish!
- I don’t like the fish!
The books is now 25% complete.
Lots of new templates are appearing on the website.
Since Christmas Eve, a new template has appeared at Photics.com every Tuesday. Two templates are already queued up for the next two weeks.
Remember, if you want to be notified when the book is available, like the second post.
OK, less talk, more work.
UPDATE: The book is now 33% done. It looks like target of completing the book in the first-half of 2020 is still in sight.
Excited for the printed book! Thanks!
Looks like there’s an update to an earlier statement…
…since December, I’ve been copying and pasting the previous book content into the new book — creating new screenshots and updating the text. That part of the project is almost done.
The goal is to have a beefy sized book — 500 pages. But after migrating the content, the book is around 250 pages. The remaining “Publishing” section content needs serious updating and the last two chapters of the “Examples” section are moving into a new game development section.
That means about half of the book will be new content.
The book is about 50% complete!
Since the project is now moving into the original content stage, I was looking back at old messages and comments for ideas. Here’s one in particular…
Remember, if you want to be notified about when the book is available, heart the second post in the thread❣️
I voted no.
I doubt this could be pulled off in a chapter (say 25 pages?). While beginners can definitely learn something in this amount of space they will be like the blind man feeling an elephant - the description of the animal will vary with the area being touched. They need to see the whole beast.
I don’t understand the resistance to buying a book dedicated to the subject.
I was actually thinking something shorter than that — closer to a cheat sheet, but probably somewhere in the middle — more like 10 pages so people can get up to speed.
The chapter would be for beginners.
So far, looks like I’m leaving the chapter out. HA HA. There are only two votes so far though.
Hopefully I’m not wasting my time with this project, as I’m putting a lot of work into the book. Nah, of course I’m not wasting my time. When I look at the book so far, I smile. I think it’s really good… and that’s without the freshly killed trees smell.
Ok, I am likely not going to buy the book ( if I was just starting out I would though. ) but… maybe
Some basic explanations of what people are seeing when they see the use of JS.
• var ( what a var is )
• What no var indicates.
•Scope of vars and global ( in regards to Hype and Doc/window)
• Scope of scene objects ( including if exists yet or not )
•Operator basics - + * = > < <= >= ! !== != == === && || : , ; $ ( string + symbol as apposed to maths +)
• basic functions named/un-named
• id v class ( also picking up ids and classes from elements in Hype )
• var & class naming conventions
• console.log() why it is your friend
As someone who is just getting to start their education and training in JS, I understand that in older code writing is what uses var and it has been substituted now by let yet, they are both used for variable declaration in JS. At least that’s what the training I’m taking right now specifies…
And so that’s why I believe JS should not only be brushed up lightly in the book, if you are going to take that route is because JS is a whole other training in itself. Things like the definitions should be synchronous with the latest and greatest standards.
Just a thought…
All the best @Photics ,
Yep let is also a good point to add. But could become confusing in a short basic explanation.
Also it is not a substitute for var.
It has different scope and definition implications
You didn’t totally rule it out, so you’re saying there’s a chance.
Maybe you too will want to have “A Book About Hype” up on your shelf, as a symbol of your mental prowess in the area of web animation, design, and development.
Not in this book. HA HA!
Because Hype supports IE 6-9, I’m sticking with “var” instead of using “let” for constants… https://caniuse.com/#feat=let
Shoot! Clicked the wronk button. Can I change my vote to “no”? I rather see you focus on Hype and after the books finished, maybe spend time on an addendum?
I think the book project is great and I will buy a copy out of curiosity alone. I am also investing in Hype Cookbook (although I was busy with birthdays and client work the past month). I think THIS book (by @Photics) is and will be a must have for beginners and people starting out. I intentionally didn’t try to overlap the scope to much with my effort. So I am focusing on “recipes”, ideas/lookups and useful code fragments. Basically it is aimed at more advanced users. Also it won’t be published as a hardback apart of maybe some print on demand copy if backers want it.
Coming back to the topic of JS in this book… it most likely a book of its own but there is this special breed of Hype specific API calls. This certainly can’t be found elsewhere and that is the sweet spot on JS for a book about Hype in my opinion at least. Also some basics on understanding JS and Hype function scopes.
Have nice weekend you all.
To add to @MaxZieb’s comments…
A post was split to a new topic: Improving Accessibility
Don’t worry, I pretended that you voted no.
Thanks for voting — poll closed.