Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[LogoForum] [ANN] Liogo 0.4 is now available

1 view
Skip to first unread message

John St. Clair

unread,
Jan 8, 2008, 2:54:17 PM1/8/08
to
The message below is being cross-posted from the LogoForum. Please
reply here at comp.lang.logo and it will be cross-posted back to the
LogoForum. The original author of this message is
laske_...@hotmail.nospam.com.


I'm proud to announce that Liogo 0.4 is now available.

Liogo 0.4 provides several great enhancements:
- LIOGOI is now a full window program mixing graphics and command line
on the same window. Both parts are customizable in size and colours. A
real turtle shape is used as turtle by default.
- Several graphics commands was added to handle images or drawing
labels,
- LIOGO now support arrays and multi-dimension arrays,
- LIOGO now comes with an OLE Automation Interface. So you could use
Liogo from any OLE enabled application or environnement like Excel or
VBScript. See OLE Tutorial for more,
- A full reference describes all existing commands with a description
and parameters meaning.
- LIOGO is now localized both at message level and at language level.
English and french are supported today.

I hope you'll enjoy this new release and I'm waiting for your feedbacks.

Merry Christmas !

Lionel Laské

__._,_.___

LogoForum messages are archived at:
http://groups.yahoo.com/group/LogoForum

John St. Clair

unread,
Jan 10, 2008, 11:46:49 PM1/10/08
to
The message below is being cross-posted from the LogoForum. Please
reply here at comp.lang.logo and it will be cross-posted back to the
LogoForum. The original author of this message is
pa...@elica.nospam.net.


lionel_laske wrote:
> - LIOGO now comes with an OLE Automation Interface. So you could use
> Liogo from any OLE enabled application or environnement like Excel or
> VBScript.

Great. This would make Liogo reusable from within other environments.

> - LIOGO is now localized both at message level and at language level.
> English and french are supported today.

What does "language level" mean? Could an English-tuned Liogo compile
Logo sources written in French-tuned Liogo?

-Pavel

John St. Clair

unread,
Jan 10, 2008, 11:50:06 PM1/10/08
to
The message below is being cross-posted from the LogoForum. Please
reply here at comp.lang.logo and it will be cross-posted back to the
LogoForum. The original author of this message is
jotap...@yahoo.nospam.com.


--- In Logo...@yahoogroups.com, Pavel Boytchev <pavel@...> wrote:
>
> lionel_laske wrote:
> > - LIOGO now comes with an OLE Automation Interface. So you could
use
> > Liogo from any OLE enabled application or environnement like
Excel or
> > VBScript.
>
> Great. This would make Liogo reusable from within other
environments.
>
>
>
> > - LIOGO is now localized both at message level and at language
level.
> > English and french are supported today.
>
> What does "language level" mean? Could an English-tuned Liogo
compile
> Logo sources written in French-tuned Liogo?
>

Hi Logo Gang!!!

Excuse my great ignorance about this issue. I know I'm an absolutely
ignorant about it, but I have a question:

LIOGO is a "Logo compiler" to get executable Logo procedures, right?

I think it's a very, very, very good idea. But LIOGO needs something
called: ".NET Framework". I really don't know "what the hell is
this", but I guess is something important because I've seen
another "mayor" market software with this essential requirement too.

My question is: if that thing ".NET Framework" is very important but
it isn't self included with Windows (at least my XP pro version
needs a 20MB extra downloaded to it), WHY TO MAKE A LOGO COMPILER
WITH SOMETHING NOT INCLUDED IN THE STANDARD WINDOWS VERSION?

My question is because there is a lot of directly "executable"
software within the "standard" basic version of Windows, so... Why
not to make a Logo compiler to get that "directly executable"
characteristic without any "extra" requirement?

Sorry, but I'm always thinking about the daily reality of the poor
part of the world, where it's hard to get a computer and it's so,
so, so hard to get a full system, at a low price, so... I think...
Why not to try to make certain things more easily?

It's just a question.

GOD BLESS YOU ALL!!!!!!!

Juan J. Paredes G.
From Curicó, Chile, South America, with love

John St. Clair

unread,
Jan 10, 2008, 11:52:52 PM1/10/08
to
The message below is being cross-posted from the LogoForum. Please
reply here at comp.lang.logo and it will be cross-posted back to the
LogoForum. The original author of this message is
pa...@elica.nospam.net.


jotape1960 wrote:

> LIOGO is a "Logo compiler" to get executable Logo procedures, right?

Right.

> WHY TO MAKE A LOGO COMPILER
> WITH SOMETHING NOT INCLUDED IN THE STANDARD WINDOWS VERSION?

Because many others have .Net installed. I also have it, because I need
it to tun some project-related stuff.

.Net has some features which make some things a lot easier.

> My question is because there is a lot of directly "executable"
> software within the "standard" basic version of Windows, so... Why
> not to make a Logo compiler to get that "directly executable"
> characteristic without any "extra" requirement?

