![]() ![]() Users can pick and choose what fields they want, how they're displayed, and can more or less build the app they want, for exactly their own idiosyncratic needs.Īn application designed for team collaboration that has the same UI as Toodledo Solo, but some of the ability to pick and choose fields and reorder their display has been curtailed. Custom searches remain an integral part of the app. ![]() Also, the application has been given a freshened-up UI that makes more use of color. Long-standing user requests, such as the ability to change completion dates, are addressed. After reading Jim_Lewis's comment regarding Slack, an app I use and love, and thinking about your comments, I'm beginning to think that perhaps two versions wouldn't be a bad idea, something like the following.Īn application like the Toodledo we all know and love, that maintains the extensive customizability that those of us with OCD can't get enough of. Indeed, I probably overstated the inadvisability of creating two versions of the product. Personally, my fingers remain crossed but as I said in an earlier post, I think the worst case is that we still have Excel and of course, we can always build anew.hopefully it won't come down to that. Fortunately, I think most of us do agree that we like\love Toodledo and hope it stays in the game. In any event, you and others have your view, I and others have mine.there is some delta which is completely fine. I think it's good to counter that when possible. without really having good data to rely upon. Īnywho.If you've been in tech for any appreciable amount of time, I suspect you'll agree with me when I say folks often like to summarily tear down suggestions\ideas\etc. the economics before the ownership change, what the new owners' goals are, what their economics and\or funding looks like, etc.) to make any assertions - if someone, including you, does happen to have that intel, then please feel free to share. Aside from Jake, Sam, Anant, & Ramon, I don't think anyone on these threads has requisite intel (i.e. What I did do, aside from speculate as to the new owners' motivations and goals, was to pushback against unsubstantiated statements that assert multiple versions is a bad idea. ![]() Regardless, I never said the new owners will do multiple versions nor even want to.nor that it even made good business sense vis-a-vis their goals\economics. See the LICENSE file for more info.Of the "problems" you mention I did touch on at a very high level in a very speculative fashion in an earlier post. ZACS was created by Main author and maintainer is Radek Pietruszewski. If you make an app using ZACS, please let us know! Author and license If you make a non-trivial contribution, email me, and I'll send you a nice ZACS sticker! Feel free to open an issue to get some guidance, and then please send a pull request addressing your issue! If there's a missing feature, a bug, poor documentation, or other improvement you'd like, don't ask what we can do to help you, ask what you can do to help the community. ZACS is an open-source project and it needs your help to thrive! If you're interested in this project - please contact us! Troubleshooting We're thinking of extending ZACS to defining styles, so that you can declare styles once in CSS and have them compile to both CSS and React Native StyleSheet in a "zero abstraction cost" fashion. Themselves are defined in a separate file. Unlike popular "CSS-in-JS" libraries, zacs only provides the "component styling" part, but styles styles added via props (third argument to zacs.xxx())įor example, width passed via zacs:inherit will override width added via props.conditional styles (second argument to zacs.xxx()).main style (first argument to zacs.xxx()).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |