Xspec delivers HTML reports with test results. I'm looking for a way to avoid having an absolute path to a CSS file in the Xspec report.
I saw that there is a command-line option -i to place the CSS inline in the HTML page. The script version uses inline=true as the default.
However, the default in the stylesheet to format the HTML report is false. I'm calling Xspec from Ant, and I don't seem to find a way to add this option in the Ant call. Is this possible?
I'm answering this even if you found out the answer by posting on GitHub, hopefully it will be useful for other people.
As answered on GitHub, the functionality to have inline CSS when running XSpec with Ant is currently in two pull requests which should be merged soon into the master branch of XSpec. In the meantime you can use the branch in this pull request to have this functionality. Any feedback is greatly appreciated!
Related
I'm a Git/GitHub beginner and don't know YAML (yet).
I found this about making an issue reporting form, but I'm sure I won't get it right the first try, so I need a way to run it as a test without inflicting it on the live project.
I searched briefly and didn't see any application that would open and render YAML the way I would use a browser for HTML.
What's the best way to approach this?
I'd normally create a new project or repo to test on and when happy, simply copy paste the final result to the project you want to have these enabled for real.
I use github actions.
My gradle project use jacoco to produce a test coverage report, on the form of a website.
How can I display it directly on the browser ?
Actually when JaCoCo builds report in html format it produces a bunch of files and folders. So, there is no possibility to open that main html file directly in your browser. But here are possible solutions that might be useful for you:
Publish generated static files on some server, like GitHub Pages for
example. Where you can see generated report in a website mode (you
can configure notification with the link when published report is
ready).
Archive generated report and upload it as artifact. Then you
can easily find each report for each job if needed.
Build report as xml and just print it in output window.
Archive generated report and send it to some your running server.
Based on your needs maybe you find some of these suggestions useful but probably first option only directly answers your question.
My question is: Is there a feature in, or a plugin for, Visual Studio Code that would load and display the contents of the server-side-includes inline when editing an .asp file? I.e., is there a way to have VSCode build and display the page for editing in a similar way that IIS does when responding to an HTTP request?
Why I'm asking: At my place of work, our web pages are complicated messes of .asp files with server-side-includes (some of which have their own includes), some of which are out of our division's control. Some of these open HTML tags that we have to close in the top level .asp file. This makes editing and debugging these pages difficult. We can't use tag matching to tell if we've actually closed everything. A standard trick of ours is to just add closing div tags until it works. Changing how the pages are built is out of our control, it is the organization's way of enforcing a standard look and feel to the overall site.
To have browsable javadocs in a project hosted at Google-code, I got from here the recipe: set the correct mime-type property (text/html) when Subversion commits HTML pages.
Does anyone knows how to configure that in Subclipse?
This related question gives the pointer to do it in Subversive (there is a Preference tab for that). I couldn't find anything similar for Subclipse.
Someone comments about doing a Team->SetProperty for the whole javadocs dir (recursively), but that is not extension specific (I'd want text/css for stylesheets, for example); and further, I guess, if when new files are created I must remember to do it again...
Is there an alternative?
Update (2001-06-11): In case somebody is interested: I couldn't find a way to accomplish this, so I ended switching to Subversive.
To configure the MIME types information, edit the following file:
Windows 7/Vista: C:\Users[YOUR_USER]\AppData\Roaming\Subversion\config
In the config file, locate the property enable-auto-props and uncomment it. It should be set to yes. Make sure there is no space at the beginning of the line:
enable-auto-props = yes
The last section will be [auto-props] and by default everything will be commented out. Add your required file type with the appropriate config.
It's possible to do part of the work in the shell, by setting mime-type via script.
In building a Tumblr theme I've got an external .css on my server which is very convenient because I can work directly in my editor, save to my server and refresh to see my results.
However, if I need to make changes to the HTML of my theme I've been making the changes in my editor, copying everything over to the "Customize Theme" option in Tumblr, then having to save there. This is really tedious and cumbersome because of the way their editor is laid out (the html covers the entirety of the the preview).
Does anyone have a smoother workflow?
Even if it involves just viewing my .html directly from my server when tweaking, then pasting it in when done. Like some way to inject test content so it's not just the html template tags?
While Tiny Giant Studios is right as far as the Theme Garden is concerned, there's nothing stopping you from externally hosting 'til your heart's content while you're actively developing.
To that end, you might try Tumblr Themr. I haven't actually tried it yet, but it sounds promising enough.
EDIT: Seeing as the original link is not resolving, you may also try their github page
The short answer is an unfortunate no.
The Tumblr system requires that all assets (from CSS files to images) be kept on the tumblr server. Seeing as theme developers (at the moment in any case) do not have direct ftp access to a theme's directory (if that even exists), one cannot work from an editor (e.g. notepadd++) alone...
I'm not sure if they're looking into changing this, but for the time being we're stuck with being copy/paste solutions.
One thing you could, however try is copying over all the HTML markup and then using browser plugins - like stylebot or developer tools for chrome - to write the CSS and once you're done, copying over all the CSS in the head section of your theme.
I have recently found that Tumblr features GitHub integration where you can just push to a repository and it updates the theme on your blog. I have not tried it myself but I probably will here in the next few hours.
Check it out!
EDIT: My mistake this is only for theme creators who plan on submitting their themes to the list of Tumblr themes that can be chosen by users. Someone may still find this useful so I will leave this answer.