Reviving the yab community

I remember Yab but never had time to start writing in BeOS. I hear Lua is the script du jour these days? Where can you get a Haiku list of languages and see which one you can work with by the way?

Nicolas

http://haikuware.com/remository/view-details/development/editors/unoffic...

zip File included yab 1.7 Source, BuildFactory, yabIDE and Examples

use #!yab instead of #!/boot/home/config/bin/yab and place the yab binary in /boot/home/config/non-packaged/bin on a PM nightly.

Is there a newer source code than this? :
http://sourceforge.net/projects/yab-interpreter/

So there is no current repository for Yab?

Would someone upload the source code for the latest version of Yab to Github. Then we can get someone to get Yab working on the Nightlies with the PackageManager.

Done! Sources at https://github.com/HaikuArchives/Yab -- with Lelldorin's fixes. It will probably need some changes to the build infrastructure, as I deleted some duplicated files.

The source files in the BuildFactory Directory are missing. These are not used to make YAB, but to compile a yab script into an executable. spacifically, you are missing the directory, BuildFactory/parts. I modified BuildFactory to use these files to make YabMain.cpp before proceeding to build the executrable. see BuildFactory.yab

/////////////////////////////////////////////////////////////
// set the application signature in YabMain.cpp
/////////////////////////////////////////////////////////////
sub SetAppSig(sig$)
	app_sig$="\n\tBString tmp(\""+sig$+"\");\n"
	open #1, This_dir$+"parts/YabMain.cpp.appsig","w"
	print #1 app_sig$
	close #1
	cmd$="cat "+This_dir$+"parts/YabMain.cpp.start "+This_dir$+"parts/YabMain.cpp.appsig "+This_dir$+"parts/YabMain.cpp.end > "+This_dir$+"YabMain.cpp"
	system(cmd$)
 
end sub

Well, one thing might help. Persuade the Haiku devs to bundle the yab executable with Haiku itself, just like python. That way yab devs can upload their apps as chmodded scripts rather than as enormous "bound" bundles. Uploading most of a meg to haikuware (this is from memory, it's been a while) for a little 100-line utility gets old fast.

Truth is, yab is unique: a strictly procedural language that can be used to write (modest) GUI applications. No need to bend your brain around object orientation. No need to keep track of a thousand libraries, it's all there in the one executable! I've found nothing else like it anywhere, on any OS. Applescript, maybe, but finding documentation on using that for anything but office automation is a lost cause, and even Apple has been neglecting it.

I was so fond of yab that I kept coming back to Haiku just to be able to work with it. But ... well, no need to go into details. Let's just say that I haven't fired up my Haiku box in months, and I come back here once in a while out of nostalgia.

There used to be a project called flyab, which was supposed to bring a subset of yab to other OS's. Perhaps that could be revived. Make it cross-platform and you'll attract a whole lot of new people, at least some of whom will try yab on its native platform.

But even if that is asking too much, if the Haiku devs could bring themselves to embrace yab and bundle it, it just might give Haiku itself a boost. Back in the Windows 3 days, you needed one file: VBRUN300.DLL, and suddenly you had access to thousands of apps. They might have been slow and buggy, but they existed. A year later, DOS was dead and Windows was everywhere. Yab could do the same thing for Haiku.

It should be simple to write a script that copies the required files (well, all of the code files) from "src" to "BuildFactory" at compile-time.

And Who is going to write this script when we already have a working YAB with source tree that already has all the files in the right places to use YAB and make your YAB script an executable binary?

This is a case of, " If it aint broke, don't fix it."

I think we all appreciate a main repository for the source, but there are not enough people with enough knowledge to make major changes to YAB. Not storing all the files will require work to make it usable, and I'm afraid this will make this repository languish. Nobody is interested in working on a project they cannot use it as-is without figuring out how to fix what this breaks. Is your intent to archive a snapshot of unusable code or to have a place for YAB to continue and grow?

Please fix the tree to include all the required files, even if they are duplicates, so that one can download the files and use them as-is. This way, developers may chose to add to or fix the code that is available, and not walk away because the project just doesn't work.

waddlesplash

Yab compiles just fine for me.

I use:

http://haikuware.com/remository/view-details/development/editors/unoffic...

Also available at beshare coquilletkd.com from FAT ELK -- me.

The layout and localization in 1.7 were removed as the Haiku appi has changed. This is probably your linker problem.

Building YAB is easy, making a YAB.hpkg is more work. This needs to include the buildfactory and IDE, including all the source files for yab in the buildfactory directory. Using the source at http://github.com/HaikuArchives/Yab is not an option as this is a borked up mess of files, part "official yab 1.7" and part " unofficial yab 1.7." This will not make yab. the "official 1.7" is broken as it includes lay-out and locale code that does not work with Haiku. The unofficioal 1.7 has these bleading edge changes reverted, and some other fixes to the code included. see http://haikuware.com/remository/view-details/de...te-error-of-textedit for good yab code that works.

I see there is a GCI task for this:
http://www.google-melange.com/gci/task/view/google/gci2013/5893234819596288

The source repository has to be fixed before this can be accomplished.

Easy solution: the package can be split in two parts, probably called yab, and yab_devel. The first one will have the interpreter and whatever runtime is needed, and the second will have the IDE, BuildFactory, and anything development related.

We don't forget about the users, but making life easier for developers is also a good thing: it makes the devs more productive, and only then they can start worrying about the users. That's also why we're still in alpha stage with Haiku. When we feel it's good enough to let users take over it, we'll do a stable release. The progress may seem slow, but it's happening.

Hi,
i dont prefer yab_devel, this sounds like a yab development version!

better is:
1.) yab-interpreter -> this is ONLY the YAB Interpreter, no IDE and Docu, Examples.
1.1) yab-IDE -> this is ONLY the IDE with Docu and Examples
1.2) yab-bf -> is ONLY the BuildFactory
Note: 1.1 need 1 and 1.2 need 1 and 1.1

