news from many major sources in one spot, what do you think?

http://seductiveapps.com/news(section'English_News')

( /news will work too )

see anything you'd like improved?
let me know

sources are listed at https://gitlab.com/seductiveapps/se...s/seductiveapps/news/appContent/newsApp/2.0.0

 

which browser are you using? and which operating system, on what type of device?

 

ok i've been doing a lot of stuff under the hood lately, and i hadn't tested these changes yet on Macs. But i have an apple store nearby, i'll head over there before next Tuesday and see if my site still works on their products.

and i know @deathshadow hates my stuff.

guess what, it's in development, says so on the front page even, and things @deathshadow insists i must do to be taken seriously by him (like concatenating my scripts, which is hell to develop under), i don't care nearly as much about as he does.

that may all seem unprofessional, but i can't get stuck in a swamp while developing new features (like CMS and social media and forum and webshop and auction-site functionality) that can scale to facebook / twitter / etc size.

that's why my software seems unprofessional... i keep my life as simple as possible while developing something like Angular for the apps platform features (but closer to the HTML, simple JS and jQuery standards than Angular, with no compile step to get to a webpage).
that means i develop in 1 browser on 1 ubuntu PC for now.

but i would like my site to work again on all platforms now that i've slashed js startup time from 10s to about 3s.
so i'll make work of that.

and @deathshadow.. if you're going to diss my site for something, be sure to pass the tip on how to fix it, rather than sink into your usual tirades and flaming behavior, ok..

 

Yeah, at first I thought it was just another of your "five minutes to get a page" until I realize scripting execution had hung. So two minutes to get a silly "loading" animation with no content. That's pure win...

Lemme guess, another 8 megabyte monstrousity to try and load 1k of plaintext? I could probably tell for sure if you weren't spawning the debugger so much.

What is that though? 178 file requests? Surprised it doesn't take three minutes before the debugger starts.

 

you can turn off that debugger, right? or tell it to bypass all breakpoints?

and what kinda menu would you like to see? i thought the fish were rather nifty, using CSS sprites created by a PHP script that takes video frames (produced by ffmpeg) and turns them into buttons with 4 states (normal, hover, selected, disabled)..

i'm also interested in loading time and getting the thing to start up properly on all internet devices. so i'll test for firefox, safari on apple products, and Internet Explorer, over the next week..

and @deathshadow, what browser and device are you using?

i develop using Chrome, on ubuntu.

 

I tried in in Vivaldi on Windows, Firefox on Windows, and Chromium on Mint. (that last one in a VM)

Vivaldi is built on the same Blink + V8 stack as Chrome, Electron, nw.js, etc -- for all intents and purposes it is Chromium just with a UI that isn't stuck in the dark ages like every other browser right now. What with EVERYONE else seeming to think browsers should look (and have interface crippled down to be) like IE3 did on the Mac.

Either way, you call debugger halting scripting execution...

I am behind a VPN right now,l so that ups the ping-time, hence right now I'm seeing 800ms ping to your hosting, meaning that 170 files cache-empty is introducing ~136 seconds of overhead on the page-load.

Probably why websites should NEVER be built with CSR or that much "JS for nothing"... and no legitimate websites are, or ever look to be.

Oh and I got a big blank page on FF in Mint at first, but that was a my bad -- I have "JavaScript Control 1.1" installed. If you're going to go full scripttard like that, at least put a noscript warning in.

 

i've also tried firefox on both ubuntu and on windows 10, and it works just fine. displays news within seconds.

 

yeah, my news app works much the same way. stores cron-curl-fetched RSS data on the server as JSON files, then does a bunch of stuff to load up enough of the most recent news to start displaying quickly.

well i'm interested to hear your idea for menu buttons..
and what do you mean by styles? CSS? i'm working on that, but i haven't figured it out completely yet. i have need for things like relative resizing (relative to the browser width and height), and that does complicate it a bit.

and the load time should be drastically cut from what it was in previous months, even with the 180 requests..
i have news on my screen within 4 seconds from starting a page load when i've visited the site before.
and about 5.5 seconds for a shift-reload that re-fetches every file as if it were the first time you loaded up the site.

writing a concatenation script shouldn't be that hard, and i'll put it on the todo list.
but other stuff, like the button images for my main management interface for the CMS features, can't be stored in a CSS sprite for instance, because that relative-to-browser-window-size resizing of buttons requires that the button images remain seperate files.

what i *could* do is set the initial display:none on the <img> tags, that should prevent them being downloaded at startup, i think.

and i'll put a no-script warning in.

perhaps.... i could also use canvas to get image data (like a button's image) from a CSS sprite sheet, and then create a new <img> that is filled with this data from the sprite sheet.
i'll look into that.

these ping times, i never knew about them until now, because i develop on localhost, and the seductiveapps.com server is attached to my own ADSL modem.
i agree now that it's an issue when i want to scale to a large visitors and users base.

i have example code that takes a uploaded jpg file and creates a thumbnail of that, in pure javascript, using canvas blob techniques.
so it should not be impossible.

and i have to build a new button component anyways, a non-video button that still has some nifty effects options.

i think i'll do this first.
the concatenation script for viewers other than a developer, can come later.

thanks for the tips and conversation so far, folks.

 

You have something wrong in your code. All I get is the following on a blank white page:

Windoz with FF.

And DOZENS of ERRORS per >>> https://validator.w3.org/nu/?doc=http://seductiveapps.com/news(section'English_News')

 

Flex-box, the incorrectly named "CSS grid layout module", vw, vh, floats, media queries, and letting flow do its job. Layout is not JavaScript's job!

... and really that's what makes MOST of your pages such heavy hard to use messes. You're using JS for stuff you don't need and shouldn't be using JavaScript to do!

MORE SO now that CSS 3 is real world deployable and we can pretty much say "Legacy IE? They get a crappy single column who cares?"

But again, 90%+ of what you do on your pages does not warrant the PRESENCE of JavaScript. Or inline style="" in the markup, or the alt attributes on HTML elements that don't even HAVE alt attributes (like your anchors), or the megabytes of code you have doing double digit kilobytes job.

 

i've always found several of the things that my CMS now does utterly impossible without resorting to all that you just mentioned, @deathshadow

and doing it like this means having to focus on only 2 sets of logic and 2 sets of files : html + js, instead of 3, html + js + css.

and yes, i should probably run the concatenation script through a minifier.
know a good js minifier for PHP? or even linux commandline? python perhaps?

@mmerlinn i recently tested FF on windows. it worked just fine.
i don't understand what's going wrong.
is it possible you paste me a log of the console output?

 

found a minifier that works.. will also do something to postpone the loading of ads and the like..
that should bring the number of initial requests down significantly.

 

I don't think any of us has actually seen your news page load, because you have a debugging line still public facing so scripting execution stops at this point:

In not one combination of browser or OS does your page go past this point:

http://www.cutcodedown.com/for_others/seductiveApps/images/stopsHere.jpg

Code (markup):

... and as @sarahk said, this is why:

http://www.cutcodedown.com/for_others/seductiveApps/images/stops_heresWhy.png

Telling it to resume, disabling breakpoints, none of that helps get it to keep running either. Don't deploy your debugging breakpoints on your LIVE copy. That's local testing's flipping job.

Then again as I've said many times, that means you don't know enough about HTML or CSS to even be USING JavaScript in the first place, but really this:

Is the "well there's your problem" -- oh noes, three different types of files for three different unrelated behaviors, nots thats. Comically silly when you have hundreds of separate files for nothing to be worried about "oh noes, I have to use a third language?" -- particularly when you have four digit megabytes of code doing double digits of kilobytes job!

PARTICULARLY when you have outright ignorant garbage like this in your markup:

<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" style="padding:0px;margin:0px;overflow:hidden;">

Code (markup):

or this:

<body style="width:100%;height:100%;overflow:hidden;padding:0px;margin:0px;" onload="jQuery(document).ready(sa.site.code.startWebsite);" ontouchmove="sa.s.c.iosOntouchmoveBody(event);" ontouchend="sa.s.c.iosOntouchendBody(event);">

Code (markup):

Anyone else care to try explaining this to him?

Laugh is I think you'd really like the CSS grid layout module, since it does out of box in ~10 lines what you seem to be wasting hundreds of lines of scripting, garbage inlined style, and hosts of other bits of code-bloat on.

 

It's a pointless excercise, he doesn't listen and he sure as hell won't take any notice.
On topic, the site doesn't load for me either, all I see is a ridiculous huge loading gif and some menu buttons that look like they came from the early nineties...

 

for the record, i do listen..
just spent a day cutting back the number of initial load requests from 186 to 54, for those who choose to live with high ping times like @deathshadow.

i'll look into the stability issues and startup issues on different browsers and OSes sometime this week.

it would help if you people would attach a console.log instead of just a screenshot.

 

i've turned off source minification and -concatenation for now, because i need accurate information on where in my sources these errors occur, if anyone decides to do post a console log of how it doesn't start up on some system/browser combo.