-- XBEL support
-- searchable, freeform "description" or "notes" field (not limited to 255 chars)
-- "manage bookmarks" GUI which displays description as MULTILINE editable field
No, no borrowing from anywhere. At least just not yet
Needs to be said (asked):
You're hosting the project on SourceForge.
Everyone wandering through here (including me) expects that this is an OPEN SOURCE project.
I just now clicked the 3 (redundant?) "Code" button links display here...
Summary
Files
Reviews
Support
Wiki
Code
Tickets
Discussion
Blog
Code
Code
...and discovered that, in fact, no source code is available at the linked "git" URLs.
No problem, except you're soliciting donations to the project, and I would be highly motivated to donate, but only if the source is available. Bear in mind that previously, when I got excited about a project and, without even hammering the developer with feature requests, contributed a chunk of money ( https://sourceforge.net/projects/leopardflower ) ...oops, his hard drive crashed and the cat ate his homework and, yeah.
That experience weighs heavily on my mind, and considering that you've already blogged about experiencing hardware failure since the outset of your project... I gotta tell you that I'm unlikely to financially support another one-man-band with grandiose goals, closed-source project. From the point of view of a prospective donor, it seems reasonable to expect that either you'll get burned out working too hard on the project, or the cat will eat your homework, or whatever.
Your "no borrowing" comment above, that adds additional worry.
Too proud?
Wants to figure it out for himself (across the next month o' sundays) as an academic exercise?
Intends to eventually sell this as a commercial software product?
In your blog posts you've already professed that you're not even committed to sticking with QTWebkit. Hey, I'm not criticizing your rationale, I understood your point about the prospect of its future developement. My point, here, is that although you're "having fun and gaining experience"... I'm likely wasting time bugtesting an app built on a foundation of sand.
A friendly (yet pointed) piece of unsolicited advice:
Also, dear one-man-band, Sir...
you've mentioned "not NOT not supporting plugins/addons".
Visit http://forum.epicbrowser.com/viewforum.php?id=6
and note which discussion topic has drawn 5,600+ views and has, by far, the greatest number of replies.
Even with a fulltime multi-person staff, building upon a relatively fully-featured chromium codebase, they can't accommodate all the requested features in the core app, and are bleeding usershare (have bled, most users have abandoned ship) due to inability to customize via addons.
Please don't rush to reply to this. Take your time, reconsider what direction you wish the project to go.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you want to buy the source you are always wellcome.
Update:
And if you do want to buy it there are two conditions:
One: It be dual licensed BSD/GPL
Two: My name is somewhere in the credits as the orignal contributor to your fork.
Update 2:
However, I will be releasing proxy checker code to github during next week. That damn thing still crashes time to time and it's time to ask coding community help.
Last edit: Stefan Fröberg 2014-08-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I still have great hope for your project. Just understand that it probably won't seem reasonable to offer financial support to the closed-source project until CD at least reaches feature parity with Qupzilla and/or Torbrowser Dooble.
Last edit: sandax 2014-08-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Needed badly? Yes!
For now, to get something started, maybe just borrow code from Dooble:
http://dooble.sourceforge.net
https://sourceforge.net/p/dooble/code/HEAD/tree/
ps:
Are you able to (im)port code from Qupzilla codebase?
https://github.com/QupZilla/qupzilla
No, no borrowing from anywhere. At least just not yet :-)
Will make my own bookmark stuff from ground zero like the whole project itself.
But I will check those two to get ideas
Last edit: Stefan Fröberg 2014-08-02
Yes, at least look over their shoulder and learn from the mistakes/hiccups they have encountered:
https://sourceforge.net/p/dooble/code/HEAD/tree/trunk/browser/Documentation/RELEASE-NOTES
https://sourceforge.net/p/dooble/bugs/search/?q=status%3Awont-fix+or+status%3Aclosed-fixed+or+status%3Aclosed
food for thought (desirable bookmark features):
-- XBEL support
-- searchable, freeform "description" or "notes" field (not limited to 255 chars)
-- "manage bookmarks" GUI which displays description as MULTILINE editable field
Needs to be said (asked):
You're hosting the project on SourceForge.
Everyone wandering through here (including me) expects that this is an OPEN SOURCE project.
I just now clicked the 3 (redundant?) "Code" button links display here...
Summary
Files
Reviews
Support
Wiki
Code
Tickets
Discussion
Blog
Code
Code
...and discovered that, in fact, no source code is available at the linked "git" URLs.
No problem, except you're soliciting donations to the project, and I would be highly motivated to donate, but only if the source is available. Bear in mind that previously, when I got excited about a project and, without even hammering the developer with feature requests, contributed a chunk of money ( https://sourceforge.net/projects/leopardflower ) ...oops, his hard drive crashed and the cat ate his homework and, yeah.
That experience weighs heavily on my mind, and considering that you've already blogged about experiencing hardware failure since the outset of your project... I gotta tell you that I'm unlikely to financially support another one-man-band with grandiose goals, closed-source project. From the point of view of a prospective donor, it seems reasonable to expect that either you'll get burned out working too hard on the project, or the cat will eat your homework, or whatever.
Your "no borrowing" comment above, that adds additional worry.
Too proud?
Wants to figure it out for himself (across the next month o' sundays) as an academic exercise?
Intends to eventually sell this as a commercial software product?
In your blog posts you've already professed that you're not even committed to sticking with QTWebkit. Hey, I'm not criticizing your rationale, I understood your point about the prospect of its future developement. My point, here, is that although you're "having fun and gaining experience"... I'm likely wasting time bugtesting an app built on a foundation of sand.
A friendly (yet pointed) piece of unsolicited advice:
Don't take the path of spinning a tale "will release the source code eventually"
http://forum.epicbrowser.com/viewtopic.php?id=394
http://forum.epicbrowser.com/viewtopic.php?id=636
http://forum.epicbrowser.com/viewtopic.php?id=357
Also, dear one-man-band, Sir...
you've mentioned "not NOT not supporting plugins/addons".
Visit http://forum.epicbrowser.com/viewforum.php?id=6
and note which discussion topic has drawn 5,600+ views and has, by far, the greatest number of replies.
Even with a fulltime multi-person staff, building upon a relatively fully-featured chromium codebase, they can't accommodate all the requested features in the core app, and are bleeding usershare (have bled, most users have abandoned ship) due to inability to customize via addons.
Please don't rush to reply to this. Take your time, reconsider what direction you wish the project to go.
My project. My rules.
If you want to buy the source you are always wellcome.
Update:
And if you do want to buy it there are two conditions:
One: It be dual licensed BSD/GPL
Two: My name is somewhere in the credits as the orignal contributor to your fork.
Update 2:
However, I will be releasing proxy checker code to github during next week. That damn thing still crashes time to time and it's time to ask coding community help.
Last edit: Stefan Fröberg 2014-08-03
I still have great hope for your project. Just understand that it probably won't seem reasonable to offer financial support to the closed-source project until CD at least reaches feature parity with Qupzilla and/or
TorbrowserDooble.Last edit: sandax 2014-08-04
Pity. I was already hoping that you would buy CD source code.
I would really need a new laptop :-)
Just joking...
Frankly, I don't know what to do when CD reaches more and more closer to being mature.
Haven't even thinked about it much.
Maybe some day I open source it for free. Maybe.