 Show Posts
|
|
Pages: [1]
|
Version 0.3.6 of Nxs has been released. Some of the changes: - The ability to download NRS and check it against the SHA-256 hash that existed in html/tools/update.html has been integrated in the Nxs UI. You can now click the Nxt logo and see the About Nxs dialog which shows the version numbers for both NRS and Nxs. If either one is outdated, an "Update" button appears. For NRS, you may drag your zip file into a drop zone to check the hash.
- Two shell scripts were added, install.sh and update.sh, for installing and updating Nxs and NRS on Linux. This feature should be very much considered "alpha" at this point and may not work exactly as expected. I have tested it enough that I am satisfied to a level that permits me to publicize it, but cannot guarantee there won't be bugs. Please check out the verify-hash.sh script that both install.sh and update.sh use to ensure I have properly implemented the SHA-256 hash verification. I am no command line expert, so it would be nice to have some confirmation from someone a little more experienced in this area.
- The files that existed from NRS' html/tools directory, admin.html and message.html, have been removed from Nxs root directory. The functionality of both of these files will soon be integrated into Nxs' UI. In the meantime, those files are still available at html/tools of course.
A full change log is available here. I'm always happy to hear comments, questions, concerns, and suggestions from the community. Feel free to give me your feedback in this thread, through a private message, or even open an issue on the GitHub repo. I should also add that, as a non-believer in the concept of intellectual property, I welcome anyone to use any of the code in your own projects with or without credit. My goal is not one of recognition, but rather to improve the software we have available to us in the Nxt community. For example, Wesley's client may benefit from using the Language class at assets/js/language.js to integrate multiple languages.
|
|
|
|
Version 0.3.4 of Nxs is how up on GitHubAll API / UI server requests are now done through POST (with a config option for GET for backwards compatibility with Nxt versions prior to 0.8 ). Nxs now has a sidebar for navigation (similar to the nxtra.org NXT Wallet's) because the advanced Nxt features such as Messages, Aliases, Asset Exchange, etc. won't fit into the navigation bar at the top. Aliases have now been implemented and can be registered and updated on the Aliases page. If you choose "Nxt Account" as your type, the Nxt account number URI will automatically be wrapped with "acct:" and "@nxt" so the full URI is something like "acct:0000000000000000@nxt". This is an attempt to help push a standard for Nxt account number alias URIs in solidarity with wesley's NXT Wallet app. In the future, these account numbers will be able to be entered as the recipient in a transaction as well. Also, aliases now show up in their registering and updating transactions on the Transactions page. Along with the new side bar, the pages interface has been completely revamped to show only one page at a time instead of the old navigation system where you could toggle widgets on and off and display multiple widgets at a time. The initial version with toggling widgets made too much of an attempt to emulate Nxt's default NRS GUI instead of rethinking the interface altogether. Rate of requests for new data is now adjustable in "assets/js/config.js" allowing Nxs to potentially run more smoothly on older computers. Repo available here along with installation instructions and the full change log can be found here. New screenshots can be found here.
|
|
|
|
Why dont we update the NXT network?
I am only waiting for client developers to say they fully support the 0.8 branch, and to have the user friendly installer packages ready, before announcing it stable. I don't think it is unstable at all. We have to move to the 0.8 branch before I can start working on incompatible features such as adding transaction type for fractional Nxt amounts. I have tested Nxs with 0.8.0e yesterday and did not run into any problems but have not yet pushed a new version to its repo. I will be testing more today with 0.8.1e and switching GET to POST before pushing a new version, but it should be up tonight or tomorrow. |
|
|
|
I posted this on forums.nxtcrypto.org but was told to mention it here: I understand that Aliases belong to the registering account forever (correct me if I'm wrong), but wouldn't it make sense to require a renewal, perhaps annually?
The reason I think this is necessary is because otherwise really good, useful aliases might get permanently lost as someone loses access to their account, dies, or simply stops using their account. In that case, some highly desired aliases will permanently be removed from the pool of usable aliases. It seems to me that a simple transaction fee once per year would be enough to prevent this from ever becoming a problem. Clients could certainly remind users to renew their aliases and even bring up the transaction dialog to renew. Also, aren't core Nxt developers using forums.nxtcrypto.org or nextcoin.org at this point? It seems to me that entire forums dedicated to Nxt should make it much easier to organize conversations than a single thread on bitcointalk.org. |
|
|
|
(1) Yes, it's all UI. But we risk alienating users by making Bitcoin even more complicated and confusing than it already is. If everyone (and every wallet app) uses different units, and they can't convert in their head easily, and it's even the slightest bit feasible to enter incorrect values... it's becomes a serious usability problem.
You are right, yet this problem too can be taken care of if done in the right way. I suggest it defaults to BTC on first startup of Armory. Then, on the Settings menu (which should ideally be separated into tabs), there is a "Display" tab with a section for Display Scale and a small table with radio buttons for each row similar to: | Abbreviation | Name | Scale | | • | BTC | Bitcoin | 1.00000000 BTC | | ○ | mBTC | Millibitcoin | 0.00100000 BTC | | ○ | uBTC | Microbitcoin | 0.00000100 BTC |
Why should it be done like that? Because it explains to a new user what the different scales are in enough detail to fully understand the display abbreviation (BTC / mBTC / uBTC), pronunciation of the unit, and the relation to the 1.0 BTC scale and yet also concise enough not to take up a ton of space in the Settings window. Perhaps there are better ideas? Maybe it could even ask you to choose a display scale with the same table + radio buttons setup when you start up Armory for the first time? |
|
|
|
|
Thank you for the compliment. There are many more features on the way. I will be definitely looking into doing QR codes with MultiBit as suggested by shads' post. I will also be adding more customization to items (like optional quantity limits to prevent people from selling more of something than they have).
|
|
|
|
|
This seems very interesting. I'll be paying attention to the development of this.
|
|
|
|
|
shads,
That is a good idea, I was unaware of what MultiBit could do. I'll look into implementing it eventually after I work out some of the higher priority issues. The easier for the customer, the better.
Thank you for your suggestion.
|
|
|
|
|
Could you provide me the URL (private message is fine if you'd prefer not to make the page you're testing on public) where you are trying to add the button? I will do some troubleshooting today to figure out why it isn't working correctly.
|
|
|
|
You can now set an item's price in the following currencies: I will now be implementing quantity limits. If you set your quantity to, say, 30, and you get 30 orders, the item will be temporarily locked and you will receive an email letting you know that the order quantity limit has been reached for the item in question. If anyone has any questions in the system, I'd be happy to answer them. Requests would be nice too. |
|
|
|
|
I've had a long break from development on Bitcoin Evolution but I'm getting to work again. I have now implemented the ability to set prices in euro and will have 3 more currencies within the week. Also, recurring subscriptions have now been fully implemented.
|
|
|
|
Prices can now be set in BTC or USD (which is converted to BTC on the order form). Here is an example payment button/form with currency conversion: Example Payment Button |
|
|
|
Bitcoin Evolution is in the final phase of development before launch. Here's a brief summary of what http://bitcoinevolution.com is all about: ------------------------------------------------------------ Bitcoin Evolution makes tracking payments for distribution of products or services much easier using a database of Bitcoin addresses that you assign to your user account which will serve as unique identifiers for tracking payments for specific products/services. ------------------------------------------------------------ You can then embed a payment button (20 different designs – 10 light, 10 dark, or alternately use your own) using a simple piece of code that calls the javascript and opens the order form. When the user completes the form, they get an email and you get an email confirming the order. Their email is a simple reminder that they will have to pay with their Bitcoin client to complete the transaction. You, as a store, have access to your orders table and can mark orders as paid and then “actioned” which, based on the type of item ordered (product, service, subscription) will show up as “product shipped”, “service rendered”, and “subscription granted”. One feature that will be added in a couple of weeks is the ability to export your entire orders table to a CSV spreadsheet file so that you may manage your orders off-site. If you sign up and log in, you will notice that you can't delete items or orders. This is simply because I was so busy getting everything else running to a good enough state for general use. I will be making many major improvements over the next 4 to 5 weeks and will continue development after that. I assure you that delete will be implemented shortly. Try adding an item and using the embed code that it provides on your website. You may test the form this way so that you can see how it all works. You can also see of the buttons in question #3 on the FAQ page ( http://bitcoinevolution.com/faq). If you choose item type “Subscription”, you will be able to select a recurring rate of a week, a month, a year, etc. I am just correcting a few minor things and the recurring subscriptions will be active as well. Any comments, questions, or critiques are welcome. |
|
|
|
I'm in the process of building a service for sales tracking where you enter in multiple addresses and then when someone fills out one of your order forms it will let you know to "watch for payment at _____" whatever the address is. Many of the features required to launch the site are already implemented and there's just a few more things that I need to do. Feel free to sign up for an account and play around or use the combination of TestUser2011 / password7: http://bitcoinevolution.com. |
|
|
|
Hi, I've been working on Bitcoin Evolution ( http://bitcoinevolution.com/ http://bitcoinevolution.net), a free sales tracking service, for the last 3 or 4 weeks and am almost ready to launch it. Feel free to get an account and play around. You will notice that there are a few features missing at the moment. When Bitcoin Evolution is completed you will be able to: - add/edit/delete items in 3 different types: products, services, and subscriptions
- subscriptions can be set up to be recurring
- set prices in BTC or USD (which will be translated to BTC with the current exchange rate)
- mark orders as paid or unpaid, and then actioned or unactioned (product shipped, service rendered, or subscription granted)
- easily embed a "Buy", "Buy Now", "Pay", or "Subscribe" button in your website provided by Bitcoin Evolution or use your own image to link the order form
- use an order form that opens in a nice modal window and can be customized
- embed the buy button with a simple piece of code
Many of the features are already in place and many of the others will be implemented shortly. If you're too lazy to sign up for an account (don't be; it's quick), you can always use one of my testing user accounts: Username: "TestUser2011" Password: "password7" The embed code is this simple: <script type="text/javascript" src="http://bitcoinevolution.com/api.js"></script>
<a href="javascript:void(0);" class="btnTransaction" onclick="btcTransaction(4, 4);">
<img src="http://bitcoinevolution.com/includes/images/btnBuyNow.png" alt="Buy Now" title="Buy Now" />
</a> You can see the buttons and order forms in action in question number 3 of the FAQ page ( http://bitcoinevolution.com/faq). Please let me know what you think. I will start a thread in the "Project Development" section soon so I can issue periodic updates as I move towards launch (I should be done all the basic features in early July, possibly sooner and will then continue to develop after that). Edit: I should also mention that I'm going to make it easy for you to export your order records to Excel (a CSV file) as well which should make it easy for people that want to use the Bitcoin Evolution service but retain their data on a spreadsheet on their computer or migrate order data to their own database. |
|
|
|
If governments and bankers defeat bitcoin, they will not defeat the many similar systems that are created to replace it, each designed to resist such attacks in a new way. Bitcoin was designed to resist attacks that defeated other internet money systems.
We will win because most people agree that communication is everyone's right, and Bitcoin is just a decentralized calculator, not even complex enough to have a multiply and divide, just plus and minus.
Yes, I think you made a good point. It's not Bitcoin that's the threat so much as it's the cryptocurrency concept in general. |
|
|
|
there's a big difference between feeding some API data and building an engine to crawl sites.
Couldn't participating sites keep a bitcoin.xml file in the root directory of their websites or something which would contain a list of all products and current prices? Websites can dynamically update xml files with cron jobs and the directory service/search engine only has to look for this file on all websites in the list. |
|
|
|
|
Could you add some Canadian cities?
|
|
|
|
|
