Misc Projects

I manged to get Ubuntu installed onto my desktop finally and before testing my Pong game on it, I decided to fiddle with ASP.NET by moving an old template of mine, known as Core, from GetSimple CMS to ASP.NET's Razor engine where it's been renamed to RazorBlue. I'm aware that it's underwhelming at the moment. The template had been abandoned for a long time, due to GetSimple's limitations. As of this writing, it only has lightbox capabilities that were inherited from the old template. I hope with ASP.NET to expand it in ways I'd hope for in the beginning now that I run and maintain my own server where I tinker with it all I please - granted, I kinda shot myself in the foot doing that as of this writing.
Cuv6eth.png
The only few changes I made before this post was switch from Vendera to Roboto references all font types, the "powered by" footer, and some menu tweaks in the CSS.

Anyway, I'm open for suggestions.
Chubby update
Seems my calculations were way off. It turns out mod_mono is a pain in the ass - even when using Xamarin's repositories. Ironically, Microsoft's .NET Core may be more suited for Linux servers so I've made a version of RazorBlue that supports this known as RazorBlue Core. The original has been renamed to RazorBlue MVC and will be supported until ASP.NET 4 is deprecated. I recommend Core for cross-platform use and MVC for Windows Server. It was quite easy to switch to from 4 to 5. I really gotta hand it to Microsoft and their Razor engine.

The Core version inherits features from the web application template I used as a base. That includes individual accounts, jquery, Hammer.js, and Bootstrap libraries. Accounts has the ability to use social network authorization for sign up and login, though this left empty by default. In the end, this is exactly what I wanted when I first made this template years ago. :D

On another note, Mono is still needed when on Linux ARM servers, such as the Pi, since .NET Core for Linux only supports x86/x64 architecture. .NET Core ARM seems to be limited to Windows IoT.
 
Last edited:
Like I said, .NET Core was a bit of bust, due to a hardware issues, and Mono doesn't help matters either. I've ported the entire template to Revel web framework, written in Go. Which will give me a reason to finally learn it, finally. Go has had ARM support for a while in Linux.
 
Like I said, .NET Core was a bit of bust, due to a hardware issues, and Mono doesn't help matters either. I've ported the entire template to Revel web framework, written in Go. Which will give me a reason to finally learn it, finally. Go has had ARM support for a while in Linux.
>ARM support
ARMv7?
 
I wish they'd just make tablet devices use desktop webpages by default, especially since tablets are really powerful nowadays >.< there are some with 3, 4GB of RAM in some cases. Sure, I understand why phones display different ones, but tablets? Nah.
 
"please, rotate to landscape"
More like irresponsible web design. :D If I saw that on my screen, I'll be like: NO, PLEASE FIX YOUR CSS, DUMBASS. And then I'd quit the website, unless I was desperate to look for something there. Just like I do with these sick "PLEASE INSTALL OUR APP, NOBODY WANTS TO DO THAT SO WE HAVE TO NAG YOU WITH A HUGE OVERLAY FILLING YOUR ENTIRE SCREEN" boxes, when I'm browsing websites on my phone.

How are you doing that anyway? By hiding the block with content and showing this warning if window width is smaller than [something]? I wonder if you could hit that by simply multitasking on a laptop/tablet. That would be a really bad UX.
 
I believe you can use CSS media queries for this. (or javascript if you really want)
 
"please, rotate to landscape"
More like irresponsible web design. :D If I saw that on my screen, I'll be like: NO, PLEASE FIX YOUR CSS, DUMBASS. And then I'd quit the website, unless I was desperate to look for something there. Just like I do with these sick "PLEASE INSTALL OUR APP, NOBODY WANTS TO DO THAT SO WE HAVE TO NAG YOU WITH A HUGE OVERLAY FILLING YOUR ENTIRE SCREEN" boxes, when I'm browsing websites on my phone.
Visit the site now, it now responds better to portrait mode but there is only so much I can do in the layout's present state. Also I hate it when websites nag you for the app version.

How are you doing that anyway? By hiding the block with content and showing this warning if window width is smaller than [something]? I wonder if you could hit that by simply multitasking on a laptop/tablet. That would be a really bad UX.
4RpPwbm.gif

Nope, not at all.
Code:
#warning-message { display: none; }
@media only screen and (orientation:portrait){
    #main { display:none; }
    #warning-message { display:block; font-size: 40px; }
}
@media only screen and (orientation:landscape){
    #warning-message { display:none; }
}
 
Well, at least your UX is now just half as bad as it could be. :D

Anwyay:
kreUTMq.png

You should really make it responsive. That box with content could be forced to fill the screen below certain width with a simple change:
aujXMgc.png

Simple change, makes stuff magically look better in portrait mode. You can throw your warning away now.
8VtWmDj.png


I suppose menu could be replaced with more compact version using media queries. What I see now is a font size bump that kinda messes it up. "Brand" image could also be shrinked to fit the top bar then, it would make your page more mobile friendly (because a huge box is not something you'd like to see on mobile).
 
aFdF14J.gif

Simple change, makes stuff magically look better in portrait mode. You can throw your warning away now.
8VtWmDj.png
Do you have a phone?
bIppFRE.png

Code:
/* ------ Adaptive ------ */
#warning-message { display: none; }
@media only screen and (orientation:portrait){
    #wrapper{
        align: center;
        width: 90%;
        font-size:1.9em;
    }
}


/* ------ Adaptive ------ */

@media only screen and (orientation:portrait){
        #menu_wrapper{
            font-size: 30px;
            height: 100px;
        }
       
        #rbmenu li a {
            height: 99%;
            padding: 30px 5px;
        }
}
 
No, I'm using my laptop to make phone calls. See, at some point, 15 inch phones would hit the market because 10 inch ones wouldn't be comfortable enough to browse webpages on. So I'm kinda already living in the future while still in 2015. Cool, huh? :D
 
Then maybe you're in the wrong place to tell me how to best write my site for mobile? Since I actually have said devices with me.
 
Back
Top