平台开发须知

May 4, 20101 like593 views

The document provides an overview of various topics including Linux, vim text editor, Jinja2 templating, building web applications with HTML, CSS, and JavaScript, and using Subversion (SVN) for version control. For Linux, it lists common commands like ls, cd, mv, cp. For vim, it describes modes, copying/pasting, searching, regular expressions. Jinja2 topics include for loops, if statements, filters. The application section discusses project structure, templating base layouts, including files, and using NieJS to interact with the DOM. Finally, SVN topics cover commands like checkout, status, add/delete/commit, resolving conflicts.

Self Improvement

linux, vim, jinja2, nieml, niejs, svn, etc...

AGENDA
? linux

? vim

? (jinja2)

?

? app/ html js

? svn

LINUX
? ls (list) ls project

? cd xx (change directory) cd project

? mv (move) mv a.txt c.txt

? cp (copy) cp a.txt b.txt

? vim vim a.txt windows

VIM 1
?

? (esc i,o,a )

? c/v y(yank) p(paste)

? ^ $

? H,J,K,L

? /,n,N

? :s/xxx/aaa :s/xxx/aaa/g :%s/xxx/aaa

? undo u redo ctrl+r

? till t

? gg G ctrl + f ctrl + b

JINJA2
http://jinja.pocoo.org/2/documentation/templates

