My 1.0 Plans > Re: Component developers: share your plans

Wed Feb 25 13:20:39 UTC 2009

I can help with the regex work if you like :)

On Tue, Feb 24, 2009 at 8:01 PM, Eli Cochran <eli at media.berkeley.edu> wrote:

> Hi folks,
>
> Here is my list of the Uplaoder. Sorry for how wordy this list is. Helps me
> make sense of it.
>
> It's all pretty much Uploader for me.
>
> • Reliable A-Grade browser support - Yes
>  > Goal #1
>    We must climb inside the SWFUpload Flash file and get it to display a
>    "real" button, one that can communicate its "button-ness" to the world.
> And
>    figure out how to get that button to release focus.
>
> • Gears support - No
>  > Unless Google changes it's file upload implementation to use the
> standard
>    multi-part form (and they will, we just don't know when) there really
>    isn't any point.
>
> • Implementation of new design features, possibly including:
>
>  • Improved error handling designs - Yes
>    > Do-able and worth doing.
>
>  • User-friendly upload time calculation - No
>    > Too much code to pull off reliably before 1.0. Implementation would
>      require careful tracking of the upload progress and then calculating
> the
>      projected time for the remaining files.
>
>      At best always a rough approximation dependent on many factors outside
> of
>      our control.
>
>  • Cancel/Done buttons - Yes
>    > Easy and worth doing.
>
>  • Elegant truncation of long file names - Yes
>    > Worth doing. Unsure of what it will take to pull it off. Hoping to
>      find some code out there that will get me most of the way there.
>      Otherwise, I can figure it out myself once we have a good pattern from
>      Erin.
>
> • Renewed Springboard example, including a "low-profile" or simple Uploader
>
>  • Tweaks to improve DOM agnosticism - Yes
>    > DOM agnosticism in the previous Springboard failed was because we were
>      using the "disabled" attribute of the <button> tag. Anchor tags do not
>      support disabled and so we needed another mechanism.
>
>      Yes, I think that we can pull this off. It's going to take some more
>      research and maybe some framework code.
>
>  • "Low-profile", simple Uploader - Probably not.
>    > We don't really have a design for this. But it would be worth doing to
>      test out some of our assumptions about the Uploader. Only if we can
> get
>      the rest done.
>
> What I need help with:
>
>    Colin (and maybe Jacob): help dissect and rework the SWFUpload Flash
> file.
>
>    Erin: Final designs for the Error messages and the File Name truncation.
>
>    Colin: lots of code reviews and sanity checking as I implement.
>
>    ??: If I need to write my own file name truncation code, a couple of
> hours
>    from a regular expression guru. Anyone?
>
> - Eli
>
> On Feb 23, 2009, at 10:27 AM, Colin Clark wrote:
>
>  Hi everyone,
>>
>> With a successful Infusion 0.8 behind us, we're looking to the next
>> release on deck: Infusion 1.0.
>>
>> As a community, we put together a wish list last month with the features
>> and improvements we're aiming for in the 1.0 release:
>>
>> http://wiki.fluidproject.org/display/fluid/Infusion+1.0+Wish+List
>>
>> Component developers, now is the time to sort through the wish list and
>> pick the features that you think can be made production-worthy over the next
>> four weeks. Take the opportunity to plan out your components and share your
>> roadmap with the mailing list. Be ruthless: favour stability, bug fixes, and
>> user experience over new features. You may also want to make a note of the
>> skills and resources you'll need to draw on from the community.
>>
>> 1.0 isn't the end; we're planning to continue the momentum of our regular
>> Infusion releases. So don't sweat it if you have to cut a few features to
>> get your component ready for this release. There will be plenty of
>> opportunities after March to keep growing Infusion as a community.
>>
>> If you need a hand with the process of breaking down your features and
>> estimating them, Michelle D'Souza is pretty experienced in this and can lend
>> a hand.
>>
>> Looking forward to hearing your plans,
>>
>> Colin
>>
>> ---
>> Colin Clark
>> Technical Lead, Fluid Project
>> Adaptive Technology Resource Centre, University of Toronto
>> http://fluidproject.org
>>
>> _______________________________________________________
>> fluid-work mailing list - fluid-work at fluidproject.org
>> To unsubscribe, change settings or access archives,
>> see http://fluidproject.org/mailman/listinfo/fluid-work
>>
>
> . . . . . . . . . . .  .  .   .    .      .         .              .
>               .
>
> Eli Cochran
> user interaction developer
> ETS, UC Berkeley
>
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work
>

-- 
Jacob Farber
University of Toronto - ATRC
Tel: (416) 946-3002
www.fluidproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20090225/aad1bb8a/attachment.html>