- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Update] Zinc-SSO now supports Dropbox !

by Sabine KnÃ¶fel

Hi Sven, after loading: Gofer it url: 'http://mc.stfx.eu/ZincHTTPComponents'; package: 'ConfigurationOfZincHTTPComponents'; load. ConfigurationOfZincHTTPComponents project latestVersion load: 'SSO'. The ZnOAuth1ConsumerData does not have a method called >>newForDropbox (but >>newForGoogle and >>newForTwitter). Also, ZnSSOServerDelegate does not have a method >>dropboxData: (but facebook, twittter and google) Did I miss something? Greetings Sabine On Sun, Jan 27, 2013 at 8:47 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 27 Jan 2013, at 13:32, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > If anyone is interested, I can write another email explaining how you > can run this demo for yourself on your own account. > > How to run the Dropbox code yourself: > > 1. Get yourself a free Dropbox account at http://www.dropbox.com > > 2. Install some client software on one or more of your computers (Mac, > Windows, Linux) or devices (iOS [iPhone, iPad, iPod], Android, BlackBerry, > Kindle Fire) and move some files around to get a feel for the service. > > 3. When you give other applications access to (part of) your Dropbox > files, you can check that at https://www.dropbox.com/account#applications > > 4. Define your own app that will try to access Dropbox files. Go to > https://www.dropbox.com/developers (Developer home) and start defining a > new app by clicking the 'Create an app' button at > https://www.dropbox.com/developers/apps - start with the access type 'App > folder'. > > 5. The two important elements you need are the 'App key' and 'App secret', > make sure to copy them correctly. > > 6. Get the very latest code in your image (we develop in Pharo 2.0, but > 1.4 or even 1.3 should work - SSL has to be fully operational). > > Gofer it > url: 'http://mc.stfx.eu/ZincHTTPComponents'; > package: 'ConfigurationOfZincHTTPComponents'; > load. > > ConfigurationOfZincHTTPComponents project latestVersion load: 'SSO'. > > 7. Start a Zn server with an appropriate delegate, configured for your app > > (ZnServer startDefaultOn: 8100) > logToTranscript; > debugMode: true; > delegate: (ZnSSOServerDelegate new > dropboxData: (ZnOAuth1ConsumerData newForDropbox > consumer: > 'vqz-app-key-zoca'; > > consumerSecret: '13u-app-secret-8l006'; > yourself); > yourself). > > (The above is a demo setup limited to Dropbox, the other demos are not > configured and won't work). > > 8. Go to http:://localhost:8100/sso-dropbox and click the link to log in - > you will be transferred to Dropbox to log in (if you aren't already) and > asked to authorise your demo app, after which Dropbox will redirect you > back to your app. > > 9. Once back in your app, sso-dropbox-callback (#ssoDropboxCallback:) will > access your account info and list the app root folder, which will then be > shown. > > 10. For the rest of the API, (currently not yet implemented), see > https://www.dropbox.com/developers/reference/api - you don't have to > worry about the whole authentication thanks to Zinc-SSO. > > We would love for others to try this (as well as the other Zinc-SSO > options, Google, Facebook, Twitter) out, in their own projects, and to > provide actual feedback and generally help improve the code and > documentation. > > As always, May the Source be with you! > > Sven > > PS: The demo app is not (yet) a production app: only you and up to 5 > explicitly listed users can use it. You have to apply for production status > later on. Also, the whole ZnSSOServerDelegate code is a demo, for an actual > project, it would be best to extract the necessary parts out of it, reusing > the underlying Zinc-SSO-OAuth1-Core framework. > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > >

Jan. 30, 2013

Re: [Pharo-project] I hate 'as yet unclassified'

by Esteban A. Maringolo

2013/1/30 Norbert Hartl <norbert(a)hartl.name>: > (SNIP) > I would make the none categorized term weaker by naming it "uncategorizied" so at least I have the change to deliberately not categorizing my methods without being annoyed by someones opinion about what is essential. I agree with this, I'd fine if the method browser doesn't have any category pane at all. Most of the times the selectors are self describing, and a short list of them. I only used the categories to search methods in classes like String, where you try to find some specific behavior (most of the time under the "printing" or "converting" category). Regards,

Jan. 30, 2013

Re: [Pharo-project] [squeak-dev] Re: I hate 'as yet unclassified'

by David Corking