2) yab-sdk -> this is a full version (1 , 1.1, 1.2)

Thanks
stargater

The beauty of BeOS/Haiku was the simple elegance of everything from the GUI to the file system layout, which they messed up a little because of the package managemnt they're developing. yab, and yab_devel is in keeping with the KISS (keep it simple stupid) principle.

KISS is an (American) English acronym for "Keep it simple and straightforward" - since most systems work best if they are kept simple rather than made complex. I sometimes forget that English is not the first language of most of the people involved with Haiku development. You didn't think I was talking about rock & roll, did you?

While we're on the subject, exactly the same argument applies to Squirrel. In some ways that was even newbie-friendlier than yab and right now it's even more broken.

We need this. We need yab, and Squirrel, and a Bethon installation that works out of the box. We need that Lua with API integration, and we need all of those integrated deeply into the OS, not something to be downloaded from a third-party site. Whether your programming background is in BASIC, Logo, Pascal, Python, Lua, Java or C, you should be able to sit down at a Haiku box and produce something straight away.

Look at what few new submissions there have been on Haikuware lately. Small yab utilities, QT ports in various stages of functionality and polish (please, porters, at least stick an icon on the thing) CLI ports, practically NO native Haiku GUI software written in C++. Am I the only one who thinks this is a crisis? If Haiku is not made attractive to developers at ALL skill levels to work with, then it will go nowhere.

There is a bounty on bountysource to get Yab to fully work on the nightlies:

https://www.bountysource.com/issues/1370888-create-a-recipe-file-for-hai...

The GCI students might like to work on it after GCI, so add your own $5 to the $5 start off fee to get them interested.

The information...

"The new Localizer makes localization easy. It also supports old ZETA locale files."

...is not correct, because this is the part of yab 1.7 (official) that does not run anymore, so we does not can compile the official version on Haiku 4.1 > Nightlies. So we remove this function and repair search and replace error and some other little things. Use this version as main Source please: http://haikuware.com/directory/view-details/development/editors/unoffici...

Remember, yab are team maui product and the main coder are jan_64. I am a initiator and yab have a code place.

You have idears or patches, then mail a patches!

http://www.haikuware.com/directory/view-details/development/language/yab

In the WIP we have nice Lokalisation Funktions and a yab app, but nice Haiku broke sometime the API, so we waiting for r1. Since you can used the latest version 1.7 (see the link).

Thanks and Happy coding, let us see what can you do with haiku. Personalty i like and love yab fullscreen demos.

stargater

I have a start on a yab.hpkg file .... it includes only the yab binary and documentation. get it at http://fatelk.com/yab My intent is to have three .hpkg files, yab, the one that is now available, source, and devel, yabide and buildfactory.

I am using the unoficial 1.7 version as the oficial version is broken. it is labeled 1.7.02

source available at the same address.

JABA is a Team Maui project. the developer is not Jan__64. JABA was build by DasJott and was an commercial project selled for Zeta OS. Now Jan__64 have the source code and the rights to make a new version of JABA. He have started to port the program to Haiku for some years. But he have not the time to do it, and now any interest on yab anymore? I dont know. I hope for a new release and any lifesigh from Jan__64 in the future.

JABA was great, but written on very early yab version. They are many things to change in the source before it will be run again on Haiku. We habe BurnItNow on Haiku, is it not good enough? I dont know. I will be fine to see JABA rebuild for Haiku, but who have the interest and time? I have too many other projects running in the moment.

May I ask what you've tried so far to get it into the repo?

Regards,
Humdinger

Sure, HaikuForever:

PulkoMandy just uploaded the packages created by haikuporter with recipes by bbjimmy. :)

Regards,
Humdinger

Do you using a nightly or a official haiku release?

The most tutorial about yab are availalbe at besly knowledge base