JINJA2 -
? {%

? {% for %} - {% endfor %}

? navigation

? {{

? {#

JINJA2 - -1
? {%extend “base.html” %}

home.html

base.html
message.html

JINJA2 - -2
? {{ super() }} block

base.html

derived.html

JINJA2 - -5
? import a macro

macros.html

sample.html

$JINJA2 - ? ? {% for a in aList %} {{ a }} {% endfor %} ? {% if a %} {{ a }} {% endif %} ? ?lters ? escape : {{ diary_content | escape }} or {{ diary_content | e }} ? more ?lters: http://jinja.pocoo.org/2/documentation/templates#builtin- ?lters$

-
base.html

user.html group_base.html

home.html

diary_base group page
.html template ?les
photo_base
.html
etc ...

APP/ -2
app sandbox

1 app html
2 app
4

request 3
get app content
1
request
5
2

app

APP/ -3
app sandbox
? app html utf-8

? app html html id css

? app html
script html

? app js dom
dom nieJS

APP/ -4
html http://123.125.48.32:8899/NIEML

APP/ -5
app html css

? app html id id test tag id
app12_test 12 appid

? link css app css <nie:css
> <nie:css src=/slideshow/ss-3961460/3961460/”xx.css”/>

? app css css app
#app_content_[appid] app id
app_content_[appid] div

APP/ -6
app html css
? html tag

? css expression

? html tag css

APP/ -7
nieJS
? js <nie:script>

? nieJS

? nieJS js
document.getElementById(id)

? value var a =
obj.value; / obj.value = “aaa” nieJS var a = obj.getValue(); / obj.setValue(“aaa”)

? document.cookie

? http://123.125.48.32:8899/NIEJS

APP/ -7
app js

? nieJS

? nieJS
js
nieJS

SVN -1
? svn co <addr> checkout

? svn up

? svn st

? svn add <?le>

? svn del <?le>

? svn mv src_?le desc_?le

? svn diff

? svn ci <?le> /

SVN -2
svn st
? A added

? C con?ict

? D deleted

? M modi?ed

? R replace

? not under version control

? under version control but missing

? ~ The ?le, directory, or symbolic link item is in the repository as one kind of object, but what's actually in your
working copy is some other kind

SVN -3
svn up
? U The ?les marked with U contained no local changes but were Updated with changes from the
repository.

? G The G stands for merGed, which means that the ?le had local changes to begin with, but the
changes coming from the repository didn't overlap with the local changes.

? C Con?ct

? U G C up C ~~

SVN -4
C con?ict ...

? C a.html

? vim >>> ===

?

?

? svn resolved a.html svn

? svn st a.html c

SVN -5

? svn co checkout

?

? svn st
svn add

? svn up con?ict

? svn st c con?ict

? svn diff > t.diff t.diff vim t.diff

? svn ci log log

This document provides an overview and introduction to Ruby on Rails. It begins with an agenda and introduction to the speaker. It then provides a brief introduction to Rails, including what industries use it, examples of popular websites built with Rails, and an explanation of its model-view-controller architecture and RESTful design philosophy. The document continues with sections on auditing Rails applications, identifying common vulnerabilities like mass assignment and cross-site scripting, and recommendations for removing vulnerabilities.

Ruby on Rails 101 - Presentation 狠狠撸s for a Five Day Introductory Coursepeter_marklund

The document is a presentation by Peter Marklund on Ruby on Rails, specifically for a five-day introductory course aimed at beginners. It covers crucial aspects such as installation, MVC architecture, ActiveRecord, routing, plugins, testing, and Ruby fundamentals. The material emphasizes Ruby on Rails' philosophy of 'convention over configuration' and highlights its strengths in building web applications efficiently.

PSR-7 - Middleware - Zend ExpressiveMilad Arabi

The document introduces PSR-7 and middleware in Zend Expressive. It discusses PSR-7 interfaces like RequestInterface and ResponseInterface that define HTTP messages. It also covers middleware and how middleware can be used to add functionality like authentication. Zend Expressive is introduced as a framework that uses PSR-7 and middleware. It has features like routing, dependency injection and templating. Examples are given of creating middleware for authentication, downloading files, and handling unavailable pages. The document concludes by thanking the reader and providing contact details.

Ruby on Rails Training - Module 1Mark Menard

The document provides an extensive introduction to Ruby and Ruby on Rails, highlighting Ruby's dynamic programming capabilities, object-oriented nature, and features like closures and metaprogramming. It also discusses the philosophy behind Ruby on Rails as a web framework focused on programmer happiness, sustainable productivity, and convention over configuration, detailing its components such as ActiveRecord for database interaction and ActionController for MVC architecture. Additionally, it covers advanced topics like validations, dynamic associations, and session management within Rails applications.

Digital Texts scholarly communication in a digital networked ageTony Hirst

1. The document discusses scholarly communication and proposes that the traditional model of journal publications no longer adequately defines communication units. 2. It suggests moving towards more granular, participatory, and networked forms of publishing like open notebooks, living documents, and composite works that dynamically combine information from multiple sources. 3. Key aspects that could be rethought include the purpose and audience of publishing, units of publication beyond journal articles, and utilizing social features like version control, issue tracking, and peer review to facilitate ongoing scholarly discourse.

Brubeck: The Lightning TalkJames Dennis

Разработка документации для RESTful API: как убить трёх зайцев одним. Moscow....Moscow.pm

The document discusses the importance of developing documentation for RESTful APIs, highlighting its benefits for both users and developers. It details the use of Perl's POD format for creating easy-to-read and maintainable documentation, emphasizing elements like API routes and methods, input parameters, and possible output errors. Additionally, it suggests that proper documentation practices result in up-to-date resources and improved testing efficiency.

Bfg Ploneconf Oct2008Jeffrey Clark

The repoze.bfg framework allows Zope developers to use WSGI technologies more easily and non-Zope developers to use Zope technologies without all of Zope. It provides URL dispatch, templating, and declarative security while avoiding features like databases, sessions, and the ZMI. Repoze.bfg uses the Zope Component Architecture and aims for familiarity, simplicity, speed, documentation, and collaboration.

Week 1Will Gaybrick

The document provides an overview of a web apps 101 course, introducing the client-server model, key technologies like HTML, CSS, JavaScript, Python and Ruby, and the basics of front-end development including using tags in HTML and applying styles in CSS. It also briefly discusses the command line and operating systems. The goals of the course are to take students from having an idea to building a prototype and then a full application, focusing more on processes and problem solving than specific content.

Week 1 (v3)Will Gaybrick

The document provides an overview of a web apps 101 course, introducing the client-server model, key technologies like HTML, CSS, JavaScript, Python and Ruby, and how front-end development works using these languages. It discusses the anatomy of web applications, front-end development with HTML, CSS, and JavaScript, and the command line interface. The goals of the course are to take students from having an idea to building a prototype and full web application through hands-on learning and equipping them with resources to become successful developers.

Week 1Will Gaybrick

This document provides an overview of a web development course. It introduces key concepts like the client-server model, HTML, CSS, JavaScript, and tools like Git, GitHub, and Heroku. The goals of the course are to take students from having an idea to building a prototype to developing a full application, with a focus on practical skills over theory. Important technologies covered include HTML for content, CSS for styling, JavaScript for interactivity, and languages like Python and Ruby for backend development. Deployment options like GitHub for hosting code and Heroku for deploying applications are also discussed.

Web Developing In SearchFrank Xu

This document summarizes a presentation about web development for search products at Taobao. It discusses the complexities of developing for platforms with 260 million pageviews and integrating multiple products. Development is done locally using Git while publishing uses Subversion for permission control. Thorough testing is emphasized through linting, integration testing, and regression testing. Assets are managed through preprocessing, timestamps, and CDN handling.

How I stopped worrying about and loved DumpRenderTreeHajime Morrita

The document discusses how the author stopped worrying and loved DumpRenderTree (DRT), a tool used for testing WebKit. It identifies three main test smells in WebKit tests: 1) obscure tests that are difficult to understand, 2) fragile tests that break easily due to minor changes, and 3) high test maintenance costs due to issues like managing golden files for each platform. It provides examples of how DRT addresses these smells through features like outputting test results as text and evaluating DOM properties with JavaScript.

Presentation to wdim_studentsScott Motte

This document provides an overview of installing Ruby and deploying a basic web application from development to production. It discusses setting up Ruby and related tools like MySQL, Git and Sinatra on Mac and Windows. It then walks through building a simple "Hello World" app locally and deploying it to Heroku using Git. The document also introduces concepts like adding stylesheets, layouts and basic JavaScript/jQuery to the app.

Git 101 for CloudStackSebastien Goasguen

This document provides an introduction to Git and version control, detailing its importance in software engineering for managing source code changes. It outlines the workflow for using Git, including creating repositories, managing branches, and making commits, while specifically referencing the Apache CloudStack project's practices. Additionally, it encourages readers to engage with version control through exercises and the creation of patches for contribution to open-source projects.

Sean coates fifty things and tricks, confoo 2011Bachkoutou Toutou

App Engine Dev Days DC 20091026jblocksom

Gaelyk - JFokus 2011 - Guillaume LaforgeGuillaume Laforge

This document provides an overview of Gaelyk, a lightweight Groovy toolkit for developing applications on Google App Engine. Gaelyk builds on Groovy's servlet support and provides enhancements to the Google App Engine Java SDK to simplify development. It allows using Groovy scripts called Groovlets instead of raw servlets and Groovy templates instead of JSPs. This provides a clean separation of views and logic for developing web applications on Google App Engine using the Groovy programming language.

Introduction to QtWebKitAriya Hidayat

QtWebKit is a web browser engine that can be used to embed web content in applications. It is based on the WebKit open source project, which powers browsers like Safari and Chrome. QtWebKit provides APIs to display web pages, run JavaScript, and integrate web content with native applications. It supports features like SVG, CSS3 animations, and device access. QtWebKit is widely used due to its cross-platform support, extensive test suite, and active open source community.

Ruby on rails探索Mu Chun Wang

This document provides an overview of Ruby and Ruby on Rails. It discusses that Ruby is an open-source, object-oriented programming language designed to make programmers happy. Rails is a web application framework built on Ruby that follows the model-view-controller (MVC) pattern. The document includes a live demo of Rails and addresses frequently asked questions about why to use Ruby and Rails given considerations of performance and popularity of the frameworks.

Python - A Comprehensive Programming LanguageTsungWei Hu

The document provides an overview of Python as a dynamic, object-oriented programming language, detailing its features, functionalities, and applications in various domains. It covers topics like file handling, socket creation, and Python's role in web frameworks and content management systems (CMS). Additionally, it highlights local resources, community support, and self-learning opportunities for Python enthusiasts.

XML-Free Programming : Java Server and Client Development without <>Arun Gupta

The document discusses XML-free programming using Java for server and client development. It presents three tenets: 1) Configuration lives with the code using annotations rather than XML, 2) Data transfer models the domain using JSON rather than XML, and 3) Programming languages should be designed for humans not machines using simpler languages like Java rather than XML-based languages. It provides examples comparing XML and alternative approaches like Groovy for each tenet.

