Hi all,

first of all, I’d like to give my sincere thanks to bsag, Reinier, and all other members of the Tracks team for a really cool app. I’ve been using it for a couple of months and find it really useful. One great feature is the mobile view. Works really well even on my small screen cell phone.

I was a little surprised to see that noone really seem to use the Assembla wiki. Personally, I think wikis are great for documenting projects. I’d like to use it both as a scratch pad for ideas, as well as documenting serious development.

Is this something you’d advice against?

(I guess it may lead to quite a lot of email traffic if using it for jotting down ideas, but OTOH it is possible to turn off email notifications).

We already have a wiki here, running on ExpressionEngine, which has a lot of useful information on it:

http://www.getontracks.org/wiki/

Rather than split content between the two wikis, which would just lead to people not knowing where stuff is, we’re keeping the Assembla wiki strictly for information to do with using Assembla, submitting tickets and so on.

Your login credentials for this forum also allow you to use the Tracks wiki I’ve linked to above, so please feel free to add any useful information you’d like to document.

btw, github has a wiki too and even supports project pages. But, like assembla wiki, we use the github wiki for github-related documentation only.

Sounds reasonable not splitting the information in two places. But do you think it is a good idea to add this kind of information in the ExpressionEngine wiki? Or is there a reason that there aren’t much development info there already?

If you think it is appropriate, I’m interested in creating a couple of pages with some development ideas. I see there is a lot if discussion in the forums, but I think the wiki gives a nice way of structuring the ideas from the forums/bugtracker.

FWIW: My background is mostly in Python and C++, but I am interested in learning Ruby just for the sake of this project. My main interest for now lies in improving the mobile view and adding dependencies/predecessors to actions/projects.

Most discussion on the development of a feature is done in the comments on the ticket of the enhancement request. Or on the mailing list. But, as our developer base is rather small, there is not that many discussion

I’d suggest you put the ticket-specific discussion / ideas at the relevant ticket. Other issues should get their own ticket too. That way we keep most discussion focussed on assembla.

For other ideas or bigger issues that do not fit a ticket, the wiki (expression engine) would be a nice place to discuss them and you can inform the mailing list about a new idea that is written out in the wiki. That way you can invite people to respond

There is a ticket (probable a few) wrt dependencies for actions. There is some discussion there for an approach to implement it. Furthermore, I’d like to hear your ideas on the mobile view

Hi bsag and Reinier,

thanks for your quick replies! I’ve had some further look into the tickets dealing with task dependencies. I see there are a lot of thoughts there already. I counted to at least five tickets with varying implementation ideas.

If noone stops me I’ll have a go at creating a wiki page that summarises the ideas from these tickets.

Regarding the mobile view - it is more small adjustments like long text fields that causes my mobile browser (Opera Mini) to have to scroll horizontally and some other minor issues. No conceptual changes at this point. I am impressed how well it works on a 176x220 pixel screen.

Hm, some trial and error needed to get things into the ExpressionEngine wiki. Is there a better manual than http://expressionengine.com/docs/modules/wiki/wiki_syntax.html around?

Just jotted down my ideas about action dependencies on http://www.getontracks.org/wiki/ActionDependencies/. Evolves mostly around a very simple GUI implementation - no fancy tree views, just treating the dependencies as an added filter/search criteria when displaying active and deferred/blocked actions.

I’ll try to find some time to check it out

I get “The path specified in your image upload preferences is not correct” when trying to upload files for my GUI mockup. Has anyone being able to upload files to the (EE) wiki?

Sorry about that - I hadn’t fixed all the config paths since upgrading to a new server. It seems to work now.

Thanks bsag!

I uploaded the screenshots to the wiki as well.