As you see in last few days I was almost inactive. I just came in into steemit and I made some votes in order to support happychallenge and I test with few post stepshoot.
Why did it happens?
Because I am very enthusiast about the idea of the plugin.What the plugin does?
The idea of #oSteem is to enhance with some features the current platform, #Steemit. For more info, here you can find the introductory article.Yes, you guess. In last 3 days my focus was on #oSteem Chrome extension. At the beginning I expect to finish the fist version of this plugin in few days, because, more or less I had a idea about what I should to to create "The VIP list" feature. And somehow I did it.
Yes, the feature exist and it works pretty well. In the first Screen shoot I have all articles from feed:
In the second screen shoot I have filtered version of my feed and now I see only articles written by my VIP user list.
And then... What is the problem?
The main problem is the integration with Chrome browser. As I wrote in the first article, my experience with Chrome extensions was zero 6 days ago. And I start to drive between Chrome extension features like in a wild forest. Actualy it is not so wild but most of simple things are made in a unexpected way.
For example: Because I need to run filter script only in the feed page after each page reload I should check the url of the page and to run the script only if the url is like: https://steemit.com/@userName/feed. Until now nothing special, BUT... in You cannot do that in a normal content JavaScript file. You should do that in a background JavaScript file...
ok... if this works like that, I'll do like that, what I can do else? after few hours of doing that finally I did it and I was very happy.
But My happy was end in few minutes... Why? Because Now I get the url, but the url is in background JavaScript file, not in content JavaScript file and in order to send it from the background to the content script I should implement a messaging system.
As a normal developer I was thinking, ok let's send message from the background file to the content file, because My useful info it's in background file and when something will change in it, the background file will send the new url almost instantly. Yeah, but it doesn't work like that.... because only background script can listen messages and for this reason from time to time I should query from content script to background script: "do you have a new link?" .... "do you have a new link?" ... and it's stupid...
Initially I was expected to launch first release today or tomorrow, but seems that I need an accommodation period with chrome extensions which doesn't work as I expected usually. For this reason, at this moment I don't have any new date to the launch.
My apologize to @transisto, @anonimnotoriu, @teutorigos and all the others that waiting for this release. I'll come soon with updates (good news, I hope). :)
I think in this weekend will be the first release :)
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
I'm not sure about. :)
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Mostly Chinese to me, but I will grow someday a developer mind. Good luck with the project, I like the outcome.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Don't worry it's a beautiful Chinese. :))
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
No worries bro! You put a lot of work into this. Writing extensions looks easy at the start but it can be complicaed and timeconsuming as well. We can wait for the release.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit