- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Vm-dev] Fixes to the SqueakSSL Plugin

by stepharo

Thanks you guys! Le 21/4/15 17:59, Tobias Pape a Ã©crit : > > Dear Smalltalkers > > Starting with Levente Uzonyi's patches to the Linux version > of the SqueakSSL-Plugin, we (Marcel Taeumel and me) have > ported this to the OS X and Windows version as well. > > Find three binaries[1] that can be used instead of > the ones found on versions found on SqueakSSL's google code > page. > > SqueakSSL: > - x86 32bit Linux ELF dynamic library > - Contains Levente's SNI feature > - needs SqueakSSL-ul.29 or equivalent for SNI support > - can work without. > - NOT linked against OpenSSL, but > _statically_ linked against LibreSSL 2.1.6 [2]. > - It should work on older and newer Debian/Ubuntu as well as on > CentOS/RedHat/SuSE systems. > > SqueakSSL.dll > - x86 32bit Windows dll (built with Visual Studio 2013) > - Uses Schannel API > - SNI Support > - needs SqueakSSL-ul.29 or equivalent for SNI support > - can work without. > - setting an Int property via sqSetIntPropertySSL(...) > - Unicode problems when extracting the correct peerName in sqExtractPeerName > > SqueakSSL.bundle > - x86 32bit OS X Mach-O dylib (Linked against OS X 10.5 SDK) > - Uses Security-Framework > - SNI Support > - needs SqueakSSL-ul.29 or equivalent for SNI support > - can work without. > --------------------------------------------------------------------------------- > > The changes necessary for Windows and OS X are not yet available in the > squeakvm svn, the linux ones are. > I have not yet found a good way to include the static linking in either > the way the Autoconf works for Cog or CMake works for the interpreter, > but I'll follow-up to this. > > -------------------------------------------------------------------------------- > > Best regards > -Tobias > > > > > [1]: http://forum.world.st/file/n4820846/squeakssl.zip > [2]: http://www.libressl.org/ > >

April 21, 2015

Re: [Pharo-dev] Improving the documentation model

by Nicolas Anquetil

This remind me of a discussion a very long time ago on a newsgroup - a young zealot of GUI (windows, buttons, mouses) was asking himself and the community how people could deny that this was the best interface on earth or how anybody could prefer text based interface - a seasonned sys. admin then started to explain all the clicks he had to perform to create one new user account. Result: for one new user some minutes of work He then added that he had to create HUMDREDS of user every year and was so very happy that he did not had to do it all by pointing and clicking but had some scripts to do it. So the answer to all this is that there are very good and valid reasons to prefer text to all the shiny interfaces of he world. And you don't even have to look very far to find some. As for programming with in a graphical way, the ability has been around for decades. I believe we can safely assume that if people are still using textual interface after such a very long period (in computer science time frame), it is most certainly because natural selection has favoured the choice that had most advantages ... nicolas PS: which does not mean that GUI are completely useless On 21/04/2015 20:03, kilon alios wrote: > Funnily enough I am in the exact opposite opinion, of Graphical > approach being vastly superior to text based approach including > programming languages. 25 years using computers and coding with them > and still cannot fathom why programming languages are still a think > and why developers and "power" users rely so much on text based > approach. But whether I like it or not the coding world is dominated > by text based solutions. > > Its a pointless debate though when it comes to pharo will depend on > the people doing the work. Personally I don't have the time of going > very deep into this and doing all the hard work it requires. My focus > is elsewhere. But I welcome any contribution. > > As a lawyer myself and a coder, I cannot even begin to compare Latex > to the convenience of Libreoffice I use at work. Its not even a debate > . Latex is something I never heard of until Pillar introduced me to > it. Can't imagine who in the right mind would use this to document > things, but I guess they have their reasons. > > I started with command line and CP/M back in 1988 but even back then > when GUIs were not mainstream (at least in my country) I was dreaming > of graphical intefaces that would lift me from the restrictions of > text based approach and the dreaded command line. I wish I had found > out about Smalltalk back then and its elegant solution to this problem. > > I love Pillar because its simple and I like the syntax, but yeah in > the end I would choose a Graphical Documentation Tool no questions asked. > > On Tue, Apr 21, 2015 at 7:39 PM, Dmitri Zagidulin > <dmitri(a)zagidulin.net <mailto:dmitri@zagidulin.net>> wrote: > > On Tue, Apr 21, 2015 at 12:15 PM, Sean P. DeNigris > <sean(a)clipperadams.com <mailto:sean@clipperadams.com>> wrote: > > I dream that all documents in my Dynabook are WYSIWYG. > However, the > computing world seems to have regressed into writing documents > in various > forms of assembly code. > > > Completely disagree, that it's a regression in any way :) > Text-based document writing has enabled so many more features > than WYSIWYG approaches have ever dreamed of. I would be happy to > debate the merits of the two approaches, feature-for-feature. > > You're basically pining for the equivalent of VisualBasic drag & > drop programming, versus the flexibility of writing code in an > editor. The latter wins, no contest. (Now, that is not to say that > text-based code editing can't be /improved/ with better IDE tools, > that's what we're all about after all.) > >