Thanks for taking a look at Squeak as well, Stephan. I think that Hernan Wilkinson suggested a smalllint script might be run as part of a CI job to report on uncategorized methods in commits. Could such a thing go on the requested features list for the Squeak and Pharo Jenkins servers? No big deal, but I think categories help me to understand large classes, at least when categories are somewhat standardized across classes. (Stephan posted his code to pharo-dev : http://forum.world.st/I-hate-as-yet-unclassified-tp4666245p4666620.html ) Have fun! David

Jan. 30, 2013

Re: [Pharo-project] I hate 'as yet unclassified'

by Ben Coman

Hernan Wilkinson wrote: > I think that classification is a matter of time and maturity of what you > are doing. > When I'm programming, using TDD or in the debugger, I don't care about > categorization, I don't want to be stopped or slowed down by that. > But before I commit the code, I run SmallLint and solve all the > uncategorized methods. That is the time when I have the whole picture and > can do a better categorization. > Interesting. My own standard practice with Monticello is to always first click the <Changes> button to help me summarize what this commit is about. Sometimes I see a leftover 'self halt' or Transcript and jump back to clean that up before saving. If Monticello had a <SmallLint> button, then I think I would make great use of it to clean up just prior committing a package revision. cheers -ben

Jan. 30, 2013

[Pharo-project] I hate 'as yet unclassified'

by Torsten Bergmann

>in the 4.3 one-click too >... >#unclassified methods by author >... >stephaneducasse 145 Interesting ;) As I wrote in http://markmail.org/message/oo4gsiyasoinkmol: <ownquote> "Removing packages or classes that are not documented is too hard ... but we should use Lint rules to check the "completeness/basic quality" of package. Similar to checkstyle for Java in Eclipse - if there are problems in a package then you have a different icon for the package and you work until it's clean because it hurts your eyes (see [10] for a screenshot)" http://www.ibm.com/developerworks/java/library/j-ap01117/checkstyle-eclipse… </ownquote> So we should have a "BAD/UGLY" icon for packages/classes that do not satisfy basic rules like "no unclassified methods", etc. Bye T.

Jan. 30, 2013

Re: [Pharo-project] I hate 'as yet unclassified'

by Norbert Hartl

Am 29.01.2013 um 16:57 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hi guys > > I spend my time recategorizing methods. > > I would like the change the intention of 'as yet unclassified' because this is a PLAGUE. > It is like throwing papers on the floor. > So we should have a different name to indicate that it should be fixed. > > > Any ideas? > > 'you are a dirty programmer - change me' > To be honest I have problems understanding why method categorization is so important. Often I don't care a single bit about categories because I don't understand them. I often categorize just to make lint happy :) What is the use? Declaring usage patterns? Declaring visibility? Use as method extensions marker? anything you like just classify? I can understand that it can help making the access of certain methods of a class easier. But that is particular true for classes with a lot of methods. Most of the classes are rather small. In most of my own developments I would consider most huge classes a design problem in my code. So I would try to fix that. And finally it is not easy to learn about them because the browser is not helping. If you browse through the methods of a class the category pane doesn't get updated. So even if I want to learn by getting used to them it is hard. I would make the none categorized term weaker by naming it "uncategorizied" so at least I have the change to deliberately not categorizing my methods without being annoyed by someones opinion about what is essential. my 2 cents, Norbert

Jan. 30, 2013

Re: [Pharo-project] I hate 'as yet unclassified'

by Stephan Eggermont

Sven wrote: >Euh, I want to fix some of them ! Good, that was the idea :) I was inspired by Doru's humane assessment primer. >Could you express this query in executable code ? >I am guessing you did this with Moose ? >Can it be done in plain Smalltalk ? I opened a Moose to take a look at the Mondrian examples, then copied that. This is the version that runs in both Squeak and Pharo. Open a workspace, Print-it on Unclassified new byAuthor Unclassified new byPackage This package intentionally contains some unclassified methods :)

Jan. 30, 2013

Re: [Pharo-project] I hate 'as yet unclassified'

by Stephan Eggermont

