[Gambas-user] Restructuring the official Gambas examples

[Ron]

Although discussing about a good structure to put them under is a good
thing,
watch out not to waste time which better had been used to code the example
themselves.

I'm missing modern world examples, not simple basic stuff.

Like how to interact with your webbrowser via websockets using Gambas.
http://sourceforge.net/p/gambasforge/code/HEAD/tree/trunk/ChatServer/.src/
I'm trying to create a gb.websocket component out of it.

How to authenticate against Facebook and other services using OAuth2 and
Gambas
https://code.google.com/p/gambas-online/

How to interface to you Raspberry Pi from Gambas.
http://www.raspberrypi.org/phpBB3/viewtopic.php?f=34&t=37659

Talking the MQTT protocol with Gambas, the new Internet of Things protocol
to be.
Started to work on it here:
http://domotiga.nl/projects/domotiga/repository/entry/trunk/DomotiGa3/.src/CMQTT.class

Regards,
Ron_2nd.



2013/4/29 Tobias Boege <taboege at ...626...>

> On Mon, 29 Apr 2013, Bruce wrote:
> > On Sun, 2013-04-28 at 19:30 +0200, Tobias Boege wrote:
> > > Hi folks,
> > >
> > > {lots} 8<
> >
> > Hi Tobi,
> >
> > Here's some "opinion", so take it as such and not criticism.
> >
>
> Too bad, for criticism helps to improve our ideas. Now you leave the work
> to
> me to make criticism out of your opinions ;-)
>
> > 1) Who uses the examples and why?
> > I would say there are two general categories of people who access the
> > examples. New gambas coders looking for answers to syntax and
> > algorithmic questions and experienced coders looking for code they have
> > forgotten how to use (I can confirm there is definitely at least one of
> > the second type!). The examples need to address both these audiences.
> >
>
> Matti already did sort of that observation. Niveau levels may therefore
> actually be too much of a classification. Dividing into newbie and
> experienced coder may be closer to the immediate needs.
>
> This could simplify the visual problems of presenting that new view to
> some extent.
>
> > 2) Avoiding a plethora of examples
> > Although having an example focus on a single aspect of gambas is
> > laudable we do not want to end up with a huge set of examples where one
> > has to load example B to understand example A, and then example C, D, E
> > etc. Any code or feature of an example should be completely self
> > contained.
> >
>
> Absolutely true. We don't have any need for an example for each of the
> language functions either. That's for the wiki or so.
>
> An example depicts one topic. Right.
>
> > 3) Comments
> > A sparsely commented class is worse than no comments at all. By this I
> > mean that comments in example code should go beyond the focus of the
> > example whenever obscure intent, algorithm or syntax is involved.  If
> > not, the naive user is left wondering what that piece of the example
> > code does and how and the experienced user, who may be reviewing the
> > code because they know that an obscure construct is demonstrated there,
> > is again frustrated because that exact bit is not commented.
> > There is no such things as too many or too detailed comments. Oh, how I
> > know this when having to go back into code I wrote a year, month, week
> > ago!
> >
>
> I disagree on that point. I can imagine too many or to detailed comments.
> My
> plans are to comment the "what" and "why" because the "how" should be
> obvious from the code. Otherwise it's bad code.
>
> Regards,
> Tobi
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
> _______________________________________________
> Gambas-user mailing list
> Gambas-user at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gambas-user
>