[TYPO3-ect] lib/div: last milestone of alpha branch

Johnny Peck johnny at slipcasemedia.com
Fri Aug 31 13:09:26 CEST 2007


Nice.  Thank you Elmar.  I refreshed my repo on the 27th but I am going 
to refresh again and play for a bit.  I have a question for you 
regarding a particular project that is based on lib/div.  I recently 
delivered a project that included lib/div *TER* version, I believe is 
version *.24, but we are already working on upgrades and various (a ton 
it would seem) bugs. Those bugs are not necessarily within lib or div 
though, in fact the only things I have found are generally typos in 
naming or small performance issues that I can't even pin down on lib/div 
to be honest.  The quality of your work is no less than incredible.

My question is, should I scratch the lib/div implementation as it 
currently stands and rebuild with the latest SVN tag?  I would like this 
project to mature into using the Beta eventually though we don't really 
have the funding for frequent changes.  Would you recommend using this 
release to do the rebuild?  Our timeline follows.

You mentioned that the timeline for lib/div Beta has changed regarding 
the road map.  I know that timelines are great when planning(or planning 
again) but can become the bane of development very easily even when you 
work non-stop, continuously learning new approaches, etc. The project I 
am about to discuss was nearly 3 months(!) behind schedule, but we won't 
get into client issues too much here.  Do you have a new timeline for 
Beta release or is the ECT still targeting the middle of September?

Most important, would it be worthwhile for the development of lib/div 
for me to move to use the SVN version for a large project, when our 
timeline for the next release to the customer is about 4-6 weeks? 
During this migration, if we get the funding we need, how could we best 
document our work (which, unfortunately, the client wishes to keep quiet 
for some reason or another even after our pleas) and do you have any 
thoughts on the best approach to contribute what we have learned?  Bug 
reports are easy and if we find any I will probably try to fix them 
myself and file them as needed to the bugtracker or just send you a mail 
via this list or directly.

Documentation would be hard due to the non-disclosure issue though in 
reality our work should be GPL'd. I don't want to discuss the issues of 
confidentiality for clients as our work pretty much lays bare her entire 
company processes from tracking employees, receiving products, managing 
and tracking product, moving products, accounting for old or bad 
product, shipping, and interfacing with her accounting systems (a 
networked Intuit accounting situation and then some, ugh!), and a lot 
more.  I understand her decision as her industry is very competitive, 
JIT(just in time) inventory movement is the only option as the product 
is highly perishable, and forecasting inventory requirements is a 
serious advantage to her.  Having this software in the hands of 
competitors would not give her the advantage anymore, thus the situation 
I am in and the basis of her decision which I respect very much.  Given 
enough time though I do think we can convince her otherwise ;).

I guess I brought up two points of interest/questions:

Do you have a new projection for the Beta release and how, given the 
circumstances, can we use our work to contribute thoughtfully?  I 
suppose only we can figure out the second part.

and...

Where is the 'Business of TYPO3' mailing list?!? Yarr!!

I suppose I should contact Micheal Stucki on the second one and start a 
wiki page though I don't know if I could satisfactorily attend to such a 
thing.  Thoughts are welcome and I am sorry, Elmar, for hijacking your 
thread as it would seem.  Please forgive me!

One small note.. I recently began work on another project that involves 
lib/div (0.0.24 as of yesterday, 0.0.25 today!) and the DAM to deliver 
records to various mediums including Flash/Flex/Adobe AIR using JSON, 
AMFPHP, XML, or a grouping of them for delivery.  I can, and will, 
deliver this work to the TER when it is completed, tested, and well out 
of my 'let's try this scenario for kicks' phase of software development. 
;)  Don't expect this until the end of the year though, which is looming 
on the horizon :\, once again.  I think I am getting old, just don't 
tell anyone and Elmar, what are you planning for the new year and the 
new focus?  You have been remarking rather regularly about your 
departure.  Do you have another framework in mind?  A new field of 
interest?  Just curious.

Aloha,

Johnny

p.s. ECT rocks!  I brought up the idea of a TYPO3 song a long time ago I 
believe on the Off-Topic list.  Maybe it is time to revisit the idea? 
We'll see...

Elmar Hinz wrote:
> Oh, the little devil:
> 
> 
>> The important feature of this version is the result browser. I decided to
>> tag this versions in TER, but not to upload them to the TER, because there
>                     ^^^^^^^
>                     in SVN
> 
> 


More information about the TYPO3-team-extension-coordination mailing list