- 浏览: 200694 次
- 来自: ...
文章分类
最新评论
-
赤道螞蟻:
如果是數據庫有定時任務,定時更新表的數據。 表中數據變化時,主 ...
用socket.io实现WebSocket的一个简单例子 -
cwalet:
在世界的中心呼喚愛 写道提示找不到 expressnpm in ...
用socket.io实现WebSocket的一个简单例子 -
在世界的中心呼喚愛:
提示找不到 express
用socket.io实现WebSocket的一个简单例子 -
Anleb:
def m1(a)
puts 'invoke m1'
pu ...
Ruby的一些疑问 -
biyeah:
补充,任何类,只要实现to_proc方法,都可以与&结 ...
Ruby的一些疑问
https://github.com/camping/camping/blob/master/book/02_getting_started
直接看文档就知道了。
源代码不大4k左右值得研究。
Camping is a web framework which consistently stays at less than 4kB of code.You can probably view the complete source code on a single page.
= Getting Started
Start a new text file called nuts.rb. Here's what you put inside:
Camping.goes :Nuts
Save it. Then, open a command prompt in the same directory. You'll want to
run:
$ camping nuts.rb
And you should get a message which reads:
** Camping running on 0.0.0.0:3301.
This means that right now The Camping Server is running on port 3301 on your
machine. Open your browser and visit http://localhost:3301/.
Your browser window should show:
Camping Problem!
/ Not found
No problem with that. The Camping Server is running, but it doesn't know what
to show. Let's tell him.
== Hello clock
So, you've got Camping installed and it's running. Keep it running. You can
edit files and The Camping Server will reload automatically. When you need to
stop the server, press Control-C.
Let's show something. At the bottom of nuts.rb add:
module Nuts::Controllers
class Index < R '/'
def get
Time.now.to_s
end
end
end
Save the file and refresh the browser window. Your browser window should show
the time, e.g.
Sun Jul 15 12:56:15 +0200 2007
== Enjoying the view
The Camping microframework allows us to separate our code using the MVC
(Model-View-Controller) design pattern. Let's add a view to our Nuts
application. Replace the <tt>module Nuts::Controllers</tt> with:
module Nuts::Controllers
class Index < R '/'
def get
@time = Time.now
render :sundial
end
end
end
module Nuts::Views
def layout
html do
head do
title { "Nuts And GORP" }
end
body { self << yield }
end
end
def sundial
p "The current time is: #{@time}"
end
end
Save the file and refresh your browser window and it should show a message
like:
The current time is: Sun Jul 15 13:05:41 +0200 2007
And the window title reads "Nuts And GORP".
Here you can see we call <tt>render :sundial</tt> from our controller. This
does exactly what it says, and renders our <tt>sundial</tt> method. We've also
added a special method called <tt>layout</tt> which Camping will automatically
wrap our sundial output in. If you're familiar with HTML, you'll see that our
view contains what looks HTML tag names. This is Markaby, which is like
writing HTML using Ruby!
Soon enough, you'll find that you can return anything from the controller, and
it will be sent to the browser. But let's keep that for later and start
investigating the routes.
== Routes
You probably noticed the weird <tt>R '/'</tt> syntax in the previous page.
This is an uncommon feature of Ruby that is used in our favorite
microframework, to describe the routes which the controller can be accessed
on.
These routes can be very powerful, but we're going to have look at the
simplest ones first.
module Nuts::Controllers
class Words < R '/welcome/to/my/site'
def get
"You got here by: /welcome/to/my/site"
end
end
class Digits < R '/nuts/(\d+)'
def get(number)
"You got here by: /nuts/#{number}"
end
end
class Segment < R '/gorp/([^/]+)'
def get(everything_else_than_a_slash)
"You got here by: /gorp/#{everything_else_than_a_slash}"
end
end
class DigitsAndEverything < R '/nuts/(\d+)/([^/]+)'
def get(number, everything)
"You got here by: /nuts/#{number}/#{everything}"
end
end
end
Add this to nuts.rb and try if you can hit all of the controllers.
Also notice how everything inside a parenthesis gets passed into the method,
and is ready at your disposal.
=== Simpler routes
This just in:
module Nuts::Controllers
class Index
def get
"You got here by: /"
end
end
class WelcomeToMySite
def get
"You got here by: /welcome/to/my/site"
end
end
class NutsN
def get(number)
"You got here by: /nuts/#{number}"
end
end
class GorpX
def get(everything_else_than_a_slash)
"You got here by: /gorp/#{everything_else_than_a_slash}"
end
end
class NutsNX
def get(number, everything)
"You got here by: /nuts/#{number}/#{everything}"
end
end
end
Drop the <tt>< R</tt>-part and it attemps to read your mind. It won't always
succeed, but it can simplify your application once in a while.
== Modeling the world
You can get pretty far with what you've learned now, and hopefully you've been
playing a bit off-book, but it's time to take the next step: Storing data.
Let's start over again.
Camping.goes :Nuts
module Nuts::Models
class Page < Base
end
end
Obviously, this won't do anything, since we don't have any controllers, but
let's rather have a look at we _do_ have.
We have a model named Page. This means we now can store wiki pages and
retrieve them later. In fact, we can have as many models as we want. Need one
for your users and one for your blog posts? Well, I think you already know how
to do it.
However, our model is missing something essential: a skeleton.
Camping.goes :Nuts
module Nuts::Models
class Page < Base
end
class BasicFields < V 1.0
def self.up
create_table Page.table_name do |t|
t.string :title
t.text :content
# This gives us created_at and updated_at
t.timestamps
end
end
def self.down
drop_table Page.table_name
end
end
end
Now we have our first version of our model. It says:
If you want to migrate up to version one,
create the skeleton for the Page model,
which should be able to store,
"title" which is a string,
"content" which is a larger text,
"created_at" which is the time it was created,
"updated_at" which is the previous time it was updated.
If you want to migrate down from version one,
remove the skeleton for the Page model.
This is called a _migration_. Whenever you want to change or add new models you simply add a new migration below, where you increase the version number. All of these migrations builds upon each other like LEGO blocks.
Now we just need to tell Camping to use our migration. Write this at the bottom of nuts.rb
def Nuts.create
Nuts::Models.create_schema
end
When The Camping Server boots up, it will automatically call
<tt>Nuts.create</tt>. You can put all kind of startup-code here, but right now
we only want to create our skeleton (or upgrade if needed). Start The Camping
Server again and observe:
$ camping nuts.rb
** Starting Mongrel on 0.0.0.0:3301
-- create_table("nuts_schema_infos")
-> 0.1035s
== Nuts::Models::BasicFields: migrating ===================================
-- create_table(:nuts_pages)
-> 0.0033s
== Nuts::Models::BasicFields: migrated (0.0038s) ==========================
Restart it, and enjoy the silence. There's no point of re-creating the
skeleton this time.
Before we go on, there's one rule you must known: Always place your models
before your migrations.
== Using our model
Let's explore how our model works by going into the _console_
$ camping -C nuts.rb
** Starting console
>>
Now it's waiting for your input, and will give you the answer when you press
Enter. Here's what I did, leaving out the boring answers. You should add your
own pages.
>> Page = Nuts::Models::Page
>> hiking = Page.new(:title => "Hiking")
>> hiking.content = "You can also set the values like this."
>> hiking.save
>> page = Page.find_by_title("Hiking")
=> #<Nuts::Models::Page id: 1, ... >
>> page = Page.find(1)
=> #<Nuts::Models::Page id: 1, ... >
>> page.title
>> page.content
>> page.created_at
>> page.updated_at
>> Page.find_by_title("Fishing")
=> nil
## Page.create automatically saves the page for you.
>> Page.create(:title => "Fishing", :content => "Go fish!")
>> Page.count
=> 2
Now I have two pages: One about hiking and one about fishing.
== Wrapping it up
Wouldn't it be nice if we could show this wonderful our pages in a browser?
Update nuts.rb so it also contains something like this:
module Nuts::Controllers
class Pages
def get
# Only fetch the titles of the pages.
@pages = Page.all(:select => "title")
render :list
end
end
class PageX
def get(title)
@page = Page.find_by_title(title)
render :view
end
end
end
module Nuts::Views
def list
h1 "All pages"
ul do
@pages.each do |page|
li do
a page.title, :href => R(PageX, page.title)
end
end
end
end
def view
h1 @page.title
self << @page.content
end
end
Here we meet our first _helper_:
R(PageX, page.title)
This is the <em>reversed router</em> and it generates a URL based on a
controller. Camping ships with a few, but very useful, helpers and you can
easily add your owns. Have a look at Camping::Helpers for how you use these.
There's a lot of improvements you could do here. Let me suggest:
* Show when the page was created and last updated.
* What happens when the page doesn't exist?
* What should the front page show?
* Add a layout.
* Jazz it up a bit.
== The last touch
We have one major flaw in our little application. You can't edit or add new
pages. Let's see if we can fix that:
module Nuts::Controllers
class PageX
def get(title)
if @page = Page.find_by_title(title)
render :view
else
redirect PageXEdit, title
end
end
def post(title)
# If it doesn't exist, initialize it:
@page = Page.find_or_initialize_by_title(title)
# This is the same as:
# @page = Page.find_by_title(title) || Page.new(:title => title)
@page.content = @input.content
@page.save
redirect PageX, title
end
end
class PageXEdit
def get(title)
@page = Page.find_or_initialize_by_title(title)
render :edit
end
end
end
The core of this code lies in the new <tt>post</tt> method in the PageX
controller. When someone types an address or follows a link, they'll end up at
the <tt>get</tt> method, but you can easily create a form which rather sends
you to the <tt>post</tt> when submitted.
There are other names you can use, but they won't always work. So for now,
don't be fancy and just stick to <tt>get</tt> and <tt>post</tt>. We'll show
you how this really works later.
You might also notice that we use <tt>@input.content</tt>. The
<tt>@input</tt>-hash contains any extra parameters sent, like those in the
forms and those in the URL (<tt>/posts?page=50</tt>).
Here's an <tt>edit</tt>-view, but you can probably do better. See if you can
integrate all of this with what you already have.
module Nuts::Views
def edit
h1 @page.title
form :action => R(PageX, @page.title), :method => :post do
textarea @page.content, :name => :content,
:rows => 10, :cols => 50
br
input :type => :submit, :value => "Submit!"
end
end
end
== Phew.
You've taken quite a few steps in the last minutes. You deserve a break. But
let's recap for a moment:
* Always place <tt>Camping.goes :App</tt> at the top of your file.
* Every route ends at a controller, but ...
* ... the controller only delegates the work.
* <tt>@input</tt> contains the extra parameters.
* The views are HTML disguised as Ruby.
* They can access the instances variables (those that starts with a single
at-sign) from the controller.
* The models allows you to store all kinds of data.
* Place your models before your migrations.
* Helpers are helpful.
Unfortunately, the book stops here for now. Come back in a few months, or join
the mailing list to stay updated, and hopefully there's another chapter
waiting for you.
直接看文档就知道了。
源代码不大4k左右值得研究。
Camping is a web framework which consistently stays at less than 4kB of code.You can probably view the complete source code on a single page.
= Getting Started
Start a new text file called nuts.rb. Here's what you put inside:
Camping.goes :Nuts
Save it. Then, open a command prompt in the same directory. You'll want to
run:
$ camping nuts.rb
And you should get a message which reads:
** Camping running on 0.0.0.0:3301.
This means that right now The Camping Server is running on port 3301 on your
machine. Open your browser and visit http://localhost:3301/.
Your browser window should show:
Camping Problem!
/ Not found
No problem with that. The Camping Server is running, but it doesn't know what
to show. Let's tell him.
== Hello clock
So, you've got Camping installed and it's running. Keep it running. You can
edit files and The Camping Server will reload automatically. When you need to
stop the server, press Control-C.
Let's show something. At the bottom of nuts.rb add:
module Nuts::Controllers
class Index < R '/'
def get
Time.now.to_s
end
end
end
Save the file and refresh the browser window. Your browser window should show
the time, e.g.
Sun Jul 15 12:56:15 +0200 2007
== Enjoying the view
The Camping microframework allows us to separate our code using the MVC
(Model-View-Controller) design pattern. Let's add a view to our Nuts
application. Replace the <tt>module Nuts::Controllers</tt> with:
module Nuts::Controllers
class Index < R '/'
def get
@time = Time.now
render :sundial
end
end
end
module Nuts::Views
def layout
html do
head do
title { "Nuts And GORP" }
end
body { self << yield }
end
end
def sundial
p "The current time is: #{@time}"
end
end
Save the file and refresh your browser window and it should show a message
like:
The current time is: Sun Jul 15 13:05:41 +0200 2007
And the window title reads "Nuts And GORP".
Here you can see we call <tt>render :sundial</tt> from our controller. This
does exactly what it says, and renders our <tt>sundial</tt> method. We've also
added a special method called <tt>layout</tt> which Camping will automatically
wrap our sundial output in. If you're familiar with HTML, you'll see that our
view contains what looks HTML tag names. This is Markaby, which is like
writing HTML using Ruby!
Soon enough, you'll find that you can return anything from the controller, and
it will be sent to the browser. But let's keep that for later and start
investigating the routes.
== Routes
You probably noticed the weird <tt>R '/'</tt> syntax in the previous page.
This is an uncommon feature of Ruby that is used in our favorite
microframework, to describe the routes which the controller can be accessed
on.
These routes can be very powerful, but we're going to have look at the
simplest ones first.
module Nuts::Controllers
class Words < R '/welcome/to/my/site'
def get
"You got here by: /welcome/to/my/site"
end
end
class Digits < R '/nuts/(\d+)'
def get(number)
"You got here by: /nuts/#{number}"
end
end
class Segment < R '/gorp/([^/]+)'
def get(everything_else_than_a_slash)
"You got here by: /gorp/#{everything_else_than_a_slash}"
end
end
class DigitsAndEverything < R '/nuts/(\d+)/([^/]+)'
def get(number, everything)
"You got here by: /nuts/#{number}/#{everything}"
end
end
end
Add this to nuts.rb and try if you can hit all of the controllers.
Also notice how everything inside a parenthesis gets passed into the method,
and is ready at your disposal.
=== Simpler routes
This just in:
module Nuts::Controllers
class Index
def get
"You got here by: /"
end
end
class WelcomeToMySite
def get
"You got here by: /welcome/to/my/site"
end
end
class NutsN
def get(number)
"You got here by: /nuts/#{number}"
end
end
class GorpX
def get(everything_else_than_a_slash)
"You got here by: /gorp/#{everything_else_than_a_slash}"
end
end
class NutsNX
def get(number, everything)
"You got here by: /nuts/#{number}/#{everything}"
end
end
end
Drop the <tt>< R</tt>-part and it attemps to read your mind. It won't always
succeed, but it can simplify your application once in a while.
== Modeling the world
You can get pretty far with what you've learned now, and hopefully you've been
playing a bit off-book, but it's time to take the next step: Storing data.
Let's start over again.
Camping.goes :Nuts
module Nuts::Models
class Page < Base
end
end
Obviously, this won't do anything, since we don't have any controllers, but
let's rather have a look at we _do_ have.
We have a model named Page. This means we now can store wiki pages and
retrieve them later. In fact, we can have as many models as we want. Need one
for your users and one for your blog posts? Well, I think you already know how
to do it.
However, our model is missing something essential: a skeleton.
Camping.goes :Nuts
module Nuts::Models
class Page < Base
end
class BasicFields < V 1.0
def self.up
create_table Page.table_name do |t|
t.string :title
t.text :content
# This gives us created_at and updated_at
t.timestamps
end
end
def self.down
drop_table Page.table_name
end
end
end
Now we have our first version of our model. It says:
If you want to migrate up to version one,
create the skeleton for the Page model,
which should be able to store,
"title" which is a string,
"content" which is a larger text,
"created_at" which is the time it was created,
"updated_at" which is the previous time it was updated.
If you want to migrate down from version one,
remove the skeleton for the Page model.
This is called a _migration_. Whenever you want to change or add new models you simply add a new migration below, where you increase the version number. All of these migrations builds upon each other like LEGO blocks.
Now we just need to tell Camping to use our migration. Write this at the bottom of nuts.rb
def Nuts.create
Nuts::Models.create_schema
end
When The Camping Server boots up, it will automatically call
<tt>Nuts.create</tt>. You can put all kind of startup-code here, but right now
we only want to create our skeleton (or upgrade if needed). Start The Camping
Server again and observe:
$ camping nuts.rb
** Starting Mongrel on 0.0.0.0:3301
-- create_table("nuts_schema_infos")
-> 0.1035s
== Nuts::Models::BasicFields: migrating ===================================
-- create_table(:nuts_pages)
-> 0.0033s
== Nuts::Models::BasicFields: migrated (0.0038s) ==========================
Restart it, and enjoy the silence. There's no point of re-creating the
skeleton this time.
Before we go on, there's one rule you must known: Always place your models
before your migrations.
== Using our model
Let's explore how our model works by going into the _console_
$ camping -C nuts.rb
** Starting console
>>
Now it's waiting for your input, and will give you the answer when you press
Enter. Here's what I did, leaving out the boring answers. You should add your
own pages.
>> Page = Nuts::Models::Page
>> hiking = Page.new(:title => "Hiking")
>> hiking.content = "You can also set the values like this."
>> hiking.save
>> page = Page.find_by_title("Hiking")
=> #<Nuts::Models::Page id: 1, ... >
>> page = Page.find(1)
=> #<Nuts::Models::Page id: 1, ... >
>> page.title
>> page.content
>> page.created_at
>> page.updated_at
>> Page.find_by_title("Fishing")
=> nil
## Page.create automatically saves the page for you.
>> Page.create(:title => "Fishing", :content => "Go fish!")
>> Page.count
=> 2
Now I have two pages: One about hiking and one about fishing.
== Wrapping it up
Wouldn't it be nice if we could show this wonderful our pages in a browser?
Update nuts.rb so it also contains something like this:
module Nuts::Controllers
class Pages
def get
# Only fetch the titles of the pages.
@pages = Page.all(:select => "title")
render :list
end
end
class PageX
def get(title)
@page = Page.find_by_title(title)
render :view
end
end
end
module Nuts::Views
def list
h1 "All pages"
ul do
@pages.each do |page|
li do
a page.title, :href => R(PageX, page.title)
end
end
end
end
def view
h1 @page.title
self << @page.content
end
end
Here we meet our first _helper_:
R(PageX, page.title)
This is the <em>reversed router</em> and it generates a URL based on a
controller. Camping ships with a few, but very useful, helpers and you can
easily add your owns. Have a look at Camping::Helpers for how you use these.
There's a lot of improvements you could do here. Let me suggest:
* Show when the page was created and last updated.
* What happens when the page doesn't exist?
* What should the front page show?
* Add a layout.
* Jazz it up a bit.
== The last touch
We have one major flaw in our little application. You can't edit or add new
pages. Let's see if we can fix that:
module Nuts::Controllers
class PageX
def get(title)
if @page = Page.find_by_title(title)
render :view
else
redirect PageXEdit, title
end
end
def post(title)
# If it doesn't exist, initialize it:
@page = Page.find_or_initialize_by_title(title)
# This is the same as:
# @page = Page.find_by_title(title) || Page.new(:title => title)
@page.content = @input.content
@page.save
redirect PageX, title
end
end
class PageXEdit
def get(title)
@page = Page.find_or_initialize_by_title(title)
render :edit
end
end
end
The core of this code lies in the new <tt>post</tt> method in the PageX
controller. When someone types an address or follows a link, they'll end up at
the <tt>get</tt> method, but you can easily create a form which rather sends
you to the <tt>post</tt> when submitted.
There are other names you can use, but they won't always work. So for now,
don't be fancy and just stick to <tt>get</tt> and <tt>post</tt>. We'll show
you how this really works later.
You might also notice that we use <tt>@input.content</tt>. The
<tt>@input</tt>-hash contains any extra parameters sent, like those in the
forms and those in the URL (<tt>/posts?page=50</tt>).
Here's an <tt>edit</tt>-view, but you can probably do better. See if you can
integrate all of this with what you already have.
module Nuts::Views
def edit
h1 @page.title
form :action => R(PageX, @page.title), :method => :post do
textarea @page.content, :name => :content,
:rows => 10, :cols => 50
br
input :type => :submit, :value => "Submit!"
end
end
end
== Phew.
You've taken quite a few steps in the last minutes. You deserve a break. But
let's recap for a moment:
* Always place <tt>Camping.goes :App</tt> at the top of your file.
* Every route ends at a controller, but ...
* ... the controller only delegates the work.
* <tt>@input</tt> contains the extra parameters.
* The views are HTML disguised as Ruby.
* They can access the instances variables (those that starts with a single
at-sign) from the controller.
* The models allows you to store all kinds of data.
* Place your models before your migrations.
* Helpers are helpful.
Unfortunately, the book stops here for now. Come back in a few months, or join
the mailing list to stay updated, and hopefully there's another chapter
waiting for you.
发表评论
-
在Rails中使用Pry
2012-02-07 06:43 2123Pry可看成是IRB的加强版。支持语法高亮等特点。 1、在Ge ... -
Markaby (Markup as Ruby)
2012-02-04 03:58 1134http://markaby.rubyforge.org/ ... -
Ruby的一些疑问
2012-01-26 01:01 13771、网点看到一断程序, def m1(a) puts 'i ... -
RSpec测试框架
2012-01-10 12:59 2949#参考http://www.slideshare.net/ih ... -
[转]Ruby - DUP vs CLONE
2012-01-09 12:57 1790http://railsblogger.blogspot.co ... -
[转]eval, class_eval, instance_eval和binding
2012-01-09 12:10 1058http://www.cnblogs.com/rubylouv ... -
[转]Ruby中的binding
2012-01-09 11:50 1542http://kkito.cn/index.php/blog/ ... -
[转]Method visibility in Ruby
2012-01-04 12:37 1116From:http://weblog.jamisbuck.or ... -
[转]浅谈Ruby on Rails中的include和extend
2011-12-30 02:20 1015http://developer.51cto.com/art/ ... -
[转]Ruby中的Rake任务详述
2011-12-29 03:47 1716Trackback: http://tb.blog.csdn. ... -
[转]ruby中的闭包
2011-12-26 10:42 2734原文: http://kenbeit.com/po ... -
ruby技巧
2011-12-26 10:40 0ruby小技巧之 http://kenbeit.com/pos ... -
[转]Ruby中的多态
2011-12-20 11:56 0原文http://kkito.cn/index.php ... -
ruby中实现闭包
2011-12-20 09:10 914ruby中实现闭包很简单 如果一个方法中返回一个proced ... -
ruby中星号的使用
2011-12-20 05:54 1865ruby中星号的使用 1、数字乘法 2 * 3 = 6 2 ... -
[转]ruby的include与extend
2011-12-20 05:09 868原文http://www.cnblogs.com/rubylo ... -
[转]Ruby常用的内部变量
2011-12-20 03:59 900Ruby常用的内部变量 原文http://www.cnblog ... -
ruby与javascript面向对象编程的比较
2011-12-06 14:05 3309原文:http://howtonode.org/object- ... -
解决ruby中文乱码
2011-12-06 04:20 7974在文件头加上#encoding=UTF-8,示例: #enco ... -
[转帖]重新认识Ruby的多态和duck type
2011-12-05 11:56 948多态在Java中是如何定义的? 原文:http://devel ...
相关推荐
Camping分析PPT学习教案.pptx
网络黎明露营这是一个 Web 实验项目的集中存储库。 大多数情况下它只适合我,但如果你有兴趣,你可以自己分叉。
Camping Adventure Game 露营冒险游戏Unity2d儿童家庭模拟游戏项目源码C# 支持Unity版本2018.3.3f1及以上 准备好来一场真正的公路旅行周末冒险了吗?适合家庭的夏令营游戏就在这里,您可以通过许多激动人心的活动...
一个新的Flutter项目。 入门 该项目是Flutter应用程序的起点。 如果这是您的第一个Flutter项目,那么有一些资源可以帮助您入门: 要获得Flutter入门方面的帮助,请查看我们的,其中提供了教程,示例,有关移动开发...
但是,网站本身主要包含在一个完整的Camping(旧的ruby http框架)文件BigOleTexas.rb中。 选择使用Camping的原因很简单:我们在DotGeek获得了一个免费的托管帐户,而Camping是(当时)他们提供的最可行的服务器。 ...
如何设置露营地搜索创建一个名为yellowstone-camping.env的文件并将其放置在此存储库的根目录中,您可以使用文件作为模板。 准备yellowstone-camping.env文件后,填写您的住宿详细信息和Pushover凭证: export ...
:globe_showing_Europe-Africa: :camera: TravelLovers是一个在线平台,旅行者可以在这里结识志趣相投的人,共享地点并获得有关如何预订下一次改变人生的旅行的建议! :camping: :globe_showing_Europe-Africa: ...
Flutter Camping应用程式使用者介面 露营应用程序用户界面。 该存储库包含用于露营应用程序的两个屏幕(“欢迎页面”和“主页”)。 预习
Tourist Camping Tycoon是一款等距露营管理模拟游戏。 您必须创建自己的露营地,并管理游客的生意,从而创造地点,商店,娱乐场所等等。 TCT是使用jIsoEngine创建的
$ python camping.py --start-date 2018-07-20 --end-date 2018-07-23 --parks 232448 232450 232447 232770 :cross_mark: TUOLUMNE MEADOWS: 0 site(s) available out of 148 site(s) :camping: LOWER PINES: 11 ...
它运行一个http服务器。 路由-表示层,它公开API,并将请求/响应数据传递给其他层。 服务-处理交易的业务层。 模型-可以访问数据库并定义数据结构的数据层。 客户端加密 Darim支持客户端加密,以保护用户的...
COLLABOARD_Android:我们是合作者:camping:
将camping_template.xml重命名为camping.xml 从@BotFather填写您的用户名和登录令牌 强烈建议将@BotFather的/ setinlinefeedback设置为Enabled,以便可以跟踪内联输入事件。 相依性 for UI 用于连接到电报的 选修...
加州NPS规划师 该站点允许用户根据他们的位置查找加利福尼亚州内最近和最远的国家公园。... 使用的技术包括:HTML,CSS,Javascript,Web API,布尔玛(Bulma)等! 实时网站: : 网站的屏幕截图:
Tourist Trap
让您的朋友编写一个客户端来使用 HTTParty 向您发送消息。 每当您添加对 API 调用的支持时,向该文件的“API 调用”部分添加两到三行的简短说明。 描述应包括要使用的 HTTP 方法、路由和任何参数以及它们的作用。...
安装野生野兽新标签,并获得喜欢在大...Wild Camping“新标签页”主题是通往美好旅程的门户,您可以根据自己的喜好个性化所有内容,与您的网络共享并通过组织和跟踪待办事项列表来掌握最重要的事情。 支持语言:English
根据数据以JSON格式打开营地数据。 当前数据来源:
一般露营日程管理里程碑管理事件管理问题管理
野营 我最终项目的网站