April 21, 2015

Re: [Pharo-dev] Improving the documentation model

by phil＠highoctane.be

Pillar is fine as long as we aren't forced into the backend quirks to get a given output. I haven't see Docbook and Docbook-XML and XSL-FO mentioned. But these are working nicely too. Lots of Linux docs are written with Docbook. I've a client who outputs supercomplicated documents with XSL-FO. A Pillar output to Docbook would be great. One must invest time in any choice to be really productive. WYSIWYG included. FWIW LibreOffice equations are written much faster when one knows the text based language than with the point and click tools. The best thing is an ability to render fast. Same as Smalltalk: fast feedback in order to iterate without a break in the flow. Le 21 avr. 2015 20:03, "kilon alios" <kilon.alios(a)gmail.com> a Ã©crit : > Funnily enough I am in the exact opposite opinion, of Graphical approach > being vastly superior to text based approach including programming > languages. 25 years using computers and coding with them and still cannot > fathom why programming languages are still a think and why developers and > "power" users rely so much on text based approach. But whether I like it or > not the coding world is dominated by text based solutions. > > Its a pointless debate though when it comes to pharo will depend on the > people doing the work. Personally I don't have the time of going very deep > into this and doing all the hard work it requires. My focus is elsewhere. > But I welcome any contribution. > > As a lawyer myself and a coder, I cannot even begin to compare Latex to > the convenience of Libreoffice I use at work. Its not even a debate . > Latex is something I never heard of until Pillar introduced me to it. > Can't imagine who in the right mind would use this to document things, but > I guess they have their reasons. > > I started with command line and CP/M back in 1988 but even back then when > GUIs were not mainstream (at least in my country) I was dreaming of > graphical intefaces that would lift me from the restrictions of text based > approach and the dreaded command line. I wish I had found out about > Smalltalk back then and its elegant solution to this problem. > > I love Pillar because its simple and I like the syntax, but yeah in the > end I would choose a Graphical Documentation Tool no questions asked. > > On Tue, Apr 21, 2015 at 7:39 PM, Dmitri Zagidulin <dmitri(a)zagidulin.net> > wrote: > >> On Tue, Apr 21, 2015 at 12:15 PM, Sean P. DeNigris <sean(a)clipperadams.com >> > wrote: >>> >>> I dream that all documents in my Dynabook are WYSIWYG. However, the >>> computing world seems to have regressed into writing documents in various >>> forms of assembly code. >> >> >> Completely disagree, that it's a regression in any way :) Text-based >> document writing has enabled so many more features than WYSIWYG approaches >> have ever dreamed of. I would be happy to debate the merits of the two >> approaches, feature-for-feature. >> >> You're basically pining for the equivalent of VisualBasic drag & drop >> programming, versus the flexibility of writing code in an editor. The >> latter wins, no contest. (Now, that is not to say that text-based code >> editing can't be /improved/ with better IDE tools, that's what we're all >> about after all.) >> >> > >

April 21, 2015

Re: [Pharo-dev] Improving the documentation model

by kilon alios

Funnily enough I am in the exact opposite opinion, of Graphical approach being vastly superior to text based approach including programming languages. 25 years using computers and coding with them and still cannot fathom why programming languages are still a think and why developers and "power" users rely so much on text based approach. But whether I like it or not the coding world is dominated by text based solutions. Its a pointless debate though when it comes to pharo will depend on the people doing the work. Personally I don't have the time of going very deep into this and doing all the hard work it requires. My focus is elsewhere. But I welcome any contribution. As a lawyer myself and a coder, I cannot even begin to compare Latex to the convenience of Libreoffice I use at work. Its not even a debate . Latex is something I never heard of until Pillar introduced me to it. Can't imagine who in the right mind would use this to document things, but I guess they have their reasons. I started with command line and CP/M back in 1988 but even back then when GUIs were not mainstream (at least in my country) I was dreaming of graphical intefaces that would lift me from the restrictions of text based approach and the dreaded command line. I wish I had found out about Smalltalk back then and its elegant solution to this problem. I love Pillar because its simple and I like the syntax, but yeah in the end I would choose a Graphical Documentation Tool no questions asked. On Tue, Apr 21, 2015 at 7:39 PM, Dmitri Zagidulin <dmitri(a)zagidulin.net> wrote: > On Tue, Apr 21, 2015 at 12:15 PM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: >> >> I dream that all documents in my Dynabook are WYSIWYG. However, the >> computing world seems to have regressed into writing documents in various >> forms of assembly code. > > > Completely disagree, that it's a regression in any way :) Text-based > document writing has enabled so many more features than WYSIWYG approaches > have ever dreamed of. I would be happy to debate the merits of the two > approaches, feature-for-feature. > > You're basically pining for the equivalent of VisualBasic drag & drop > programming, versus the flexibility of writing code in an editor. The > latter wins, no contest. (Now, that is not to say that text-based code > editing can't be /improved/ with better IDE tools, that's what we're all > about after all.) > >

April 21, 2015

Re: [Pharo-dev] Improving the documentation model

by nacho

The other day I was thinking about this. I thought that it would be a great idea to have a pillar rendering engine inside Pharo. In that way the documentation written will be available in the image WYSIWYG with no need for recompilation. The update of books will be easy, just do a Software Update and the documentation is up to date. a Pillar rendering, WYSIWYG editor would be great. cheers Nacho *Lic. Ignacio Sniechowski, MBA* *Prosavic SRL* *Tel: (011) 4542-6714* On Tue, Apr 21, 2015 at 2:49 PM, kilon.alios [via Smalltalk] < ml-node+s1294792n4820973h56(a)n4.nabble.com> wrote: > Funnily enough I am in the exact opposite opinion, of Graphical approach > being vastly superior to text based approach including programming > languages. 25 years using computers and coding with them and still cannot > fathom why programming languages are still a think and why developers and > "power" users rely so much on text based approach. But whether I like it or > not the coding world is dominated by text based solutions. > > Its a pointless debate though when it comes to pharo will depend on the > people doing the work. Personally I don't have the time of going very deep > into this and doing all the hard work it requires. My focus is elsewhere. > But I welcome any contribution. > > As a lawyer myself and a coder, I cannot even begin to compare Latex to > the convenience of Libreoffice I use at work. Its not even a debate . > Latex is something I never heard of until Pillar introduced me to it. > Can't imagine who in the right mind would use this to document things, but > I guess they have their reasons. > > I started with command line and CP/M back in 1988 but even back then when > GUIs were not mainstream (at least in my country) I was dreaming of > graphical intefaces that would lift me from the restrictions of text based > approach and the dreaded command line. I wish I had found out about > Smalltalk back then and its elegant solution to this problem. > > I love Pillar because its simple and I like the syntax, but yeah in the > end I would choose a Graphical Documentation Tool no questions asked. > > On Tue, Apr 21, 2015 at 7:39 PM, Dmitri Zagidulin <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4820973&i=0>> wrote: > >> On Tue, Apr 21, 2015 at 12:15 PM, Sean P. DeNigris <[hidden email] >> <http:///user/SendEmail.jtp?type=node&node=4820973&i=1>> wrote: >>> >>> I dream that all documents in my Dynabook are WYSIWYG. However, the >>> computing world seems to have regressed into writing documents in various >>> forms of assembly code. >> >> >> Completely disagree, that it's a regression in any way :) Text-based >> document writing has enabled so many more features than WYSIWYG approaches >> have ever dreamed of. I would be happy to debate the merits of the two >> approaches, feature-for-feature. >> >> You're basically pining for the equivalent of VisualBasic drag & drop >> programming, versus the flexibility of writing code in an editor. The >> latter wins, no contest. (Now, that is not to say that text-based code >> editing can't be /improved/ with better IDE tools, that's what we're all >> about after all.) >> >> > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/Improving-the-documentation-model-tp4820814p4820973.h… > To start a new topic under Pharo Smalltalk Developers, email > ml-node+s1294792n1294837h40(a)n4.nabble.com > To unsubscribe from Pharo Smalltalk Developers, click here > <http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML > <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > ----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- View this message in context: http://forum.world.st/Improving-the-documentation-model-tp4820814p4820976.h… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 21, 2015

Re: [Pharo-dev] Roadmap

by Dmitri Zagidulin

Aha! Good to know. Thanks :) On Tue, Apr 21, 2015 at 1:37 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 21 Apr 2015, at 19:06, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > On Mon, Apr 20, 2015 at 7:26 PM, Dmitri Zagidulin <dmitri(a)zagidulin.net> > wrote: > > Similar question - are there any roadmap plans to add Dictionary > literals to Pharo? > > You can already do things like > > { 'key' -> 'value'. 'key2' -> 'value2' } asDictionary > > YES ! > > You could also write: > > { #foo->100. #bar->200 } asDictionary. > { #foo->100. #bar->200 } asOrderedDictionary. > { #foo->100. #bar->200 } asSmallDictionary. > > And everyone will know exactly what you mean, imagine that ;-) >

April 21, 2015

Re: [Pharo-dev] Seaside One Click Experience on Pharo 4?

by Paul DeBruicker

I'm against it without a commitment to also update all the docs that use the one click. So its not just repackaging an image and vm into a one click experience. Its a bigger task that will need weeks of work. The docs are debugged and work. Seaside hasn't changed much. Pharo has changed ... more. If the point of the Seaside docs is to learn Seaside then what is there now is fine. Dmitri Zagidulin wrote > Thanks, Torsten. > I will definitely include those instructions in whatever documentation I > can get my hands on. > > But that's *in addition* to advocating that we update our Seaside > One-Click > experience image. (For the reasons that I outline earlier in this thread, > namely that the vast majority of existing docs (books, sites, blog posts) > point new users to the One-Click images.) > > On Mon, Apr 20, 2015 at 3:48 PM, Torsten Bergmann < > astares@ > > wrote: > >> Hi Dmitri, >> >> not directly a one-click but in Pharo 4.0 you can load on your own: >> >> - open World menu -> "Tools" -> "Configuration Browser" >> - load Seaside directly (which as of today is Seaside 3.1.4) >> >> After loading you can use "Tools" -> "Seaside control panel" to add an >> adaptor >> (see attached screenshot) and then browse Seaside on the defined port >> like >> http://localhost:8080 >> >> >> If you like you can also load "Bootstrap" framework directly from the >> config browser >> - which is a wrapper for twitter bootstrap (see >> http://pharo.pharocloud.com/bootstrap) >> >> There is also work going on for a Seaside 3.2. Dont know about the >> timeline. >> Ideally you should ask on the seaside-dev list: >> >> http://lists.squeakfoundation.org/pipermail/seaside-dev >> >> Bye >> T. >> >> >> >> Gesendet: Montag, 20. April 2015 um 20:45 Uhr >> Von: "Dmitri Zagidulin" < > dmitri@ > > >> An: "Pharo Development List" < > pharo-dev@.pharo > > >> Betreff: Re: [Pharo-dev] Seaside One Click Experience on Pharo 4? >> >> (Just wanting to make sure this issue doesn't get lost in the general 4.0 >> release activity and celebration). >> >> What's a good place to open an issue, as a reminder/to-do item to create >> a >> Seaside+Pharo4 one-click image? The general Pharo fogbugz? >> >> Or, who would be the people to talk to? (Sean? :) ) >> >> >> On Fri, Apr 10, 2015 at 3:10 PM, stepharo < > stepharo@ > > wrote: >> It should not be that complex: >> putting the vm in the folder and the pharo 40 image + sources files. >> >> Stef >> >> Le 10/4/15 19:51, Dmitri Zagidulin a Ã©crit : >> >> Are there any plans to update the old Seaside One Click Experience for >> Pharo 4.0 (and the latest stable Seaside)? >> >> And if not, what would be the level of effort required? (And/or, who >> would >> be the people to talk to, to set it up?) >> >> The reason I ask is, users new to web development on Pharo overwhelmingly >> get recommended to use the One Click images. >> >> - on >> http://www.seaside.st/download/pharo[http://www.seaside.st/download/pharo] >> - >> "The Seaside One-Click Experience is the easiest way to get started with >> Seaside." Uses Pharo 1.4, I believe. >> >> - Learning Web Development with Seaside 3 ( >> http://seaside.gemtalksystems.com/tutorial/chapter01.pdf[http://seaside.gem… >> ) >> also points to the Pharo download link above. Same deal, 1.4. >> >> - Dynamic Web Development with Seaside ( >> http://book.seaside.st/book[http://book.seaside.st/book] ) also points to >> the One-Click. >> >> - Countless blog posts / tutorials link to it. >> >> - And, finally, Updated Pharo By Example (the Seaside chapter), also >> recommends the One Click image. >> >> Given how much work the community has done since Pharo 1.4, would it not >> make sense to update the integrated images? >> -- View this message in context: http://forum.world.st/Seaside-One-Click-Experience-on-Pharo-4-tp4818966p482… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 21, 2015

