Topic: [ANN][SIM] Simcoin - A Simple Coin - page 58. (Read 157763 times)
yup, they look same.
Is it an ActiveX control by chance?
A lot of Windows computers out there have blockers from these.
A lot of Windows computers out there have blockers from these.
No, that would be the easy way out
It's just a plain COM object, we should be fine.
So for Windows client I've decided to go with IE. Yes, it's not particularly fast or smart, but it does the job and is included in every version of Windows, so the client will be small.
Currently, the exe file is just 86 Kb and the icon takes 32 of them
Currently, the exe file is just 86 Kb and the icon takes 32 of them
Is it an ActiveX control by chance?
A lot of Windows computers out there have blockers from these.
Here is something that could ease you job maybe:
https://github.com/rogerwang/node-webkit
https://www.npmjs.org/package/nodewebkit
https://github.com/rogerwang/node-webkit
https://www.npmjs.org/package/nodewebkit
25 Mb? No, thank you.
Weekly progress report
This was a rather slow week. Most of it was consumed by client skeleton development. It might seem simple to integrate a browser into your app, but for C++ and IE it's not as easy as dropping a control on your form, I dare you try it
Hello.
Here is something that could ease you job maybe:
https://github.com/rogerwang/node-webkit
https://www.npmjs.org/package/nodewebkit
I will delete any posts with excessive overquoting.
It's a disease that doesn't get enough attention nowadays.
Respect the time of your readers.
It's a disease that doesn't get enough attention nowadays.
Respect the time of your readers.
Distribution update
Weekly progress report
This was a rather slow week. Most of it was consumed by client skeleton development. It might seem simple to integrate a browser into your app, but for C++ and IE it's not as easy as dropping a control on your form, I dare you try it
Anyway, you saw the test version of the client with basic networking.
What else? Wrote a unit test for Salsa20. Had to revisit several topics and modify things / update documentation. That's how iterative design process works, you go in circles. The Vault file format, for example, is now on its 3rd draft, and each one was a complete rewrite. Updated and simplified packet encryption.
So, that's it, two big chunks of work: client skeleton and design/documentation updates.
See you in a week!
Weekly progress report
This was a rather slow week. Most of it was consumed by client skeleton development. It might seem simple to integrate a browser into your app, but for C++ and IE it's not as easy as dropping a control on your form, I dare you try it
Anyway, you saw the test version of the client with basic networking.
What else? Wrote a unit test for Salsa20. Had to revisit several topics and modify things / update documentation. That's how iterative design process works, you go in circles. The Vault file format, for example, is now on its 3rd draft, and each one was a complete rewrite. Updated and simplified packet encryption.
So, that's it, two big chunks of work: client skeleton and design/documentation updates.
See you in a week!
Deposits:
I was too lazy to export it with dates, so here are a few key points:
64 - April 14
91 - April 15
127 - April 18
163 - April 20
181 - April 21
208 - April 25
226 - April 26
Fat yellow line is a 10-deposit moving average.
I was too lazy to export it with dates, so here are a few key points:
64 - April 14
91 - April 15
127 - April 18
163 - April 20
181 - April 21
208 - April 25
226 - April 26
Fat yellow line is a 10-deposit moving average.
I want to post this as a reminder to myself and to help explain why things are moving slow.
[delusion of grandeur mode on]
When you have 130+ people invested in your project, it's very tempting to work on exciting buzz-features that will give appearance of significant progress, rather than on the tedious tasks that have to be done. Yet, it's the tedious and unexciting tasks that distinguish serious software projects from hacks of "script-kiddies". Things need to be thought through. Alternatives must be weighed. Optimal solutions satisfying multiple criteria must be found. Things need to be documented. There need to be unit tests. There need to be tools. There need to be integrity checks. All the invisible, time-consuming and boring stuff.
It's tempting, for example, that since I now have a skeleton for the client, to start drawing pretty screens, even if nothing is working yet and the underlying mechanics doesn't exist. "Hey, but it will look like we're almost done! People will be glad to see the progress!" Shut up, brain. That's why most open-source projects suck.
So this is a reminder, that every morning I need to make a conscious effort when organizing the to-do list for the day, to work on what has to be done, instead of what would make it look like we're moving fast. Let other coins work on cool stuff, that's how we got where we are.
[delusion of grandeur mode off]
P.S. Yes, I work on weekends.
[delusion of grandeur mode on]
When you have 130+ people invested in your project, it's very tempting to work on exciting buzz-features that will give appearance of significant progress, rather than on the tedious tasks that have to be done. Yet, it's the tedious and unexciting tasks that distinguish serious software projects from hacks of "script-kiddies". Things need to be thought through. Alternatives must be weighed. Optimal solutions satisfying multiple criteria must be found. Things need to be documented. There need to be unit tests. There need to be tools. There need to be integrity checks. All the invisible, time-consuming and boring stuff.
It's tempting, for example, that since I now have a skeleton for the client, to start drawing pretty screens, even if nothing is working yet and the underlying mechanics doesn't exist. "Hey, but it will look like we're almost done! People will be glad to see the progress!" Shut up, brain. That's why most open-source projects suck.
So this is a reminder, that every morning I need to make a conscious effort when organizing the to-do list for the day, to work on what has to be done, instead of what would make it look like we're moving fast. Let other coins work on cool stuff, that's how we got where we are.
[delusion of grandeur mode off]
P.S. Yes, I work on weekends.
Thanks for the update.
P.S. Keep up the good work and don't forget to take a break once in a while, it helps clear up the mind and see things in a new light.
Who said that the rest of us had a life?!?!? 
Haha, I knew some of you are the same workaholics as me
Just wanted to reassure investors that I'm not fooling around playing golf on weekends (yet).
I want to post this as a reminder to myself and to help explain why things are moving slow.
[delusion of grandeur mode on]
When you have 130+ people invested in your project, it's very tempting to work on exciting buzz-features that will give appearance of significant progress, rather than on the tedious tasks that have to be done. Yet, it's the tedious and unexciting tasks that distinguish serious software projects from hacks of "script-kiddies". Things need to be thought through. Alternatives must be weighed. Optimal solutions satisfying multiple criteria must be found. Things need to be documented. There need to be unit tests. There need to be tools. There need to be integrity checks. All the invisible, time-consuming and boring stuff.
It's tempting, for example, that since I now have a skeleton for the client, to start drawing pretty screens, even if nothing is working yet and the underlying mechanics doesn't exist. "Hey, but it will look like we're almost done! People will be glad to see the progress!" Shut up, brain. That's why most open-source projects suck.
So this is a reminder, that every morning I need to make a conscious effort when organizing the to-do list for the day, to work on what has to be done, instead of what would make it look like we're moving fast. Let other coins work on cool stuff, that's how we got where we are.
[delusion of grandeur mode off]
P.S. Yes, I work on weekends.
[delusion of grandeur mode on]
When you have 130+ people invested in your project, it's very tempting to work on exciting buzz-features that will give appearance of significant progress, rather than on the tedious tasks that have to be done. Yet, it's the tedious and unexciting tasks that distinguish serious software projects from hacks of "script-kiddies". Things need to be thought through. Alternatives must be weighed. Optimal solutions satisfying multiple criteria must be found. Things need to be documented. There need to be unit tests. There need to be tools. There need to be integrity checks. All the invisible, time-consuming and boring stuff.
It's tempting, for example, that since I now have a skeleton for the client, to start drawing pretty screens, even if nothing is working yet and the underlying mechanics doesn't exist. "Hey, but it will look like we're almost done! People will be glad to see the progress!" Shut up, brain. That's why most open-source projects suck.
So this is a reminder, that every morning I need to make a conscious effort when organizing the to-do list for the day, to work on what has to be done, instead of what would make it look like we're moving fast. Let other coins work on cool stuff, that's how we got where we are.
[delusion of grandeur mode off]
P.S. Yes, I work on weekends.
[quote ]
(I already invested because NxtChg and his vision)
[/quote]
Exactly...If he can achieve his goal, that builds a solid foundation for future crypto currencies to expand upon...that would be huge! I appreciate the small POC's that are provided to the community to help us both see progress and glean some insight as to how the future Simcoin may work.
(I already invested because NxtChg and his vision)
[/quote]
Exactly...If he can achieve his goal, that builds a solid foundation for future crypto currencies to expand upon...that would be huge! I appreciate the small POC's that are provided to the community to help us both see progress and glean some insight as to how the future Simcoin may work.
So, for the client I've decided to use an embedded browser instead of native interface.
This approach has many advantages:
I considered embedding Google Chrome or Firefox, but they are huge - tens of megabytes!
So for Windows client I've decided to go with IE. Yes, it's not particularly fast or smart, but it does the job and is included in every version of Windows, so the client will be small.
Currently, the exe file is just 86 Kb and the icon takes 32 of them
So here's a test version:
https://simcoin.info/simcoin_v01.zip
please run it and tell me if everything is Ok.
The logo is a transparent PNG, it shouldn't have any white borders (unless you are still using IE6 ).
Click on buttons. The last one sends a packet to simcoin.info server and waits for reply. This is to test firewalls and other networking issues.
This approach has many advantages:
- easy to program
- dynamic interface, much more flexible than native
- easily skinnable and can be made to look pretty
- clear separation of UI code and core functions
- portable: html/js code is cross-platform
- looks the same on all platforms
- native hyperlinking, useful for the built-in "blockchain explorer"
- localization is much easier
I considered embedding Google Chrome or Firefox, but they are huge - tens of megabytes!
So for Windows client I've decided to go with IE. Yes, it's not particularly fast or smart, but it does the job and is included in every version of Windows, so the client will be small.
Currently, the exe file is just 86 Kb and the icon takes 32 of them
So here's a test version:
https://simcoin.info/simcoin_v01.zip
please run it and tell me if everything is Ok.
The logo is a transparent PNG, it shouldn't have any white borders (unless you are still using IE6
).Click on buttons. The last one sends a packet to simcoin.info server and waits for reply. This is to test firewalls and other networking issues.
Perhaps now is the time to reconsider the IPO, with this and other news in the near future, people investing today can risk their money with significantly more confidence than those who invested a week ago. I'm not suggesting to close the IPO, but the reward should be looked at.
With due respect to NxtChg and his work, but this is coded in 20 minutes. Do you really think that this will convince anyone to invest?
(I already invested because NxtChg and his vision)
Aha-ha, fantastic!
They stole and uglified it
No, of course that's not mine. This is most probably a scam.
On the other hand, I think we will see more and more cryptos using my idea of doing IPO this way, so some of them might be legit, but probably not the ones who are so quick and sloppy.
Thanks, that was what I thought..
I should also mention, do not send NXT to that address from an account that has a considerable sum because NXT and Nxn pass phrases are the same. If anything, make new NXT account, send funds to it, then send funds to the IPO...
Aha-ha, fantastic!
They stole and uglified it
No, of course that's not mine. This is most probably a scam.
On the other hand, I think we will see more and more cryptos using my idea of doing IPO this way, so some of them might be legit, but probably not the ones who are so quick and sloppy.
Thanks, that was what I thought..
Aha-ha, fantastic!
They stole and uglified it
No, of course that's not mine. This is most probably a scam.
On the other hand, I think we will see more and more cryptos using my idea of doing IPO this way, so some of them might be legit, but probably not the ones who are so quick and sloppy.
Did you make this? http://nxncoin.com/
or did someone steal your designs?
or did someone steal your designs?
There's nothing in "It will just end one day without any warning." and "There won't be an announced deadline... but it will definitely not be closed until April 20." (posted april 10) that implies the IPO would remain open until...... well, when?........... perhaps after the coin is on exchanges?
Are you even reading what you are typing?
How is "No end date" doesn't mean "IPO will remain open"
This is exactly what it means! That the IPO will remain open until who knows when.
Yes, maybe until the coin is on exchanges, maybe until the Judgement Day. No promises were given to you about the end date.
You know what I am saying is not outrageous and I am being polite, so your "defence by semantics" is not encouraging.
Enough. This argument is now closed.
It's a question of getting less, people have calculated their investment without realising that the IPO is, essentially, open-ended. Ok, fair enough.
How is it my or other investors fault? It was said so right from the start.
There's nothing in "It will just end one day without any warning." and "There won't be an announced deadline... but it will definitely not be closed until April 20." (posted april 10) that implies the IPO would remain open until...... well, when?........... perhaps after the coin is on exchanges?
You know what I am saying is not outrageous and I am being polite, so your "defence by semantics" is not encouraging.
And.... what am I accusing investors of?
By the way, if somebody wants to quit and sell their share to somebody else - find a buyer, announce transaction publicly and I will move your share to another account.
Jump to: