Type:
Feature
Priority:
Normal Normal  
State:
Open
Subsystem:
Server Web
Reporter:
Bjørnar Sundsbø (bsundsbo) Send Email
Assignee:
Kirill Maximov (maxkir) Send Email
Affects:
No affected versions
Fix for:
Backlog
Created:
16 months ago (04 Jul 2007 11:27)
Updated:
16 months ago (04 Jul 2007 18:20)
Votes:
0
Resolved:
JIRA source:
TW-2938

I would like an additional parameter for the <report-tab> element. I want to be able to specify if the report should be opened in a new window/tab. I have implemented a Sandcastle report, but because of the javascripts for the report, the url is relocated to Index.aspx. If i modify the script to relocate to http, it will flicker because its' trying to reclaim the IFrame (i think).

  • Yegor Yarko (yaegor) Send Email
    16 months ago (04 Jul 2007 11:31)

Seems, if the tab will open new browser window, it will not be a tab :) it will be just a link (ideally, with distinctive icon to note that a new window will be opened)


Maybe we should provide a way to add such artifacts links on the build results page and in build results pop-up (on overview).

  • Yegor Yarko (yaegor) Send Email
    16 months ago (04 Jul 2007 11:36)

Bjørnar,


For the time being you may open the report right from the artifacts. If you wish, you may add some simple HTML file to the artifacts that will open the report. This way the report will receive easy entry point and the report files may still be stored in an archive.

  • Bjørnar Sundsbø (bsundsbo) Send Email
    16 months ago (04 Jul 2007 16:32)

Yes, you are right, it will be a link, not a tab c",)


What I did, was to include a simple HTML file which will open a new window with the report, and display the text "The API has been opened in a new window". The only problem with the opening, was that the browser starts nagging about popups, but I think I should be able to find my way out of that mess (or tell the browser to accept popups from the site).


A more pressing issue I have with the report is that it seems to fail to display stylesheets from a directory higher up in the archive than the HTML file. Index.html reference a stylesheet TOC.css in the same directory within the archive as index.html. Within index.html is an IFrame which opens a file in the html subfolder. The css reference is ../styles/presentation.css, which fails to be applied to the displayed HTML page. Is there a problem with links in archives going up a few levels?


As an additional note, I wouldn't mind more documentation on extending TeamCity.


I think I should also add that I really like your product :o)

  • Bjørnar Sundsbø (bsundsbo) Send Email
    16 months ago (04 Jul 2007 16:49)

Artifacts link on result and build page sounds like a good idea.

  • Yegor Yarko (yaegor) Send Email
    16 months ago (04 Jul 2007 17:58)

Bjørnar,


The case you describe works OK for me. (I am attaching a simple example - html-upStyles.zip) It works OK loading all the styles when opened from build's artifacts. If the problem reproduces and TeamCity is to blame, please submit a new issue to address it.


As to good plugability documentation, creating one is one of the targets of our next version of TeamCity. For now,
some basic description at http://www.jetbrains.net/confluence/display/TW/Plugin+Development
(with attached sources of coverage plugin)
and a bunch of forum posts like:
http://www.intellij.net/forums/thread.jspa?messageID=5186195&#5186195
http://www.intellij.net/forums/thread.jspa?messageID=5190869&#5190869
can help.
For more, please ask at forums and we will try to provide open API guidance.

  • Bjørnar Sundsbø (bsundsbo) Send Email
    16 months ago (04 Jul 2007 18:20)

The sample you posted worked. I will have to look into the issue when I find the time. If I find something wrong, I will send you the sample. I can't send what I have now, as it contains loads of API documentation.

Old New
Bjørnar Sundsbø (bsundsbo) - 16 months ago (04 Jul 2007 18:20)

JetBrains Tracker revision #2008 [13-Nov-2008 11:56] (version #56) Copyright 2007-2008 JetBrains s.r.o.