Re: [Pharo-dev] Roadmap

by Sven Van Caekenberghe

> On 21 Apr 2015, at 19:06, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > On Mon, Apr 20, 2015 at 7:26 PM, Dmitri Zagidulin <dmitri(a)zagidulin.net> wrote: > Similar question - are there any roadmap plans to add Dictionary literals to Pharo? > You can already do things like > { 'key' -> 'value'. 'key2' -> 'value2' } asDictionary YES ! You could also write: { #foo->100. #bar->200 } asDictionary. { #foo->100. #bar->200 } asOrderedDictionary. { #foo->100. #bar->200 } asSmallDictionary. And everyone will know exactly what you mean, imagine that ;-)

April 21, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] de6e0a: 50003

by Yuriy Tymchuk

Oh, it should be replaced by StartupPreferencesLoader. Iâll submit a slice > On 21 Apr 2015, at 19:20, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > So now startup actions are not working because StartupLoader was removed. What are the plans about this? > >> On 21 Apr 2015, at 17:40, GitHub <noreply(a)github.com> wrote: >> >> Branch: refs/heads/5.0 >> Home: https://github.com/pharo-project/pharo-core >> Commit: de6e0a2db24ff07aaa850ca0fbea53e8860cbb0e >> https://github.com/pharo-project/pharo-core/commit/de6e0a2db24ff07aaa850ca0… >> Author: Jenkins Build Server <board(a)pharo-project.org> >> Date: 2015-04-21 (Tue, 21 Apr 2015) >> >> Changed paths: >> A AST-Core.package/NumberParser.class/class/testing/isNumber_.st >> A AST-Tests-Core.package/NumberParserTest.class/instance/tests - Float/testIsNumber.st >> R Deprecated40.package/NBWin32Caret.class/README.md >> R Deprecated40.package/NBWin32Caret.class/class/accessing/getBlinkTime.st >> R Deprecated40.package/NBWin32Caret.class/definition.st >> R Deprecated40.package/NBWin32Menu.class/README.md >> R Deprecated40.package/NBWin32Menu.class/definition.st >> R Deprecated40.package/NBWin32MessageBox.class/README.md >> R Deprecated40.package/NBWin32MessageBox.class/class/instance creation/messageBox_text_title_flags_.st >> R Deprecated40.package/NBWin32MessageBox.class/class/instance creation/test.st >> R Deprecated40.package/NBWin32MessageBox.class/definition.st >> R Deprecated40.package/NBWin32Process.class/README.md >> R Deprecated40.package/NBWin32Process.class/class/accessing/getCurrentProcess.st >> R Deprecated40.package/NBWin32Process.class/class/accessing/getCurrentProcessId.st >> R Deprecated40.package/NBWin32Process.class/definition.st >> R Deprecated40.package/NBWin32Process.class/instance/accessing/getPriorityClass.st >> R Deprecated40.package/NBWin32Process.class/instance/testing/isHighPriorityClass.st >> R Deprecated40.package/NBWin32Process.class/instance/testing/isIdlePriorityClass.st >> R Deprecated40.package/NBWin32Process.class/instance/testing/isNormalPriorityClass.st >> R Deprecated40.package/NBWin32Process.class/instance/testing/isRealtimePriorityClass.st >> R Deprecated40.package/NBWin32ShellTest.class/README.md >> R Deprecated40.package/NBWin32ShellTest.class/definition.st >> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testGetCommandLine.st >> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testGetComputerName.st >> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testGetDriveType.st >> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testNoDebuggerPresentByDefault.st >> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testNumberOfProcessors.st >> R Deprecated40.package/NBWin32Thread.class/README.md >> R Deprecated40.package/NBWin32Thread.class/class/accessing/getCurrentThread.st >> R Deprecated40.package/NBWin32Thread.class/class/accessing/getCurrentThreadId.st >> R Deprecated40.package/NBWin32Thread.class/definition.st >> R Deprecated40.package/NBWin32Thread.class/instance/testing/isThreadAllAccess.st >> R Deprecated40.package/Password.class/README.md >> R Deprecated40.package/Password.class/definition.st >> R Deprecated40.package/ShadowLabelMorph.class/README.md >> R Deprecated40.package/ShadowLabelMorph.class/definition.st >> R Deprecated40.package/ShadowLabelMorph.class/instance/drawing/drawOn_.st >> R Deprecated40.package/StartupLoader.class/README.md >> R Deprecated40.package/StartupLoader.class/class/accessing/default.st >> R Deprecated40.package/StartupLoader.class/definition.st >> R Deprecated40.package/TimeStamp.class/README.md >> R Deprecated40.package/TimeStamp.class/class/instance creation/now.st >> R Deprecated40.package/TimeStamp.class/class/instance creation/readFrom_.st >> R Deprecated40.package/TimeStamp.class/definition.st >> R Deprecated40.package/TimeStamp.class/instance/printing/printOn_.st >> R Deprecated40.package/TimeStamp.class/instance/squeak protocol/asTimeStamp.st >> R Deprecated40.package/TimeStamp.class/instance/squeak protocol/species.st >> R Deprecated40.package/TimeStamp.class/instance/squeak protocol/storeOn_.st >> R Deprecated40.package/extension/CheckBoxModel/instance/whenLabelChanged_.st >> R Deprecated40.package/extension/Class/instance/name_.st >> R Deprecated40.package/extension/CompiledMethod/instance/messagesDo_.st >> R Deprecated40.package/extension/Date/instance/leap.st >> R Deprecated40.package/extension/DateAndTime/instance/asTimeStamp.st >> R Deprecated40.package/extension/ImageModel/instance/whenActionChanged_.st >> R Deprecated40.package/extension/ImageModel/instance/whenImageChanged_.st >> R Deprecated40.package/extension/LabelModel/instance/text.st >> R Deprecated40.package/extension/LabelModel/instance/text_.st >> R Deprecated40.package/extension/LabelModel/instance/whenLabelChanged_.st >> R Deprecated40.package/extension/LabelModel/instance/whenTextChanged_.st >> R Deprecated40.package/extension/Locale/class/addLocalChangedListener_.st >> R Deprecated40.package/extension/Locale/class/isoLocale_.st >> R Deprecated40.package/extension/Locale/class/localeChanged.st >> R Deprecated40.package/extension/Locale/class/localeChangedListeners.st >> R Deprecated40.package/extension/LocaleID/class/previous.st >> R Deprecated40.package/extension/Matrix/class/column_.st >> R Deprecated40.package/extension/Matrix/class/row_.st >> R Deprecated40.package/extension/MenuMorph/class/fromArray_.st >> R Deprecated40.package/extension/MenuMorph/instance/addTranslatedList_.st >> R Deprecated40.package/extension/MenuMorph/instance/addUpdating_action_.st >> R Deprecated40.package/extension/MenuMorph/instance/addUpdating_target_action_.st >> R Deprecated40.package/extension/MenuMorph/instance/add_action_.st >> R Deprecated40.package/extension/MenuMorph/instance/add_target_action_.st >> R Deprecated40.package/extension/MenuMorph/instance/title_.st >> R Deprecated40.package/extension/MorphicUIManager/instance/request_initialAnswer_centerAt_.st >> R Deprecated40.package/extension/NonInteractiveUIManager/instance/request_initialAnswer_centerAt_.st >> R Deprecated40.package/extension/Object/instance/asReactiveVariable.st >> R Deprecated40.package/extension/OldClassBuilderAdapter/instance/anonymousSubclassOf_.st >> R Deprecated40.package/extension/OldClassBuilderAdapter/instance/becomeCompact_.st >> R Deprecated40.package/extension/OldClassBuilderAdapter/instance/becomeCompact_simplyAt_.st >> R Deprecated40.package/extension/OldClassBuilderAdapter/instance/becomeUncompact_.st >> R Deprecated40.package/extension/PluggableTextMorphWithLimits/instance/ifLocked_.st >> R Deprecated40.package/extension/PluggableTextMorphWithLimits/instance/ifLocked_ifUnlocked_.st >> R Deprecated40.package/extension/RGClassDefinition/instance/classSymbol.st >> R Deprecated40.package/extension/RGMethodDefinition/instance/classSymbol.st >> R Deprecated40.package/extension/RPackage/instance/correspondingMcPackage.st >> R Deprecated40.package/extension/RPackageOrganizer/instance/renamePackage_in_.st >> R Deprecated40.package/extension/RadioButtonModel/instance/whenLabelChanged_.st >> R Deprecated40.package/extension/Stream/instance/isMessageStream.st >> R Deprecated40.package/extension/String/instance/asTimeStamp.st >> R Deprecated40.package/extension/String/instance/do_toFieldNumber_.st >> R Deprecated40.package/extension/String/instance/padded_to_with_.st >> R Deprecated40.package/extension/String/instance/splitInteger.st >> R Deprecated40.package/extension/String/instance/tabDelimitedFieldsDo_.st >> R Deprecated40.package/extension/String/instance/withFirstCharacterDownshifted.st >> R Deprecated40.package/extension/SystemAnnouncement/class/fromInternal_.st >> R Deprecated40.package/extension/TClass/instance/classPoolFrom_.st >> R Deprecated40.package/extension/TClass/instance/ensureClassPool.st >> R Deprecated40.package/extension/ToolRegistry/instance/shortcuts.st >> R Deprecated40.package/extension/ToolRegistry/instance/userManager.st >> R Deprecated40.package/extension/UIManager/instance/displayProgress_at_from_to_during_.st >> R Deprecated40.package/extension/UIManager/instance/request_initialAnswer_centerAt_.st >> R Fuel.package/extension/TimeStamp/instance/fuelAccept_.st >> R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script611.st >> A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script612.st >> R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50002.st >> A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50003.st >> M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st >> >> Log Message: >> ----------- >> 50003 >> 15330 NumberParser>>#isNumber: >> https://pharo.fogbugz.com/f/cases/15330 >> >> 15368 unload Deprecate40 in Pharo5 >> https://pharo.fogbugz.com/f/cases/15368 >> >> http://files.pharo.org/image/50/50003.zip >> >> > >