As there was a discussion on the Pharo mailing list on the number of these methods, I thought to check in the 4.3 one-click too. Some synchronisation would be possible by adding a hash over the method source, compare one method in the other system to see if it was classified there. Stephan #unclassified methods by package Etoys-Experimental 126 Morphic-Widgets 112 MorphicExtras-GeeMail 94 Collections-Text 90 Monticello-Repositories 79 ToolsTests-Browser 76 Multilingual-Display 76 Monticello-UI 72 Nebraska-Morphic-Collaborative 62 Monticello-Versioning 61 Tests-Monticello 52 Multilingual-TextConversion 49 Monticello-Merging 46 MorphicExtras-Demo 46 Morphic-Windows 45 MorphicExtras-Books 39 Etoys-Outliner 35 Tools-Browser 33 Network-RemoteDirectory 33 Tests-Bugs 32 Compression-Streams 32 Monticello-Storing 31 Sound-Scores 28 Tests-Monticello-Mocks 28 MorphicExtras-Navigators 27 MorphicExtras-AdditionalSupport 25 Morphic-Explorer 24 Nebraska-Morphic-Remote 22 Monticello-Patching 22 Tests-Files 20 Monticello-Chunk Format 20 Morphic-Text Support 20 Nebraska-Morphic-Experimental 20 Exceptions-Kernel 16 MorphicExtras-Text Support 16 MorphicExtras-Support 15 Monticello-Modeling 15 Sound-Synthesis 14 Tools-Inspector 14 MorphicExtras-Palettes 11 MorphicExtras-SoundInterface 10 Collections-Streams 10 TraitsTests-Kernel 10 Tests-Utilities 9 System-Changes 9 ST80-Pluggable Views 9 MorphicExtras-AdditionalWidgets 8 Installer-Core 7 Compiler-Exceptions 7 Morphic-Menus-DockingBar 7 Nebraska-Network-ObjectSocket 7 Files-Kernel 7 Monticello-Loading 6 ST80-Views 6 MorphicExtras-Widgets 6 MorphicExtras-AdditionalMorphs 6 Tests-ObjectsAsMethods 6 Multilingual-Editor 5 SMBase-domain 5 MorphicTests-Widgets 5 Nebraska-Audio Chat 5 MorphicTests-Kernel 5 ToolBuilder-Kernel 5 ST80-Controllers 4 Etoys-Stacks 4 Morphic-Menus 4 ST80-Framework 4 MorphicExtras-SqueakPage 4 CollectionsTests-Weak 4 MorphicTests-Layouts 4 Morphic-Pluggable Widgets 4 SUnit-Tests 4 Tests-Hex 4 ToolBuilder-SUnit 3 Etoys-Scripting 3 Graphics-Fonts 3 Kernel-Methods 3 Multilingual-Scanning 3 Files-Directories 3 SUnit-Extensions 3 ToolBuilder-Morphic 3 SystemChangeNotification-Tests 3 Morphic-Basic 3 ST80-Support 2 Network-Kernel 2 Etoys-Scripting Tiles 2 Kernel-Classes 2 Graphics-Primitives 2 Collections-Arrayed 2 MorphicExtras-Postscript Canvases 2 Services-Base 2 Graphics-Display Objects 2 Balloon-Fills 2 NetworkTests-UUID 1 PackageInfo-Base 1 Tools-FileList 1 CollectionsTests-Text 1 NetworkTests-RFC822 1 Services-Base-GUI 1 Tests-System-Support 1 System-Support 1 ST80-Editors 1 Etoys-Tile Scriptors 1 System-FileRegistry 1 Etoys-Scripting Support 1 NetworkTests-Url 1 Morphic-Kernel 1 ToolsTests-Inspector 1 #unclassified methods by author RAA 438 stephaneducasse 145 ar 144 avi 99 yo 97 gvc 80 fbs 80 tk 80 di 76 nice 73 ab 73 sd 58 jm 47 dgd 44 sw 41 ul 35 nk 35 cmm 27 27 cwp 26 bf 26 md 19 kb 12 wiz 12 jrp 11 kph 7 dvf 6 Tsutomu 6 ajh 6 mjr 6 ls 6 rej 6 apb 5 dtl 5 acg 4 gk 4 sbw 4 abc 4 bp 4 nb 4 jmv 3 spfa 3 laza 3 rr 3 JPF 3 MarcusDenker 3 al 3 Igor.Stasenko 3 BG 2 tetha 2 pk 2 btc 2 jrd 2 eem 2 mha 2 tfel 2 mir 1 jcg 1 mist 1 LC 1 tlk 1 djp 1 sumim 1 DSM 1 TN 1 aoy 1 DF 1 alain.plantec 1 gm 1 th 1 bvs 1 sma 1 jf 1 sps 1 tonyg 1 hh 1 tak 1 '

Jan. 30, 2013

Re: [Pharo-project] I hate 'as yet unclassified'

by Sven Van Caekenberghe

