jose/LogSource
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

restyle
Some checks are pending
Deploy Arise to html branch / Deploy Arise (push) Waiting to run
Details

Browse source
This commit is contained in:
Jose Falanga 2025-10-13 19:11:32 -03:00
parent a232e5c209
commit a59a61e1f5
3 changed files with 108 additions and 111 deletions
Download patch file Download diff file Expand all files Collapse all files

7
arise-source/config/header.html
View file

@ -44,13 +44,6 @@
<!-- End Favicon -->
<!-- Styesheet+Logo -->
<style>
html * {font-family:monospace,sans-serif;}
body {background-color:#121619;margin:40px auto;max-width:650px;padding:0 10px;color:#65f85a;}
a {color:#b8f1b4;}
hr {color:#65f85a;}
.topbar a {color:#65f85a;}
</style>
<link rel="stylesheet" href="/config/main.css">
<div class="logo"><a href="/"><img src="/config/logo.png" /></a></div>
<!-- End Styles+Logo -->

54
arise-source/config/main.css
View file

@ -1,4 +1,3 @@
/*** Core page styles to set the primary colours and styles to be inherited by everything else ***/
/* Core Styling */
@ -14,11 +13,8 @@ body{
background-color: #121619;
padding: 0 10px;
}
/********************************/
/********************************/
/*** Post styling. This section is for defining markup classes to make it easier to write prettier posts. ***/
/*** Post styling ***/
img {
max-width: 100%;
max-height: 100%;
@ -30,19 +26,34 @@ img {
display: block;
}
/* Inline code */
code {
background-color: #293137;
border-radius: 16px;
padding-left: 30px;
padding-right: 30px;
line-height:2em;
padding-top: 1px;
padding-bottom: 1px;
line-height: 2em;
color: #65f85a;
font-family: monospace;
}
/* Block code (Arise syntax highlighting) */
pre.sourceCode,
pre.sourceCode code,
pre.sourceCode code span {
font-family: monospace, "Courier New", Courier, monospace;
background-color: #293137;
color: #65f85a;
line-height: 1.4em;
padding: 4px 16px;
border-radius: 16px;
display: block;
overflow-x: auto;
}
/* pre element itself */
pre {
overflow-x: auto;
white-space: pre-wrap;
@ -71,7 +82,7 @@ hr {
max-width: 300px;
}
#endline { /* Special kind of <hr> for spacing out footnotes from the rest of a post */
#endline {
color: #65f85a;
margin-left: auto;
margin-right: auto;
@ -80,19 +91,20 @@ hr {
}
a {
color:#b8f1b4
color: #b8f1b4;
text-decoration: none;
}
h1 {
line-height:1.2
line-height: 1.2;
}
h2, h3 {
padding-top: 24px;
line-height:1.2
line-height: 1.2;
}
/* Style for inline dates. These are configured via a separate include file in /config/content_header.html. See notes on Arise page creation for more details. */
/* Inline dates */
.date {
padding-bottom: 0;
margin-bottom: 0;
@ -111,19 +123,15 @@ h2,h3{
}
}
/********************************/
/********************************/
/*** Modular component styles ***/
/*** Modular component styles. Includes styling for the headers, navigation controls, and footer. ***/
/* Site logo. Styled to responsively move to either left or be centred, depending if the page is being viewed on desktop or mobile respectively. */
/* Logo */
.logo {
margin-bottom: 20px;
text-align: center;
}
/* Navbar styling. */
/* Navbar styling */
.topbar {
padding-right: 10px;
border-top: 1px solid #65f85a;
@ -136,7 +144,7 @@ color:#65f85a;
text-decoration: none;
}
/* Site footer styling */
/* Footer styling */
.footer {
border-top: 2px solid #65f85a;
font-size: 12px;
@ -144,10 +152,6 @@ text-decoration:none;
text-align: center;
}
/********************************/
/********************************/
/*** Other misc garbage ***/
/* Arise Index Style */
@ -157,7 +161,7 @@ text-decoration:none;
border-top-style: solid;
text-align: center;
padding-right: 10px;
padding-bottom: 5px
padding-bottom: 5px;
}
.arise-toc-th {
padding-bottom: 20px;

2
arise-source/rehosted/vertical-vs-horizontal/index.md
View file

@ -14,7 +14,7 @@ rss_hide:: "true"
# Vertical Slice vs. Horizontal Layer
> Originally posted in the now defunct uber.typepad.com blog. You can find an archived version on [The Internet Archive](https://uber.typepad.com/birthofagame/2009/04/vertical-slice-vs-horizontal-layer.html)
> Originally posted in the now defunct uber.typepad.com blog. You can find an archived version on [The Internet Archive](https://web.archive.org/web/20250914133730/https://uber.typepad.com/birthofagame/2009/04/vertical-slice-vs-horizontal-layer.html)
I've [mentioned before](../find-the-fun) [(archive)](https://web.archive.org/web/20250914133730/https://uber.typepad.com/birthofagame/2008/10/find-the-fun-fi.html) I think the Vertical Slice (VS) is one of the most abused industry practices. By definition, it ought to be a version of your software that is near final quality in a small subset of its domain that represents the overall product. If you're making Call of Duty 4 it might be "just one mission" complete with working AI controlled enemies, HUD art, polished control scheme, in-mission cinematics, and near final quality art assets. The problem is getting to this vertical slice actually requires completing a huge portion of the game. For example, the subset of character rigs and animations required for the level may be 80% of the animations needed for the entire game. The UI and HUD are an often underestimated amount of work yet having near final quality versions of them for "just one mission" is saying that entire subsystem needs to be nearly complete. The requirements may say 3 weapons out of the 15 that will be in game, but you'll be doing more than 1/5th of the code underneath to meet those requirements. If employed too early in development the VS can derail an entire project or worse put it on the fast track to nowhere.