User talk:Omei/Cloud Lab Data Mining Tool: Difference between revisions

From Eterna Wiki

Latest comment: 14 July 2013 by Omei

(an idea)
(Path to integration with Eterna?)
Line 16: Line 16:
<p>Well, I was just thinking that it may solve (granted, in the long run) the cross-domain problem a little more elegantly than using GreaseMonkey...</p>
<p>Well, I was just thinking that it may solve (granted, in the long run) the cross-domain problem a little more elegantly than using GreaseMonkey...</p>
<p>-- [[User:ElNando888|ElNando888]] ([[User talk:ElNando888|talk]]) 07:30, 14 July 2013 (UTC)</p>
<p>-- [[User:ElNando888|ElNando888]] ([[User talk:ElNando888|talk]]) 07:30, 14 July 2013 (UTC)</p>
<p>----</p>
<p>I'm completely open to having the code integrated with Eterna.&nbsp; I didn't want to put off programming until I had all the answers to procedural questions, so I just got to work in an environment I knew I could be productive in.&nbsp; I figured that once I had something worhwhile to show Jee, we could discuss how it might best be made more widely available.</p>
<p>I'm not clear on the relationship between the git repository and the development server.&nbsp; Is code deposited into git automatically accessible to scripts running on the development server?&nbsp; Or does someone manually vet them and then copy them to the server?&nbsp; And is there a provision for user-provided html, or only javascript libraries?&nbsp;</p>
<p>Is there a mechanism already in place where&nbsp;</p>
<ol>
<li>I could easily update .html and .js files, and</li>
<li>Users could load the html in their own browser window?&nbsp; (Even with full support for HTML, I don't think the little output frame in the current scripting interface would make a satisfactory platform for the kind of report I envision.)</li>
</ol>
<p>If so, I would probably start doing that now.&nbsp; My main concern is not getting too many users too quickly, because I don't want to end up spending all my time on documentation and support instead of development.&nbsp; Because of that, having it only on the development server for now would be a plus, not a negative.</p>
<p>[[User:Omei|Omei]] ([[User talk:Omei|talk]]) 20:52, 14 July 2013 (UTC)</p>

Revision as of 20:52, 14 July 2013

== Volunteer ==

Hi Omei,

I think this is indeed a serious difficulty in current Cloud Lab, and I salute your effort. I'd like to offer my help. There isn't much I can do at the code level (I'm a C/C++ developer, not a web/javascript guru), but I'm known in my professional circle for being quite talented at finding bugs, even in source code I'm unfamiliar with. And if nothing else, I'd love to beta-test, since there has been a few times where I needed a question answered, and had to manually browse the labs in search of relevant SHAPE data.

Just let me know how can I be of assistance :)

-- ElNando888 (talk) 06:02, 4 July 2013 (UTC)Reply[reply]

PS: I'm going to make minor edits to the page, not changing anything, just linking things a bit. Just revert the edit if you have objections.

----

No objections at all to you enhancing the page.  Thx.  As to skill sets, I'm not a web web/javascript guru either. As an independent software developer, I've worked in a lot of different environments, but embedded systems in C/C++ work represents a plurality, if not a majority, of my work. If you want to install the Greasemonkey plugin (easy, even if you haven't had experience with it), I'll send you the code any time you want.

Omei (talk) 17:53, 4 July 2013 (UTC)Reply[reply]

----

Just send it any time you want, and don't worry about me, I'll deal with GreaseMonkey (and any other dependencies) without bothering you more than necessary :)

-- ElNando888 (talk) 09:54, 6 July 2013 (UTC)Reply[reply]

----

Hi Omei,

I'm not sure if it would make any sense or help in any way, but have you considered the possibility of integrating part of your code in EteRNA directly? In other words, I'm asking if you are aware that the dev team have opened a door for third party code, at https://github.com/EteRNAgame/EteRNA-Script-Interface ? There are a few examples of pieces of code at https://github.com/EteRNAgame/EteRNA-Script-Interface/tree/master/Eterna/library As you can see, a few players submitted some code. The ViennaRNA ports to javascript are from me, and Justin also created the LibNando.js with a few silly snippets that I wrote earlier for the scripting interface. What I mean to say, is that you could have a LibOmei.js there too. At first, this code would only be available on the development server (eternadev.org), but if enough players "push" to have it on the production server, it could be available for all.

Well, I was just thinking that it may solve (granted, in the long run) the cross-domain problem a little more elegantly than using GreaseMonkey...

-- ElNando888 (talk) 07:30, 14 July 2013 (UTC)Reply[reply]

----

I'm completely open to having the code integrated with Eterna.  I didn't want to put off programming until I had all the answers to procedural questions, so I just got to work in an environment I knew I could be productive in.  I figured that once I had something worhwhile to show Jee, we could discuss how it might best be made more widely available.

I'm not clear on the relationship between the git repository and the development server.  Is code deposited into git automatically accessible to scripts running on the development server?  Or does someone manually vet them and then copy them to the server?  And is there a provision for user-provided html, or only javascript libraries? 

Is there a mechanism already in place where 

  1. I could easily update .html and .js files, and
  2. Users could load the html in their own browser window?  (Even with full support for HTML, I don't think the little output frame in the current scripting interface would make a satisfactory platform for the kind of report I envision.)

If so, I would probably start doing that now.  My main concern is not getting too many users too quickly, because I don't want to end up spending all my time on documentation and support instead of development.  Because of that, having it only on the development server for now would be a plus, not a negative.

Omei (talk) 20:52, 14 July 2013 (UTC)Reply[reply]