- Pharo-dev - lists.pharo.org

[ANN] Bootstrap for Seaside3 project (Release 0.1.0)
by Torsten Bergmann Oct. 3, 2013

Oct. 3, 2013

Hi, there are various frameworks out there helping you to ease common tasks in web development. One of them is Bootstrap (http://getbootstrap.com) that is used more and more to easily style web sites and web applications. We had wrappers for Bootstrap supporting Seaside in the past already: - the TwitterBootstrap project on SS3 from the Seaside team - the TBootstrap project from Gaston Dall Oglio Unfortunately these projects are not up to date with the latest Bootstrap version, not covered by tests, had no docu or examples, no CI, ... To provide better support for Bootstrap and Seaside3 development I created a fresh project called "Bootstrap for Seaside" (or "Bootstrap" for short). This new project is - nearly feature complete regarding components (Nav, Navbar, Jumbotron, Buttons, Alarms, Layouts, ...) - uses the latest Bootstrap libraries (http://getbootstrap.com) - covered by more than 160 tests - completed with an example browser that shows Bootstrap components and according Smalltalk code - available at STHub (http://smalltalkhub.com/#!/~TorstenBergmann/Bootstrap) - documented (see mentioned project website on STHub) with docu support for PharoOnlineHelp and catalog - controlled by CI (https://ci.inria.fr/pharo-contribution/job/Bootstrap/) - easily loadable using config browser in Pharo 2.0 Attached are some screenshots from the project itself. More details can be found in the more docu at the project site on SmalltalkHub. Just scroll down at the info page provided there. You can easily load it in a fresh Pharo 2.0 as "Bootstrap" from the config browser. It loads Seaside3 as a dependency. After loading evaluate ZnZincServerAdaptor startOn: 8080 to start the webserver and go to http://localhost:8080/bootstrap to browse the samples. Feel free to use it for your next Pharo/Seaside/Bootstrap based web project and thanks in advance for any contribution you may give to the project in the future. Bye T.

3 2

about configuration to manage the image
by StÃ©phane Ducasse Oct. 3, 2013

Oct. 3, 2013

Now I redid the configuration of Refactoring and Critics and publish the new package in the correct repository (ok marcus you did it so this is great but it will not scale) because there was a new changes touching all the packages. So this was a bad idea from me. => for now no separate repository => no move of package in between => I suggest that we load in the image the configuration and probably the process should manipulate configurations (I did not want to touch the metacello toolbox), I think that I will lose days thereâ¦. Or we simply gave up with the idea to have an image that can be modular. So we have to think and get smart. Stef

2 2

FOSDEM devroom
by Stephan Eggermont Oct. 2, 2013

Oct. 2, 2013

The FOSDEM organisation has accepted a devroom proposal for all smalltalk and related projects. Please let me know what you'd like to see there, and what you'd like to show. It will be one day in the weekend of 1-2 february in Brussels https://fosdem.org/2014/ Cheers, Stephan

1 0

Glorp, Fuel, Native postgres driver, Voyage/Mongo, any in GemStone?
by Mariano Martinez Peck Oct. 2, 2013

Oct. 2, 2013

Hi guys. First, let me apologize for the amount of emails I am sending. I am doing an analysis to see if GemStone is a good candidate for a project I am working and so it deserves some research. I wondered if any has ever tried porting any of these tools to GemStone: Fuel, Glorp, Native PostgreSQL driver, Voyage and MongoDB. Thanks a lot in advance, -- Mariano http://marianopeck.wordpress.com

4 7

reloading with green tests RB in Pharo 3.0
by StÃ©phane Ducasse Oct. 2, 2013

Oct. 2, 2013

Using a new and clean configuration I can reload RB (critics, environment, core/changes) I hope to get the time to reload Nautilus and atfter the others. I really think that we will need to be able to execute unload and postLoad action (we can already). I wonder if I will be able to do it for KeyMapping for example. We will see. Stef

1 0

new bug in RPackage
by StÃ©phane Ducasse Oct. 2, 2013

Oct. 2, 2013

esteban tomorrow I can show you the bug I found. during the test of the correct reloading of RB (ConfigurationOfRefactoring project version: #stable) load in my noNautilus and no RB I got systemMethodRecategorizedActionFrom: ann "a protocol has been renamed a method has been removed. // WILL BE TREATED WITH SystemMethodRemovedAnnouncement a method has been moved to another category -maybe from the classic category to an extending package -maybe from an extending package to another extending package -maybe from an extending package to a classic category - maybe from a classic category to another classic category" | oldProtocol newProtocol method methodPackage destinationPackage | oldProtocol := ann oldProtocol. "old protocol might be nil:" oldProtocol asString ifNil: [oldProtocol := '']. newProtocol := ann newProtocol. method := ann methodRecategorized. "1). See compiledMethod >> packageFromOrganizer:" "we have to pay attention that this announcement can come from TraitDescription>>updateOrganizationSelector:oldCategory:newCategory: . In this context, it can happen that the method referenced by the event is nil. In this case I think we should change nothing" method isNil ifFalse: [ "If the method origin is not the one of the event, we do not care about that method" method origin = ann methodClass ifFalse: [^ self]. methodPackage := method packageFromOrganizer: self. "if newProtocol is nil, it means that we are in a 'methodRemoved' case. Nothing should be modified (all the work will be done when catching methodRemovedAnnouncement) " newProtocol isNil ifTrue: [^self]. "it can happen that oldProtocol is Nil. in this case we should do nothing" oldProtocol ifNil: [^ self]. "maybe the category has changed" newProtocol asLowercase = oldProtocol asLowercase ifFalse: [ "according the extension specified is valid or not, the method will be defined as an extension of an external package or in the class parent package" destinationPackage := (self hasPackageForProtocol: newProtocol inClass: method methodClass) ifTrue: [ self packageForProtocol: newProtocol inClass: method methodClass ] ifFalse: [ (newProtocol beginsWith: '*') ifTrue: [ self ensureExistAndRegisterPackageNamed: newProtocol allButFirst capitalized ] ifFalse: [ method methodClass package ] ]. methodPackage := (self hasPackageForProtocol: oldProtocol inClass: method methodClass) ifTrue: [ self packageForProtocol: oldProtocol inClass: method methodClass ] ifFalse: [ method methodClass package ]. "then, we will remove the method from the method package, and add it to the destination package (we check before that the source package and the destination package are different)." methodPackage = destinationPackage ifFalse: [ (methodPackage methods includes: method) ifTrue: [ methodPackage removeMethod: method ]. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ where method was ClassTrait>>#soleInstance and apparently it does not exit raising an error classDefinitionSelectors in RPackage is a Set(#instanceVariableNames: #classTrait #copy #adoptInstance:from: #compile:classified:withStamp:notifying:logSource: #baseTrait #name #baseTrait: #isClassTrait #definition #classTrait: #initializeWithBaseTrait: #new #isBaseTrait) classExtensionSelectors is Set new and after investigation: soleInstance on ClassTrait is defined as an extension on *refactoring-core => destinationPackage addMethod: method. SystemAnnouncer uniqueInstance methodRepackaged: method from: methodPackage to: destinationPackage. ] ] ]

2 3

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Oct. 2, 2013

Oct. 2, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=wi… 1 regressions found. Zinc.Zodiac.ZnHTTPSTests.testGetPharoVersion

1 0

[update 3.0] #30439
by Marcus Denker Oct. 2, 2013

Oct. 2, 2013

30439 ----- 11748 ConfigurationCommandLineHandler should allow multiple groups https://pharo.fogbugz.com/f/cases/11748 11747 Delete working copy of RB-Pharo-Platform https://pharo.fogbugz.com/f/cases/11747 11744 some themes are abstract https://pharo.fogbugz.com/f/cases/11744 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-MarcusDenke… http://smalltalkhub.com/mc/Pharo/Pharo30/main/ConfigurationCommandLineHandl… http://smalltalkhub.com/mc/Pharo/Pharo30/main/ConfigurationCommandLineHandl…

2 1

IDE Nice idea
by Torsten Bergmann Oct. 2, 2013

Oct. 2, 2013

>Did you try "Groups" for that ? Yes, it is useful - but unfortunately not the same power and fast workflow. Even the TestRunner is able to filter its category list. I really do not understand why the filter was it removed from Nautilus instead of making it optional (via setting). Bye T.

1 0

Oct. 2, 2013

When I try (MCWorkingCopy forPackage: (MCPackage named: 'NautilusRefactoring')) unload NautilusUI allInstances do: [ :inst | SystemAnnouncer uniqueInstance unsubscribe: inst]. Smalltalk garbageCollect. (MCWorkingCopy forPackage: (MCPackage named: 'NautilusCommon')) unload. (MCWorkingCopy forPackage: (MCPackage named: 'Nautilus')) unload I get the attached system. I do not understand why SpecDebugger has something to do with navigationHistory. Any idea? I also think that we are not good at making sure what we load can be cleanly unloaded. Without that discipline we will never have a modular system. Stef

3 6