https://github.com/vuejs/vue/issues/4677
Hope to my needs, can be answered.
many thanks.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 4 years ago.
Improve this question
I've just started learning structured data and I'm still trying to wrap my head around the concept.
First I started out with Microdata using schema.org vocabulary and now I'm learning JSON-LD.
The thing that is bugging me is that 'how do search engines know that the structured data that I'm providing in the head matches with the content of the page?' because in the specific case of JSON-LD I'm not specifying which element contains what information.
This was not the case in Microdata where I provide the structured data in the element itself. And to add to my confusion I've read in multiple articles that Microdata & JSON-LD have the same result, which means my understanding of Microdata is wrong too!
Please help me with this.
Thank you
Think of JSON-LD and MicroData working in compliment. Where there's a lot of content on your page, go with MicroData as the work is already there. You're familiar, and so you know about structuring your page to work with it. JSON-ld is basically an easy short-cut for identification.
(This is not intended as an 'expert' answer, but a simple answer for someone still learning the ropes.)
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Look, under page title there's a very nice link, including categories of the website.
I really do want that thing on my website. The problem is the syntax of my website:
Main page: index.php
Category: index.php?p=part&id=[ID]
Subcategory: index.php?p=cat&id=[ID]
Article: index.php?p=post&id=[ID]
What should I do? Changing syntax is no good for me, but I'm pretty sure I can do some magic with htaccess RewriteEngine, but it's not going to look much better.
Huge thanks in advance :)
Ooops, almost forgot. Can I have some kind of guide to a proper sitemap? I already searched for it myself, but every guide offers it's own way to make it, and I'm totally confused.
These breadcrumb links in the SERPS are not only from microdata, but are from the breadcrumb navigation links on the sites pages. (which can indeed be marked up with microdata, but do not have to be) Google will tend to use them if urls are very long in my experience.
More info here:
http://googleblog.blogspot.com/2009/11/new-site-hierarchies-display-in-search.html
and here:
http://www.youtube.com/watch?feature=player_embedded&v=-LH5eyufqH0#!
and here
http://support.google.com/webmasters/bin/answer.py?hl=en&answer=185417
It's called microdata. You can find the officially supported microdata at schema.org. Keep in mind that using microdata does not guarantee your search results will be affected.
This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.
Closed 10 years ago.
Is there any library containing an object to create a drop-down list like an HTML <select> for my iPhone app? I have all the values in an array and want to allow the user to choose one.
I would start by looking at the UIPickerView class reference and documentation. There is also links to sample projects on the OSX documentation.
See this answer for an example of what a UIPickerView looks like.
You can take a look at this github project (disclaimer: I wrote it): https://github.com/daschae/Nine90. The select control attempts to deliver the same experience as mobile Safari. It has served me well, and I'm open to feedback regarding its fitness for your purpose.
This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.
Closed 10 years ago.
The form loads well into SharePoint and looks proper in Chrome and Firefox but for some reason my font styles are not applying and my input field settings aren't taking affect in IE 7 and 8.
Very frustrating, especially because there's no where to check the code to see if there's some stray tags that should have been cleared out.
Anybody run into this before?
Whats the best method to clean it up?
problem solved. it was a stylesheet issue. the stylesheet was being loaded in twice for some reason. This created this bizarre conflict.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I want to make a technical documentation of an existing web site for developers so that new developers can continue to work with it. In existing codes, little (or not at all) in-code comments or doc-strings are available (bad practice, I know). Yeah, I have seen some posts related to these. But those were not that detailed. Here are all my questions:
What to include?
How to organize? I mean, can you suggest some hierarchy so that new developers can easily get onto the track?
What are the best practices?
Can you show some samples?
How can it be made easy? Some ppl suggests wiki tool but I know nothing about it, will it be useful? Can you suggest any tool with some quick starting tutorial?
I have never made one. So I appreciate any kind of answer. Thanks in advance.
(Links will be helpful but please give a quick and lucid summary of it)
Quick and lucid:
Think of it like any paper.
What is the goal of the app (website)? [why?]
How does it achieve this goal?
What problems have arisen?
What problems could arise?
What could be expanded upon? [why?]
What problems could expansion cause? [why?]
What naming/formatting conventions should continue to be followed?
Outline format is great.
In addition to Nona's suggestion I would also say that it is important to break down the code and explain any conventions and intentions of the code so that there is uniformity between developers for things like ID values, CSS classes, and JavaScript function names. Be as specific as you determine necessary to prevent a new person to the team from reinventing work.
If you're looking for a quick way to get through your code, try .NET Reflector. It gives you a broad overview of all your classes, methods, properties, etc. so that you can write all the technical documentation you need without actually going through the files. It's super easy to browse through and it will even show you the code itself.
Have you thought about representing what is there with some UML notation? That's what UML is for! If the new developers are good then they should be able to understand it.