April 21, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] de6e0a: 50003

by Marcus Denker

It had a comment: Deprecated => use StartupPreferenceLoader > On 21 Apr 2015, at 19:20, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > So now startup actions are not working because StartupLoader was removed. What are the plans about this? > >> On 21 Apr 2015, at 17:40, GitHub <noreply(a)github.com> wrote: >> >> Branch: refs/heads/5.0 >> Home: https://github.com/pharo-project/pharo-core >> Commit: de6e0a2db24ff07aaa850ca0fbea53e8860cbb0e >> https://github.com/pharo-project/pharo-core/commit/de6e0a2db24ff07aaa850ca0… >> Author: Jenkins Build Server <board(a)pharo-project.org> >> Date: 2015-04-21 (Tue, 21 Apr 2015) >> >> Changed paths: >> A AST-Core.package/NumberParser.class/class/testing/isNumber_.st >> A AST-Tests-Core.package/NumberParserTest.class/instance/tests - Float/testIsNumber.st >> R Deprecated40.package/NBWin32Caret.class/README.md >> R Deprecated40.package/NBWin32Caret.class/class/accessing/getBlinkTime.st >> R Deprecated40.package/NBWin32Caret.class/definition.st >> R Deprecated40.package/NBWin32Menu.class/README.md >> R Deprecated40.package/NBWin32Menu.class/definition.st >> R Deprecated40.package/NBWin32MessageBox.class/README.md >> R Deprecated40.package/NBWin32MessageBox.class/class/instance creation/messageBox_text_title_flags_.st >> R Deprecated40.package/NBWin32MessageBox.class/class/instance creation/test.st >> R Deprecated40.package/NBWin32MessageBox.class/definition.st >> R Deprecated40.package/NBWin32Process.class/README.md >> R Deprecated40.package/NBWin32Process.class/class/accessing/getCurrentProcess.st >> R Deprecated40.package/NBWin32Process.class/class/accessing/getCurrentProcessId.st >> R Deprecated40.package/NBWin32Process.class/definition.st >> R Deprecated40.package/NBWin32Process.class/instance/accessing/getPriorityClass.st >> R Deprecated40.package/NBWin32Process.class/instance/testing/isHighPriorityClass.st >> R Deprecated40.package/NBWin32Process.class/instance/testing/isIdlePriorityClass.st >> R Deprecated40.package/NBWin32Process.class/instance/testing/isNormalPriorityClass.st >> R Deprecated40.package/NBWin32Process.class/instance/testing/isRealtimePriorityClass.st >> R Deprecated40.package/NBWin32ShellTest.class/README.md >> R Deprecated40.package/NBWin32ShellTest.class/definition.st >> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testGetCommandLine.st >> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testGetComputerName.st >> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testGetDriveType.st >> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testNoDebuggerPresentByDefault.st >> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testNumberOfProcessors.st >> R Deprecated40.package/NBWin32Thread.class/README.md >> R Deprecated40.package/NBWin32Thread.class/class/accessing/getCurrentThread.st >> R Deprecated40.package/NBWin32Thread.class/class/accessing/getCurrentThreadId.st >> R Deprecated40.package/NBWin32Thread.class/definition.st >> R Deprecated40.package/NBWin32Thread.class/instance/testing/isThreadAllAccess.st >> R Deprecated40.package/Password.class/README.md >> R Deprecated40.package/Password.class/definition.st >> R Deprecated40.package/ShadowLabelMorph.class/README.md >> R Deprecated40.package/ShadowLabelMorph.class/definition.st >> R Deprecated40.package/ShadowLabelMorph.class/instance/drawing/drawOn_.st >> R Deprecated40.package/StartupLoader.class/README.md >> R Deprecated40.package/StartupLoader.class/class/accessing/default.st >> R Deprecated40.package/StartupLoader.class/definition.st >> R Deprecated40.package/TimeStamp.class/README.md >> R Deprecated40.package/TimeStamp.class/class/instance creation/now.st >> R Deprecated40.package/TimeStamp.class/class/instance creation/readFrom_.st >> R Deprecated40.package/TimeStamp.class/definition.st >> R Deprecated40.package/TimeStamp.class/instance/printing/printOn_.st >> R Deprecated40.package/TimeStamp.class/instance/squeak protocol/asTimeStamp.st >> R Deprecated40.package/TimeStamp.class/instance/squeak protocol/species.st >> R Deprecated40.package/TimeStamp.class/instance/squeak protocol/storeOn_.st >> R Deprecated40.package/extension/CheckBoxModel/instance/whenLabelChanged_.st >> R Deprecated40.package/extension/Class/instance/name_.st >> R Deprecated40.package/extension/CompiledMethod/instance/messagesDo_.st >> R Deprecated40.package/extension/Date/instance/leap.st >> R Deprecated40.package/extension/DateAndTime/instance/asTimeStamp.st >> R Deprecated40.package/extension/ImageModel/instance/whenActionChanged_.st >> R Deprecated40.package/extension/ImageModel/instance/whenImageChanged_.st >> R Deprecated40.package/extension/LabelModel/instance/text.st >> R Deprecated40.package/extension/LabelModel/instance/text_.st >> R Deprecated40.package/extension/LabelModel/instance/whenLabelChanged_.st >> R Deprecated40.package/extension/LabelModel/instance/whenTextChanged_.st >> R Deprecated40.package/extension/Locale/class/addLocalChangedListener_.st >> R Deprecated40.package/extension/Locale/class/isoLocale_.st >> R Deprecated40.package/extension/Locale/class/localeChanged.st >> R Deprecated40.package/extension/Locale/class/localeChangedListeners.st >> R Deprecated40.package/extension/LocaleID/class/previous.st >> R Deprecated40.package/extension/Matrix/class/column_.st >> R Deprecated40.package/extension/Matrix/class/row_.st >> R Deprecated40.package/extension/MenuMorph/class/fromArray_.st >> R Deprecated40.package/extension/MenuMorph/instance/addTranslatedList_.st >> R Deprecated40.package/extension/MenuMorph/instance/addUpdating_action_.st >> R Deprecated40.package/extension/MenuMorph/instance/addUpdating_target_action_.st >> R Deprecated40.package/extension/MenuMorph/instance/add_action_.st >> R Deprecated40.package/extension/MenuMorph/instance/add_target_action_.st >> R Deprecated40.package/extension/MenuMorph/instance/title_.st >> R Deprecated40.package/extension/MorphicUIManager/instance/request_initialAnswer_centerAt_.st >> R Deprecated40.package/extension/NonInteractiveUIManager/instance/request_initialAnswer_centerAt_.st >> R Deprecated40.package/extension/Object/instance/asReactiveVariable.st >> R Deprecated40.package/extension/OldClassBuilderAdapter/instance/anonymousSubclassOf_.st >> R Deprecated40.package/extension/OldClassBuilderAdapter/instance/becomeCompact_.st >> R Deprecated40.package/extension/OldClassBuilderAdapter/instance/becomeCompact_simplyAt_.st >> R Deprecated40.package/extension/OldClassBuilderAdapter/instance/becomeUncompact_.st >> R Deprecated40.package/extension/PluggableTextMorphWithLimits/instance/ifLocked_.st >> R Deprecated40.package/extension/PluggableTextMorphWithLimits/instance/ifLocked_ifUnlocked_.st >> R Deprecated40.package/extension/RGClassDefinition/instance/classSymbol.st >> R Deprecated40.package/extension/RGMethodDefinition/instance/classSymbol.st >> R Deprecated40.package/extension/RPackage/instance/correspondingMcPackage.st >> R Deprecated40.package/extension/RPackageOrganizer/instance/renamePackage_in_.st >> R Deprecated40.package/extension/RadioButtonModel/instance/whenLabelChanged_.st >> R Deprecated40.package/extension/Stream/instance/isMessageStream.st >> R Deprecated40.package/extension/String/instance/asTimeStamp.st >> R Deprecated40.package/extension/String/instance/do_toFieldNumber_.st >> R Deprecated40.package/extension/String/instance/padded_to_with_.st >> R Deprecated40.package/extension/String/instance/splitInteger.st >> R Deprecated40.package/extension/String/instance/tabDelimitedFieldsDo_.st >> R Deprecated40.package/extension/String/instance/withFirstCharacterDownshifted.st >> R Deprecated40.package/extension/SystemAnnouncement/class/fromInternal_.st >> R Deprecated40.package/extension/TClass/instance/classPoolFrom_.st >> R Deprecated40.package/extension/TClass/instance/ensureClassPool.st >> R Deprecated40.package/extension/ToolRegistry/instance/shortcuts.st >> R Deprecated40.package/extension/ToolRegistry/instance/userManager.st >> R Deprecated40.package/extension/UIManager/instance/displayProgress_at_from_to_during_.st >> R Deprecated40.package/extension/UIManager/instance/request_initialAnswer_centerAt_.st >> R Fuel.package/extension/TimeStamp/instance/fuelAccept_.st >> R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script611.st >> A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script612.st >> R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50002.st >> A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50003.st >> M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st >> >> Log Message: >> ----------- >> 50003 >> 15330 NumberParser>>#isNumber: >> https://pharo.fogbugz.com/f/cases/15330 >> >> 15368 unload Deprecate40 in Pharo5 >> https://pharo.fogbugz.com/f/cases/15368 >> >> http://files.pharo.org/image/50/50003.zip >> >> > >

April 21, 2015