New thread. exchange. it's in bad shape. what do we do? as such right now we need to kill off what is there. i would want to focus on it being a code-side accessible service. not web page. that means that e's wallpaper/theme etc. dialogs access it. if you want to upload - lets make a client that lets you upload/contribute. lets remove the web part and just focus on the "extend e/efl content into web hosted and shared content". this makes it simpler, gets rid of the "framework" and leads to a nice http+text or soap etc. etc. server and everything done nicely via that and lib exchange + an app front end. some stand-alone elm based apps to do the upload + listing of content and download for now would be a good start.
-- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
