I am learning how to make an AnimatedList. I ran the example from the documentation. Although it is not nearly as easy to understand and use as a ListView, the example worked. However, there was a message on the documentation page:
This page is deprecated and its content may be out of date.
Usually when something is deprecated there is a better way to do it, but I cannot find any other information. What is wrong with that documentation page that makes it deprecated?
It looks like this style of documentation has been discontinued.
Thus, the code is not up to date and also not maintained anymore.
/docs/catalog/samples is not really part of the "Docs" tab on flutter.io anymore.
It only redirects to a "curated list of samples", which is not related to the /docs/catalog/samples/... section of flutter.io.
The AnimatedList class can be found in the widgets documentation.
Some of the widgets have samples built into their docs page. An example of this would be Column.
Hence, the conclusion that the old samples are not needed anymore.
Related
I am currently learning Flutter and followed the official introduction on the Flutter website, which worked without any problems. On the page there was a link to part 2 on Google Developers Codelab.
First there is some information, including a code template for the second part, which is the same as my code on part 1. Then the actual coding part starts and here is the problem. It says to make changes in a widget that I don't have and wasn't mentioned before. The problem is that I know basically nothing about flutter and don't know where it belongs and also the whole context is missing, so I don't know what else is in the widget.
At the end of the chapter is again a code template given in case of problems, but again there is no trace of the widget. Maybe I've overlooked something, but I'm pretty sure that there is an error at this point.
Edit
This is the problem:
And this is their code template without any trace of a _buildRow() method
I have seen official flutter firestore material only in pub.dev
But there even wasn't a single sentence about getDocuments().
Which site should I look at if I want to do a full formal study on this?
I have already seen cookbooks on flutter dev.
Not much to study, there is even implementation on API refrence. However its just few lines, but I don't know what more there could be...
You can get there from package main page, on the right.
In the following documentation, https://github.com/reactiveui/ReactiveUI/blob/docs/docs/basics/routing.md
It states that by setting up ReactiveUI.Mobile, you will be able to achieve correct handling of the back button for free. I've tried to look around for documentation but can't seem to find any.
Could someone point me to a suitable link / sample that I can refer to?
It states that by setting up ReactiveUI.Mobile, you will be able to achieve correct handling of the back button for free. I've tried to look around for documentation but can't seem to find any.
Setting up RxUI.Mobile is super platform-dependent, and you only get a free back button on WP8 Silverlight apps. I'd stick with just using routing (or avoiding routing altogether) for now. RxUI.Mobile will probably change quite a bit in 6.0 (it's my least favorite part of the framework at the moment).
I get the following errors from the Google Rich Snippet Tool for my website http://iancrowther.co.uk/
hcard
Warning: This information will not appear as a rich snippet in search results results, because it seems to describe an organization. Google does not currently display organization information in rich snippets
Warning: At least one field must be set for Hcard.
Warning: Missing required field "name (fn)".
Im experimenting with vcard and Schema.org and am wondering if I'm missing something or the validator is playing up. I have added vcard and Schema.org markup to the body which may be causing confusion. Also, I am making the assumption I can use both methods to markup my code.
Update:
I guess with the body tag, I'm just trying to let Google discover the elements which make up the schema object within the page. I'm not sure if this is a good / bad way to approach things? However it lets my markup be free of specific blocks of markup. I guess this is open to discussion but I like the idea of having a natural flow to the content that's decorated in the background. Do you think there is any negative impact? I'm undecided.
I am in favour of the Person structure, this was a good call as this is more representative of the current site content. I am a freelance developer and as such use this page as my Organisation landing page, so I guess I have to make a stronger decision of the sites goals and tailor the content accordingly, ie Organisation or Person.
I understand that there is no immediate rich snippet gains, but im a web guy so have a keen interest in these kind of things.
With schema testing, I find it easiest to start from the most obvious problem, and try to work our way deeper from there. Note, I have zero experience with hcard, but I don't believe the error you mentioned actually has anything to do with your hcard properties.
The most obvious problem I see, is that your body tag has an itemtype of schema.org\Organization. When you set an itemtype on a dom element, you are saying that everything inside of that element is going to help describe that itemtype. Since you've placed this on your body element, you are quite literally telling Google that your entire page is about an organization.
From the content of your page, I would recommend changing that itemtype to schema.org\Person. This would seem to be a more accurate description. Once you make that change and run the scanner again, you may see more errors relating to the schema and we can work through those too (for example, you'll probably need to set familname and givenName).
With all of that said, you should know that currently there are no rich snippets that you will gain from adding this schema data. Properly setting this up on your page, is only good to do, especially since we don't know what rich snippets Google or others will expose in the future, but currently you won't see any additional rich snippets in Google search results from adding these tags. I don't want to discourage you from setting this up properly but I just want to set your expectations.
Every single GWT example I look at contains references to $PP_OFF. See http://code.google.com/p/google-web-toolkit-doc-1-4/wiki/DevGuideStyleSheets or http://khanzeeshan.wordpress.com/2009/06/12/creating-project-for-gwt-1-5-3/ for example.
What does $PP_OFF mean?
It's a bit of defunct wiki markup. The Google Code wiki treats {{{...}}} blocks as code and attempts to pretty-print them, which doesn't always work well; $PP_OFF is, or was, an undocumented feature that's supposed to stop that happening. See http://groups.google.com/group/gwt-google-apis/msg/04ae50fdd4339294 for the only mention of this that I can find online.
You should completely ignore it wherever you see it.
(You might be wondering why it would appear on some random person's WordPress blog, which of course isn't using the Google Code wiki. The answer appears to be that the person in question just copied-and-pasted stuff from Google's documentation. See http://code.google.com/webtoolkit/doc/1.5/tutorial/create.html if you're curious about the original source which, of course, he didn't credit.)