State of the art: server-side javaScript - NantesJSAlexandre Morgaut

1) The document provides a history of server-side JavaScript, beginning with its origins in 1995 and discussing key developments through 2011. 2) It outlines the growing JavaScript ecosystem, including large communities, conferences, libraries, frameworks, development tools, and engines like V8 and SpiderMonkey. 3) Server-side JavaScript aims to integrate well with other platforms and APIs, as seen in solutions like Rhino for Java and JScript.NET for .NET.

Better Front-end Development in Atlassian PluginsWojciech Seliga

The document outlines the evolution of front-end development in Atlassian plugins, highlighting the transition from back-end technologies to modern web-based frameworks. It discusses the introduction of various tools and methodologies including AUI, REST, web resource contexts, and Soy templates, which enhance the user interface and interaction. The presentation emphasizes structured approaches to JavaScript development and the benefits of modern frameworks for maintainability and speed.

Groovy Domain Specific Languages - SpringOne2GX 2012Guillaume Laforge

The document discusses Groovy domain-specific languages (DSLs), which are tailored programming languages designed to address specific problem domains while contrasting them with general-purpose languages. It highlights the benefits of using DSLs, such as improved expressiveness and the ability to involve domain experts in application design, alongside potential drawbacks like learning costs and limited applicability. Additionally, it covers Groovy’s capabilities for building DSLs, emphasizing its flexible syntax and integration with Java applications.

