Inspired by this post, I wrote a CoffeeScript implementation. This is a very interesting phenomena that revealed the beautiful philosophy behinds the nature, a slight push to the collection of simplicity can make miracles : D
As you can see, each particle is just moving around on a circle orbit with the same velocity, only the initial position is different. However, when they are made a whole, things begin to be interesting.
There are plenty of tutorials about how to setup a minimum Goagent server and client. I won’t reinvent the wheel here. Who may want to read this post.
This theme is build on the top of zsh and the famous OH MY ZSHELL. Besides, it has been included in the official OH MY ZSH repo : D
To a compatible theme, I think it’s better not to use special characters like ╭ ➜ ✗ . If you want your theme works fine on both Unix and Windows, a clean format and a simple color scheme are necessary. Therefore, I use only ANSI Character Set and ANSI Colors. The main goal of this theme is to make the *nix servers’ admins happy. This theme is even more robust than the default theme robbyrussell.
I separate each command group with an empty line in front of the “#” prompt. The indicator words are all in a dim color. The most eye-catching color yellow is assigned to the current directory. For other colors’ setting, the same color will be assigned to different location with a long distance. And the more important it is, the more warmer color it is assigned to.
For the purpose of making the beginner to learn the command line easier, I set the dollar symbol “$” as the main command prompt. The “%” or “#“ indicates the current state of the terminal. The “L” indicates current shell level, it can be useful when you are in nested shells. The last “N” indicates the current command number, with the time stamp you it may help you calculate how long a command takes.
The basic theme format:
|
1 2 |
PRIVILEGES USER @ MACHINE in DIRECTORY on git:BRANCH STATE [TIME] L:SHELL_LEVEL N:LINE_NUM $ COMMAND |
There are so many ways to get the program to have the ability of auto-update. But as I’ve known, there is no way can absolutely make sure the program will update itself as expected. For example, you have defined some data type, in your program and store the data locally. And you have happily distributed your product to thousands users. Then months pass, you add some details to the basic data type. You migrate all the user data properly, and everything gone fine. Not a single complain heard from you users. Things turned complicate when the third time you update your data type. Now you have 3 types of data. Some of your users may be still the oldest version. Fortunately, you have left a tag in the data type to mark the version of the data type. So you take your time to check the version, and implement 2 method to migrate the data.
How about if this pattern continues for around 10 times? How many migration methods you should implement? Nine, of course. But if for some reason some of your users have reversed the version to an old one? From the basic principles of combination, we need 10×9 which means 90 methods to meet the requirement. That sounds crazy.
The main problem is because you can’t be sure whether all the users have always updated to the newest version. In other words, you need to find a solution to sync all the users program version and don’t hurt their data. On one can predict the future, we never know how the data finally like.
To be continued…
When copying some of my old project files from Windows 7, the origin system text file encoding made some troubles for me. So in December, I wrote a small tool to help me out. But before days, the same problem came out again when the old mp3 ID3 tagged files met the iTunes. Therefore, I extended the tool to automatically convert the mp3 files to the specified encoding. I used the ID3iconv to help with the tag editing.
Here I just want to mention one thing, sometimes it might be more aesthetic use another language to present the comments. The comments will be easier to be found through a bunch of codes.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 |
#!/usr/bin/env python #-*-coding:UTF-8-*- # Dec 2012 ys import re import urllib2 import os class Robot(): def __init__(self, host, max_depth=3): self.host = host self.max_depth = max_depth self.log_file = os.path.dirname(os.path.abspath(__file__)) \ + os.sep + 'robot_log.txt' def start(self): # This pattern will ignore all the relative url. self.reg = re.compile(r'''<a href="(?P<url>http.+?)(#.*?)?".+?/a>''') # Avoid infinite loop. # Such as the sub page contains a url directs to the home page. self.url_dict = {} self.walk('http://www.' + self.host) def walk(self, url, depth=0): if self.is_walked(url): return # The number of dash represents the depth of the url. print '- ' * depth + url content = '' try: page = urllib2.urlopen(url) content = page.read() self.save_content(url, content) except urllib2.HTTPError, e: # Such as the 404 or bad network connection. print e, ' >> ', url depth += 1 # Search the urls in the page. # The finditer will generate a iterator. for i in self.reg.finditer(content): u = i.group('url').rstrip('/') if not self.is_current_domain(u): continue # Whether the url is belong to current host. # Whether it is reached the max recursion depth. if depth < self.max_depth: # Recursion. self.walk(u, depth) elif not self.is_walked(u): print '- ' * depth + u # We don't need to search other domain's url. # Or the the url that has been handled. def is_walked(self, url): if url in self.url_dict: return True else: self.url_dict[url] = True return False def is_current_domain(self, url): if self.host not in url: return False else: return True def save_content(self, url, content): sep = '\n\n' + '*' * 60 + '\n\n' content = sep + url + sep + content f = open(self.log_file, 'a') f.write(content) f.close() # Ctrl + C to exit. try: robot = Robot('stackoverflow.com') robot.start() except KeyboardInterrupt: print "\nTerminated" exit() |
I think the general MVC architecture is not perfect enough for a complex dynamic application. The most confusing part of the MVC is it’s Controller. It receives the user sent data, sends commands to change the state of the Model, and also takes the responsibility to change the presentation of the view.
I think it could be simpler:
To separate each component’s responsibilities, and make the architecture more open. I replaced the Controller with the Service. The Service only handles the data that the View requests, such as REST, or sends commands to change the Model’s state. All UI logic is moved to the View, and all View requests are async based. So that we can take the full control of the representing flow the application. The front-end developers will only need the client knowledge and skills to construct the dynamic content of the application.
The disadvantages of this architecture are obvious. The client should at least supply a programmable interface. Such as the HTML based web application, the browser should support javascript and the javascript is enabled. And looser coupling means lower performance.