Skip to main content

Small Basic for biginners












Microsoft recently introduced Small Basic, a programming language for beginners. It's a strip down version of BASIC with only 15 key words. It seems to be a fun programming environment & definitely worth while trying. You can write both console & graphical interface enabled programs & even develop your own version of Logo.
Some of the features include:
  • Its free
  • 15 key words that support basic programming concepts including conditions & iterations
  • Intellisense & context sensitive help
  • Define variables on the fly, no need to explicitly define them
  • Graphic programming
  • Subroutines
  • Third-party libraries can be plugged, API is given
It even comes with a simple but comprehensive user guide that introduce basic programming concepts & Small Basic.
Though it's intended for beginners, even advanced develops can use it to write scripts that perform simple day to day tasks.

Comments

Hasala said…
Hi Dilum aiyya,

Nice to c u in the web, hope u r having fun and doing fine in Canada.

Y the microsoft Basic, they r trying 2 fools the world with their tricks, But v wont get caught, FOSS GAMBAS is much better i guess :) , but keep us posted on your news, for u taught us our first CS module so v r ever in debt to u. Wish u a very happy and succesful new year ;)
Dilum Bandara said…
Thanks for the comment. I think you miss the point...
Small basic is just a beginner’s interface to programming (can't even create an executable) whereas Gambas is suppose to be a fully fledged IDE. Windows support in Gambas is not the best, which is the platform most beginners use.
We started programming with DBase, FOXBase, Pascal, & C. No GUIs at all. We were happy even if we can write a simple sorting algorithm at that time. Whereas today’s programmers want to start with GUIs that make things much harder. So it's nice to have a beginners platform. It doesn't matter whether it's from FOSS community or Microsoft. The key thing is its availability.
simona said…
Hi Dilum, can you email me at simonamaloney@yahoo.com I have some questions for you. Thanks, Simona

Popular posts from this blog

1. Building P2P Simulators with OverSim - Where to Begin

This could be a series of blog posts about extending or developing your own OverSim applications & overlay networks. OverSim has a minimal tutorial on writing your own application & overlay network; however, it doesn't show the big picture. So, I'm wasting lots of time playing with code & trying to understand the rest. Good thing is, I like it more & more as I understand. You need to change/develop only a few things, but finding out which ones is a hell of a task. I hope this will not only make my life easy but also will be useful to new comers. Here's what you need to do: You need some background on OMNeT++ OverSim extend OMNeT++. But sometime it has its own way of doing things (to make your task even simple) so understand the differences . Develop several OMNeT++ simulators. TicToc is a good one to start with. Extend it as you imagine. Read Towards a Common API for Structured Peer-to-Peer Overlays , which is the basis for OvseSim's AP...

Key Application Layer Functions

Constructor  Can be use to set message to NULL . Better not to skip defining the constructor. Destructor Can be use to clear/delete messages using cancelAndDelete() . New version seems to be motivating to use a destructor so better not to skip. void initializeApp(int stage) Can be used to initialize the application, read parameters from omnet.ini file, set statistic collectors, GUI display variables, start timers, set UDP port, etc. stage - Indicate which stage your are in. MIN_STAGE_APP indicates this module is being created while MAX_STAGE_APP indicates all modules were created. We typically need MIN_STAGE_APP to i nitialize application & variables. void finishApp() Called when application is terminating. Can be used to summarize stat. New version seems to be motivating us to delete messages in the destructor.   void handleTimerEvent(cMessage* msg) Handle event timer. Use to generate new periodic messages, other events, or check for lost messages. Bett...

4. DHTTestApp & DHT

DHTTestAPP & DHT work together where DHTTestAPP utilizes the DHT to store & retrieve (key, value) pairs. DHT utilize the underlying overlay to route queries. DHTTestAPP Is a Tier2 application that periodically issue DHT put, get, & modify queries. The implementation consist of 2 modules: GlobalDhtTestMap - Provides a data structure & functions to maintain a global list of (key, value) pairs. Random keys are taken from this list to issue DHT get & modify queries. DHTTestApp - Issues DHT put, get, & modify queries after some delay derived from a truncnormal distribution.  Put messages - Use to add a random (key, value) pair into the DHT. A put message (represented as DHTputCAPICall ) consists of a random key, random value, expiration time ( ttl ), & whether (key, value) pair can be modified. Then the message is send to the Tier1 application using sendInternalRpcCall() method, which will store (key, value) pair in the DHT. When a successful re...