チケット #5 (closed defect: fixed)

登録: 2 年 前

最終更新: 4 ヶ月 前

yamlに変わる拡張子を決める。

報告者: ikeji 担当者: somebody
優先度: major マイルストーン: First Release 0.1
コンポーネント: pragger バージョン:
キーワード: 関係者:

チケットの概要

windowsだと、関連付けがしたい。 yamlに関連付けするのはちょっと。 config.pra ?

添付ファイル

チケットの履歴

2007/02/15 01:43:09 更新者:anonymous

  • コンポーネントcomponent1 から pragger に更新されました。

2007/05/14 23:53:27 更新者:ikeji

  • ステータスnew から closed に更新されました。
  • 解決方法fixed に更新されました。

config.praに確定。

もちろん、関連付け以外では関係なし。

2008/05/09 16:30:53 更新者:anonymous

2008/05/31 15:30:25 更新者:anonymous

Cantera Doors are the leaders in the creation of custom wrought iron door grills.

This leadership position gives us the opportunity http://www.domainkr.cn to work with all of our clients to guarantee that your door will meet your exact needs. After we gather specifications and ideas from you, our award winning designers will create your door guaranteeing that the final product is both technically accurate and beautiful. http://www.buygoldbullion.cn Once this is done our designers pass it over to our manufacturing facility. There, your wrought iron door will be created by skilled artisans, http://www.fencelist.com.cn giving you a one-of-a-kind finished product, with its own copyright and trademark to guarantee your doors authenticity. This process is what makes each of our doors unique, and makes your door a true work of art. If you think that a wrought iron door might be the perfect http://www.show-china.com.cn way to finish your home or business, please visit our portfolio to see our full line of wrought iron door grills. When you are done please visit us at one of our showrooms or request more information by filling out our online form.

2008/09/18 09:56:02 更新者:anonymous

Both annotations and contributions will only clutter the interface by default as a design pattern rather than trying to put it all together. That way you can never create offline or print docs of high quality without again having the devs or current admins maintain the comments and annotations. Hopefully a small Wiki quality team will evolve (i am against ops or admins) to review and summarize the contributions. I hope this gives us more users as contributors than having the docs focused on the devs. Cheers, duns china tour Apparel shoes installing metal stair rails Interior stair handrail exterior baluster Glass wood stainless wrought CONTEMPORARY designs stairways aluminum modern log banister DECK outdoor price posts vinyl curved railsinstalling metal stair rails Interior stair handrail exterior baluster Glass wood stainless wrought CONTEMPORARY designs stairways aluminum modern log banister DECK outdoor price posts vinyl curved rails bags Kitchen Food and Wine Furniture) Flowers and Gifts Wall Art Computer Components I still prefer a wiki like approach since the php (or mysql) docs are very cluttered when you have to take their comments in account. On the other hand they are professionally maintained imho, since they are *much* better than KDE documentation. KDE is by far larger and has so many different apps, which need screenshots and end user not dev/api docs, that more help is needed as long as the devs prefer to code than to write nice docs. And it is their choice to some degree imo. Technically interested but non-dev end users, which are plenty out there, are the users of and the best contributers to the docs, since they know what to write about. And they are certainly more than devs.


追記/更新 #5 (yamlに変わる拡張子を決める。)




チケット属性を変更する
操作