Is there a way to get ghost doc to modify an existing XML comment for a method (made by Ghost doc) to add a "modified by" line when you re run it on the method?
I personally think this is what source control is for, but they want to do it in the XML,
so it's a new work requirement.
(Disclosure: I represent the company that offers GhostDoc)
I agree with you that "modified by" belongs with source control and not XML comments.
But if you still want to get it done with GhostDoc you can use the tag to hard code "modified by" in Options. This won't set set current date/time dynamically though.
If you need the current date/time option, you can get this done with GhostDoc Pro only - use its T4 template based comments to configure the "modified by" comment/section with the BCL DateTime.Now function for the current time.
I hope this helps.
Related
I want to add the following functionality within a page's dialog.
Suppose you have text field A and text field B (to the dialog's yaml file).
I want to make field B available for the author (input) only when text field A has content.
I know it is a straightforward problem but i am relatively new to magnolia.Any help is appreciated
Thanks in advance
Unfortunately fields are completely atomic and independent so there's no way of fields reacting to each other without rewriting DialogPresenter to make them aware of each other.
You can see example of how this can be done e.g. in magnolia-external-form module if you use enterprise version of Magnolia. Code for it is in Magnolia's git repo.
HTH,
Jan
First of, is there any real documentation of the toolkit ? What I would like is to specify a range of selectable dates. For example I don't want to display dates before today. If the user select a start date of Jan. 27th 2012, I want to allow only dates after these for the return date
Documentation is a little bit sparse for the toolkit - your best bet is to look in the source of the sample app but they don't cover all the scenarios.
The default control doesn't seem to support a minimum or maximum value for the selected date, but if you download the source you should be able to modify it according to your needs. The layout of the source is pretty straightforward and you should be able to find an acceptable place to add the code, the only thing you need to decide is how you handle it from a UI perspective. In my opinion, you are better off handling the range check once the control returns - if it is an invalid date, pop up a message and re-show the control.
I've found that in the absence of documentation, the WindowsPhoneGeek blog (in this specific case see link here) usually does a good job of explaining the Silverlight Toolkit components in their various articles.
These articles can be a great help when following ZombieSheep's advice of taking a look at the toolkit sample code.
See the screenshot here:
I'd like the user to just type a city or country name and the autocompleter will show suggested items.
How should I start for creating it?
Are there any API(s) or web services for me to call?
Where can I find the database of all cities/countries in the world?
I think this would be the best database for your situation, check it out:
http://www.geodatasource.com/cities-free.html
You first need a autocomplete plugin.
I recommend to use the jQuery-Ui Auto Complete Plugin.
The database could as example be this, but eventually try to search a bit for yourself.
There was already a question on stackoverflow about a database for cities of the world.
A simple text file with all cities may also be this.
There are very much of those libraries, but you have to chose the right one for you.
My solution may not be the best, but it's a starting point:
Google a list with all countries (ISO-Standard), paste it into a txt-file. Then you can simply read that file with PHP an create a select menu with the contents of the file.
It does not incorporate the cities, but maybe it helps you in some way.
First of, is there any real documentation of the toolkit ? What I would like is to specify a range of selectable dates. For example I don't want to display dates before today. If the user select a start date of Jan. 27th 2012, I want to allow only dates after these for the return date
Documentation is a little bit sparse for the toolkit - your best bet is to look in the source of the sample app but they don't cover all the scenarios.
The default control doesn't seem to support a minimum or maximum value for the selected date, but if you download the source you should be able to modify it according to your needs. The layout of the source is pretty straightforward and you should be able to find an acceptable place to add the code, the only thing you need to decide is how you handle it from a UI perspective. In my opinion, you are better off handling the range check once the control returns - if it is an invalid date, pop up a message and re-show the control.
I've found that in the absence of documentation, the WindowsPhoneGeek blog (in this specific case see link here) usually does a good job of explaining the Silverlight Toolkit components in their various articles.
These articles can be a great help when following ZombieSheep's advice of taking a look at the toolkit sample code.
I can 't seem to find an example of the format Magmi wants for the csv data. Could someone please provide a one-line example of a successful product import?
Edit:
Magmi Wiki: http://sourceforge.net/apps/mediawiki/magmi/index.php?title=Main_Page
actually, it will depends on many factors (if you're importing images, creating categories, relationing configurable products, etc...), so there isn't a correct answer to your question.
But you can export a csv file of all magento's sample products (system -> Import/Export -> Dataflow - Profiles -> Export All Products) and take that as a reference, Magmi will understand it.
Notice that in order to use some parameters (for example the visibility values "Not Visible Individually", "Catalog and Search", etc...) as strings you'll have to use Magmi's "Generic Mapper" plugin.
I have spent the last month using it intensively, and must say I love it. If you have a more specific question don't hesitate to ask, it's still fresh in my brains :)
HTH
The trick is that Magmi often has it's own column names and requirements for field values. So, if you have a standard Magento import CSV, certain columns and fields will not get parsed.
for example, on a typical import magento uses "config_attributes" & "associated" as column names. For Magmi, you must use "configurable_attributes" and "simples_skus" respectively
As for the field requirements, the fields must often be in integer format. Magmi provides a "Generic mapper v0.0.6a" plugin that takes care of most of the standard mappings. For example, rather than using strings to assign "visiblity", magmi requies this value to be integer. The Generic mapper uses a configuration file that takes care of this:
visibility.csv
"Not Visible Individually",1
"Catalog",2
"Search",3
"Catalog, Search",4
Magmi is a wonderful addon - and really powerful with the plugins.
For information on it I'd recommend using the wiki at http://wiki.magmi.org/index.php?title=Main_Page.
For the csv, look at http://wiki.magmi.org/index.php?title=Import_-_CSV_datasource.
But as OSdave said, it is really powerful, and doesn't work with one csv format since you can remap and manipulate the fields anyway.
Hope that helps a little.