Euh, I want to fix some of them ! Stephan, Could you express this query in executable code ? I am guessing you did this with Moose ? Can it be done in plain Smalltalk ? Sven On 30 Jan 2013, at 14:02, Stephan Eggermont <stephan(a)stack.nl> wrote: > In Pharo 20498, sorted by author in the method timestamp: > > gvc 1550 > AlainPlantec 320 > 216 > GaryChambers 215 > CamilloBruni 163 > IgorStasenko 159 > stephaneducasse 152 > avi 148 > Igor.Stasenko 128 > StephaneDucasse 85 > SeanDeNigris 81 > MarcusDenker 78 > ab 75 > GuillermoPolito 68 > tween 52 > BenjaminVanRyseghem 51 > ar 46 > di 40 > RAA 38 > alain.plantec 38 > EstebanLorenzano 35 > FernandoOlivero 33 > nice 31 > tk 29 > nk 28 > cwp 26 > dvf 22 > rr 20 > PavelKrivanek 18 > MarianoMartinezPeck 18 > yo 18 > sd 18 > bf 16 > SvenVanCaekenberghe 16 > JMM 16 > marcus.denker 14 > wiz 12 > ajh 12 > mjr 12 > cipt 10 > abc 10 > md 10 > HenrikSperreJohansen 9 > MikeRoberts 8 > AndyKellens 6 > LukasRenggli 6 > noha 6 > ClementBera 6 > jrd 6 > GastonDallOglio 6 > 2011-01-24T15:34:00+01:00 6 > DeboraFortini 5 > stephane.ducasse 5 > lr 5 > 2011-01-24T15:33:00+01:00 4 > dgd 4 > DamienCassou 4 > TestRunner 4 > bkv 4 > BG 4 > Alexandre 4 > AndrewBlack 4 > sw 4 > SimonAllier 3 > DanielAvivEstebanAllende 3 > ASB 2 > mas 2 > pmm 2 > simondenier 2 > BernardoContreras 2 > th 2 > damienpollet 2 > NicoPaez 2 > CamilloBrui 2 > sps 2 > MiguelCoba 2 > eem 2 > NikoSchwarz 2 > JavierPimas 2 > GabrielOmarCotelli 2 > mir 2 > ul 2 > 2011-01-24T15:50:00+01:00 2 > jf 2 > c 2 > ls 2 > al 2 > NorbertHartl 2 > djp 2 > AdrianLienhard 2 > TorstenBergmann 2 > AlexandreBergel 2 > tbn 2 > DiogenesMoreira 2 > GuyHylton 1 > ThierryGoubier 1 >

Jan. 30, 2013

Re: [Pharo-project] Nautilus usability

by jannik laval

