*As long as I can view the documentation inside Pharo , thats perfectly fine for me. *
When I said I will extend the pharo help tool, I only meant it in a minimum kinda of way. Small convenience like basic navigation, shortcut bindings, possibly embedding in with system browser and debugger , index search , links (not www links, but links to the documentation) and images. These things don't exist now, and I dont see anyone working on such features, so I decided it was time for DIY. I prefer my documentation the Spartan way, simple and straight to the point. I think 99% of the issue here is finding people willing to document Pharo. I will most certainly do my part, but we need to motivate people to document at least libraries they make , in a single place. Whether that is the image , or the web, makes small diffirence. What matters is documentation itself. I don't have unrealistic expectations of pharo in general , I know we are small but active community , but still small. >From my side, I will document NBOpenGL with my GLTutorials , Nativeboost and Morphic. All that documentation will be of course gradual , slow and partial as to be expected from a person with very limited free time. I also don't care about wikis as much I care about internal documentation. Its a matter of convenience. But I have been using wikis and google searches when internal docs were simply not an option. So there is definitely room for everything here and I would never even dream of discouraging anyone from trying his own idea of how to do stuff. As matter of fact I love variation and original ideas :) Clément Bera-4 wrote > 2013/9/19 kilon < > thekilon@.co > > > >> This is why I insist on collecting things on one place, inside pharo. Web >> is >> all over the place, its great for finding information and for getting >> people >> work together , but not great learning things you are not familiar with. >> >> Why not having the documentation the same way as in Eclipse ? > > I mean the documentation would be on the web, available to anyone, > and each class / each package inside Pharo has a link towards its online > documentation. > This way the image size does not grow because of massive documentation. > It could be that showing the documentation of a class / package in Pharo > would directly > show inside Pharo a view of the web page corresponding to its actual > documentation. > > >> Actually GUI wise Mophics is one the best examples. Think about it, if >> you >> try to use any GUI in python for example, you are out of luck it has >> none. >> Even Tkinter which is the gui it comes with cpython is not coded in >> python >> , >> its coded in tk a scripiting language. Python GUI APIs widely used >> include >> PyGTK , PyQT , WxPython , all of them wrappers for C/C++ libraries. Other >> dynamic languages follow the same recipe. >> >> Of course these frameworks are much more documented than morphic , but >> unlike morphic they follow a monolithic widget architecture, and >> modifying >> the source in any way requires a mandatory knowledge of C/C++. And we >> should exclude their myriad of problem , GTKs notorious buginess on macos >> and windows , QT massive complexity for big GUIs up to the point it offer >> a >> dedicated programming language QML just for designing GUIs. >> >> On the other hand morphic is to a very large extend smalltalk. So you get >> a >> lot of power but also a lot more simplicity. Some areas however are in >> need >> for some more love and of course documentation is lacking and the speed >> of >> the gui is far from breathtaking. >> >> Morphic is a very big reason why I am with pharo, to be exact I find its >> ability to do visual coding and transform a smalltalk object to a visual >> element very appealing and I would love to work on that. Morphic halos is >> another very nice feature. The other reason is live coding of course. >> >> I will try to add to the documentation of morphic, I agree 100% we need >> more >> of it. >> >> FDominicus wrote >> > kilon < >> >> > thekilon@.co >> >> > > writes: >> > >> >> How does "extending Pharo help tool " sounds ? :) >> >> >> >> I am struggling to learn how morphic really works, especially >> >> TreeMorph. >> > Well that is a thing I tried more than once, but somehow I never >> > understood on how to make good use for Morphic for me. I checked a lot >> > of tutorial but then even simple things like menues seem to be doable >> > but not for me.. >> > >> > It is strange and not "nice". >> > >> > Regards >> > Friedrich >> >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/if-Pharo-is-key-for-you-tp4708875p4709143.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> -- View this message in context: http://forum.world.st/if-Pharo-is-key-for-you-tp4708875p4709184.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
