Fork me on GitHub

#1 2015-08-07 01:18:14

Wolfy
Member
Registered: 2015-05-12
Posts: 313

eyeReader

Well, here I am again. EyeReader is an interesting little ebook reader. I just got all the bugs out of it and wrote an instructional manual on how to use its partial set of BBCodes to create ebooks in eyeReader compatible format. The app only has one remaining problem. When a user clicks on a link, the page is automatically sent to a browser tab.  I want to send it to either eyeIFramize or eyeNav instead.

Here is the patch of code that they used to hard code it to the top of a blank tab.  Hopefully, someone can show me a quick fix for it.

// Perform URL Search
	$Text = preg_replace("/\[url\]([$URLSearchString]*)\[\/url\]/", '<a href="$1" target="_blank">$1</a>', $Text);
	$Text = preg_replace("(\[url\=([$URLSearchString]*)\](.+?)\[/url\])", '<a href="$1" target="_blank">$2</a>', $Text);
         //$Text = preg_replace("(\[url\=([$URLSearchString]*)\]([$URLSearchString]*)\[/url\])", '<a href="$1" target="_blank">$2</a>', $Text);

I think I need to start a function that sends "$1" to eyeIFramize, but I don't know how.

Last edited by Wolfy (2015-08-07 01:29:51)


Wolfy
https://www.facebook.com/groups/oneye/
Currently accepting new users...  http://www.OS1.hawkwolf.net
onEye admins: OS1 is a beta testing hotbed. Non-core apps available upon request.

Offline

#2 2015-08-07 11:14:26

Wolfy
Member
Registered: 2015-05-12
Posts: 313

Re: eyeReader

Wow, I just noticed the last line is commented out.  It doesn't make any difference though.  I have no clue as to what the first two lines are even supposed to be doing, but if I click a link it loads it in a new browser tab. The app is running perfectly.  I just don't like that one little part, because ultimately my goal is to keep users inside the OS until they choose to leave, while it seems the rest of the web is determined to pull them out of it, with or without warning, and since I must assume that most onEye users would use eyeNav to access web sites and services exactly as their designers intended, there's definitely no cause. It makes me wonder where were all the cloud/web os lobbyists while the internet giants were corn-holing us with this blanket/no exception, same server only rule? Maybe they took a pit stop in Amsterdam. I can't say I would really blame them.   lol.

What should have happened is an exception should've been made specifically for web/cloud os browsers.  There should already be a special User Agent ID or a spoof code that would only work from inside a web/cloud os, or even something like a pipe that would grant a web/cloud os browser the same permissions and capabilities as if it were a browser tab.

If the idea of a web/cloud os survives this debacle then I have no doubt that eventually there will be such a compromise, but until that day, it's time for eyeNav to completely stop trying to access google.  It doesn't work anyway, so it should be removed from the search engine settings unless/until it does again. That only leaves Bing, but Bing is a pretty big boy on the block too, and so far still loads into a frame nicely, plus they build some attractive pages that make google's attempts look like childish locker room humor. So all in all, Bing is actually a pretty good fit for onEye, at least unless they also decide to go with this same server only crap. 

Finally, I'm really sorry for the wall of text/quasi-rant this turned into, but while I'm thinking about eyeNav, I just remembered that I might have found a way to restore the back and forward buttons. The code works in the browser-based browser where I found it, but I just downloaded it today and haven't had a chance to really look it over yet.  Even so, I think there's a good chance it will work for eyeNav.

I attempt to test one previously untested app and to repair one or two broken apps every day. In the process, I trip over a lot of stones in the core and find bugs or odd behavior almost everywhere I look. Some days, it feels like nothing works the way it should, or if it does work, its not the way I want it to work.  I have lists of feature requests, starting with adding the user's real name and email address as mandatory during new user sign up.  Currently, if they don't go into prefs and add this data voluntarily then I really have no way to know who most of my system's users are or how to contact them, and I don't like that. On the far extreme extreme, it includes a web server inside onEye, to serve up html and php, web native images, videos and vector graphic formats, but first, I would rather see the bugs fixed, lost functions restored, plugins upgraded, etc. A house built on a weak foundation will fall. In the short term, I think we need one or two bad-ass, fresh out of college, volunteer web programmers with nothing but spare time and an intense desire to assist Lars (and maybe me too!). Sure, I'm just dreaming, but it's fun to dream and doesn't cost much.

Thanks for listening.  smile


Wolfy
https://www.facebook.com/groups/oneye/
Currently accepting new users...  http://www.OS1.hawkwolf.net
onEye admins: OS1 is a beta testing hotbed. Non-core apps available upon request.

Offline

#3 2015-08-08 17:42:53

lars-sh
Administrator
From: near Hamburg, Germany
Registered: 2011-07-14
Posts: 731
Website

Re: eyeReader

The following should work: Add the first code segment to that "a" (link) tag and that second one to "events.eyecode".

First: http://pastebin.com/y6FVD5BG

Second: http://pastebin.com/Fijggq9G

PS: Untested. Please give me some feedback.


Best regards,
Lars Knickrehm

The oneye project.

Offline

#4 2015-08-12 01:57:34

Wolfy
Member
Registered: 2015-05-12
Posts: 313

Re: eyeReader

The "a" code is from events.eyecode, but I don't think that will make a difference.

I understand about adding the function, but I don't know how to add the onclick code to the "a" tag.  It doesn't make sense to me.


Wolfy
https://www.facebook.com/groups/oneye/
Currently accepting new users...  http://www.OS1.hawkwolf.net
onEye admins: OS1 is a beta testing hotbed. Non-core apps available upon request.

Offline

#5 2015-08-12 13:45:00

lars-sh
Administrator
From: near Hamburg, Germany
Registered: 2011-07-14
Posts: 731
Website

Re: eyeReader


Best regards,
Lars Knickrehm

The oneye project.

Offline

#6 2015-08-12 21:45:12

Wolfy
Member
Registered: 2015-05-12
Posts: 313

Re: eyeReader

Yep, you nailed it.  It now sends links to eyeNav.  The email link section hasn't been tested, and the instructional docs could use a little more editing, but it should be ready for release soon.  I just got notice that the new github client for windows is available for testing.  I will check that out soon too.


Wolfy
https://www.facebook.com/groups/oneye/
Currently accepting new users...  http://www.OS1.hawkwolf.net
onEye admins: OS1 is a beta testing hotbed. Non-core apps available upon request.

Offline

Board footer

Powered by FluxBB