Try Lhogho. No graphics yet, but all number/word/list-related primitives
are there.

> Why not to try to make certain things more easily?

Lhogho compiles directly to machine code, although this is, IMO, the
hardest way of implementing a Logo.

John St. Clair

unread,
Jan 11, 2008, 12:02:35 AM1/11/08
to
The message below is being cross-posted from the LogoForum. Please
reply here at comp.lang.logo and it will be cross-posted back to the
LogoForum. The original author of this message is
laske_...@hotmail.nospam.com.

--- In Logo...@yahoogroups.com, Pavel Boytchev <pavel@...> wrote:

> > - LIOGO is now localized both at message level and at language
level.
> > English and french are supported today.
>
> What does "language level" mean? Could an English-tuned Liogo
compile
> Logo sources written in French-tuned Liogo?
>

"Language level" means that all structural keywords and all framework
procedures are localized both in english and in french. So, if you
choose to draw a square "in english", you must write:

to square :n
repeat 4 [forward :n left 90]
end

And you must compile as a DLL using:

liogoc -target:dll -lang:en square.lgo

If you choose to draw your square "in french", you must write:

to carré :n
répète 4 [avance :n gauche 90]
end

And you must compile as a DLL using:

liogoc -target:dll -lang:fr square.lgo

But in both case your DLL is usable from the other language.
So you could write:

for [i 10 100 10] [carré :i]

in an english program calling the french DLL.
Or you could write:

pour [i 10 100 10] [square :i]

in a french program calling the english DLL.

Note that "-lang" option is need only if you want to build your Liogo
program on another language that the one choosed at Liogo setup.

Does it make sense for you Pavel ?

Lionel.

John St. Clair

unread,
Jan 11, 2008, 12:03:50 AM1/11/08
to
The message below is being cross-posted from the LogoForum. Please
reply here at comp.lang.logo and it will be cross-posted back to the
LogoForum. The original author of this message is
laske_...@hotmail.nospam.com.

--- In Logo...@yahoogroups.com, "jotape1960" <jotape1960@...> wrote:
>
>
> My question is: if that thing ".NET Framework" is very important
but
> it isn't self included with Windows (at least my XP pro version

> needs a 20MB extra downloaded to it), WHY TO MAKE A LOGO COMPILER

> WITH SOMETHING NOT INCLUDED IN THE STANDARD WINDOWS VERSION?
>
>

Of course, you're right but, except if your name is Pavel ;-) it's
really hard to write a Logo compiler "from scratch" ("from scratch"
means using only something included in a standard windows version).

.NET Framework help me to write lot of cool Liogo stuff:
- Native code generation: no need to write assembly,
- Localization: no need to write a local resource manager,
- OLE Automation: no need to write most of COM stuff,
- Vista support: WPF is natively callable from .NET,
- Interoperability: it's really easy to call .NET code from Liogo,
- Multi-threading: it's a native feature of .NET,
- ...

There are Pros and Cons to use .NET as developpement platform for
Liogo but I must confess that without .NET, I probably didn't take
time to write a Logo compiler ! Only a "superman" like Pavel can do
this spending several years to write the better Logo compiler:
Lhogho !

By the way, .NET Framework becomes really a part of Windows operating
system. You can't use Windows Update or install a service pack for
Windows without getting .NET Framework. Vista for example comes
natively with .NET Framework 2.0 and .NET Framework 3.0.

aaa1p...@gmail.com

unread,
Jan 28, 2008, 10:24:46 PM1/28/08
to
On Jan 8, 11:54 am, "John St. Clair" <john.stcl...@verizon.net> wrote:
> The message below is being cross-posted from the LogoForum. Please
> reply here at comp.lang.logo and it will be cross-posted back to the
> LogoForum. The original author of this message is
> laske_lio...@hotmail.nospam.com.

>
> I'm proud to announce that Liogo 0.4 is now available.
>
> Liogo 0.4 provides several great enhancements:
> - LIOGOI is now a full window program mixing graphics and command line
> on the same window. Both parts are customizable in size and colours. A
> real turtle shape is used as turtle by default.
> - Several graphics commands was added to handle images or drawing
> labels,
> - LIOGO now support arrays and multi-dimension arrays,
> - LIOGO now comes with an OLE Automation Interface. So you could use
> Liogo from any OLE enabled application or environnement like Excel or
> VBScript. See OLE Tutorial for more,
> - A full reference describes all existing commands with a description
> and parameters meaning.
> - LIOGO is now localized both at message level and at language level.
> English and french are supported today.
>
> I hope you'll enjoy this new release and I'm waiting for your feedbacks.
>
> Merry Christmas !
>
> Lionel Laské
>
> __._,_.___
>
> LogoForum messages are archived at:http://groups.yahoo.com/group/LogoForum

Do I have to install the .NET before I can run liogo?

Can I run liogo on windows without installing .NET ?

Is liogo compatible with win95? win98? winME? win2k?

Please advice.

0 new messages