17
I Use This!
Activity Not Available

News

Analyzed about 3 years ago. based on code collected over 3 years ago.
Posted almost 13 years ago by bherlig
Contents 1 The story 2 Enter Templates 3 Putting it All Together 4 ...And Beyond 5 Shortcuts for Everyone! The story While I do have a throughout knowledge of Origo, I'm no expert in each and every one of its third party components. But only ... [More] practice makes perfect, right? I was delighted the first time I found out that you can reference issues in a concise way, using the custom build-in handle [[issue:xxx]]. Someone apparently realized that always typing the full path to the issue would be tedious. My only gripe with this shortcut, is the way the link is rendered: it's verbatim what you enter: issue:xxx, which I think could be more elegant, and also shorter. A common way of referencing issues is to just to state its number: #xxx. Luckily, Mediawiki's powerful syntax and rendering capabilities provides us with an easy way to customize the above shortcut to our liking, as all links can be given custom titles. So most of the time when linking to an issue, I've used the above shortcut, but with a custom defined title. Instead of [[issue:xxx]], I was using [[issue:xxx|#xxx]] (note the pipe-symbol separating the link from the given title), resulting in a nice short link #xxx. Enter Templates Of course we could change the implementation of the issue handle, but this would add complexity to both the code and the usage of the handle. After thinking a bit about better ways to achieve my goal of not only a concisely displayed link, but also of a terse way to write it in the wiki page's source code, I've (re-)discovered Mediawiki's templates. Templates enables you to define a standard text, and reuse it by embedding it within other wiki pages. While there is a convention to put templates into a separate namespace (by prefixing template pages with Template:, in Origo they are defined in the normal, non-prefixed namespace - they are created just like normal wiki pages. But the best part about it: the template text is parameterizable! Supporting both named an enumerated parameters, we can define a template using some parameters, and use it by passing some arguments. Putting it All Together There we have the perfect tool for customizing just about any wiki-markup. Here's how I used them for issue linking. Create a new wiki page used as a template. I've named the page i for issues, to make it as short as possible). Here's its content:[[issue:{{{1}}}|#{{{1}}}]] You can see that this resembles the "issue-link-with-custom-title" from above. Note that the issue's number is replaced by a parameter (the first parameter when using the template). Simply use the template (again and again) by embedding the template-syntax (two curly braces) in any regular wiki-page:{{i|xxx}} Note the parameter "xxx", which is separated by a pipe-symbol. Defining this simple template now enables me to quickly link to issues. It might not be super short, but if you're working on a page linking to a lot of issues (like I [Origo Releases often do]), it saves quite some time. But why stop there? ...And Beyond As mentioned above, we can use templates to customize any wiki markup. When closing an issue with a fix, we from the Origo Team like to state the Subversion revision containing the fix. Linking this revision number to the Diff-page is quite tedious, though. Here's how such a link - including custom title - looks like: http://svn.origo.ethz.ch/wsvn/origo/web/?op=revision&rev=xxxx This is not only quite a long string to type, but also to remember! Templates to the rescue... I created another template page called rev: [http://svn.origo.ethz.ch/wsvn/origo/?rev={{{1}}} rev.{{{1}}}] Note the similarity to the issue template? One parameter, used in both the link and the customized title. Linking to a revision is now a trifle: {{rev|xxxx}} Shortcuts for Everyone! Of course you can use these templates in your project, too. Just create a new wiki page in your project(s), and copy the code above, save - and you're ready to quick-link, too. Did you find other good uses of templates? Feel free to share them in the comments below. [Less]
Posted almost 13 years ago by bherlig
Dear Origo users, I'm happy to announce that we just successfully concluded another update of Origo. As announced in January's blog post, we were able to fix some prominent bugs that caused problems in various parts of Origo. Here are the most ... [More] prominent changes Pathauto rules We've had problems with wrongly generated links, in both work items (and thus the mail notifications) and wiki-pages. We now generate (and sanitize, i.e. remove some special characters) in the front-end, and send them to the back-end to insert into the work-item system. Nice URL's Issues now get a "nice" URL. While you could already access issues by the path ..../issues/123, one was redirected to another URL ..../nodes/42. With this latest update, the "nice" URL's are now permanent, and will show up in your browser's location bar. Note that this affects only newly generated issues! API-Changes To keep Origo flexible, we had to change some API calls (related to the project type and its visibility. Developers of applications interfacing with Origo through its public API should refer to the changelog for a detailed description. As always, the more technical details of this update and its list of bug-fixes can be viewed in Origo's changelog. What's next? We're already tackling the next release - Milestone 2010.2 is planned an being worked on, where we will improve the current work item system. Regards, The Origo Team [Less]
Posted about 13 years ago by bherlig
We finished moving the servers, well before the deadline. All services are up and running once more, and are ready to be used. As always, should you notice any problems, please don't hesitate to contact us.
Posted about 13 years ago by bherlig
Dear Users, On the upcoming Monday, we have to relocate our servers to another data centre within the premises of our hosting provider, ETH Zürich. This concerns all our machines, which means that all of Origo's services will be offline for a couple ... [More] of hours. When: Monday, January 25, 9:00 a.m. CET (Zürich time), 8:00 a.m. GMT/UTC Affected Services: all Duration: open, but at least 5 hours Of course we will try to keep the downtime as small as possible. Barring unforeseen circumstances, we expect Origo to be up and running in the early afternoon. [Less]
Posted about 13 years ago by bherlig
The Origo Team just finished planning the next development milestone for Origo. With a release date of Tuesday, February 16 2010, its goals include fixing prominent bugs, namely Fixing wrongly generated links (e.g. #721, #608 and #303) Various ... [More] image-upload issues, partly caused by wrong link-generation (e.g. #714) In other related news, I'm happy to announce that I'm now employed by Oriact to work part-time on Origo. This means that Origo I'm now able to devote more time to Origo, including administration, continued user support, and of course development time as well. [Less]
Posted about 13 years ago by patrick
Happy new year to all Origo Users We just updated Web SVN to a never version and also switched to a more modern layout. Beside many improvements and fixes this version fixes a lot of issues related to moved or renamed files/directories. Your Origo Team
Posted about 13 years ago by patrick
We just upgraded all repositories to subversion 1.6. Among other benefits such as new and improved features this should also reduce the overhead of our backup and therefore the performance of the subversion repository during the night should improve ... [More] drastically. See http://subversion.tigris.org/svn_1.6_releasenotes.html for details of new and improved features of subversion 1.6 Your Origo Team [Less]
Posted about 13 years ago by patrick
We finished deploying a new update with several fixes see changelogfor the changes.
Posted over 13 years ago by schoelle
The OpenExpo will open its doors in Winterthur next Wednesday and Thursday (September 23/24), an exposition devoted to open source software. A number of well-known projects are participating. OpenExpo is part of the topsoft trade fair. Entry is free. ... [More] http://www.openexpo.ch/ As already last year, the Origo team will be present at the OpenExpo. We are looking forward to present Origo a larger audience. For you, the OpenExpo is a unique opportunity to get to know the people behind Origo. We are looking forward to get to know as many of you as possible. You can chat with us about technicalities, exchange ideas about new and existing features, or just talk with us and give feedback. We are also looking for people that are interested in joining the team and improve the project. There is always enough work around. We are looking forward to see you, The Origo Team PS: attached is a flyer that we are distributing at the OpenExpo. Print it, fold it, and give it to all of your friends. AttachmentSize origo-leaflet.pdf1.63 MB [Less]
Posted over 13 years ago by patrick
Due to a problem with one of our servers, several of our services were down today (mainly subversion repositories and download). This has been fixed now.