So the code has not been ported ... yet.
StateTracker is a Roassal3D mecanism, that should not been used in standards
OpenGL.
Using R3StateTracker here introduce a dependency between NBOpenGL from
Roassal3D that is really bad, as Roassal3D has one from NBOpenGL.
The additional risk is to blur
On ne rigole pas …
http://www.programmez.com/node/20771
Le 28 mai 2014 à 09:49, Jean Baptiste Arnaud jbaptiste.arn...@gmail.com a
écrit :
So the code has not been ported ... yet.
StateTracker is a Roassal3D mecanism, that should not been used in standards
OpenGL.
Using R3StateTracker
Take a look at the Keymapping package.
There is a documentation chapter on the ci server
https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/
Stephan
Hi,
I am working on some NativeBoost bindings to a library. I am organizing
my work along the API of a java binding of the same library. As nights
go by, I created some methods that I didn't have yet use for as self
shouldBeImplemented, writing the others with test first.
What is the easiest way
Open Nautilus, right click on your package, ‘Choose Open restricted browser’
It would open a new Nautilus scoped to your package.
Then in the code pane, just type ’shouldBeImplemented’, select the text and
right click,
and finally select 'Implementors'
Ben
On 28 May 2014, at 13:57, Markus
You can right click on your package and select browse scoped.
Then senders/implementors queries and refactorings will be scoped to your
package (modulo a bug that includes unrelated trait methods that I need to fix
:) ).
On 28 mai 2014, at 13:57, Markus Fritsche mfrits...@reauktion.de wrote:
Here is the bug entry the fix:
https://pharo.fogbugz.com/f/cases/13281/Wrong-environment-when-browsing-scoped
On 28 mai 2014, at 14:08, Camille Teruel camille.ter...@gmail.com wrote:
You can right click on your package and select browse scoped.
Then senders/implementors queries and
Hi,
It is second time in a week that I have to analyze a problem related to a
package getting dirty because of loading another package. But when looking
for changes, the first package becomes clean again.
One occurrence of the problem can be seen in the latest moose image:
- download the latest
Hi Usman,
look if the loaded package has overrides on other packages. If yes, it
will dirty them, and looking for changes will clean them.
Thierry
Le 28/05/2014 15:59, Usman Bhatti a écrit :
Hi,
It is second time in a week that I have to analyze a problem related to
a package getting dirty
Hi all... and Sven ;-)
I'm mapping my objects with NeoJSONWriter, and I found it is not writing
the properties whose values are null.
NeoJSONPropertyMapping#writeObject: anObject on: jsonMapWriter
| value |
value := getter value: anObject.
value
ifNotNil: [ jsonMapWriter writeKey: propertyName
Stef sent me this url
https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/?
I think it cover part of your second point.
regards
art
On Mon, May 26, 2014 at 7:52 AM, kmo vox...@gmail.com wrote:
I think the new pharo website could be improved by the addition of two new
Hi Esteban,
Your wish is my command ;-)
In #bleedingEdge you can now do:
String streamContents: [ :stream |
(NeoJSONWriter on: stream)
writeNil: true;
mapAllInstVarsFor: Point;
nextPut: Point new.
which will give you:
{x:null,y:null}
instead of:
{}
which
On 26/5/14 19:19, Sven Van Caekenberghe wrote:
Object#name should be removed,
+1
it is possible, I tried it once.
Most senders of #name are asking for the name of a class.
On 26 May 2014, at 18:15, Stephan Eggermont step...@stack.nl wrote:
Do I understand correctly that name is to be
13 matches
Mail list logo
