Advertisement
I've been using sdidesk for several weeks now and i must say it really fits me! I'm disorganized by nature and have tried evrything from paper diaries, pda's, pims, plain paper notebooks, but i never had the discipline to stick with them for more then a week.
Sdidesk has a very short learningcurve, you only have to take some time to watch the screencasts and it gives me all the freedom to structure all the information i want. It's still a little buggy here and there which teaches you to hit ctrl-s reguarly, this has not stopped me from using it. The power is in its simplicity i think, i also took a look at wikidpad but that userinterface is much more intimidating for the unstructured mind. The net(work)pages are great for making db-model diagrams.
Question: are you still working on newer versions of sdidesk, or are you bussy doing other projects?
Sdidesk has a very short learningcurve, you only have to take some time to watch the screencasts and it gives me all the freedom to structure all the information i want. It's still a little buggy here and there which teaches you to hit ctrl-s reguarly, this has not stopped me from using it. The power is in its simplicity i think, i also took a look at wikidpad but that userinterface is much more intimidating for the unstructured mind. The net(work)pages are great for making db-model diagrams.
Question: are you still working on newer versions of sdidesk, or are you bussy doing other projects?
Advertisement
Advertisement
-
Re: i like it!
Thu, April 27, 2006 - 12:39 PMThanks Pieter.
People who like SdiDesk are what keeps me going
... plus I need it to be better for myself :-)
And, yep, I'm too lazy to want anything more complex than the SdiDesk interface. That's an important part of what it's about.
So what's going on with SdiDesk? Essentially, I've bitten the bullet and decided to rewrite it in the Python programming language.
I know it's a bad idea to rewrite code from scratch, but SdiDesk is currently written in VisualBasic 6 which has been abandoned by Microsoft. And to allow me to keep the program up-to-date (in terms of having libraries of components available etc) and to encourage other programmers to get involved, I need it to be built in a living language.
The conversion is actually going to take place in several phases. Before trying a full blown SdiDesk I'm producing another tool, which is essentially a kind of programmer's editor based on the same navigation and page-store as SdiDesk. It has the same navbar, forward, backward controls, full text search, page histories etc. And it stores pages the same way on the file-system. So you can actually read and edit SdiDesk pages with it. However it doesn't do the fancy HTML rendering of pages, or have the network diagrams or other special data-types. It doesn't (and probably won't, as a default) turn WikiWords into links.
What it does do, is run Python scripts which are written on pages.
The idea is that this is going to be my actual development editor for working on the code-base. But it's not an SdiDesk replacement. Nevertheless, many of it's components will also serve in the full SdiDesk when it does arrive.
This editor is going to be out in a few more weeks (depending on how much time I have), and then the new SdiDesk itself will (hopefully) come a couple of months later. (But note, these are wild guesses, and SdiDesk will be ready when it's ready. :-)
What I can promise is that SdiDesk certainly hasn't been abandoned. And there will be newer versions coming with more cool stuff.
phil
BTW : if you don't know what this is all about, current SdiDesk downloads and screencasts are here : www.nooranch.com/sdidesk/w...i/HomePage
