Extension talk:Semantic Project Management

two tiny "issues"
Hi,

I just recognised two tiny "issues":


 * All extensions to Semantic MediaWiki are just moving to a new section on the version list of MediaWiki on Special:Version specially created for them. For consitency reasons it would be nice to see this one there too. I have looked at the source code of another semantic extension to see how it is done there: $wgExtensionCredits[defined( 'SEMANTIC_EXTENSION_TYPE' ) ? 'semantic' : 'specialpage'] Most probably this is not the whole story, but this might give you a first hint for coding.
 * The version is still on 0.3.1 in the code.

I am very happy that this extension has become reality and I a sure that it will be useful. Thank you for your work. I am going to give it a try this weekend.

Cheers --kgh 16:01, 26 November 2010 (UTC)


 * Thanks for your helpful comments! I fixed these two minor issues. I will look at the others in the near future. --Frank 09:57, 30 November 2010 (UTC)


 * Hi Frank, that's great. Thank you! Cheers --kgh 10:10, 30 November 2010 (UTC)

I18N
Hi,

I just saw that not all messages are available for I18N so far. Apart from the name of „Special:Semantic Project Management“ the whole interface is still available only in English. I am sure that this is in the pipeline so please do not feel offended by this post. Actually I just want to convey that I18N is very important for a software to spread and prosper.

Cheers --kgh 16:37, 26 November 2010 (UTC)

mktime
Hi, I have done some testing with this extension and get the following warnings in conjunction with "Real start date", "Real finish date", "Planned start date" and "Planned finish date": Warning: mktime expects parameter 1 to be long, string given in /.../SemanticProjectManagement/includes/SPM_ProjectManagementClass.php on line 711 Warning: mktime expects parameter 1 to be long, string given in /.../SemanticProjectManagement/includes/SPM_ProjectManagementClass.php on line 723 Warning: mktime expects parameter 1 to be long, string given in /.../SemanticProjectManagement/includes/SPM_ProjectManagementClass.php on line 778 Warning: mktime expects parameter 1 to be long, string given in /.../SemanticProjectManagement/includes/SPM_ProjectManagementClass.php on line 789 There seems to be a problem with the date conversion, though I am not sure. Cheers --kgh 23:12, 29 November 2010 (UTC)
 * After some thinking I have found the cause of the problem. You have to set "datetime" as the input type with Semantic Forms. Perhaps it would be good to let this extension autocomplete 00:00:00 in case not time parameter is entered by the user or the input type "date" is used. Cheers --kgh 23:39, 29 November 2010 (UTC)
 * A Workaround for this is to comment the mentioned lines and set the variables manually:

//$endtime = date("U",mktime($time3[0],$time3[1],$time3[2],$time2[1],$time2[2],$time2[0])) $endtime = '00:00:00';
 * I have fixed this issue. It always appeared if no explicit time was specified in the date sting. Please use the new version in SVN

--Frank 14:55, 12 March 2011 (UTC)

Date format

 * Hi, I strongly suggest to utilise the ISO-style date format YYYY/MM/DD for the output of dates by this extension to achieve better standardisation and even more important usability. Currently it is MM/DD/YY. Cheers --kgh 23:18, 29 November 2010 (UTC) PS I suppose it is better for MM and DD to be zero-padded, e. g. "01" rather than "1". --kgh 00:38, 1 December 2010 (UTC)
 * Hi, another thing I just realised. In case of the formats week and month, e. g. "11/14 - 11/20/10" gets shortened to "'10". I think it should better be "2010" or "10". Regarding the format week it would be very very cool to get, e. g. "10/46". However, one can overdo it too. :) Cheers --kgh 22:56, 30 November 2010 (UTC) PS One last thing: The first day of the week should ideally be Monday and not Sunday, e. g. "11/15 - 10/11/21" (ISO-standard).

Using this extension
Hi, I have to admit that I failed to get this extension working properly. It has something to do with the attributes connecting tasks with the work package and so forth since only the work package is rendered into the chart and not the connected tasks. A hint how it is done exactly will be greatly appreciated. Alternatively it would be cool if there was a publicly accessible wiki there this extension is running for me and others to see how it is done there. Thanks and cheers --&#91;&#91;kgh&#93;&#93; 22:25, 6 December 2010 (UTC)

Demo can be found here --Frank 15:59, 12 March 2011 (UTC)

I had to revert the SPM_Setup page after using the frontend to make multiple levels work again. --213.196.208.206 16:08, 3 September 2011 (UTC)

Add this extension to MediaWiki's Bugzilla
It would be nice to have Semantic Project Management listed as component of MediaWiki's Bugzilla --Planetenxin 06:52, 31 March 2011 (UTC)

[BUG] Conditions in ask ignored
Hi folks,

I've trouble with conditions getting ignored. In my case, only Issues with Start Date defined should be rendered in the Gantt.

My query:

As a result I get a number of error messages, one for each Issue with undefined Start Date/End Date ERROR: No valid time for E-Mail no startdate! no enddate! ERROR: No valid time for Dokumente erstellen no startdate! no enddate! ...


 * MW: 1.16.1
 * SMW: 1.5.5
 * SPM: SVN as of 2011-03-30
 * Special:SemanticProjectManagement: Level=1, Category=Issue,Property=-

Any ideas? --Planetenxin 07:03, 31 March 2011 (UTC)

Fatal Error : isKnown
Hi, I get this error while testing this extension : Fatal error: Call to a member function isKnown on a non-object in /var/www/wiki/extensions/SemanticProjectManagement/includes/SPM_ProjectManagementClass.php on line 439

Someone did already get this ?

Resource column
To populate the resource column include the resource parameter

This is a non-documented functionality --Xavier Atero 09:07, 26 May 2011 (UTC)

How to open task links in the same window
Modify SemanticProjectManagement\libs\jsgantt.js as follows: // function to open window to display task link

JSGantt.taskLink = function(pRef,pWidth,pHeight)

{

if(pWidth) vWidth =pWidth;  else vWidth =400; if(pHeight) vHeight=pHeight; else vHeight=400;

// var OpenWindow=window.open(pRef, "newwin", "height="+vHeight+",width="+vWidth); window.location = pRef;

} Discussion regarding pop up size and target window here --Xavier Atero 11:45, 26 May 2011 (UTC)

Parameter to choose display format?
Hi,

Extension works fine for me! One question: is there a way to choose the default display format? It is Day now and for me Week or Month would be more appropriate.

--AdSvS 10:07, 23 June 2011 (UTC)

Porting this to SMW 1.6.0
Hi, are there plans to port this to SMW 1.6.0? If yes, is there already a schedule for this? I would love to use this extension. Cheers --&#91;&#91;kgh&#93;&#93; 14:24, 5 August 2011 (UTC)


 * Hi again, is there a perspective for SMW 1.6+? Cheers --&#91;&#91;kgh&#93;&#93; 17:37, 1 November 2011 (UTC)

Bug in combination with AdminLinks
Seems there is a small bug related to the registration of this extension with Extension:Admin Links. In SemanticProjectManagement.php, where it says  it should actually state.

Patch: Index: SemanticProjectManagement.php

=
====================================================== --- SemanticProjectManagement.php	(revision 101353) +++ SemanticProjectManagement.php	(working copy) @@ -108,7 +108,7 @@ 		return true; $smw_docu_row = $displaying_data_section->getRow( 'smw' ); wfLoadExtensionMessages( 'SemanticProjectManagement' ); -	$srf_docu_label = wfMsg( 'adminlinks_documentation', wfMsg( 'spm-name' ) ); +	$spm_docu_label = wfMsg( 'adminlinks_documentation', wfMsg( 'spm-name' ) ); $smw_docu_row->addItem( AlItem::newFromExternalLink( "http://www.mediawiki.org/wiki/Extension:Semantic_Project_Management", $spm_docu_label ) ); return true; }

Remco de Boer 12:31, 31 October 2011 (UTC)

Hi, I keep receiving this error in my httpd/error_log
PHP Fatal error: Declaration of SPMGanttChart::getResultText must be compatible with that of SMWResultPrinter::getResultText

How to?
Can you please give me some direction where to go and create the PM items? I created the "levels" structure in special pages, but where do I go to add the items?

works with mw1.18.1 smw1.7.1
so happy, because i am not aware of php a weeks ago, and i am not a programmer, but i fixed it, work with mw1.18.1 and smw1.7.1. I spend three days

on configuring zend studiu (the remote debugg modules). However, i failed, so i just use vim and var_dump, everything seems so good.


 * Heiya, that's sounds pretty cool. perhaps you might want to share the code with us. A patch via bugzilla would be great. Cheers --&#91;&#91;kgh&#93;&#93; (talk) 09:21, 8 April 2012 (UTC)


 * i modified /includes/SPM_WBS.php  /includes/SPM_ProjectManagementClass.php  /includes/Ganttchar.php ,i can email these files from my email(extirpate0832@gmail.com). Becase i do not know how to use bugzilla.


 * Yes, I can file the patch for you so you do not have to worry about bugzilla. I will send you an e-mail. Great and thank you. Cheers --&#91;&#91;kgh&#93;&#93; (talk) 17:22, 9 April 2012 (UTC)


 * Done. :) --&#91;&#91;kgh&#93;&#93; (talk) 17:26, 9 April 2012 (UTC)


 * I do not know if it is a problem. Even on the example pages. http://km.aifb.kit.edu/projects/process/index.php/Project_Management.


 * Because in the special page of this example. There are three levels

of categories: Work Package, Task, Deliverable. And they are set to different colors: Red ,Yellow, and Green. The curious thing which confused me is why there are black lines in the ganttchart. Are they have special meanings or just are the bugs of this extension?


 * Another problem which costed me much time is not well fixed yet. When i thought i had finished my work, i went to the special page, and modified the settings, although I turned everything back to original. My ganttchart which was good and pretty changed, only the pages of "Work Package" were shown, and the colors are FF0000(red). I believed that no matter your MW is 1.81 or 1.56, no

matter your SMW is 1.71 or other version, if you save the special pages, this problem might occur. I guess it is cause by the variable "m_allSame" which is affected by the action of "Save". So i made a rough fix on it, i just set the variable m_allSame=true.