So sorry - if any one responded to this post - my server has crashed
for the last couple of days and all email has been down... 

If anyone has a response for my post (below) please send to
uglyshz-at-gmail.com - thank you:)

--- In flexcoders@yahoogroups.com, "1charmedlife" <[EMAIL PROTECTED]> wrote:
>
> Hi All,
> 
> I'm a total noob to Flex, after years of working in Flash MX and doing
> my own web work for 1.0 companies who wanted Flashy Things, I got out
> of the business, but am now going into a business that very much will
> need a custom application and it looks like Flex is probably a
> suitable platform.
> 
> We're looking to achieve the following:
> 
> 1. Our application needs to work cross-platform/cross-browser and
> include (on the flashy side) something like the  DisplayShelf Component 
>
<http://www.quietlyscheming.com/blog/components/tutorial-displayshelf-co\
> mponent/>  over at QuietlyScheming
> GUI for asset collections.  Navigating through a picture of the
> asset, then selecting the image should bring up all the underlying
> asset data.  We do not yet have a spec on what kind of database this
> should all be kept in but are open to suggestions.
> 
> 2. Application will include "sharable" databases (users can decide to
> make their collection of assets browseable by other members or not).
> 
> 3. Application will include transactional orders by users (no
> eCommerce at this time - tranactional components are billable to
> physical users accounts only).
> 
> 4. Application itself will be free - so use of Open Source code or
> code under MIT license is preferable.
> 
> So, in light of those things, the questions I have are:
> 
> 1. Is Flex an appropriate platform for something like this?
> 
> 2. What's the best way to find folks who might want to bid on or
> otherwise get involved with our project?
> 
> We're an alpha stage company running on um... our day jobs and a few
> credit cards at this point, so anyone willing to help us get a scope
> of work, time and labor requirements, etc. would help us a lot!
> 
> Thanks for your answers or suggestions:)
>


Reply via email to