Mun VS. Muse

(Bold what applies.)



Older? muse/mun
Taller? muse/mun
Richer? muse/mun
Neater? muse/mun
Nicer? muse/mun
Smarter? muse/mun
Funnier? muse/mun


Who is a better friend? muse/mun
Who lies the most? muse/mun
Who swears the most? muse/mun
Who reads more? muse/mun
Who is more creative? muse/mun
Who is more troubled? muse/mun
Who has better morals? muse/mun

Whipped up a quick dragon description template (ended up looking kind of similar to the one in giapetonflightrising's post, sorry I just went with a basic three-site-items-on-the-left thing). I might try to do two or three more before I put them into a forum post.

Would this be more appropriate for Guides or General Discussion, I wonder?

Free to use, just copypaste the code here into your dragon’s desc and customize to your heart’s content.

Magazine Cover Templates: 1&2/?
Newsweek: {download}
  • everything uses the Titling Gothic font family {download}
  • this is an incredibly simple to use psd; all you need is one large image and whatever article titles you want on the cover
VOGUE: {download}
  • you will need the following fonts to use this: Didot, AvantGarde, and Dubiel
  • Didot is only used for the title and the date/edition #, AvantGarde is used for all the article titles, and some subtitles, and Dubiel is used for the subtitles. I recommend installing all the fonts to get the best use out of this psd!
  • you may need to learn how to make a transparent .png for this, but it’s not always necessary
  • feel free to add, take away, or move the titles

And the last description layout for tonight, featuring cameos from Some Random People On My Friendslist’s Avatars. 

For the dragon pictures, I just used some people’s avatar dragons, but you could always crop and make your own images instead. The banner at the top is just Bamboo Falls with some cheap quick filters slapped onto it.

Free to use, free to modify, code is here.

개인적으로 템플릿 엔진 역사상 큰 전환점을 가져다 주었다고 꼽는 아이디어가 두 개 있다.

첫번째는 Kid1가 제안한 템플릿 상속블럭 개념. 그 전까지 웹 개발의 템플릿 작업은 어떻게 잘 템플릿을 쪼개서 인클루드할 것이가, 정도의 개념에서 벗어나지 못하고 있었는데, Kid가 제안한 템플릿 상속 아이디어는 템플릿 엔진 설계에 있어서 IoC에 해당하는 것이었다. 결국 Kid 자체는 XML 기반이라는 불편함과2 썩 빠르지 않은 구현 덕분에 망했지만, 템플릿 상속이라는 아이디어 자체는 워낙 훌륭해서 Django 템플릿에도 이어지게 되고, Django가 성공하면서 최근의 템플릿 엔진은 모두 상속 기능을 지니게 되었다.

두번째는 문자열 치환을 잘 하자는 기존의 모든 템플릿 엔진이 고수하던 근본적인 방식을 집어던지고 Haml이 제안한 트리(tree) 자체를 다루자는 획기적인 방식. 어쨌든 출력 결과가 XML/(X)HTML이고, 사람이 볼 데이터가 아니라 다른 소프트웨어가 볼 데이터라면 문자열을 직접 다룰 이유가 없다는 것이다! 대부분 사람들은 Haml이 Python과 같은 들여쓰기 문법을 채택했다는 점을 특징으로 보는데, 사실 들여쓰기 문법을 트리(tree)를 표현하기 좋은 방식으로서 선택된 부수적인 결정이지, 핵심적인 디자인 결정은 결국 문자열 대신 트리를 다루자는 관점이다.

템플릿 상속은 아이디어가 나온지 10년 가까이 된 현재 이미 널리 퍼진 상태고, 문자열 치환 대신 트리 자체를 다루자는 아이디어는 나온지 5년 정도 되었으니, 나머지 5년 안에는 널리 퍼졌으면 하는 바램이다.

  1. 사이트가 망했는지 접속이 안된다. PyPI 패키지 이름은 kid이다. 

  2. Kid 설계자가 딱히 XML 취향이라 그랬던 것은 아니고, 그 당시까지 Python 템플릿 엔진들은 죄다 XML 기반이었고 그게 대세였기 때문에 “무난하고 익숙한 방식”을 따르겠다는 디자인 의도였던 것 같다. 

Another equally-quick description template. The banner on the left I made by cropping the Media page wallpaper of Icewarden. In a perfect world, I’d maybe make some nice-looking ones for all the deities, but my photoshop filter technique is weak, and I’m not sure what sort of dimensions would be ideal for that. 

Code for this one is here. You can customize the runestones by changing them to the relevant flight and alter the items, font colours, etc., but for now, you’re on your own if you want a side banner.

character psd #5 »» "VOGUE"
  • everything should be pretty straight forward; you need two images, two epithets/labels, and a little blurb for the cover.  everything except for the lorem ipsum text is editable!
  • this psd works best for celeb-type rps, but please only use it if the characters are characters, and NOT real-life people
  • fonts used are Didot, AvantGarde, and Dubiel; you MUST have these fonts installed or the psd won’t work!
  • like/reblog if you download, and feel free to message me if you have any questions! 
download »» {mf}
Display Logic

Views are the most important entity, as they are what is directly requested by the client. For example, when the client request the context /main/hamburger, the object, settings and view associated with it are loaded.
The template is what is loaded around the view. This is determined by information provided by the /main/hamburger context.
The machine display mechanism diverges from most with the concept of components. Components can be though of as light-weight views, wherein they are written in PHP, but do not have an associated context object or JS controller. Components are subsets of each view, and to access a different components view, the name of the view has to be explicitly stated.

Components are never displayed on their own, they are always a part of a template or view. They are held in areas inside of templates and views. These areas act as containers for components to be loaded into.

To create called menu_space an area in a view: 


As far as HTML goes, an area is really just a div that is of the _m_area CSS class who’s ID consists of _m_ appended to the front of the name provided. Areas nested inside of other areas are given ID’s accordingly. For example, an area named spaced inside of the area one would be given the ID _m_one_spaced.

To place the component called mike in the area one: 


To place the component called mike, which is located in the context /show/best in the area one: 


—-To note, accessing components outside of your current context is not suggested at this point as JS Controller logic is connected to the context itself.—-

To place the component called mike/great in the area spaced inside of the area one: