Docs needs to be updated!
kefahB opened this issue · 3 comments
Hi everyone,
It is really a shame that the docs of such a grate repos to be with a lot of error .. we spends ours in order to understand how it works!
Please, let's make it clear and intuitive for every body, we should think about new member to NS, if they hurt to the docs as it, they will go to other technology!!.
Tabs is a small example:
<Page xmlns:mdt="@nativescript-community/ui-material-tabs">
<mdt:MDTabs selectedIndex="1"> <!-- HERE >> mdt:MDTabs -->
<!-- The bottom tab UI is created via TabStrip (the containier) and TabStripItem (for each tab)-->
<mdt:MDTabStrip>
<mdt:MDTabStripItem> <!-- HERE >> mdt:MDTabStripItem-->
<Label text="Home"></Label>
<Image src="font://" class="fas"></Image>
</MDTabStripItem> <!-- --------- HERE >> no mdt -->
<mdt:MDTabStripItem>Item class="special"> <!-- LOK AT THIS!! -->
<Label text="Account"></Label>
<Image src="font://" class="fas"></Image>
</MDTabStripItem>
<mdt:MDTabStripItem>Item class="special">
<Label text="Search"></Label>
<Image src="font://" class="fas"></Image>
</MDTabStripItem>
</MDTabStrip>
<!-- The number of TabContentItem components should corespond to the number of TabStripItem components -->
<mdt:MDTabContentItem>
<GridLayout>
<Label text="Home Page" class="h2 text-center"></Label>
</GridLayout>
</MDTabContentItem>
<mdt:MDTabContentItem>
<GridLayout>
<Label text="Account Page" class="h2 text-center"></Label>
</GridLayout>
</MDTabContentItem>
<mdt:MDTabContentItem>
<GridLayout>
<Label text="Search Page" class="h2 text-center"></Label>
</GridLayout>
</MDTabContentItem>
</Tabs> <!-- --------- HERE >> no mdt and no MDTabs -->
</Page>@kefahB i can understand tour frustration. But i need you to understand that those are community project managed by people on their free time. No one is paying me others to maintain this.
You might have lost time (which I don't think are hours) I spends hours a week maintaining this, answering people and ensuring this works best for you.
You are welcome to create PRs for doc that would be a great help.
Side note: docs are great I agree but as a user of other libs I always tend to look at demos and examples first. They are almost always more up to date than docs ( because devs like me use it to test).
And this repo is no different. The vue app will always be showih the most recent way of using any component.
I am sorry and sad you are not happy. Yet my answer will always be the same about doc. If you don't like it you are welcome to create a PR. It will help you, me and all.the community
Dear @farfromrefug,
Of course I know that everybody work freely and generously .. and please understand that my post here is not because I am not happy or some think, you may know when I am facing an issue I do push a PR if my competence allow me to do so.
My post is purely to go forward with NS.
About the demo, look at the repo, when you navigate to the demo snippets you do not found the demo for Nativescript Core!, yes you can say it almost the same but not always.
With all respect for those who spend there times for this repo espcially for you dear friend
@kefahB ok i hear but then for example avoid capital letters in your title ;) does not feel really nice or understanding.
About the demo. I get your frustration about core demo. But again understand our situation. Managing demo app is a lot of work too, and you wont be able to maintain all flavors (more are coming!!!!) especially with a big plugin like this one.
And tbh i absolutely never use core. So i simply wont write one. The community is free to add one
Finally vue syntax is really close to core one. ONce you ve understood how corexml works, porting vue to core should be easy. But most of all i know you can read the vue template, understand it and thus use it as a doc to write your core app.
Thanks for your kind words.