Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export to nlogo #248

Closed
mrerrormessage opened this issue Jun 22, 2015 · 6 comments
Closed

Export to nlogo #248

mrerrormessage opened this issue Jun 22, 2015 · 6 comments

Comments

@mrerrormessage
Copy link
Contributor

Should be able to save NetLogo Web files to nlogo file format.

@mrerrormessage mrerrormessage self-assigned this Jun 22, 2015
@mrerrormessage mrerrormessage added this to the Tortoise 1.0 milestone Jun 22, 2015
@SethTisue
Copy link
Contributor

#189, #193

(or is that different?)

@mrerrormessage
Copy link
Contributor Author

I believe this is a component of #193, but that doing #193 properly would involve more effort than just saving NLW files to the .nlogo file format.

@mrerrormessage
Copy link
Contributor Author

I've been working on this, and have it working in principle, but there are a few questions I wanted to discuss around the UI. Find here a screenshot of my current implementation's UI.
screen shot 2015-06-23 at 8 30 41 am
I would like some feedback on the UI, and in particular:

  • What is the correct place in the Galpagos UI for the "export to nlogo" button? It seems important enough that we don't want to hide it, but ancillary enough that we don't want to clutter up the main UI with it.
  • How do we want to handle filenames? For simplicity, I did the bare minimum and given all downloaded files the name "model.nlogo", testing show that it opens cleanly in NetLogo 5.2. To me, it seems like the best course of action would be to somehow choose a name when they elect to export the file.
    The other alternative is to deduce the file name from the name of the file the user started working from.

@qiemem
Copy link
Member

qiemem commented Jun 23, 2015

What is the correct place in the Galpagos UI for the "export to nlogo" button? It seems important enough that we don't want to hide it, but ancillary enough that we don't want to clutter up the main UI with it.

Next to the compile button perhaps.

How do we want to handle filenames? For simplicity, I did the bare minimum and given all downloaded files the name "model.nlogo", testing show that it opens cleanly in NetLogo 5.2. To me, it seems like the best course of action would be to somehow choose a name when they elect to export the file. The other alternative is to deduce the file name from the name of the file the user started working from.

Either of those options seem fine to me. We could also have a "name" field somewhere in the UI that the user fills out. Whether we use a persistent name field or a dialogue that comes up on save, I think it should be seeded with the name of the model they started working from.

@mrerrormessage
Copy link
Contributor Author

Sounds good. I'll start work on that. If there are other comments, we can discuss further.

@TheBizzle
Copy link
Member

Duplicate of #199.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants