Are you also using Cosmo for your contract development? Or have you moved on to a different tool? Which one?
peter used the cosmo editor with one release he made. but, with the contract editing and development, which is what most end users would use, already built into the MIST wallet, direction was pushed in that direction. with dApp deployment, if its written in serpent, ive been using pyepm. its taken a lot of futzing to build the file right for deployment, but now that ive gotten comfortable with it, i dont find i even look at other development platforms like truffle or whatnot. and since im really working on top of other peoples work, vetting the contracts and javascript whatsits and making sure they implement correctly on the SOIL network, most of the time, the deployment package for development is pretty standard. ive noticed a commonality to using grunt for front end work, which gives me conniptions, it never likes to remain installed globally on my server. dunno why. gremlins. its always gremlins.
Thanks.
Had hoped to have my DApp ready by now. Instead I am on my 3rd day now, studying solidity examples, and trying to get a better contract-IDE working. Started with Cosmo because of your recommendation here (if obsolete then edit that old post! Cost me a long time.); but Cosmo is unready, has bugs, and questions asked as github issues just don't get answered. And 'Mix' is very hard to install on Debian.
> already built into the MIST wallet
Is that SOILsafe ?
I have just tried it out.
This won't work: https://github.com/Arachnid/solidity-stringutils#basic-usage
import "github.com/Arachnid/solidity-stringutils/strings.sol";
contract MyContract { }
Error: :1:1: Error: Source not found: File not supplied initially.
import "github.com/Arachnid/solidity-stringutils/strings.sol";
Perhaps import from local file works? Where do I have to put 'strings.sol' in soilsafe?
Or can't SOILsafe/mist work with libraries?