weekly update

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
marvil07's picture

WU12: Version Control API and family changes

Here the last 3-weeks WU :-)

Now the details.

Read more
marvil07's picture

WU9: Version Control API and family changes

Well, I miss one WU, but here the 2-weeks update :-D .. a little late :-p

Week 1: Making backend class abstraction work with git backend and planning interfaces again.
in the middle: lot of sdboyer interaction!
Week 2: Choose where to use interfaces and where inheritance can make the work better.

Now the details.

Read more
marvil07's picture

WU7: Version Control API and family changes

This week my mentors and me made a new plan to beat our targets, so you can see how it changes at my project wiki.

Well, this week I also divided it more less into the same sections :-D

Read more
marvil07's picture

WU6: Version Control API and family changes

I miss one WU again(:-( mainly because of final deadlines in my courses last week), but here are the news for both weeks.

It's divided in 3 sections: tests, stable branch and oop branch.

Read more
snufkin's picture

WU: Bot tests and documentation

Completely forgot that we need to write weekly updates, thought everything moved to the wikis, sorry about that.

Read more
marvil07's picture

WU4: Version Control API and family changes

I missed one WU, so what have been done since then:

  • array access really helps to migrate to OOP, so each class implements that SPL interface
  • Like it was expected, dia auto-generation only did the easy part, and like it's mentionen in WU2 I made a bulk update on each class trying map all needed functions as methods. After that I needed to make lots of manual changes, to use the methods and data members, but also fix the last ones to made relations between classes.
  • I'm using references to the "parents" on "children", instead of lists of "children" on "parents" or both approaches (like item class repository data member instead of list of items on repository). This is not definitive, but now it's like this.
  • Replace username on versioncontrol core in favor of author and commiter.
  • Use already defined database identifier names instead of "id". This is mainly for use the cool drupal_write()
  • New stuff working pushed on versioncontrol core oop branch, but like you imagine I needed a backend to test, so I used my own branch of git backend
    • Repository add/edit/delete/fetch
    • VCS Account add/list
Read more
haxney's picture

WU 2: Completion of Version Control Integration

A little late this week, as I was moving into my summer apartment.

Read more
marvil07's picture

WU2: Version Control API and family changes

Coding:

Read more
haxney's picture

WU1: Completion of Version Control Integration

This week was not a terribly busy one, with most of my time spent getting acquainted with the APIs of Drupal, the versioncontrol module, and Subversion. I was able to complete the pre-commit hook for Subversion, as well as the basic configuration for the other Subversion hooks.

Read more
marvil07's picture

WU1: Version Control API and family changes

Last week was kind of little productive one :-(, but good news, coding started :-D

  • Closing initial aspects of how to make the OOP implementation of versioncontrol
  • Coding started:
    • It's based on initial dia2code files, but like you are thinking, it's just first draft. So now it could be possible to include more aspects postponed on diagram and I'll clean by hand all not-useful code.
    • Just first attempt, more coming on oop branch.

The plan is replace functionality with OOP keeping the branch as stable as possible.

PS: We did not agree on a title format for weekly updates, so I propose one: "WU: "

Read more
Subscribe with RSS Syndicate content