search

tt-acm / DesignExplorer

Design Explorer is an open source web interface for exploring multi-dimensional design spaces
http://tt-acm.github.io/DesignExplorer/
MIT License
102 stars 62 forks source link

Image hosting for free opensource design explorer? #18

Closed mnaugle-tt closed 9 years ago

mnaugle-tt commented 9 years ago

@mostaphaRoudsari @bhowes-tt --

thoughts on this one?

-1st, are we going to host a blank Design Explorer page on our site where anyone can come and upload data and populate their own interface? I had been assuming this was the idea, correct me if I am wrong.

-2nd, if so, it seems the csv file should just have a full url that points to an image of each iteration that the user hosts wherever they like. We can suggest dropbox or google photos in our documentation. This way the only thing they need to input into the page is their CSV file.

-3rd, maybe we do not enable 3D on this "free page"? Leave that to people that are willing to go to the future github page and get the source themselves?

mostaphaRoudsari commented 9 years ago
  1. Yes
  2. That's true. I was thinking the same.
  3. Why do you want to remove it from the free page? I think that is actually the most exciting part that can get so many people to click around. Are you concerned about generating the geometries? I'm still not sure what happened to va3c exporters from Grasshopper and Revit?
mnaugle-tt commented 9 years ago

Re: 3 -- yeah that was a bit of my hesitation. I guess if we get that out in the world at the same time as Design Explorer and we have a good tutorial about how it all works it will cross pollinate :smile_cat: some chatter for both projects!!

bhowes-tt commented 9 years ago

I agree on 1 and 2.

Re: 3. With a bit more work, we can get Spectacles to open a json file from a url (like dropbox). I tried (quickly) to get this working from google drive and ran into cross origin request security issues. It worked from dropbox and a github gist.

The Spectacles.Grasshopper and Spectacles.Revit exporters are alive and well as open github repos in our account. I have some clean up work to do in the Revit and WebViewer repos, and after that I'm planning on publicly releasing / promoting the project on our website, twitter, etc. It would be awesome if I could point to this project as an active Spectacles use case!!!

mostaphaRoudsari commented 9 years ago

Sounds like that the best strategy is to have them out together at the same time and make a big announcement. Should we start putting a deadline on this?

Do we want to release them at the Symposium? Or we can release them sooner and use it for promoting the symposium and the Hackathon. These projects won't be developed if we didn't have that hackathon! :thought_balloon:

bhowes-tt commented 9 years ago

I want to start promoting Spectacles soon ... like this week or next. There's still quite a lot to do, but I'd like to put it out there sooner rather than later and start spreading the word. How much more time is needed on the Design Explorer before it's presentable?

I don't think we need to publish Spectacles and the Design Explorer at exactly the same time... But both should be out there and working well before the symposium in my opinion. Publishing them close together will certainly help the marketing effort.

mnaugle-tt commented 9 years ago

yeah i don't think we want to actually publish them at the same time. do one then a week or two later put the other out. it helps keep the buzz going longer.

mostaphaRoudsari commented 9 years ago

Sounds good. Let's release Spectacles first and then design explorer as a case that it's getting used. Maybe within one week after each other? I think end of August is a pretty safe deadline to get DesignExplorer out there.

mnaugle-tt commented 9 years ago

I'd say we should have some live examples for each and some splash pages for both. Not sure what you had in mind for the 'release' of spectacles, but I've been assuming there will be other pages built around these to present (ie. brand) them as products and us as service providers for customization and implementation. Might be worth spending a little time discussing that sooner than later as there are a few pathways I can see us going down for public release.

bhowes-tt commented 9 years ago

Yes let's discuss further during the meeting on Thursday.

The plan as I understand it is to create a new page for each project in the /apps section of our website. So just like Platypus has a page in /apps that describes the project briefly and links out to food4rhino and a blog post or two, the project pages for these two can point to github, examples and demos, downloads, blog posts etc. We could add some copy about customization services on those pages too of course.

mostaphaRoudsari commented 9 years ago

Addressed 1 and 2 via b0e10f5b12cc56976a2431d4da446dfd07b3f4b3

@mnaugle-tt we can open a new issue with number 3 after tomorrow's meeting.