I'm creating an MVC app, following the tutorial. I noticed that the routes.jl file is a read-only file. Why is that so? Shouldn't it be writable, because we need to change it by adding more routes?
The same question applies to files like connection.yml etc. Why are they read only?
The reply I received from the community is that it is not meant to be read only. It becoming read only, is a bug which was supposed to have been fixed earlier.
Related
I have a need to document methods/functions in *.cpp code files that are not part of a .NET solution. Up until now my workaround has been to create a solution, but this is a time consuming step for all the different files I come across.
Does anyone know how this can be accomplished?
Scott,
Unfortunately, this is the workaround that you have to use as long as GhostDoc relies on some of the information from Visual Studio CodeDOM... The CodeDOM does not provide any info when you open just a single file.
Do you mind me asking if there is particular reason you are opening single file in VS? Other that these might be random files that are not part of a solution?
Thanks!
I've being using JSLint for some time now and recently found JSHint. Reading the docs I learned that it can be configured using a .jshintrc file but I could not found if it's possible to generate this file using the CLI.
Is there a flag in the CLI to generate such file (preferably with all the options set) or another tool that allows me to do that?
Not really going to answer your question but I found the JShint I use on some article about code style guides, in a free HTML eBook SpeakingJS - Style guide.
They talk about Google's guideline, AirBNB's guideline, jQuery's guideline, and others, most of the time those links provide its a ready to use jshint file ... may be this could help you :).
If you want to generate your own JSHint, I don't know if you are familiar with Yeoman but this project is exactly what you re looking for : https://github.com/losingkeys/generator-jshint
After generating it, any text editor can be used to edit such a simple file.
The ability meteor gives through its interaction with cordova to create mobile applications is incredible. I have one question however concerning the file structure: (https://docs.meteor.com/#/full/structuringyourapp). There is no documentation concerning a folder specific to Cordova. As I have been writing my application, it seems incredibly tedious to use if (Meteor.isCordova) for any segment of code that I want specific functionality for the mobile app. I tried creating a top level folder cordova such as is already done with client, server etc... and removing the Meteor.isCordova wrapping my js code, but that process was unsuccessful. Is there a way to do what I am trying to do just in a different manner?
There are currently no special folder for code which should only run on mobile. However it is a nice feature and I have created an issue on GItHub. If you'd like to see this feature, I'd encourage you to comment on it.
I am trying to generate a Sandcastle help file for a website. In the properties window for project, there aren't any options for creating the XML Documentation File required for Sandcastle.
The Build tab in the property pages only contains options for: Start Action, Build Solution Action, and Accessibility validation. I don't have any options for Output, or XML documentation file, like my other projects have.
The website I'm working with does not have an actual .proj file, which could be the problem. If this is the problem, what is the best way of creating one for a project that is under source control and being worked on by many people with minimal disruption?
This is using Visual Studio 2005 professional.
The problem with websites in VS2k5 is that, when they get compiled, the resulting dlls are a mess. No namespaces, weird names, etc.
If you truly want to generate a Sandcastle Help File, look at converting your website into a web application. You can definitely generate source code docs for that.
I haven't tried it yet, but you might want to try the following
Documenting Web Sites / Projects from Eric Woodruff's site. It gives the specifics on how it can be done.
Update: I did try it and it works for regular websites. The only issue I can see is
that the websites don't have namespaces. So when I run it I get a topic by
FolderName_WebPage Class format without any logical grouping. So it is alhpabetical by
folder and page name. Once you got the content created, you can edit the help file using
a helpcompiler / builder and group the topics as needed.
if you're familiar with Liferay you'll know that when you make an itsy-bitsy change to a css file you shall rebuild the theme and redeploy it.
As for redeploying I made a symlink (mind you I'm on Windows: for the curious creating a symlink on Vista is just a matter of issuing mklink /d dir1 dir2).
But what about rebuilding the stuff with maven? I'd rather skip that step. Basically what it does is combyining and packing all CSS in one everything_packed.css. Is there a sort of config variable to tell liferay just to include the raw files and skip redeployment alltogether?
Thanks
Guys I found the solution myself.
You should have a file called portal-ext.properties file in
$TOMCAT_DIR/webapps/ROOT/WEB-INFO/classes
Or more specifically for my win setup in
C:\liferay\webapps\ROOT\WEB-INF\classes
The file would hold the value
theme.css.fast.load=false
This will prevent liferay to be looking for the everything_packed.css and so you're free to modify your stuff without rebuilding and CTRL-R to refresh the page and see the changes.
Just for completeness, as this question is somewhat old and the problem already solved: There's a lot more along these lines, e.g. javascript, layouts etc. that can be used uncached. This is documented in either the Liferay Wiki (as Developler Mode) or the Development Guide, available from the documentation site (though currently it's not there for the last version - if it's still not there when you're reading it, look for it (PDF) in the older versions.
It's advisable to use these settings only in development, not in production, as putting all css and javascript in as few files as possible results in a huge performance impact.
to include all those settings, just can also just add the following line into your portal-ext.properties file:
include-and-override=portal-developer.properties
this will include all the developer specific settings, and when you want to remove them, you can just comment out this line.
you can edit the css files of your theme from Webapps{your theme}\css
And can see the changes directly.
You can edit almost every file which doesn't require compilation.like .jsp files but not .java files