These are chat archives for ethereum/homestead-guide
_`This is a title of a section`creates a clickable crossreference. It is called implicit reference cos it is implicitly defined by all sectioning markup and the resulting crossref will just have the entire title
.. mylabel::in front of the section referenced: see http://www.sphinx-doc.org/en/stable/markup/inline.html and write
:ref:`about clients <mylabel>`
@zelig De-webification is ongoing. My focus right now is on fixing naming in docs (ethereum/webthree-umbrella#250), and I should have purged the vast majority of those by Homestead. We deferred actually reorganizing the repositories until after Homestead, because of the broad impact on the build files, automation, etc. That is captured as ethereum/webthree-umbrella#251, in the milestone targeting March 24th. I can't wait.
You will have seen this target graph, right?
Though we'll actually be a better even than than, severing the dependency from Solidity to cpp-ethereum as well, so "eth" and "Solidity" will become peers, with Mix and AlethZero/AlethOne depending on both.
So for now, I guess your package should have eth, AlethOne, AlethZero and Mix.
We're working to kill AlethOne and AlethZero, probably by making their functionality into Mist plugins/DAPPs. Also, for Mix, we're exploring using Electron, to see if we can make that into plugins to Mist, Visual Studio Code, Atom, etc.
Good to see you, @hughlang!
Maybe you could just do a high-level triage, and see whether the sections make sense. Also looking again at the Introduction seems sensible. That is the single document which is the most important of all, because it is the one which people are likely to read first, and sets the tone for everything else.
Especially with all the froth around $1B and Bitcoin-rivalry there is right now, I think it really important that newcomers to Ethereum reading these documentation come away with the impression of "Possibility-enabling world computer", not "Bitcoin, but better".
Well - maybe it is a 5 min conversation and we go with what we have? We've got to have the conversation, though.
Moved "The Homestead Documentation Initiative" to the end of the TOC
for Mix, we're exploring using Electron, to see if we can make that into plugins to Mist, Visual Studio aCode, Atom, etc.
RE: Looking to switch to Electron. Yes, it would be very cool if we can get there. Essentially we would drop all GUI elements in the C++ codebase, because cross-platform C++ GUIs are a total pain in the ass.
We've basically got "eth", which will end up as a headless EVM. jsconsole to be removed imminently, because "geth attach" works, and Chriseth also made a tiny node.js console which does just the same, but without having to build the whole of V8 (https://github.com/ethereum/ethereum-console).
And we have Solidity, which will stay as is, but be entirely decoupled from eth.
And that leaves us with "productivity stuff" in Mix and Aleth which should really just be optional plugins to Mist. I really hope we can make it happen. It would be such a better and simpler setup.
rm -rf build/htmlbefore make html
Hey, @klmoney, @LiteBit, @azulmarino and @madhancr!
Last chance for any of who want to "unmask" before Homestead, so that your contributions to the documentation are associated with your true names.
Understand completely if you are intentionally pseudonymous. Just want to give you the opportunity if you want it.