thegoodfellas/blogset-br huggingface dataset:
mostraram que os cosmeticos anteriormente ao uso de propriedadesvegetais, eram feitos com oleo mineral que prejudicava muito a pele pela suacomposicao de macro moleculas que nao deixa a absorcao de outros componentessaudaveis ocorrer. Fora outro fator que e a composicao a basede agua, a agua hidrata e nao nutre, por isso pode ate dar uma sensacao demelhora da pele, pois quando entra em contato com as celulas causa um inchacomomentaneo, mas em poucas horas e absorvida pela corrente sanguinea.O oleo de coco pode ser aplicado diretamente na pele e nos cabelos. NaIndia e comum usar oleo de coco como um condiconador natural. Se voce deseja usar o oleo como condicionador, nao ultrapasse de umacolher de cafe (para cabelos curtos e medios) e colher de cha para cabeloslongos. Esta tecnica pode ser usada antes do banho. Depois lavar o cabelo comum xampu sem sal. (tecnica indiana) ou voce pode usar pouco depois dos cabeloslavados e enxaguar. Separe uma toalha do seu enxoval para fazer isso, podeocorrer um leve cheiro de oleo. Ha quem possa trocar os oleos de banho industrializados (mineral) poroleo de coco com algumas gotas de lavanda ajuda a nutrir e muito a pele. Para quem tem picadas de inseto, pode anotar uma receita, macere folhasde coentro com oleo de coco alivia e muito. Pode ser utilizado comocicatrizante junto a curcuma, e no alivio de eczemas e dermatites de contato,bem como no tratamento do herpes e candidiase.Vamos la caderninho nas maosContra picadas de inseto Uma colhe de oleo de coco para um punhado de coentro, macere bem eaplique na regiao afetada ( otimo para picada de butuca, mosquito oupernilongos, borrachudos)CicatrizanteUma colher de sopa de oleo de coco e uma colher de cafe de curcuma ouacafrao da india, misture bem e passe na regiao afetada ( ajuda no combate depele acneica ( cuidado que o acafrao mancha roupas e fica com a pele um poucoamarelada) se for o caso aplique nas espinhas a seguinte receita: uma colher decafe de oleo de coco, 5 gotas de O.E de tea tree e 5 gotas de lavanda. Para nutricao da peleTres colheres de oleo de coco com 20 gotas de O.E. de lavanda e 5 O.E degeranio. Passar antes do banho ou apos o banho.O.E = Oleo EssencialCabelos, normais secos ou oleosos. Apenas puro. Cabelos com Caspa quantidade de 5colheres de cha de oleo de coco e 20 gotas de O.E de Tea Tree ou oleo de cococom sumo de um quarto de limao. Tem que lavar o cabelo com agua abundante e naose expor de maneira nenhuma ao sol. Muita saude!!!
apessoa supra toda a deficiencia de nutrientes de acordo com sua predisposicao,doshas e desarmonias. Nossa preocupacao e a introducao correta da alimentacao vegetariana. Para agendar seu horario - cris_ayres@ayurelements.com - 21-77122411Servico oferecido nas cidades do Rio de Janeiro e Sao Paulo
triggered quirks mode. The last time I tried to count, there were 5 doctypes that triggered almost standards mode, and 73 that triggered quirks mode. But I probably missed some, and Im not even going to talk about the crazy things that Internet Explorer 8 does to switch between its four four! different rendering modes. Heres a flowchart. Kill it. Kill it with fire.)Now then. Where were we? Ah yes, the doctype:That happens to be one of the 15 doctypes that trigger standards mode in all modern browsers. There is nothing wrong with it. If you like it, you can keep it. Or you can change it to the HTML5 doctype, which is shorter and sweeter and also triggers standards mode in all modern browsers.This is the HTML5 doctype:Thats it. Just 15 characters. Its so easy, you can type it by hand and not screw it up.Source: http://diveintohtml5.info/semantics.html#blank-space-gotcha
So people.. there's being a long time I have no time to publish here, but in the next days I'm planning to talk a little bit about some interesting SEO tools. This should be interesting for those who are interested in Web Marketing and e-commerce, in general.Here I present you the tools I'm going to talk about:Google Insights for searchAlexaGoogle AnalyticsYes, there are lots of others SEO tools, and there are much more concepts involved in this subject, than just tools, such as web development, but just to introduce you, I'll talk about these three tools in the next posts and give you some ideas. Usually the developers use the attribute font-size in CSS specifying the font size in px, pt or em, for example. Most of them don't know it doesn't work in Opera... So, you need to have in mind that Opera follows the W3C specifications and, as it's true, if you are trying to change de font-size attribute for Opera Browser without success, you can see how to do this by visiting this website or just by taking a look at the following image:I really think it helps in the standardization for the use of the fonts... I'm not telling that I like it, because it forbides us to make hacks, but we must try to do the things ok, right? Hoje resolvi postar em portugues para disseminar aos brasileiros que estao pensando em comprar um novo Smartphone um pouco da minha experiencia de uso com o Moto g, o novo Smartphone da Motorola.Pesquisei muito antes de compra-lo, pois sempre fui fa da Samsung e Nokia. A primeira barreira a ser vencida foi a da marca. Essa foi facil superar, pois ao pesquisar descobri que o Moto g foi desenvolvido pela Motorola enquanto a empresa pertencia ao Google. Isto implica no fato de que o Moto g combinou muito bem seu sistema operacional com seu hardware (processador, memoria...).A segunda barreira foi que, apos descobrir o Moto g, fui um pouco mais alem e descobri o Moto x (que e considerado por muitos a obra prima do Google junto a Motorola). Nao vou entrar em detalhes sobre este aparelho, mas o que pesquisei conclui que apesar de ele ter um processador de dois nucleos (contra um de 4 do Moto g), seu processador e sim melhor. Isto, alem de outros recursos de reconhecimento de voz que o Moto x tem me seduziram a querer compra-lo, ate que seu preco de 1399 reais me fez optar por desistir (deixo claro que o valor dele ainda e baixo se comparado a outros modelos do mesmo nivel de outras marcas.) Como nao queria gastar mais de 1000 reais, voltei a cobicar o Moto g novamente e analisar concorrentes da Samsung. Do meu ponto de vista a Samsung pecou por ter lancado uma gama de aparelhos diferentes e com variadas opcoes (e aquela questao do paradoxo da escolha, onde voce oferece opcoes demais e o cliente passa a ter muitas duvidas e nao se decide.) Acabei aceitando o Galaxy s3 mini como concorrente do
Moto g (ambos inclusive estavam custando o mesmo preco). O Moto g bateu o s3 pra mim por alguns detalhes, como protecao Corning Gorila glass 3 contra riscos na tela, velocidade de transferencia de dados ao usar internet (21mbps contra 14 do s3 mini), camera frontal de 1.3mp contra uma vga do s3, alem do dispositivo da Motorola ser 2 anos mais moderno que o da Samsung e vir ja preparado para receber o Android KitKat e , o melhor de tudo, o processador do Moto g que e um quad-core.Esses foram os principais pontos que me ajudaram a optar pelo aparelho da Motorola, alem tambem de ele vir com o Android puro (sem customizacoes e aplicativos que as empresas costumam adicionar, o que pode tornar o desempenho do aparelho um pouco lento as vezes).Moto G VS Samsung Galaxy s3 mini (fonte: gsmarena.com)Bom, hoje completam 2 semanas que estou com o aparelho e realmente so tenho elogios a respeito. Os servicos do Google funcionam muito bem, o reconhecimento de voz para localizar lugares e dirigir usando o GPS e outra coisa sensacional (mas que e independente do aparelho, e sim do sistema operacional (ou seja, deve funcionar bem em qualquer aparelho com Android).Tambem usei o Bluetooth para transmitir musicas pelo som do carro e funcionou tranquilamente. Antes deste aparelho, eu tinha um Samsung Galaxy Ace, que comprei em 2011 quando estava na Franca ainda e o aparelho nao estava mais suportando novos aplicativos, acusando falta de espaco interno. O Moto g tem duas versoes, uma com 8Gb e outra com 16Gb de armazenamento interno (fornecendo ainda 50gb disponiveis no Google drive). Por alguma razao o meu Google drive ainda nao reconheceu e me forneceu estes 50gb, mas acredito que conseguirei resolver este problema assim que tiver um tempinho, entrando em contato pelo suporte da Motorola que posso acessar diretamente pelo aparelho.PS: Uma outra novidade interessante e que a Motorola divulgou na semana passada que em breve, o drive mode (diferencial forte do Moto x) sera disponibilizado para o Moto g. Esta funcao identifica quando o usuario esta dirigindo, le as notificacoes recebidas e ainda permite respostas rapidas enquanto o usuario nao pode olhar a tela.Algumas fontes de pesquisa: Comparacao Moto G vs Samsung Galaxy S3 miniInformacao sobre a linha de processadores dos aparelhos
So fellows, two weeks ago I had the pleasure of participating in a User Experience design course.It was managed by Edu agni, and began on Friday with the Responsive Day, where we learned some concepts of "Mobile First" and Responsive web design.Nowadays, when we design a website, we should consider that it can be seen in several types of devices (desktop, tablets, smartphones). This way, the mobile first concept says that we should start developing for the smaller device and then improve the system for the desktop version (when I say desktop version, I refer to a website displayed in a laptop/desktop browser).But why to start by the mobile version? The answer is simple: If you start to think how to design for a small screen device, you will focus on the information that really matter. This will ensure that the user experience is 'usable'. Also, you can optimize user experience by adding some media queries and applying some styles to display and position information for other devices with different resolutions (designers applies the therm Progressive Enhancement in this context, where you start developing from the simplest, and keep improving the system for other resolutions).Besides that, we also learned some techniques to understand user requirements (to define it!) such as User Cases, User Stories, Scenarios, Card Sorting. This last one we practiced a bit and it was a very interesting experience, which I'll probably try to apply in the product I work.Usability Evaluation was one of the main topics we learned in the UX course, and of course, Jacob Nielsen was referenced, as expected, with his 10 heuristics (I'm planning to talk about it in a future post).Well, It was really productive and I could 'update' my skills as front-end developer.Here is a pub about the UX Weekend (by the way, I'm in the video! haha) O JavaScript surgiu em 1996 no Netscape Navigator, num contexto onde otimizacao nao era algo muito considerado pelos desenvolvedores, embora as paginas levassem bastante tempo para carregar.Seu surgimento veio com o proposito de melhorar a experiencia do usuario, realizando tarefas mais simples diretamente na pagina ao inves de utilizar o servidor para isso (imagina voce preencher um formulario, esperar de 30s a 60s pra envia-lo apos submeter, e depois receber uma validacao de que um campo nao foi preenchido?! pois e!) Nessa epoca o JS era utilizado meramente para enviar mensagens.Com a chegada do IE4 no mercado e o dynamic HTML (capacidade de alterar elementos das paginas sem precisar recarrega-las), a quantidade de JS nas paginas so aumentou. Em seguida, veio a introducao do DOM (Document Object Model), que nada mais e do que uma abordagem unificada do DHTML que foi adotada pelo IE5, Netscape 6 e Opera, o que logo foi acompanhado pela padronizacao do JavaScript no ECMA-262 (3a edicao).A medida em que estes progressos iam acontecendo, sistemas web mais complexos iam surgindo e aumentava a quantidade de codigo JS nas suas paginas. O problema e que a engine do JS ainda era a mesma de 1996, onde as paginas ainda nao eram tao recheadas
de JS. Browsers como o IE6 (se e que podemos chama-lo de browser rs), que surgiu em 2001 se tornaram mais lentos com o passar dos anos pois as paginas que iam surgindo utilizavam cada vez mais codigos javascript, e como a engine era muito antiga, nao estava preparada. Em suma, ela trabalhava de forma a procurar um numero fixo de objetos na memoria para determinar quando deveria coletar o lixo. Nos primordios do JS, os desenvolvedores nao atingiam este limite, mas com o aumento de codigo JS nas paginas, a quantidade de objetos aumentou e aplicacoes mais complexas foram sendo desenvolvidas, entao este limite passou a ser atingido com frequencia, exigindo cada vez mais dos browsers.Os desenvolvedores web evoluiram, mas as engines estavam paradas no tempo.Embora os diferentes browsers da epoca tivessem logicas diferentes (e ate um pouco mais eficientes) para lidar com o problema da coleta de lixo, a maioria deles utilizava um interpretador JavaScript para executar o codigo. Como se sabe, a interpretacao de codigo exige a traducao entre o codigo e e as instrucoes do computador que devem ser executadas, o que e um processo bem mais lento, se comparado com a compilacao.Compiladores ja funcionam diferente. Eles determinam a partir de uma analise lexica, o que o codigo esta tentando fazer e entao otimiza-o produzindo um codigo mais rapido para a execucao da tarefa.Em 2008 o Google lancou o Chrome, o primeiro navegador com uma engine otimizadora de JavaScript, o V8, o qual faz a compilacao 'just-in-time' do JS e e capaz de produzir codigo de maquina a partir de JS e executa-lo, resultando na sua execucao de forma bem mais performatica. Seguindo essa ideia novas engines de JS vieram surgindo e com o passar dos anos evoluindo, como o Nitro do safari, o traceMonkey, JaegerMonkey SpiderMonkey, etc..Mesmo com estes avancos no tempo de execucao no core do JavaScript, ainda ha situacoes que as engines modernas nao conseguem resolver, como operacoes que afetam a aparencia das paginas, atrasos provocados pela latencia da rede, etc. Assim, o desenvolvedor JavaScript precisa buscar conhecimento para entender varios aspectos diferentes, como latencia, bloqueio e downloads em paralelo, interacao com o DOM, etc, preocupando-se sempre com a melhor forma de escrever seu codigo, para obter um melhor desempenho na execucao de seu codigo, melhorando por consequencia a experiencia do usuario ao navegar nas paginas.
So, after sometime, here I am publishing for WikiComputacao again. Well, after these almost 2 years without posting anything here, I have some news. I enjoyed a great experience doing an internship for a French enterprise (Fruition Sciences SAS - a French startup that optimizes Wine production), where I developed some enhancements to their Decision-Making support system, using PHP (MVC framework), MySQL, jQuery, HTML and CSS.I returned from France in october 2012 to complete my Computer Science Bachelor degree, and I had the opportunity to study one last course at UDESC. I picked up HCI (Human-Computer Interaction). I found this topic really interesting. I had the opportunity to study systems usability, ergonomics and other related concepts.I may have forgotten to mention, but before I go to France, I was doing an internship at Render Multimidia LTDA (a Brazilian e-commerce that sells online courses), and during this period, I was trained to be the Front-end engineer in a team composed by 3 back-end developers and me (the front-end developer). At this point, some third-party enterprise was hired to design the new pages of the e-commerce, and I was creating the html+css+javascript effects from PSD files sent to me by the designers.I enjoyed a lot this work, and since I was in charge with 'only' this job, I could improve my front-end knowledges really well.When I went to France, I did an internship as a back-end developer, so I could improve my 'back-end' skills. I came back to Brazil and after one month I got hired by NeoGrid (a Brazilian Multi-National leader in Supply Chain Management), where I started my career as junior developer. There, we work in a SCRUM team, so we're all front-end/back-end developers at the same time.I'm currently programming in Java (J2EE, JSP, Struts, Oracle, Liquibase). It's been an awesome experience. We also have QA analysts to help us testing the issues we solve (Funny story: If you have already worked with QAs you're probably aware of these phrases:"It works in my machine!" "This problem was not caused by my code changes!", "This is not related to the issue I'm currently working". haha It's a 'funny' war that I'm used to call "QA vs Dev".PS: I don't know why the QA is a mouse in the cartoon... so don't blame me!!!Another awesome thing is that we follow almost all the 12 topics to pass in the JOEL TEST.Well... This was just an introduction to let you up to date about my current situation. As I mentioned, I enjoyed studying HCI concepts. Now, I'm trying to improve my knowledge in this major field and help my team to keep finding better solutions to the products we develop. This way, I came to Florianopolis this weekend to do the ResponsiveDay and User-Experience Design course (UX Weekend), conducted by Edu Agni, a Campus Party Brazil Design Consultant. I just came back from the #ResponsiveDay and it was very productive. Tomorrow we will start the UX Weekend.I'll be talking about it soon, in my next post. A documentis always set to one of three modes:
no-quirks mode, the default; quirks mode,used typically for legacy documents; limited-quirks mode. Unless statedotherwise, a document must be in no-quirks mode.The mode isonly ever changed from the default if the document is created by the HTMLparser, based on the presence, absence, or value of the DOCTYPE string. [HTML]No-quirksmode was originally known as "standards mode" and limited-quirks modewas once known as "almost standards mode". They have been renamedbecause their details are now defined by standards. (And because Ian Hicksonvetoed their original names on the basis that they are nonsensical.)fonte: http://hsivonen.iki.fi/doctype/html5-mode.pdfQuirks ModeIn theQuirks mode, browsers violate contemporary Web format specifications in orderto avoid breaking pages authored according to practices that were prevalentin the late 1990s.StandardsModeIn theStandards mode, browsers try to give conforming documents thespecification-wise correct treatment to the extent implemented in a particularbrowser. HTML5 calls this mode the no quirks mode.AlmostStandards ModeFirefox,Safari, Chrome, Opera (since 7.5) and IE8 also have a mode known as AlmostStandards mode, that implements the vertical sizing of table cellstraditionally and not rigorously according to the CSS2 specification. HTML5calls this mode the limited quirks mode.Possible Impacts:There areseveral effects that most browsers use in Quirks Mode:In some browsers, the box model changes to the IE 5.5 version of the box model in quirks mode.Some browsers don't inherit styles into tablesQuirks mode affects the parsing of CSS and CSS layout dramatically, if you are converting pages to standards mode from quirks mode, be sure to test your CSS layout and parsing extensively.Watch for changes to scripting when in quirks mode. Firefox changes the way the id-attribute works, for example. IE8 and IE9 have very dramatic changes to scripting in quirks mode.These information are the result of a study I made while working in a legacy product, to understand the behavior why the browser was running under quirks/compatibility mode and find the best solution, considering possible impacts... I strongly recommend to use the latest doctype declaration (i.e. for HTML5) and replace deprecated CSS styles for the html5 equivalent ones).References:http://www.w3.org/html/wg/drafts/html/master/syntax.html#the-initial-insertion-modehttp://hsivonen.iki.fi/doctype/ie8-mode.pnghttp://hsivonen.iki.fi/doctype/http://msdn.microsoft.com/en-us/library/cc196988(v=vs.85).aspxhttp://msdn.microsoft.com/en-us/library/ie/hh869300(v=vs.85).aspxhttp://www.quirksmode.org/css/quirksmode.htmlhttp://webdesign.about.com/cs/doctype/a/aaquirksmode.htmhttp://blogs.msdn.com/b/ie/archive/2011/12/14/interoperable-html5-quirks-mode-in-ie10.aspx
This is one of my favorites SEO tools. Google insights for search is a Google free service that allows you to check and compare how often the keywords you are checking are searched on the internet by the users. These results will be shown to you by periods of months and years, and if the keyword you are using is something that people has been searching for years, it will also give you a forecast about the next months. Can you see how can you use it in your e-commerce?So... first situation:You have a product that you don't know what's the best label you should give to him in your website (and I'm talking about this, because it's really important to know what's the best name to your product, and the best name is the more related to your product, that is also the most searched for users). So, how do you choose it? Let's suppose your boss wants to sell carpets in the e-commerce, and you have to choose if carpet is the name the most searched for the users. Go to Google Insights for search and search for "carpet" and its synonyms. In the following image you'll see an example:As you can see, the red line shows the frequency the word 'Carpet' has been searched, and the blue shows the same about the word 'Tapestry'. You can also notice that Google insights for search made a forecast for the keyword most searched. This information allows you to choose the name carpet, that will easily induce the users to go to find your products.Let's think about one second situation:You want to give a discount price for some product that you are not selling well. How can this service help you? Think about this: you go to Google Insights and search for this product. You will check the months people look for this product more often. After that, you will be able to see the months you can give the discount. If you are not selling this in a month that people really search for this product, you can think about the reasons why you are not having success in doing it. Maybe your competitors are giving more discounts... anyway, you have something to think about.As you can see, Google Insights for Search is a really interesting tool, and not just for people who works for e-commerces. Even for writing this post, I used this service. As my mother language is Portuguese, I was in doubt if I should use feature or tool, when I talk about "SEO tools". Yes.. I chose "tools" because after searching in the service, I discovered that people use much more the word 'tools' instead of 'features'. And if people use more this, propably it's the reason why you found my blog and you're reading this. I hope you enjoy it! A audiencia publica para discutir o metro de Salvador foi realizada nesta quinta-feira (21), no Centro de Cultura da Camara Municipal, e foi marcada por tumulto. Mais uma vez, o governo e o municipio nao chegam