librelist archives

home // archives //

« back to archive

Hackety plans/roadmap?

Hackety plans/roadmap?

From:
Scott Werner
Date:
2010-04-04 @ 18:30 
Steve, I was wondering if you had a list of what you wanted to get
accomplished for hh before releasing.  What I've gathered so far is:

Documenting the code

Testing (are there any examples of testing shoes apps, I'm new to testing
but need to learn and what better place to start?)

Re-integrating lessons/making new lessons

Integrating the yaml/sql gems

And that's about all I've got, am I missing anything?

After looking through the code a bit, I thought it might make sense to
eventually pull out the special shoes 'widgets' like sidetab() and so on
into something like a shoesUI library in an effort to simplify the code.
Might even help out the shoes community/project as well.

Re: [hacketyhack] Hackety plans/roadmap?

From:
Steve Klabnik
Date:
2010-04-04 @ 21:38 
Sure. The more I think about it, the more I see two releases in Hackety's
future:

A sort of .95 maintenance release, with a big old 1.0 to follow.

0.95 goals:

* Documentation/exploration/testing. These are all three sides of the same
coin. Documenting the code as well as the processes involved, which requires
exploring the code, and testing everything to make sure that it works
properly. I don't think lots of the Web calls do, for example.

I don't have any good resources for testing Shoes apps, sadly. This'll
require some research and trying stuff out.

* Integrating YAML/sqlite gems. And anything else where appropriate. Right
now, Hackety makes calls to the website via serializing objects via YAML and
then unserializing them on the other end. What? Yeah. JSON would be a lot
better.

* fixing up and testing the website integration, and fixing various bugs in
that as well.

1.0 goal:

Implementing Lessons, then promotion and PR.

beyond 1.0:

Interacting with the community, and iterating from there.


Make sense? Thoughts, anyone?

Re: [hacketyhack] Hackety plans/roadmap?

From:
Eric Mill
Date:
2010-04-04 @ 22:21 
Thought about HH's interaction with the web: it would be cool to
define a general API by which your site can interact with the Hackety
Hack client.  So I could have ericmill.com support the "Hackety Hack
API" in the same way that Wordpress supports the "Twitter API", and I
could be a host for lessons, user-written programs, and perhaps host
programs that the community could easily download into their client
and play with.

-- Eric

On Sun, Apr 4, 2010 at 5:38 PM, Steve Klabnik <steve@steveklabnik.com> wrote:
> Sure. The more I think about it, the more I see two releases in Hackety's
> future:
> A sort of .95 maintenance release, with a big old 1.0 to follow.
> 0.95 goals:
> * Documentation/exploration/testing. These are all three sides of the same
> coin. Documenting the code as well as the processes involved, which requires
> exploring the code, and testing everything to make sure that it works
> properly. I don't think lots of the Web calls do, for example.
> I don't have any good resources for testing Shoes apps, sadly. This'll
> require some research and trying stuff out.
> * Integrating YAML/sqlite gems. And anything else where appropriate. Right
> now, Hackety makes calls to the website via serializing objects via YAML and
> then unserializing them on the other end. What? Yeah. JSON would be a lot
> better.
> * fixing up and testing the website integration, and fixing various bugs in
> that as well.
> 1.0 goal:
> Implementing Lessons, then promotion and PR.
> beyond 1.0:
> Interacting with the community, and iterating from there.
>
> Make sense? Thoughts, anyone?

Re: [hacketyhack] Hackety plans/roadmap?

From:
Steve Klabnik
Date:
2010-04-04 @ 22:26 
Absolutely. Wouldn't that be a great project for someone graduating from
Hackety proper...


I'll have to write all of this up as a wiki page soon.

Archives based on code by Armin Ronacher //