2013/1/30 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > On Jan 30, 2013, at 2:11 PM, jannik laval <jannik.laval(a)gmail.com> wrote: > > > > 2013/1/30 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > >> >> >> Ben >> >> On Jan 30, 2013, at 10:30 AM, jannik laval <jannik.laval(a)gmail.com> >> wrote: >> >> Hi, >> >> 2013/1/30 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> >> >>> >>> >>> Ben >>> >>> On Jan 30, 2013, at 10:03 AM, jannik laval <jannik.laval(a)gmail.com> >>> wrote: >>> >>> Hi Benjamin, >>> >>> I am trying to use Nautilus and going to Pharo 2.0 (I am using 20480). >>> I have some remarks about the usability of the tool. I think the idea is >>> cool and I begin to appreciate it. >>> >>> But, I have some problems: >>> >>> - When I am on a method and search senders (b,n). If there is only one >>> sender, another browser is opened focusing on the sender of the method. But >>> the method call is not highlighted. When I have to parse long methods, I >>> loose time. >>> >>> >>> True :) >>> >>> - About the keyboard shortcuts: please I need the same shortcuts >>> everywhereâ¦ Not everywhere because I know it takes time to do that. BUT >>> everywhere in nautilus itself. The shortcuts are not the same in the >>> sourcecode panel (old shortcuts) and in the list of entities (new >>> shortcuts). >>> As a user, I would like to have the possibility to disable the new >>> shortcuts to have the same shortcuts everywhere in my environment. >>> >>> >>> It's implemented Nautilus side, but KeyBindings still need some love :) >>> >>> >>> - About the package menu: >>> >there is too much items: 4 items to add package in groups is too much. >>> I would prefer one item (add as group) and a menu More. >>> > Why is there a "Search code" in "rewrite code" item ? The name does >>> not make sense. >>> >>> >>> Probably comes from OB :) >>> >> >> And should be changed. >> >> >>> >>> > Create Slice should be in the DEBUG mode. Which could be disabled in >>> the Settings. >>> >>> >>> Debug mode ? Why ?? >>> >> >> Or a different menu that is available for the core team or guys who need >> this feature. >> I do not use it even if I am in a pharo sprint. >> >> >> The browser is by nature a development tool :) >> > > Don't be stupid. You know what I want to say. > > > I know, I was teasing you :) > The goal behind, as Esteban said, is to help people who wants to > participate, even for "stupid" fix, like a typo, a comment, or just a temp > var renamed. > We got the feeling that when we do such a fix, then we are "often" too > lazy to open a bug entry, create a slice etc. Because indeed, the process > is a bit too complex I think. > > My point of view is that we can't complain that people are not involved if > we do not ease at maximum the way to do it :) > > > >> >> >> >>> >>> >>> - The "Show instance variables" and "Show class variables" does not show >>> the variables but the accessors to the variables, no ? >>> >>> >>> Yes, as the other browsers did, but I can change the name ;) >>> >> >> Yes please >> >> >>> >>> >>> - Is it possible to have a popup on the icons in Nautilus. There is lots >>> of icons that I don't know what they mean. >>> >>> >>> There are (or at least should, maybe a bug) >>> >> >> There are only on active icons. The others have no information popup. >> >> >>> >>> - It is the same for the color of classes and methods: Why are there >>> methods in gray ? classes in gray ? >>> >>> >>> Extensions >>> >> >> Thank you, but "in the browser" how can I know that ? >> >> >>> >>> >>> - The command "edit a comment", which is a clickable icon, opens a new >>> window. I would prefer that it has the same behavior than the button >>> "Comments": opening the comments in the same browser. >>> >>> >>> No, thanks to the popup and shortcuts, you can edit in a row a lot of >>> classes very quickly >>> >> >> Not agree. We have too much opened window, and when I write a comment, I >> want to write ONE and write it well. >> >> >> Take the first class to comment, >> >> start: press space >> type your comment >> save (cmd+s)(it closes the window) >> press arrow down >> goto: start >> >> Can't be faster :) >> > > You are right ! I am just surprised about that. > So this is not an issue :D > > > :D > > > >> >> >> >>> >>> >>> - in the lists of the browser, I would like to select multiple packages >>> without using the mouse. Is it possible ? In all the browsers, the shift-up >>> and shift-down can do that. >>> >>> >>> PluggableListMorph can't do that, but NewList can. >>> >>> Unfortunately, I think the integration will be in 3.0 >>> >> >> ARGhhhh >> >> >> If you have time to make it work you are more than welcome >> > > I have the same problem as you: lake of time ! > > > The same as every one I think ^^ That the major problem of open source > communities :) > > > >> >> >> >>> >>> >>> - When I select multiple packages, the classes of all these packages >>> should appear. Not only the ones of the last selected package. >>> >>> >>> There is a bug entry and discussion about that. Due to extension, it's >>> quite complicated to due and raises some issues. >>> >> >> >>> >>> >>> - what does the locker means in the source code editor ? I understood >>> that the method cannot be modifiedâ¦ But I can, so I don't understand. >>> >>> >>> It's a feature not yet really used. You can pin a text panel, and have >>> multiples. We need to polish that as well :) >>> >> >> It does not work fine. There are some UI issues (the top of the method is >> hidden because of the new buttons on the bottom of the window). If it is >> not used and polished, please remove it. >> >> >> I will try to make it work, but with the lectures, it's a bit complicated >> :S >> >> >> >>> >>> >>> - The history navigator is not shared between browsers. >>> >>> >>> There is a bug entry for this >>> >>> >>> That is a good beginning I think. >>> I give you my point of view as a user of the browser. This is the main >>> tool I am supposed to use in Pharo and I would like to not be frustrated >>> using it. >>> >>> >>> You know I love feedback :) >>> >> >> Thank you >> >> >>> Do you know what I like more ? Bug entries :P >>> >> >> Here, I am a user. I take time to send you a mail, and I don't want to >> take time to open bug entries. You can do it if you think the ideas are >> good. :P >> >> >> I though you was also part of the community :P >> > > A community is not a bug tracker but also all the communication around. > I just wanted to discuss and share my point of view. > > > I know :) Again, I was teasing you :D ( and I know you do not like the > issue tracker :P) > > I have not problem with opening bug entries from someone else mail ^^ > For sure, next time I will open a bug entry. On my todo list: Open a bug entry for Nautilus :DDD Cheers, Jannik > > Ben > > > Now, I am not sure it was a good idea. > Be cool, guys ! > > Jannik > > >> >> Ben >> >> >> >> Cheer, >> Jannik >> >>> >>> >>> Thanks again >>> Ben >>> >>> >>> >>> My 2 cents, >>> Jannik >>> >>>

Jan. 30, 2013