Rapid Templating with ServeNathan Smith

This document summarizes a presentation about using Sass, Compass, and Serve for rapid templating and designing in the browser. It discusses how responsive design has changed workflows, and tools like Sass, Compass, and Serve allow collaborative work between designers and developers. Serve is presented as a tool that allows building prototypes that resemble the final product through templating with Sass and Compass in a Rails-like MVC structure, without the overhead of a full Rails app.

Bentobox exerciseRails Girls Zurich

This document provides an overview of common technologies used to build websites, including programming languages (PHP, Ruby, Python), frameworks (Ruby on Rails, Django, Lift), databases (MySQL, MongoDB), markup languages (HTML, XML), styling (CSS), and servers (Apache, Nginx). It discusses the roles of these technologies and how they interact through examples like LAMP stacks. The document seeks to teach others the "language of the web" by explaining the purposes and relationships between these foundational web development tools.

Ant, Maven and JenkinsKenu, GwangNam Heo

平台开发须知

1. linux, vim, jinja2, nieml, niejs, svn, etc...

2. AGENDA ? linux ? vim ? (jinja2) ? ? app/ html js ? svn

3. Linux

4. LINUX ? ls (list) ls project ? cd xx (change directory) cd project ? mv (move) mv a.txt c.txt ? cp (copy) cp a.txt b.txt ? vim vim a.txt windows

5. AGENDA ? linux ? vim ? (jinja2) ? ? app/ html js ? svn

6. VIM --- dreamweaver ...

