How do I export the components of an app in Lotus Domino Designer? -

i have legacy lotus domino web application - database data, of course, javascript, resources - including png , jpg images, subforms html , css, etc.

i want export application - not data, app structure - can reuse images, html , css in other, more modern web frameworks (e.g. rails or nodejs or php or python or whatever) consume html templates , css , js files.

how export html, css, js, png, jpg, etc. is? happy take entire file structure shown in designer, want actual html/css/js/images/etc. in there.

i tried using "source control disk sync" option, files saved in strange domino-specific xml format, underlying html/css/etc stored hex. not helpful.

as example, might have in app shared elements\subforms\main.login.subform (and many others) like:

<style> #service-content {     background-color: #fff; }  label, input {     width: 100px;     display: inline-block;     padding: 3px 5px;     margin-bottom: 10px; }  input {     width: 300px; }  #login-message, h1 {     text-align: center; }    </style> <div style="width: 450px; margin: 0 auto">     <input type="hidden" value="/<computed value>/page?readform" name="redirectto" />      <h1>login</h1>         <!-- lots of html here --> </div> <!--// navigation --> 

i want extract (and others it).

edit:

as @andrewb pointed out in comments below, worth better explanation.

the domino app in question uses (mostly) static html , js retrieve data agents via ajax. ui (html/css/js) reusable backed, moderate amount of work.

but works if can original static pages out. these statics stored under resources\files\ or shared elements\subforms\

edit 2:

when turn off binary dxl export per @sjcaged, output above raw html looks following (this end):

<font name='courier new' pitch='fixed' truetype='true' familyid='30' color='#4200ff'/>"submit"</run> <run><font name='courier new' pitch='fixed' truetype='true' familyid='30'/> </run> <run><font name='courier new' pitch='fixed' truetype='true' familyid='30' color='purple'/>value</run>     <run><font name='courier new' pitch='fixed' truetype='true' familyid='30'/>=</run> <run><font name='courier new' pitch='fixed' truetype='true' familyid='30' color='#4200ff'/>"login"</run> <run><font name='courier new' pitch='fixed' truetype='true' familyid='30'/> </run> <run><font name='courier new' pitch='fixed' truetype='true' familyid='30' color='teal'/>&gt;&lt;/</run> <run><font name='courier new' pitch='fixed' truetype='true' familyid='30' color='#3f8080'/>div</run> <run><font name='courier new' pitch='fixed' truetype='true' familyid='30' color='teal'/>&gt;</run></par> <par def='3'><run><font name='courier new' pitch='fixed' truetype='true' familyid='30'/></run> <run><font name='courier new' pitch='fixed' truetype='true' familyid='30' color='teal'/>&lt;/</run> <run><font name='courier new' pitch='fixed' truetype='true' familyid='30' color='#3f8080'/>form</run> <run><font name='courier new' pitch='fixed' truetype='true' familyid='30' color='teal'/>&gt;</run></par> <par def='3'> <run><font name='courier new' pitch='fixed' truetype='true' familyid='30' color='teal'/>&lt;/</run> <run><font name='courier new' pitch='fixed' truetype='true' familyid='30' color='#3f8080'/>div</run> <run><font name='courier new' pitch='fixed' truetype='true' familyid='30' color='teal'/>&gt; </run></par> <par def='2'><run><font name='monospace'/>&lt;!--// navigation --&gt;</run></par></richtext>     </body> <item name='$$scriptname' summary='false' sign='true'><text>main.nav</text></item></subform> 

@deitch, there: want enable source control. how works synchronizes content of database (either automatically or manually) standard filesystem directory. see topic "setting source control enablement feature" more information.

to make work, though, requires changing preference. in designer, first go file | preferences | designer | source control. make sure "use binary dxl" not set. see topic "selecting way represent design elements on disk" more information on difference -- basically, using regular dxl separates design element data [i.e. code] dxl-formatted metadata wrapping design element has in database, binary dxl puts them both binary blob , prevents external applications being able edit them. there other options here well, see topic "setting source control enablement feature preferences" more information.

after done, (still in designer) right-click project, select "team development", , 'set source control application'. may or may not show splash screen , have select next, present dialog box asking type name of on-disk project. make sure second line points directory not yet exist (by default, "use default location" checkbox selected, point notes data directory , append whatever entered name on-disk project new directory name). when select finish, export eclipse virtual filesystem within nsf filesystem, using directory root.

(not perspectives show "team development" entry. notably, java perspective doesn't. domino designer perspective, however, does. change perspective, select window | open perspective , select perspective use.)

once done, can use external tools add directory source control [which always idea]; long "use binary dxl" unselected, can use external tools manipulate code , data considered part of application.