I have an interface (ISomeInterface) with full xml comments, and some derived classes with matching xml comments.
If I change the comment in the interface, is it possible to update the comments in all derived classes with GhostDoc (or any other tool)?
I appreciate this may cause unwanted changes in some scenarios but I'm not concerned about that in this case.
Yes, you can use Re-Document command of the GhostDoc v4.0 Beta - it will recreate XML documentation while preserve your custom tags.
Let me know if this helps.
Thanks!
Related
I would like to retrieve some properties e.g. jcr:created using Sightly or any related syntax for the panel component in AEM adaptive forms. 1
The previous Sighlty syntaxes that I have attempted to retrieve the crx/de properties include:
${properties.jcr:created}
${pageProperties\[jcr:created\].getTime.toString}
${guidePanel.jcr:created}
${resource.jcr:created}]
I have tried the following syntaxes but unable to retrieve the value from the property and in worst cases, the component may not be rendered on screen.
I have looked up on Adobe forum sites and past stackoverflow questions that other people may have asked. I have tried the solutions and given answers but was unable to achieve the result. I would greatly appreciate for any help or sharing of applicable knowledge if you have encountered similar issues or previously attempted to solve similar problems. Thank you!
You can always create Use class in Java or Javascript to access these properties, it's cleaner and testable. Better than that, you can use Sling Models which are more readable and easier to implement, here is a good presentation about it https://www.slideshare.net/accunitysoft/understanding-sling-models-in-aem
Properties of resources are readable without any extra definitions needed.
So you might want to check what resource is handled in your component by adding this:
${resource.path}
Then you can check the returned path in CRXDE if there really is a jcr:created property available at this path - which should be the case if you are accessing a resource that has a proper sling resource type. Then this call should give a valid return value:
${resource.path} ___ created:
${properties.jcr:created.getTime.toString}
If the path is not displayed as well, then it would help if you could post
the repo path of the content resource you are processing
the sling:resourceType
the path to the component's ht(m)l file that you are using
I am using the Zend Framework and I cannot locate in the documentation the values I can specify in the application.ini file. Does anyone have a link to where I could see them?
Thanks,
Darren
There is no exhaustive list, since you can specify arbitrary configuration values that are specific to your app.
The "built-in" stuff is mostly about configuting build-in resource plugins, so a good source of information on those might help you. The manual describes them in fair detail.
Is there some tool in Xcode that allows me to store snippets of code I often reuse in various applications so I do not have to retype it each time? I am talking about things like all the code that goes into defining Table Delegate Methods and Table Source Methods, UIAlertViews code and such. I just would like to have my own private repository where I can put snippets of code I think I may need in the future in other apps. Is there anything like that? Thanks for any help.
I guess the answer to your need is discussed in this page http://www.turkeysheartrhinos.com/?p=8. Look at the "Custom TextMate – Like Macros" section.
In Interface Builder you can drag and drop components you've built into the library under the Custom Objects list. These can be reused in other XIBs you build later.
I'm not sure about code snippets in Xcode itself, I would find that useful too. If you are talking reuse though, can you put alot of your generic stuff in superclasses that you can inherit from when appropriate?
Try "Edit User Scripts..." under the script menu in Xcode. Look at the scripts under the "HeaderDoc" header to see some examples of inserting templates into code. You'll have to reformat your snippets into blocks of Perl like these, but this approach also gives you those neat tab-through-able input areas like you see when you autocomplete method calls.
How about using the tool "sinppets" ?
In a large Application is there any way to distinguish user-defined classes with built-in classes without checking ?
You haven't specified which platform you're talking about, but in both Java and .NET, you're recommended to use the organisation name in the namespace, e.g. Microsoft.CSharp.* or com.google.base.*. That means if you know the full name of the class, it should be fairly obvious where it comes from... and an IDE will generally show you the full name of the class (including the namespace) if you hover over the brief name in code.
If this doesn't help, please clarify the question.
Who is going to distinguish it? Developers? Classes?
If Developers - Naming conventions
If Classes - you might wanna check the inheritance (parent)
I agree with Joh Skeet, you simply need to hover over the name of the class toget where it came from.
But, -- IF you're using .NET, and need a way to do it programmatically -- you could use reflection to get the assembly where the said class is defined, and probably the assembly does have the Company meta-data property set.
After I've generated the interface/implementation files for entities of a model file in XCode, I've not found a way to keep any custom code (validation methods, etc...) I've added to those generated files, given the scenario where I've added an attribute to a model entity and need to re-generate the interface/implementation files. Does anyone know of a way to make this happen? I've just been doing the copy/paste shuffle, but there has to be a better way.
Assuming that you're only talking about adding methods, and not new instance variables, I'd recommend using Objective C categories to add additional behavior to your model classes. Here's a blog post along the same lines.
Use mogenerator, which uses the Generation Gap design pattern to prevent your customizations from being overwritten when the code is re-generated.