spazcore-dev Google Group

Re: Documentation Assistance

2009-08-17T01:30:05Z

No, there is not. The current document was really a "brain dump" of
what SpazCore is and how it relates to Spaz, some basics about what it
consists of, and what we should be working on. It's a bit out of date,
and certainly could use a lot more detail. There's also almost no
detail about coding or examples.

Re: Documentation Assistance

2009-08-12T22:47:12Z

OK that makes sense. I'd noticed there was a section about how to build Spaz
and that seemed more appropriate for developer content, which is why I
asked. For the developer wiki on GitHub, is there a particular table of
contents structure that already exists somewhere? There are several items on

Re: Documentation Assistance

2009-08-12T22:31:05Z

That is stuff specific to the desktop app.

SpazCore is a set of components we're using for the basis of different
versions of Spaz. It could also be used in other apps, though.
SpazCore is really only of interest to developers.

Spaz itself is multiple applications, currently a desktop app and a

Re: Documentation Assistance

2009-08-12T22:14:08Z

I noticed there were topics covered in the "Spaziki" [1] that weren't in the
Github wiki, unless I'm mistaken and I just didn't find it. In particular
the "Customizing Spaz" section didn't seem to be addressed in the GitHub
wiki. Is this stuff that you want to keep around? If so, should it go over
to the GitHub wiki? Or would you like an entry in the tenderapp FAQ with

Re: Documentation Assistance

2009-08-12T22:06:26Z

I know dude, that's not what I meant. Thing is, I don't know what I
meant. That's the beauty of the web -- you say a thing at a time and
it's there forever ;-)

Re: Documentation Assistance

2009-08-12T22:06:09Z

So we're talking about the same thing, here's what I'm referring to:

[link]

The Github repos all have their own wiki. I would like to use this
wiki for developer docs. So, we keep them where they are.

I think the voice is pretty decent here (I used "we" since it's not

Re: Documentation Assistance

2009-08-12T21:53:53Z

I've been looking at the developer documentation that already exists in the
wiki. Would this stay in its current location, or are you proposing this
should be moved to the source repos? I'm willing to do this if it needs
doing :) I also notice that the docs in the wiki have a particular "voice"
to them. Would you want to maintain that "voice" or go for something more

Re: Documentation Assistance

2009-08-12T13:54:22Z

We're all busy, Graeme; please don't feel bad that others want to help
too. You are a huge part of the Spaz project.

Also, remember that we're talking on this list about SpazCore, so this
would be developer-oriented docs. Stuff specifically for Spaz *users*
should be handled in Tender (FAQ/KB stuff), or in a separate help

Re: Documentation Assistance

2009-08-12T09:37:05Z

Aww geez. That hurts.

Augustina, some of the stuff from here ([link])
has been transferred to here ([link]). But the
"new" style (i.e. tenderapp) doesn't seem to lend itself to structured
documentation. At least to my eyes. So I'm wondering how something

Re: Documentation Assistance

2009-08-11T18:05:48Z

I'm terrible about getting back to people, so I apologize for that.
But, we do need better docs, and any work you could do in that area
would be massive.

Really the only docs there are to speak of at the moment are code
comments and the examples directory. Of course I know how it all works
in *my* head, so I may not be the best person to judge what should be

Documentation Assistance

2009-08-11T16:45:22Z

Hi! I wanted to find out what areas you need docs written or edited
for. I contacted Ed privately indicating I am interested in creating
developer docs for the API down the road. I would like to start out
with end user docs. Are there topic areas you need covered in the FAQ/
Knowledgebase? Generally I start by looking at forums to see if any

Re: New SpazCore junk

2009-06-23T20:25:47Z

Coolness! I only caught the Event lib bit earlier when scanning my
email since Google shortened the post before delivering.

New SpazCore junk

2009-06-22T22:17:11Z

(sorry for the cross-posting. I'm a jerk)
So I made some SpazCore updates recently. Here's a quick overview:
- Added Event helpers for binding and triggering events. This is to be
used instead of jQuery stuff. Listener supports modifying the scope
the handler is executed in.
<[link]>

Hello World

2009-05-04T13:23:24Z

I'm starting using spazcore to create my own twitter client. Let me
see if I got the idea right to do my first hello world

1) include all required libs?
<script type="text/javascript" src="JQuery/jquery-1.3.2.min.j s"></
script>

Re: New example twitter search app

2009-04-01T15:00:05Z

Thanks for putting this up, I'll be looking at this later today/
tonight to help me.

Re: SpazCore Roadmap

2009-04-01T14:58:41Z

Threw together some initial stuff for handling storage/retrieval of
data last night, mostly just a knockoff of the JazzRecord HTML5Adapter
with the addition of finder and deletion methods. It's on my fork of
the repo under spazlocker.js. It doesn't have all the niceties of
JazzRecord itself but I'm wondering if I might end up swapping it out

New example twitter search app

2009-04-01T14:33:48Z

I added a really simple Twitter Search example "app" (I cringe at
calling it an app, since it's just one html file).
<[link]>
I think this shows off a lot of what you can do with SpazCore now.
Note that to load it, you'll need to have a browser that will allow

Re: SpazCore Roadmap

2009-03-31T19:42:51Z

Like we just talked about on IM, @thynctank already is taking the lead
role on DB stuff, but I'm betting he'd be very open to offers for
help!

--
Ed Finkler
[link]
Twitter:@funkatron
AIM: funka7ron
ICQ: 3922133
XMPP:funkat...@gmail.com

Re: SpazCore Roadmap

2009-03-31T19:23:10Z

Ok I'll start playing with the DB abstraction library. An ORM can be
added on TOP of it but DBALs aren't ORMs.

Re: SpazCore Roadmap

2009-03-31T17:49:06Z

baahhahahahah that sounds like planning.

So, sorta. I have the README file from the git repo. I've filled in
estimates of how close we are to completion on each aspect:

--------------

Initially, I'd like to target the following platforms:

* AIR
* Titanium
* Palm webOS

Here's what is planned at the moment:

SpazCore Roadmap

2009-03-31T17:28:23Z

@funkatron, would you happen to have a roadmap designed or thought for
this? A list of things you'd like to get done?