7. VIM 1 ? ? (esc i,o,a ) ? c/v y(yank) p(paste) ? ^ $ ? H,J,K,L ? /,n,N ? :s/xxx/aaa :s/xxx/aaa/g :%s/xxx/aaa ? undo u redo ctrl+r ? till t ? gg G ctrl + f ctrl + b

9. AGENDA ? linux ? vim ? (jinja2) ? ? app/ html js ? svn

10. JINJA2 http://jinja.pocoo.org/2/documentation/templates

11. JINJA2 - ? {% ? {% for %} - {% endfor %} ? navigation ? {{ ? {#

12. JINJA2 - -1 ? {%extend “base.html” %} home.html base.html message.html

13. JINJA2 - -2 ? {{ super() }} block base.html derived.html

14. JINJA2 - -3 ? include sample sample2

15. JINJA2 - -4 ? macro html after render

16. JINJA2 - -5 ? import a macro macros.html sample.html

17. JINJA2 - ? ? {% for a in aList %} {{ a }} {% endfor %} ? {% if a %} {{ a }} {% endif %} ? ?lters ? escape : {{ diary_content | escape }} or {{ diary_content | e }} ? more ?lters: http://jinja.pocoo.org/2/documentation/templates#builtin- ?lters

18. AGENDA ? linux ? vim ? (jinja2) ? ? app/ html js ? svn

19. - base.html user.html group_base.html home.html diary_base group page .html template ?les photo_base .html etc ...

20. AGENDA ? linux ? vim ? (jinja2) ? ? app/ html js ? svn

21. APP/ -1 html app html

22. APP/ -2 app sandbox 1 app html 2 app 4 request 3 get app content 1 request 5 2 app

23. APP/ -3 app sandbox ? app html utf-8 ? app html html id css ? app html script html ? app js dom dom nieJS

24. APP/ -4 html http://123.125.48.32:8899/NIEML

25. APP/ -5 app html css ? app html id id test tag id app12_test 12 appid ? link css app css <nie:css > <nie:css src=/slideshow/ss-3961460/3961460/”xx.css”/> ? app css css app #app_content_[appid] app id app_content_[appid] div

26. APP/ -6 app html css ? html tag ? css expression ? html tag css

27. APP/ -7 nieJS ? js <nie:script> ? nieJS ? nieJS js document.getElementById(id) ? value var a = obj.value; / obj.value = “aaa” nieJS var a = obj.getValue(); / obj.setValue(“aaa”) ? document.cookie ? http://123.125.48.32:8899/NIEJS

28. APP/ -7 app js ? nieJS ? nieJS js nieJS

29. AGENDA ? linux ? vim ? (jinja2) ? ? app/ html js ? svn

30. SVN

31. SVN -1 ? svn co <addr> checkout ? svn up ? svn st ? svn add <?le> ? svn del <?le> ? svn mv src_?le desc_?le ? svn diff ? svn ci <?le> /

32. SVN -2 svn st ? A added ? C con?ict ? D deleted ? M modi?ed ? R replace ? not under version control ? under version control but missing ? ~ The ?le, directory, or symbolic link item is in the repository as one kind of object, but what's actually in your working copy is some other kind

33. SVN -3 svn up ? U The ?les marked with U contained no local changes but were Updated with changes from the repository. ? G The G stands for merGed, which means that the ?le had local changes to begin with, but the changes coming from the repository didn't overlap with the local changes. ? C Con?ct ? U G C up C ~~

34. SVN -4 C con?ict ... ? C a.html ? vim >>> === ? ? ? svn resolved a.html svn ? svn st a.html c

35. SVN -5 ? svn co checkout ? ? svn st svn add ? svn up con?ict ? svn st c con?ict ? svn diff > t.diff t.diff vim t.diff ? svn ci log log

36. SVN -6 vim t.diff

37. AGENDA ? linux ? vim ? (jinja2) ? ? app/ html js ? svn

38. Q&A - END -

狠狠撸

平台开发须知

Recommended

More Related Content

Similar to 平台开发须知 (20)

平台开发须知