François Revol | 5 Feb 16:21 2016
Picon
Gravatar

Re: Gambas

On 05/02/2016 16:01, Sean wrote:
> Qt 4 is fairly well supporred, there are x11 dependencys that are
likely the problem

Indeed, likewise for Qt5 (although it wants some more stuff as well),
but I don't have time to look at it, so feel free to do so.

I build with:

./reconf-all && ./configure -C --prefix=/system/non-packaged && make
clean && make && make check

> Sent from XFINITY Connect Mobile App

Instead of advertising broken mobile apps they should fix them to
respect In-reply-to headers :D

François.

Mattia Tristo | 4 Feb 23:39 2016
Picon

Gambas

---------- Messaggio inoltrato ----------
Da: "Mattia Tristo" <redmoonapache-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Data: 03/feb/2016 22:53
Oggetto: Gambas
A: <haiku-uGLqWuYN4qNg9hUCZPvPmw@public.gmane.org>
Cc:

Cheers to all!!!

Is gambas BASIC port finish?

Mattia Tristo

Mattia Tristo | 3 Feb 23:15 2016
Picon

Encript\Decript

Encript and decript algorithm at beos.altervista.org

In BASIC

Cheers
Mattia Tristo

Glenn Holmer | 1 Feb 15:23 2016

NFS issue

I have an interesting NFS issue: my main desktop machine normally runs
Fedora Linux, and I have a second test machine with Haiku installed (on
bare metal). Both of these machines have several operating systems on them.

If I try to mount an NFS export from Haiku on the test machine with the
main machine as the server, there's a long pause followed by "mount
failed (No route to host)". I can, however, ping greyhand from Haiku.
The command line is:

mount_nfs greyhand:/mnt/common gcommon 1002 10002

Now interestingly, if I reboot the main machine to Ubuntu Studio (which
is Debian-based), the NFS mount from Haiku works just fine. Also, with
the main machine running Fedora and the test machine running any of
several Linux flavors, the NFS mount works as well.

Anybody have any ideas why this particular combination (Fedora 23 as NFS
server and Haiku as NFS client) isn't working for me? The entry in the
exports file is the same for both Fedora and Ubuntu Studio:

/mnt/common 192.168.1.0/24(rw,sync,no_root_squash,no_subtree_check)

Haiku was just updated to hrev50067 using "pkgman full-sync".

--

-- 
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."

Thomas Mueller | 29 Jan 12:47 2016

Run haiku on NFS?

Is it possible to run Haiku from NFS share/directory?  

I see "man diskless" in Linux and the BSDs but haven't seen anything in this regard for Haiku?

So would the answer be no, or is what I see for Haiku behind the times?

Tom

Mark Hellegers | 24 Jan 18:46 2016
Picon

Setting up an outbound only e-mail account

Hello,

there used to be a way to set up an outbound only e-mail account (at 
least with the Mail Daemon Replacement), but I don't see how to set 
that up in the current mail setup of Haiku. I tried to leave out the 
server address of the incoming connection, but then I get an error 
every time I try to send/receive e-mail in the mail daemon status log.
Is this functionality still there or has it been removed?

Kind regards,

Mark Hellegers

--
Spangalese for beginners

`Rangleugar mho shwarma.'
`Your Christmas elf is on fire.'

ty armour | 23 Jan 20:24 2016

but yeah

a great place to start with tutorials would probably be writing a raspberry pi compatable version of haiku as well as writing in support for the arduino.

you could write tutorials on comping haiku and running haiku under virtualbox and then get into writing 64 bit versions of haiku

but what you want to do is grab all the documentation you can find for nvidia and intel and amd chips and write device drivers and kernel drivers based on the documentation you find.

and you want to post that documentation online so that everyone can know how to search for their documentation and how to implement their hardware set.

this is gonna be fun
ty armour | 23 Jan 20:09 2016

if you are interested

simply post more information online, and post all of the tutorials and all of the code you can think of.

hell you can even make tutorials for making a raspberry pi compatable version of BEOS.

I am sure it can be done if we put our heads together.

you could even make tutorials on writing custom versions of Blender and hydrogen and lmms and stuff, and custom file servers etcetera, I like developing thigns because it will allow me to create custom components

Thanks again and I will keep desiging things for now


also the great thing about tutorials is that everyone loves DIY and they love free software and cheap hardware. so it makes sense to post tutorials because everyone will want to develop the software then.
ty armour | 23 Jan 20:04 2016

this is just a friendly request for further documentation

I did see the tutorials on writing a graphics card, perhaps a few real world examples may be nice too, like find the documentation for a graphics card post it online, and post the resulting code for the device driver with references to the documentation.

I am really looking for the following:
For tutorials on developing every single aspect of haiku, from writing a 64 bit version of haiku and writing custom bootloaders to getting flash support and browser support in haiku.

you could even give tutorials on writing basic audio frameworks and graphics frameworks, as well as basic server frameworks etcetera and then people could really get involved in haiku development.

I have a plan to build USB instruments and digital mixers among many other things. and if you give a bunch more tutorials Im sure I can get them to be compatable with haiku. I also design a lot of software, but again I just need the proper syntax to implement my software.

I do understand it will be a process for me, but hey tutorials are definitly the place to start when it comes to developing software and hardware.



You could even try to give tutorials and things for compiling linux applications under BEOS. it can be done, but again you just have to develop the core of haiku to enable that.

Thanks for your time
-Ty
Vale Tolpegin | 22 Jan 19:52 2016
Picon

A new web app for Hardware tests

Hi,

Before I get into the actual content of the email, I'd like to introduce myself. My name is Vale Tolpegin and I am a student participating in this year's GCI competition. I am really interested in Haiku and have really enjoyed my time working on it so far!

One of the projects I worked on required the creation a web app that can show a rating and compatibility overview of hardware for Haiku. The goal is to eventually have a system that can be hosted by Haiku which will allow people to submit hardware test reports.

At the moment, a lot of work has been done to prepare the system and get an initial working version. I have designed the backend to use Django, on top of which I am using only CSS & HTML which keep the pages very lightweight. In addition, I am using the style that the main Haiku website uses. The technical specs of the current site's front-end pages are as follows:

- Page size is roughly 135 KB with all files hosted locally (no JQuery required)
- CSS is Bootstrap with Shijin4

As I stated earlier, the backend is written using Python and Django's web server framework. I have not done any load testing yet, in part because we do not have a test instance of the final version of the server setup. The current status of implemented features includes most of the requirements of the final version, just in very simple implementations. Features implemented include:

- Login & Logout. The backend authentication is currently just Django's built in authentication system, but I have enabled support for LDAP, so the implementation of LDAP will be simple on the final production-ready version of the server.
- Submitting tests. Once logged in, you can submit a test for a component or a device.
- Editing tests. Almost all fields of a component and device can be edited.

Although I have done a lot of work so far, a lot more will be required to get the server to a production-ready state. This includes:

- Code refactoring. I need to break up the views for the site and separate them properly to create an easy-to-understand system that others can maintain.
- More in-depth hardware analysis options in the form. Currently, I only allow the user to briefly explain whether each component passed or not, and do not provide the user the ability to give a lengthy explanation for what happened in the test.
- Automatic hardware analysis. This is a little more complicated and will take some more work, but it is the preferred path for the production version. I'm currently planning on using mmu_man's HardwareChecker script to accomplish this.

A picture of the main page is attached to this email. If you would like to checkout the code, the github repository is located at https://github.com/DarkmatterVale/Haiku-Configuration-Repo.

Thoughts? Comments? Suggestions? Ideas?

Thank you,
Vale Tolpegin
Pete Goodeve | 21 Jan 05:39 2016
Picon

Re: The state of Haiku

On Thu, Jan 21, 2016 at 12:08:10AM +0100, Mark Hellegers wrote:
> > 
> > Probably worth reminding folks that BeShare is still active.  You can 
> > share
> > zips and hpkgs there.  Several people have put up hpkgs they have 
> > built.
> > New stuff is likely to get mirrored, even if the original source is 
> > not always
> > on-line.
> > 
> 
> Hello Pete,
> 
> while BeShare can be used to get packages from, it suffers from the 
> same problem as the suggestion by Stefano that I don't need a 
> repository. Ordinary users will look for new software in HaikuDepot and 
> it it is not there it might as well not exist. This is the same 
> situation as existed with BeOS and Bebits. If it wasn't on Bebits it 
> didn't exist. I know I am exaggerating a bit here, but that's basically 
> how it worked.

But I see no real reason that this has to be exclusively so.  BeBits
was the place to go because it was "the place to go".  In fact it was 
quite independent of Be Inc.  And actually in the BeOS days, BeShare
was quite widely used too.  For some reason that didn't continue on
into the Haiku era.

It's certainly true that BeShare doesn't get that much traffic these
days, but I assume it's an awareness problem.  If everyone realizes
it's an alternative to the depot, I don't see why it couldn't become
a useful source -- especially for all that stuff that isn't so vulnerable
to DLL Hell [to borrow from that OS we won't mention...]

> 
> When I write an application, I want to upload my application somewhere 
> where users are most likely to find it. We had that with Bebits and 
> later Haikuware and now we have HaikuDepot.
> Unfortunately, getting your application listed in HaikuDepot is much 
> harder at the moment than it was for Bebits and I only have experience 
> with porting open source software using Haikuporter. I don't even know 
> how to get closed source software on there, unless I want to start my 
> own repository and tell users to add the url to HaikuDepot. I find that 
> to be a big roadblock to releasing software for Haiku and I doubt that 
> will scale when there are many third party developers releasing 
> software.
> 
I have similar worries.  There are just too many roadblocks at the moment.
Hopefully these will get smoothed out eventually, but at the moment it's
tough.  It would be great if we could actually get a revived BeBits/Haikuware
but that doesn't seem likely.  If enough people get interested, BeShare
might be at least a partial substitute.

	-- Pete --


Gmane