I like history … but when it comes to software I depend upon for my livelihood … I tend to prefer to look to the future and not the past. Thanks for all the prior references to the existing options … but when considering that Hype Pro is a totally new offering … a tutorial for a version or more back that I devoured in it’s prime, is really of little use now. Otherwise, maybe we would be better off saving the money on apps and simply hard code our HTML 5 projects from scratch. Some attention to detail to offer insight on the finer points of what is possible with the app could go a long way in advancing the user base for such an app. I love that Hype is based upon a WYSIWYG fashion … but I would think it would behoove the developers to understand that not all of we users that shelled out the cold hard cash to acquire Hype Pro are life-long, dyed in the wool, HTML 5 aficionados … How are those offerings (which I utilized ages ago) supposed to help me with Hype Pro! I understand the basics … I wish to push the envelope! The tutorial page for Hype Pro shows one tutorial for “getting Started with Hype 3.0” … Not Hype Pro … followed by 9 Hype 2.5 tutorials with 1 hype 2.0 tutorial then two more for v1.5. If the developers don’t see the advantage to consider such an offering … there’s not much more I can do to encourage them. Look … I’m not sure where the conversation is leading … I was interested in more in-depth tutorials (not necessarily a book) that would help me utilize Hype Pro more effectively in my daily workflow to serve my client’s interests in a more efficient manner. So, I’ve been waiting to see what happens – while trying improving my skills with the software. Yet, if Hype is going to add more game development features… as suggested in the Is there a Physics API? thread …then that could change the theme / focus of the book. It might just be easier to start working on the book straight away. Yet, to properly run a campaign, a lot of work is required. To solve that problem, I thought about doing a Kickstarter. I’m not sure if this is a large enough community. My big concern about making a Hype book is that the software is too exclusive. So, I’m not sure if that’s three people in favor of the book. If I’m remembering it correctly, I think someone one commented that my GameSalad book didn’t focus enough on the “why”. Yet, it’s been a pretty good learning experience and I think it would translate into great examples for teaching how to use Hype. I’ve been working on a Hype project that has been a source of great frustration for me. Does that mean someone else would like to see a Hype book? The number one most common problem with software documentation is that it is written by technical writers on behalf software authors (people who worked their tails off to create inventive and powerful functions) rather than by “normal” people and it tends to focus so heavily on “how” but often leaves out the “why”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |