"Having a complete package is a good thing."

This is true. But the world is not static. There is 16-bit PWM now. There is 
8-bit DAC. There is floating-point math. Neither of which is supportet by 
jallib, IMO.

Advertising by posting projects in the web is a way, and an easy one. It is 
one, however, which many people go. I'd like to repeat the proposal I've made 
before: Soon is the time to apply for a gratis open-source-project booth at 
http://www.linuxtag.org/2014/en/ .


If someone is going to help a little in any way, I'm prepared to put quite some 
effort in such a project. I'm familiar with trade fairs and I can reach the 
location by subway.

I even have some hundred old PCBs as giveaways, which can be used for MAX232 
level converters. I can laser-cut the jallib URL onto those PCBs.


I have touch sensors and a LED-tile with 40 RGB-LEDs as exhibits.

Is anyone even a little interested?



________________________________
 Von: mattschinkel <[email protected]>
An: [email protected] 
Gesendet: 2:19 Mittwoch, 19.Februar 2014
Betreff: [jallib] Re: jallib team
 


Hi Rob,
The team has done a great job with the package we have created. It seems that 
Jallib is mostly complete, which causes less commits. Having a complete package 
is a good thing.
I and others just don't have time lately, although I do plan to get back into 
it and write more tutorials and put more work into bits of my current libs. 
When I was writing the tutorials and posting about them on Jallist and 
elsewhere, it was good advertising. This seemed to produce new interest.
You are a huge contributor at the moment. We all greatly appreciate the work 
you put into the device files. I'm not sure how to word this, but if you look 
at the amount of work you are putting in, and compare it to the number of other 
committers/users, it seems like you are doing too much for the "worth" of the 
additional device files. I think the answer is no, but is there any way to 
automate your device file creation? It may be more efficient to put your work 
in elsewhere. You could also choose to only update device files once per year, 
or whenever there is a need to do so do too a request. I don't think people use 
these new device files much.
I think we need to think up new projects and idea's, and you could assist 
better here. Maybe start a large project as a group and try to build something 
crazy that can get attention.
Some examples of things that could help, please add.
1. Help Kyle with the compiler to get new devices to work with it to get 
interest in the language.
2. Help Kyle with the compiler to make Jalv2 a cool scripting language for 
linux/windows. will need a new set of libs, and therefore more commits.
3. Work on whatever lib needs the most work. I'd say that would be the GLCD 
libs. Do a complete rewrite?
4. Start a project.. Send Jallib to space? Start an AI project? Build a robot?
5. Publish a book
 
Matt.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/jallib.
For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/jallib.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to