release 0.5
Rob Hamerling
Hi guys,
Are we heading for a year-end release? Before the winter holiday season?
And what open ends do we have that should be closed before that release?
Regards, Rob.
--
Rob Hamerling, Vianen, NL (http://www.robh.nl/)
Sebastien Lelong
Sounds like a good idea to me.
Seb
--
You received this message because you are subscribed to the Google Groups "jallib" group.
To post to this group, send email to jal...@googlegroups.com.
To unsubscribe from this group, send email to jallib+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
--
Sébastien Lelong
http://www.sirloon.net
http://sirbot.org
William
> Are we heading for a year-end release? Before the winter holiday season?
> And what open ends do we have that should be closed before that release?
>
detail? It might be possible to get the CAN-related libraries and
samples into the next release, but I also have travel and family plans
during the next weeks.
William
mattschinkel
Matt.
Sebastien Lelong
OK, then let's release ! Rob, can you run your script checking what's in TORELEASE, what's not ? Everybody will have to carefully look at it, to be sure there's no missing files left on the side of the road.
If you're OK, I'll modify release script to include tutorials PDF book.
Release 0.5 will keep 2.4l compiler version.
About release process, William, see the recipe here: http://code.google.com/p/jallib/wiki/ValidationProcess
Cheers,
Seb
--
You received this message because you are subscribed to the Google Groups "jallib" group.
To post to this group, send email to jal...@googlegroups.com.
To unsubscribe from this group, send email to jallib+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
mattschinkel
bugs so I did not add them to the torelease file. It may be ready for
the next release.
Matt.
On Dec 4, 1:48 am, Sebastien Lelong <sebastien.lel...@gmail.com>
wrote:
>
> OK, then let's release ! Rob, can you run your script checking what's in
> TORELEASE, what's not ? Everybody will have to carefully look at it, to be
> sure there's no missing files left on the side of the road.
>
> If you're OK, I'll modify release script to include tutorials PDF book.
>
> Release 0.5 will keep 2.4l compiler version.
>
> About release process, William, see the recipe here:http://code.google.com/p/jallib/wiki/ValidationProcess
>
> Cheers,
> Seb
>
> > I'll be ready for a release.
>
> > Matt.
>
> > On Dec 2, 2:46 am, Rob Hamerling <robhamerl...@gmail.com> wrote:
> > > Hi guys,
>
> > > Are we heading for a year-end release? Before the winter holiday season?
> > > And what open ends do we have that shoul
>
> d be closed before that release?
>
>
>
>
>
>
>
> > > Regards, Rob.
>
> > > --
> > > Rob Hamerling, Vianen, NL (http://www.robh.nl/)
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "jallib" group.
> > To post to this group, send email to jal...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > .
> Sébastien Lelonghttp://www.sirloon.nethttp://sirbot.org- Hide quoted text -
>
> - Show quoted text -
Rob Hamerling
Sebastien Lelong wrote:
> OK, then let's release ! Rob, can you run your script checking what's in
> TORELEASE, what's not ?
appeared after I ran jallib to compose samples from board and test
files. But I have not tested these samples. Nevertheless I suppose there
is no reason to withhold these from TORELEASE and I've added 'm.
See the attached file for the result.
> Everybody will have to carefully look at it, to
> be sure there's no missing files left on the side of the road.
>
> If you're OK, I'll modify release script to include tutorials PDF book.
>
> Release 0.5 will keep 2.4l compiler version.
Sebastien Lelong
My fat32 lib and sample are in SVN and work, but may have some issues/
bugs so I did not add them to the torelease file. It may be ready for
the next release.
I guess lots of files may have some issues and/or bugs, yet they are released :)
The important point is (amonst being JSG compliant) accompanying samples & documentation.
What I mean is, if you tested your lib/sample, I suggest you put it in TORELEASE, maybe with a "beta" annotation in CHANGELOG. If you prefer to wait 0.6 release, then no problem, we'll wait ! You're the one who can decide.
Cheers,
Seb
To unsubscribe from this group, send email to jallib+un...@googlegroups.com.
--
Sebastien Lelong
If you're OK, I'll modify release script to include tutorials PDF book.
I now have doubts... Tutorial book PDF weighs approx. 2MB, zipping it won't save much space. So, adding it to jallib-pack (other packages may remain the same as now) will make grow the whole up to something like 5MB. Does it sounds too big ? Should PDF stay as a separate download ? I'd prefer putting it in jallib-pack, since the goal for this package is to provide everything needed for jallib, documentation and tutorials being an important part. What's your opinion on this ?
Also, should bee packages also contain PDF file ? Maybe once I finally automate DITA generation, bee could contain bleeding edge PDF books...
Seb
William
William
Sebastien Lelong
Seb
What timeframe are you talking about for this release?
William
--
You received this message because you are subscribed to the Google Groups "jallib" group.
To post to this group, send email to jal...@googlegroups.com.
To unsubscribe from this group, send email to jallib+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
Sunish Issac
Sunish
mattschinkel
interested in contributing.
However, I would like to see a text files in the sample folder that
contains a list of samples. A text file such as "sample_list.txt".
This list could be created automaticly by your jallib-pack compiler.
This way you can still look through the list by PIC.
I would actually like to see the libs split between devices & other
libs, but I guess it's too late for that now, we would break all the
includes. The number of libs may be large later on.
Matt.
On Dec 5, 10:01 pm, Sunish Issac <sunish....@gmail.com> wrote:
> With the release of so many samples, looks like its time to split the
> samples folder. Spliting by sample type would be more sensible than by PIC
> name. IIRC there was discussion about this before.
>
> Sunish
>
>
>
> > wrote:
> > Releases usually takes one or two weeks to get completed, it depends how
> > much surprises we discover...
>
> > Seb
>
> > What timeframe are you talking about for this release?
>
> >> William
>
> >> --
>
> >> You received this message because you are subscribed to the Google Groups
> >> "jallib" group.
> >> To post to this group, send email to jal...@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> .
> >>http://groups.google.com/group/jallib?hl=en.
>
> > --
> > Sébastien Lelong
> >http://www.sirloon.net
> >http://sirbot.org
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "jallib" group.
>
> > To post to this group, send email to jal...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > .
Rob Hamerling
Hi
Sunish Issac wrote:
> With the release of so many samples, looks like its time to split the
> samples folder. Spliting by sample type would be more sensible than by
> PIC name. IIRC there was discussion about this before.
maybe some work. But is that so bad? It's nothing compared to the effort
to build and provide this collection, and for free. You must not look a
gift horse in the mouth!
Specify your criterium for splitting of the sample directory. Number of
files, other? It may already help to split off the blink samples, these
use no libraries at all.
Splitting by type (I suppose you mean used library) is not so straight
forward since many samples use more than one library. So be more
specific with your suggestion.
About splitting the include library: Device files might be put in a
separate directory, which would require one extra directory in the
include pathspec. But in my view there is even less reason to split,
because users have hardly any reason to look in a library.
Sunish Issac
I had not thought about sample files using multiple libraries.
If no other split is possible, may be we can atleast split by PIC10,12,16 and 18 families.
Sunish
--
Sebastien Lelong
Once upon a time samples were split by device. I was quite happy with this structure, because I could access all samples available for a given target. Then samples were all put into a single directory. And even if there were a lot of files, this flat structure was something easy to use (search for a sample not available for your PIC, using a feature, just to get some example code, ...). I now like this structure.
So, I agree with Rob, current structure does the trick, and splitting it isn't that easy. Since one sample can use multiple libraries, it can be that simply flat. Splitting by family is like splitting by device, you may get lots of file in PIC16, and not much in PIC10.
Splitting samples should bring a functionality other than "there are less files into a single directory". Jallib API doc (jalapi), for each library, provides samples using it. This is an interesting entry point. Since going from samples to libraries isn't that flat, maybe we can go further and start to build a database, queried from our website ("I want some samples using SPI library, whatever the PIC, or using 16F886, or using a PIC in PIC16 family, or using a PIC closed to mine, that is in the same datasheet, or the same datasheet as PIC X, Y, Z, ......)
Cheers,
Seb
Sebastien Lelong
0.5 beta1 release packages are available on group file section:
http://groups.google.com/group/jallib/files
Let me know if something's gone wrong. I've included tutorial PDF book in jallib-pack packages only.
Cheers,
Seb
Wayne
> Hi guys,
>
>
> 0.5 beta1 release packages are available on group file section:
>
> http://groups.google.com/group/jallib/files
>
>
> Let me know if something's gone wrong. I've included tutorial PDF book in
> jallib-pack packages only.
>
latest release?
Wayne
> Cheers,
> Seb
>
> 2009/12/6 Sebastien Lelong <sebastie...@gmail.com>
>
>> Hi guys,
>>
>>
>> Once upon a time samples were split by device. I was quite happy with this
>> structure, because I could access all samples available for a given target.
>> Then samples were all put into a single directory. And even if there were a
>> lot of files, this flat structure was something easy to use (search for a
>> sample not available for your PIC, using a feature, just to get some example
>> code, ...). I now like this structure.
>>
>> So, I agree with Rob, current structure does the trick, and splitting it
>> isn't that easy. Since one sample can use multiple libraries, it can be that
>> simply flat. Splitting by family is like splitting by device, you may get
>> lots of file in PIC16, and not much in PIC10.
>>
>> Splitting samples should bring a functionality other than "there are less
>> files into a single directory". Jallib API doc (jalapi), for each library,
>> provides samples using it. This is an interesting entry point. Since going
>> from samples to libraries isn't that flat, maybe we can go further and start
>> to build a database, queried from our website ("I want some samples using
>> SPI library, whatever the PIC, or using 16F886, or using a PIC in PIC16
>> family, or using a PIC closed to mine, that is in the same datasheet, or the
>> same datasheet as PIC X, Y, Z, ......)
>>
>>
>> Cheers,
>> Seb
>>
>>
>>
>>>> .
>>>> http://groups.google.com/group/jallib?hl=en.
>>>>
>>>>
>>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "jallib" group.
>>> To post to this group, send email to jal...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> .
Sebastien Lelong
Is there still a problem adding the 'm' version of the compiler to the
latest release?
You seem to really like this version :) What features/fixes should make jallib wait for a final release ?
I'm not in favor of releasing jallib with a beta compiler, but others may have a different opinion. What usually occur is jallib waits for compiler to release, then gets released after. We could wait, and we could also release more often.
Cheers,
Seb
To unsubscribe from this group, send email to jallib+un...@googlegroups.com.
Wayne
Search settings Google account settings
Advanced SearchSebastien Lelong wrote:
>> Is there still a problem adding the 'm' version of the compiler to the
>> latest release?
>>
>>
> You seem to really like this version :) What features/fixes should make
> jallib wait for a final release ?
> I'm not in favor of releasing jallib with a beta compiler, but others may
> have a different opinion. What usually occur is jallib waits for compiler to
> release, then gets released after. We could wait, and we could also release
> more often.
I do recall the Rob asked that we start testing with that version some
weeks ago. IIRC you were trying to get in into the latest bee version
around the beginning of November. I had the impression that we should
test it at assist Kyle. but I may be mistaken.
If you can't or don't want to include it it's OK with me. I don'r know
how or when Kyle will release it if no one helps test it though.
Don't mind me, I'm just a fly on the wall wanna be contributor to this
project.
I have another request while I'm able. Would it be possible to put in a
section of the Web page for users to ask questions of the Experts? I
think it would be a good source for the FAQ section. The current FAQ
page seems to be entice people to switch to JALv2, but is little help to
someone who has switched and wants to advance. JMHO
Wayne
>>>>>> For more options, visit this group at
>>>>>> http://groups.google.com/group/jallib?hl=en.
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>> Groups
>>>>> "jallib" group.
>>>>> To post to this group, send email to jal...@googlegroups.com.
>>>>> To unsubscribe from this group, send email to
>>>>> jallib+un...@googlegroups.com<jallib%2Bunsu...@googlegroups.com>
>>>>> For more options, visit this group at
>>>>> http://groups.google.com/group/jallib?hl=en.
>>>>>
>>>>
>>>> --
>>>> Sébastien Lelong
>>>> http://www.sirloon.net
>>>> http://sirbot.org
>>>>
>>>
>>>
>>
>> --
>>
>> You received this message because you are subscribed to the Google Groups
>> "jallib" group.
>> To post to this group, send email to jal...@googlegroups.com.
>> To unsubscribe from this group, send email to
Sebastien Lelong
I do recall the Rob asked that we start testing with that version some
weeks ago.
Right, buildbot uses 2.4m beta for its regular builds. Some of us exclusively uses 2.4m-beta.
IIRC you were trying to get in into the latest bee version
around the beginning of November. I had the impression that we should
test it at assist Kyle. but I may be mistaken.
Bee packages looks like final packages, and don't include beta compiler (that's what I think it should). Helping Kyle can be done without bee package :)
If you can't or don't want to include it it's OK with me. I don'r know
how or when Kyle will release it if no one helps test it though.
Again, helping Kyle can be done without bee. Or do I miss something ?
Don't mind me, I'm just a fly on the wall wanna be contributor to this
project.
I have another request while I'm able. Would it be possible to put in a
section of the Web page for users to ask questions of the Experts? I
think it would be a good source for the FAQ section. The current FAQ
page seems to be entice people to switch to JALv2, but is little help to
someone who has switched and wants to advance. JMHO
Nice idea ! How do imagine this can be done ? Question on mailling list, with different answers, that could be synthetized on website as a kind-of FAQ ?
Cheers,
Seb
To unsubscribe from this group, send email to jallib+un...@googlegroups.com.
Wayne
>>
>> I do recall the Rob asked that we start testing with that version some
>> weeks ago.
>
>
> Right, buildbot uses 2.4m beta for its regular builds. Some of us
> exclusively uses 2.4m-beta.
>
>
>> IIRC you were trying to get in into the latest bee version
>> around the beginning of November. I had the impression that we should
>> test it at assist Kyle. but I may be mistaken.
>>
>
> Bee packages looks like final packages, and don't include beta compiler
> (that's what I think it should). Helping Kyle can be done without bee
> package :)
list. Guess I must have been wrong again.
>
>> If you can't or don't want to include it it's OK with me. I don'r know
>> how or when Kyle will release it if no one helps test it though.
>>
>
> Again, helping Kyle can be done without bee. Or do I miss something ?
>
>
>> Don't mind me, I'm just a fly on the wall wanna be contributor to this
>> project.
>>
>> I have another request while I'm able. Would it be possible to put in a
>> section of the Web page for users to ask questions of the Experts? I
>> think it would be a good source for the FAQ section. The current FAQ
>> page seems to be entice people to switch to JALv2, but is little help to
>> someone who has switched and wants to advance. JMHO
>>
>>
> Nice idea ! How do imagine this can be done ? Question on mailling list,
> with different answers, that could be synthetized on website as a kind-of
> FAQ ?
post to here and the JalList to get it going.
Another would be a section added to the web page for questions from
users to ask questions. As I don't know anything about drupal though, I
don't know if that is possible or not.
Regarding the tutorial. I have been meaning to ask if the picture that
starts the "Getting Started" section could/should be made readable. If
it can, it might be informative if the pic could be identified. As it
is now it is just confusing, to me at least. It adds nothing to the
content of that section.
Sorry to have bothered you again. I'll get back to reading the list and
trying to progress to the next stage.
Regards
Wayne
>> <jallib%252Buns...@googlegroups.com<jallib%25252Bun...@googlegroups.com>
>>>>>>>> For more options, visit this group at
>>>>>>>> http://groups.google.com/group/jallib?hl=en.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> --
>>>>>>> You received this message because you are subscribed to the Google
>>>> Groups
>>>>>>> "jallib" group.
>>>>>>> To post to this group, send email to jal...@googlegroups.com.
>>>>>>> To unsubscribe from this group, send email to
>>>>>>> jallib+un...@googlegroups.com<jallib%2Bunsu...@googlegroups.com>
>> <jallib%2Bunsu...@googlegroups.com<jallib%252Buns...@googlegroups.com>
>> <jallib%252Buns...@googlegroups.com<jallib%25252Bun...@googlegroups.com>
>>>>>>> For more options, visit this group at
>>>>>>> http://groups.google.com/group/jallib?hl=en.
>>>>>>>
>>>>>> --
>>>>>> Sébastien Lelong
>>>>>> http://www.sirloon.net
>>>>>> http://sirbot.org
>>>>>>
>>>>>
>>>> --
>>>>
>>>> You received this message because you are subscribed to the Google
>> Groups
>>>> "jallib" group.
>>>> To post to this group, send email to jal...@googlegroups.com.
>>>> To unsubscribe from this group, send email to
>>>> jallib+un...@googlegroups.com<jallib%2Bunsu...@googlegroups.com>
Rob Hamerling
Hi Wayne,
Wayne wrote:
[about JalV2 2.4mbeta]
mattschinkel
>starts the "Getting Started" section could/should be made readable. If
>it can, it might be informative if the pic could be identified. As it
>is now it is just confusing, to me at least. It adds nothing to the
>content of that section.
That section didn't have any images at the beginning, so I wanted to
have something there.
I guess splitting the samples directory doesn't help too much, however
maybe the blink samples could go somewhere else. I like the database/
search idea.
Maybe a small program could be put in the jallib-pack that could
display or search the sample files. On the website would will nice but
it will take us some time.
I bet there are samples & libs that I have not seen that I may be
interested in, but just haven't noticed them.
Matt.
> >>>>>> Yes Rob. I was thinking of splitting the sample folder, not the
> >>>> lib/include
> >>>>>>> files.
> >>>>>>> I had not thought about sample files using multiple libraries.
>
> >>>>>>> If no other split is possible, may be we can atleast split by
> >>>> PIC10,12,16
> >>>>>>> and 18 families.
>
> >>>>>>> Sunish
>
> >>>>>>> On Sun, Dec 6, 2009 at 2:18 PM, Rob Hamerling <
> >>>> <jallib%2Bunsu...@googlegroups.com<jallib%252Bunsubscribe@googlegroups.com>
> >> <jallib%252Buns...@googlegroups.com<jallib%25252Bunsubscribe@googlegroups.com>
> >>>>>>>> For more options, visit this group at
> >>>>>>>>http://groups.google.com/group/jallib?hl=en.
>
> >>>>>>> --
> >>>>>>> You received this message because you are subscribed to the Google
> >>>> Groups
> >>>>>>> "jallib" group.
> >>>>>>> To post to this group, send email to jal...@googlegroups.com.
> >>>>>>> To unsubscribe from this group, send email to
> >>>>>>> jallib+un...@googlegroups.com<jallib%2Bunsu...@googlegroups.com>
> >>>> <jallib%2Bunsu...@googlegroups.com<jallib%252Bunsubscribe@googlegroups.com>
> >> <jallib%252Buns...@googlegroups.com<jallib%25252Bunsubscribe@googlegroups.com>
> >>>>>>> For more options, visit this group at
> >>>>>>>http://groups.google.com/group/jallib?hl=en.
>
> >>>>>> --
> >>>>>> Sébastien Lelong
> >>>>>>http://www.sirloon.net
> >>>>>>http://sirbot.org
>
> >>>> --
>
> >>>> You received this message because you are subscribed to the Google
> >> Groups
> >>>> "jallib" group.
> >>>> To post to this group, send email to jal...@googlegroups.com.
> >>>> To unsubscribe from this group, send email to
> >>>> jallib+un...@googlegroups.com<jallib%2Bunsu...@googlegroups.com>
> >>>> For more options, visit this group at
> >>>>http://groups.google.com/group/jallib?hl=en.
>
> >> --
>
> >> You received this message because you are subscribed to the Google Groups
> >> "jallib" group.
> >> To post to this group, send email to jal...@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> jallib+un...@googlegroups.com<jallib%2Bunsu...@googlegroups.com>
> >> .
> >> For more options, visit this group at
Sebastien Lelong
I bet there are samples & libs that I have not seen that I may be
interested in, but just haven't noticed them.
http://mientki.ruhosting.nl/pic-tools/jal/libs2/jal_libs_overview.html
Seb
Sebastien Lelong
I have another request while I'm able. Would it be possible to put in a
section of the Web page for users to ask questions of the Experts? I
think it would be a good source for the FAQ section. The current FAQ
page seems to be entice people to switch to JALv2, but is little help to
someone who has switched and wants to advance. JMHO
This dicussion has moved to "jalsitedev" group: http://groups.google.co.in/group/jalsitedev/browse_thread/thread/509065037f9574c0
You can join to give some more ideas !
Cheers,
Seb
To unsubscribe from this group, send email to jallib+un...@googlegroups.com.
William
Since we've got this new compiler from Kyle, may I suggest that we
delay the next release of JALLIB, until we've had time to get
comfortable with the new compiler?
I'm especially interested in a close review of the interrupt handlers
for the 18F devices. This may take some time.
William
mattschinkel
releases, but could we split the samples on SVN the same way the libs
are split? It's quite annoying to try to find my own samples when they
are mixed in the same directory.
Seb, check your email
Matt.
Rob Hamerling
William wrote:
> Since we've got this new compiler from Kyle, may I suggest that we
> delay the next release of JALLIB, until we've had time to get
> comfortable with the new compiler?
releases. On the other hand 2.4m(beta) fixes some nasty bugs of 2.4l, so
we better wait until the real 2.4m is released! My impression is that we
don't have to wait very long.
Regards, Rob
William
> Well, 2.4m is still in beta and we should not include beta-stuff in our
> releases. On the other hand 2.4m(beta) fixes some nasty bugs of 2.4l, so
> we better wait until the real 2.4m is released! My impression is that we
> don't have to wait very long.
>
version so far-- solved my interrupt grief instantly!
William
Sebastien Lelong
Well, 2.4m is still in beta and we should not include beta-stuff in our
releases. On the other hand 2.4m(beta) fixes some nasty bugs of 2.4l, so
we better wait until the real 2.4m is released! My impression is that we
don't have to wait very long.
Cheers,
Seb
mattschinkel
Matt.
Rob Hamerling
Hi Seb and others,
Sebastien Lelong wrote:
Let's wait for final compiler version.
> This will probably postpone 0.5 release to January. Happy new year release ?
Well, 2.4m seems to be stable and we still could release this year,
but a 'new year' release is fine with me too. We should not wait much
longer and show ourselves 'alive and kicking' on Jallist and maybe other
places.
Regards, Rob.
Sebastien Lelong
I agree, let's release ! I have some time for this these days :)
I'm preparing SVN and release packages, following http://code.google.com/p/jallib/wiki/ValidationProcess, or do you (or someone else) want to give a try ?
Cheers,
Seb
--
You received this message because you are subscribed to the Google Groups "jallib" group.
To post to this group, send email to jal...@googlegroups.com.
To unsubscribe from this group, send email to jallib+un...@googlegroups.com.
Rob Hamerling
Hi Seb and others
Sebastien Lelong wrote:
>
> I agree, let's release ! I have some time for this these days :)
> I'm preparing SVN and release packages, following
> http://code.google.com/p/jallib/wiki/ValidationProcess, or do you (or
> someone else) want to give a try ?
Please you've the most experience!
Below my latest TORELEASE analysis. There are still a few 'floating'
files which should either be removed or added tot TORELEASE: "whom the
cap fits, let him wear it".
Regards, Rob.
------------------------------------------------------------
Checking file /jallib/TORELEASE against contents of /jallib/
TORELEASE contains 202 device files
68 function libraries
415 samples in following categories:
(based on primary library)
5 ADC samples
205 blink samples
45 I2C samples
41 LCD samples
20 PWM samples
30 serial samples
18 USB samples
51 Other samples
15 project files
0 other files
Unreleased libraries (excluding unreleased device files)
--------------------------------------------------------
include/external/can/can_mcp2515.jal
include/external/can/mcp2515.jal
include/external/lcd/glcd_common.jal
include/external/lcd/js_replace.jal
include/external/lcd/lcd_dog_m_4.jal
include/external/lcd/lcd_dog_m_8.jal
include/external/lcd/lcd_dog_m_spi.jal
include/external/lcd/lcd_dsm0822a.jal
include/external/lcd/lcd_ks0108.jal
include/external/lcd/lcd_sterm_master.jal
include/external/media/mp3_decoder_sta015.jal
include/external/motor/period_skip/period_skip.jal
include/external/rtc/rtc_ds1302.jal
include/external/storage/eeprom/ee_25aa02e48.jal
include/external/temperature/temperature_sht.jal
include/jal/lowpassfilter.jal
include/jal/now.jal
include/jal/print_ng.jal
include/peripheral/can/can_legacy.jal
include/protocol/canopen.jal
include/protocol/can_ascii.jal
21 unreleased libraries (+ 104 unreleased device files)
Unreleased Samples (excluding unreleased blink samples)
-------------------------------------------------------
sample/16f648a_i2c_sw_master_check_bus.jal
sample/16f648a_i2c_sw_master_echo.jal
sample/16f648a_lcd_hd44780_4.jal
sample/16f648a_pwm_led.jal
sample/16f648a_pwm_led_highres.jal
sample/16f648a_pwm_sound.jal
sample/16f819_canopen_mcp2515_txhb.jal
sample/16f819_ee25aa02e48_lcd.jal
sample/16f819_mcp2515_can_monitor.jal
sample/16f876a_rtc_timeset.jal
sample/16f877a_keyboard.jal
sample/16f877a_lcd_hd44780_4.jal
sample/16f877a_pwm2.jal
sample/16f877a_pwm_led_highres.jal
sample/16f877a_pwm_sound.jal
sample/16f877a_rtc_timeset.jal
sample/16f877a_timer0_interval.jal
sample/16f877_period_skip.jal
sample/16f88_lcd_hd44780_4.jal
sample/16f88_serial_format.jal
sample/16f88_timer0_interval.jal
sample/18f14k50_blink_ii.jal
sample/18f2450_blink_ii.jal
sample/18f2585_can_monitor.jal
sample/18f2585_can_serial_adapter.jal
sample/18f2585_can_serial_hw.jal
sample/18f452_mp3_decoder_sta015.jal
sample/18f4550_blink_ii.jal
28 unreleased sample files (+ 104 blink samples)
Unreleased Project files
------------------------
project/delay_calibrate/delay_calibrate.jal
project/delay_calibrate/serial_hardware_hacked.jal
2 unreleased project files
Sebastien Lelong
Below my latest TORELEASE analysis. There are still a few 'floating'
files which should either be removed or added tot TORELEASE: "whom the
cap fits, let him wear it".
Or some not tested enough to be in TORELEASE.
I suggest we go with current repository, leaving these unreleased files. After all, if there are not in TORELEASE there must be a good reason, right ?
Seb
--
You received this message because you are subscribed to the Google Groups "jallib" group.
To post to this group, send email to jal...@googlegroups.com.
To unsubscribe from this group, send email to jallib+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
Joep Suijs
>>
> After all, if there are not in TORELEASE there must be a good reason, right
> ?
>
Joep
Rob Hamerling
Sebastien Lelong wrote:
>
> Below my latest TORELEASE analysis. There are still a few 'floating'
> files which should either be removed or added tot TORELEASE: "whom the
> cap fits, let him wear it".
>
>
> Or some not tested enough to be in TORELEASE.
> I suggest we go with current repository, leaving these unreleased files.
> After all, if there are not in TORELEASE there must be a good reason,
> right ?
Yes several may not be in TORELEASE for a good reason, but 'a few' are
present in Jallib for quite a long time. I have the impression these
have been forgotten by the original author(s).
Regards, Rob.
Sebastien Lelong
Packages are being uploaded. Can someone prepare an announce mail for jallist ?
Cheers,
Seb
--
You received this message because you are subscribed to the Google Groups "jallib" group.
To post to this group, send email to jal...@googlegroups.com.
To unsubscribe from this group, send email to jallib+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
Rob Hamerling
Sebastien Lelong wrote:
> Packages are being uploaded. Can someone prepare an announce mail for
> jallist ?
I've still the text of 0.4 which was my last turn.
For the volunteer I've attached the file!
Regards, Rob
Sebastien Lelong
as for me, I won't be able to do this before january 4th...
cheers
seb
--
Sébastien Lelong
Le 30 déc. 2009 à 19:55, Rob Hamerling <robham...@gmail.com> a
écrit :
> --
>
> You received this message because you are subscribed to the Google
> Groups "jallib" group.
> To post to this group, send email to jal...@googlegroups.com.
> To unsubscribe from this group, send email to jallib+un...@googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/group/jallib?hl=en
> .
>
>
>
> To JalV2 users,
>
> Release 0.4 of Jallib is available from the *Downloads* section of
> the *Jallib* project site, see the links at the bottom of this
> message. The *pack* files contain device files, function
> libraries, documentation in HTML format, the latest JalV2 compiler
> (version 2.4l) and numerous sample programs to help you to
> understand how to use the libraries and device files. We have also
> a shared *blog* where we explain how to use jallib, what can be
> done with it, common pitfalls, etc. This is "work in progress",
> but you can subscribe to this blog and stay in touch with us and
> read about our latest adventures :)
>
> The major enhancements in Jallib 0.4 are:
> - Includes the latest compiler version JalV2 2.4l.
> - More and improved device files, based on MPLab 8.33, extended
> with aliases for I/O pins such as pin_AN0, pin_SDI, pin_CCP1, etc.
> - More and improved libraries such as a new library for LCD
> backlight, I2C library now also for the 18Fs, queue libraries, a
> more precise delay library for a wider range of clock
> frequencies, a new library for Parallel ATA harddisk, completey
> rewritten ADC libraries, several enhancements and additions for USB.
> - Many more and enhanced sample programs.
> - Several new USB projects, among which an USB bootloader.
> For more details see the file CHANGELOG in the download packages.
>
> Note: The device files and some libraries in this version of
> Jallib require compiler version 2.4l because of the use of
> the new 'alias' keyword.
>
> Have fun, and inform us of your experiences with Jallib!
>
> The Jallib Team.
>
> Jallib project: http://code.google.com/p/jallib/
> Jallib team: http://code.google.com/p/jallib/people/list
> Jallib group: http://groups.google.com/group/jallib
> Jallib blog: http://jallib.blogspot.com/
>
>
William
I have some time over the next few days, to prepare some of my
libraries and samples for the release, if it isn't too late.
But it sounds like it is too late??
William
Sebastien Lelong
>
>
> I have some time over the next few days, to prepare some of my
> libraries and samples for the release, if it isn't too late.
>
> But it sounds like it is too late
it is... sorry :)
cheers
seb
>
William
no word at all since Dec 15, then you decide to release over a 24 hour
period, during the holidays. I don't think that was reasonable.
William
William
wrote:
> > But it sounds like it is too late
>
> it is... sorry :)
>
To show my good faith, I've added several libraries and samples to the
TORELEASE file.
And I've done so, within 48 hours of your mentioning wanting to do a
release (previously you said we would wait until the New Year). I
think this is a pretty good response, considering I was out of town
for part of the time in question. Also, I note that you only waited 5
hours from mention to 'branch'. Surely that was too hasty.
Please reconsider,
William
Rob Hamerling
Hi William,
William wrote:
> To show my good faith, I've added several libraries and samples to the
> TORELEASE file.
>
> And I've done so, within 48 hours of your mentioning wanting to do a
> release (previously you said we would wait until the New Year). I
> think this is a pretty good response, considering I was out of town
> for part of the time in question. Also, I note that you only waited 5
> hours from mention to 'branch'. Surely that was too hasty.
First of all and for everybody:
Happy new year and a fruitful collaboration in Jallib!
In defense of Seb: he was indeed quick, but release 0.5 was only
postponed due to the announcement of Kyle that compiler 2.4m was due.
That gave you 2 weeks extra for what you had to to with your Jallib
contributions.
And it is not so bad to miss the bus: at least we have new material for
release 0.6 which we could release any time, and we have weekly builds
for those who need your libs and samples desperately.
Regards, Rob.
Rob Hamerling
Hi Seb,
Sebastien Lelong wrote:
> Packages are being uploaded. Can someone prepare an announce mail for
> jallist ?
Since (almost) everybody seems to be on holiday, busy, offline or has
another reason not to do the announcement .... see Jallist.
William
>
> In defense of Seb: he was indeed quick, but release 0.5 was only
> postponed due to the announcement of Kyle that compiler 2.4m was due.
>
I also want to wish all a happy New Year.
But may I respectfully ask that we establish/document the finer
details of the release process. I would suggest at least a 48 hour
'final boarding call'.
Also, it seems unlikely that Kyle's latest official version has had
any serious testing with JALLIB. This is not good, in my opinion.
William
mattschinkel
reduce this to every 3 months?
We could also create a standard, or set dates for the next releases.
This way everyone has notice for the next release. If you miss the
release date, you may miss the bus.
jan 1st
march 1st
june 1st
sept 1st
Matt.
Sebastien Lelong
having fixed release dates doesn't make much sense IMO, releases
should be driven by content, not by dates.
cheers
seb
--
Sébastien Lelong
Le 1 janv. 2010 à 21:16, mattschinkel <mattsc...@hotmail.com> a
écrit :