Re: libseed-list A couple o' wee Tutorials

[Tim Horton <hortont424 gmail com>]

That looks perfect (and thanks for the commit!) - I'm on the road, sorry I didn't get to that one (or the others) on bugzilla earlier!

Master was the right place, too. We always do new development on master and then branch off for x.y releases when hard code freeze happens.

Also, 2.29.91 release is on Monday, so anything you get in by then will be in the next release. Then, 2.29.92 is March 8th, and hard code freeze is on the 15th; 2.30 is March 29th. You're free to commit at any point (we like to keep master fluid) except the 15th, because it's unclear at what point during that day I'll create the 2.30 branch.

Also, yell at me before making C-side API changes, because we have to make sure even *more* that we stay stable there (we don't want to cause Epiphany crashes!).

Anyway, thanks for the commit and the patches! It's awesome to have other people poking around :-)

--Tim

On Feb 20, 2010, at 22:40, Alan Knowles wrote:

> What's your general git commit process? (I'm more of a svn/cvs guy) - so git's got a bit of a learning curve..
> git clone ssh://myaccount git gnome org/git/seed
> // make changes
> git commit [the file that changed]
> -> fill in summary + description.
> git push origin HEAD
> ** last one pushed to 'master'.. not sure if that's where it's supposed to go....
> 
> Regards
> Alan
> 
> 
> 
> 
> 
> 
> --- On 19/Feb/2010, Tim Horton wrote: 
>> +1; you guys are free to do whatever you want to the wiki, and a page with tutorials sounds like a *great* idea
>> 
>> Also, if you have Gnome Git access, you're both free to commit to Seed. I'll still make releases, check on tests, and keep an eye on what's going on, certainly, but having school and various other things going on right now makes it hard to have much time for Seed; it would be great to have other people committing directly without the overhead of bugzilla/patches (on both ends).
>> 
>> The Gnome reference manuals are generated by gtk-doc, which does scan the source. However, I think racarr was talking about coming up with a way to work around that to generate something more like the PyGtk reference (http://library.gnome.org/devel/pygtk/stable/). But I don't think that went anywhere.
>> 
>> With all the different bindings going on, we should definitely come up with some sort of global solution for this, though, which takes GIRs, and, given some mapping information for each language, generates nice gtk-doc. Not sure how to do this, though.
>> 
>> There's a lot of stuff in the Seed reference manual about the C-side API, but not very much about JS-side stuff (which is mostly in the old, really bad, pure-HTML reference stuff that you guys have seen around). I had planned to move that over but haven't gotten a chance to do that, and it's been a really long time.
>> 
>> On Feb 18, 2010, at 13:51, Alan Forbes wrote:
>> 
>>> I think it would be a great idea until something more professional can
>>> be done (I believe the Gnome reference manuals are generated from source
>>> code so not sure if it is technically possible to generate manuals to
>>> reflect introspected bindings) and allow folk new to the project to find
>>> stuff quicker rather than trawling through the web.
>>> 
>>> If it goes ahead, I'll keep it up to date with my own tutorials and
>>> others, although it might not be updated as quickly at certain times due
>>> to work, family and other commitments.
>>> 
>>> 
>>> 
>>> 
>>> On Thu, 2010-02-18 at 13:30 +0800, Alan Knowles wrote:
>>>> Forgot to add - perhaps we should set up a page
>>>> http://live.gnome.org/Seed/Tutorials
>>>> 
>>>> Regards
>>>> Alan
>>> 
>>> _______________________________________________
>>> libseed-list mailing list
>>> libseed-list gnome org
>>> http://mail.gnome.org/mailman/listinfo/libseed-list
>