On Monday, June 30, 2014 2:04:57 PM UTC+2, Hamish Willee wrote:
>
> Hi Warren, MSC
>

Hi Hamish, thanks for the update!

On Tuesday, 24 June 2014 21:03:23 UTC+10, Warren Seine wrote:
>>
>> Regarding the documentation content, here's what I would suggest:
>>
>>    - clean up the demo list
>>       - separate demos from tools / engines / libraries (it's somehow 
>>       confusing right now)
>>    
>> At this point they are all demos, in the sense that they demonstrate C++ 
> code that was ported using emscripten.
>

My idea here was to separate the "wow effect" initiatives from 
emscripten-compatible C++ libraries. The first one is mostly to see what 
can be done. The second one has to avoid starting from scratch when porting 
code to HTML5. On the list, I can see Cocos2D, Box2D.js, Minko (disclaimer: 
I work for Aerys, the company behind Minko), Esenthel, Oryol, lzma.js, 
sql.js, all projects in the Programming Languages part...

Also, several links are broken (TeX), not relevant (Text-to-Speak) or even 
*spam* (OpenJPEG).
 

> We could separate them, but what would you group them as (they would not 
> be helpful top level headings). Some options:
> a) Rename "Demos" to "Emscripten-ported C++ code" to make it clear that 
> some of these are tools and frameworks. 
>

Pretty much everything would be "Emscripten-ported code". But considering 
my point above, not everything is a demo. Some are toolkits (de facto a 
demo, but re-usable).
 

> b) Just have good graphical demo examples here (e.g. the games section). 
> Move the other examples to their own wiki page and link from the bottom of 
> the demos section.
>
 
Yes, only keep up-to-date, amazing demos.

>
>>    - update the demo list with direct link to the code (if available) 
>>       and the actual demo
>>       - format it as a table ("name", "description", 
>>       "author", "submission date", "demo link", "source code")I
>>    
>>
> I have formatted the list in a table as suggested. I made the name into a 
> link, so perhaps should remove the "demo link" heading? 
>

Yes. 
 

> Is it worth having a "version" column for the Emscripten version?
>

Not IMHO. And it will be hard to collect.
 

> At this point my tidying the table further is not a priority. If anyone 
> wishes to take on this task or add the missing information, please be my 
> guest.
>

Ok.
 

> Thanks
> Hamish
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to