GroG's blog

Interface Agreement

GroG's picture
Hi,
 
I'd like to get some input on this interface and a little feedback on how to make it stronger or more clear.
 
PinArrayControl
 
Kwatters said the pinEnable(String pin) method in Arduino is confusing. 

Mostly Human ... heh .. right ...

GroG's picture

So many short blurbs come to mine.


Peers, Tweaks & DNA - but were afraid to ask...

GroG's picture

This is probably long overdue, but I'll try to explain how to tweak DNA (Descriptions of Neighboring Autotoma) 
 

The head arduino is created inside the InMoovHead service.


SuperSized Fullscreen MRL

GroG's picture

juerg asked for fullscreen gui .. and since I was polishing in the area - we now have fullscreen mrl.

The fullscreen button is a toggle button -


Festo Tentacles

GroG's picture

I want at least 7 more !


Down The Arduino Rabbit Hole

GroG's picture

Setting the arduino board type needs to come from the user's UI or helper functions like arduino.setBoardUno().

Currently the board can set the type, by data coming back from the board.  Although I would prefer this method, if Arduino & its firmware was capable of providing all the necessary information.  But its not.  Sad, too, because I like "plug and play"


Avoid Interface Primitive Parameter Types

GroG's picture

I think interfaces should NOT be using primitive types.  We should always use the Object form of the primitive.

For example :
In 
instead of this :

enablePin(int address);

do this :

enablePin(Integer address);

In the past I thought int was somehow more effecient or cleaner than using the Object form, but in MRL-Land that is not the case.  In fact it can cause problems.


On the Soap Box about DigitalWrite AnalogWrite & PinMode

GroG's picture

Ok, I feel the need to get on the SoapBox again, because I'm currently working with Swing UI and pin control. 

I have made tonnes of mistakes, the stuff I'm refactoring now could be a shiney example of what "not to do". With that said, I think Arduio's following functions were a mistake :


VInMoov

GroG's picture

moz4r having fun with virtual inmoov :)


Normalize Normalize ! The chaos is the only confusing part !

GroG's picture

Sometimes we need to figure out unecessary complexities, so that we can make things more accessable.

I'm talking about Arduino Board Type.  Something you'd think is very straight forward, yet .. its not.  Not because it can't be, but I think because few have taken the time to make sense of it.

"Board Type" is a general term, but there are potentially 2 things which depend on it.