-
Notifications
You must be signed in to change notification settings - Fork 17
/
About_us.html
526 lines (454 loc) · 30.7 KB
/
About_us.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
<!DOCTYPE html>
<!--[if lt IE 7]> <html class="ie ie6 lt-ie9 lt-ie8 lt-ie7" lang="en"> <![endif]-->
<!--[if IE 7]> <html class="ie ie7 lt-ie9 lt-ie8" lang="en"> <![endif]-->
<!--[if IE 8]> <html class="ie ie8 lt-ie9" lang="en"> <![endif]-->
<!--[if IE 9]> <html class="ie ie9" lang="en"> <![endif]-->
<!--[if !IE]><!-->
<html lang="en" class="no-ie">
<!--<![endif]-->
<!-- Mirrored from themicon.co/theme/beadmin/ by HTTrack Website Copier/3.x [XR&CO'2014], Fri, 29 Jan 2016 16:44:20 GMT -->
<head>
<!-- Meta-->
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=0">
<meta name="description" content="">
<meta name="keywords" content="">
<meta name="author" content="">
<title>About Us</title>
<!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries -->
<!--[if lt IE 9]><script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script><script src="https://oss.maxcdn.com/libs/respond.js/1.4.2/respond.min.js"></script><![endif]-->
<!-- Bootstrap CSS-->
<link rel="stylesheet" href="app/css/bootstrap.css">
<!-- Vendor CSS-->
<link rel="stylesheet" href="vendor/fontawesome/css/font-awesome.min.css">
<link rel="stylesheet" href="vendor/animo/animate%2banimo.css">
<link rel="stylesheet" href="vendor/csspinner/csspinner.min.css">
<link rel="shortcut icon" type="image/png" href="img/favicon.jpg"/>
<!-- START Page Custom CSS-->
<!-- END Page Custom CSS-->
<!-- App CSS-->
<link rel="stylesheet" href="app/css/app.css">
<!-- Modernizr JS Script-->
<script src="vendor/modernizr/modernizr.js" type="application/javascript"></script>
<!-- FastClick for mobiles-->
<script src="vendor/fastclick/fastclick.js" type="application/javascript"></script>
</head>
<body>
<!-- START Main wrapper-->
<div class="wrapper">
<!-- START Top Navbar-->
<nav role="navigation" class="navbar navbar-default navbar-top navbar-fixed-top">
<!-- START navbar header-->
<div class="navbar-header" >
<a href="#" class="navbar-brand">
<div>
<h3>eXpOS<span style="color:#14ddb3">NITC<span></h3>
</div>
</a>
</div>
<!-- END navbar header-->
<!-- START Nav wrapper-->
<div class="nav-wrapper" style="background:black">
<!-- START Left navbar-->
<ul class="nav navbar-nav">
<li>
<!-- Button used to collapse the left sidebar. Only visible on tablet and desktops-->
<!--a href="#" data-toggle-state="aside-collapsed" class="hidden-xs">
<em class="fa fa-navicon"></em>
</a>
<!-- Button to show/hide the sidebar on mobile. Visible on mobile only.-->
<a href="#" data-toggle-state="aside-toggled" class="visible-xs">
<em class="fa fa-navicon"></em>
</a>
</li>
<li>
<h3 class="pull-right" style="color:white"> About Us</h3>
</li>
</ul>
<!-- END Left navbar-->
</div>
<!-- END Nav wrapper-->
</nav>
<!-- END Top Navbar-->
<!-- START aside-->
<aside class="aside">
<!-- START Sidebar (left)-->
<nav class="sidebar">
<ul class="nav">
<!-- START Menu-->
<li id="home">
<a href="index.html" title="Home" data-toggle="" class="no-submenu">
<em class="fa fa-home"></em>
<span class="item-text">Home</span>
</a>
</li>
<li>
<a href="documentation.html" title="Documentation" data-toggle="" class="no-submenu">
<em class="fa fa-files-o"></em>
<span class="item-text">Documentation</span>
</a>
</li>
<li>
<a href="Roadmap.html" target="_blank" title="Roadmap" data-toggle="" class="no-submenu">
<em class="fa fa-road"></em>
<span class="item-text">Roadmap</span>
</a>
</li>
<!-- <li>
<em class="fa fa-download"></em>
<span class="item-text">Downloads</span>
</a> </li>-->
<li>
<a href="faq.html" title="FAQ" data-toggle="" class="no-submenu">
<em class="fa fa-question"></em>
<span class="item-text">FAQ</span>
</a>
</li>
<li>
<a href="googlegroup.html" title="googlegroup" data-toggle="" class="no-submenu">
<em class="fa fa-link"></em>
<span class="item-text">Google Group</span>
</a>
</li>
<li>
<a href="https://exposnitc.github.io/user-contrib/" target="_blank" title="user-contrib" data-toggle=""
class="no-submenu">
<em class="fa fa-link"></em>
<span class="item-text">User Contributions</span>
</a>
</li>
<li>
<a href="feedback.html" title="Feedback" data-toggle="" class="no-submenu">
<em class="fa fa-comments"></em>
<span class="item-text">Student Feedback</span>
</a>
</li>
<li class="active">
<a href="About_us.html" title="About Us" data-toggle="" class="no-submenu">
<em class="fa fa-group"></em>
<span class="item-text">About Us</span>
</a>
</li>
<li>
<a href="http://xosnitc.github.io" title="Read about XOS" class=" no-submenu" >
<em class="fa fa-link"></em>
<span class="item-text">Read about XOS</span>
</a>
</li>
<!-- END Menu-->
</ul>
<span style="position: absolute; bottom: 40px;color:white;" >National Institute of Technology, Calicut</span>
<a style="position: absolute; bottom: 2px; right: 2px" rel="license" href="http://creativecommons.org/licenses/by-nc/4.0/"><img alt="Creative Commons License" style="border-width:0" src="./img/creativecommons.png" /></a>
</nav>
<!-- END Sidebar (left)-->
</aside>
<!-- END aside-->
<!-- START Main section-->
<section id="philosophy" style="text-align:justify;font-size:17px">
<!-- START Page content-->
<div class="content-wrapper">
<div class="row">
<!-- START dashboard main content-->
<div class="col-lg-12">
<!-- START widget-->
<h3>eXpOS Philosophy</h3>
<p>Any pedagogical operating system project offered as part of an undergraduate junior level operating system course needs to satisfy two requirements:</p>
<ol>
<li>The student must be given as much depth and detail as possible about the central operating system concepts.</li>
<li>The quantity of work involved must not exceed what a student is able to do in a four month semester.</li>
</ol>
<p>The problem before the teacher is to decide on how much compromise on (1) must be done in favour of (2). eXpOS is our stance in this matter.</p>
<br/>
<p>There are three central principles that have been kept in mind in designing the eXpOS educational tool:</p>
<ol type="a">
<li><a href="https://en.wikipedia.org/wiki/Edsger_W._Dijkstra" target="_blank">“Separation of concerns”</a></li>
<li><a href="https://en.wikipedia.org/wiki/Albert_Einstein" target="_blank">“Things shall be made as simple as possible, but no simpler”</a></li>
<li><a href="https://en.wikipedia.org/wiki/Fred_Brooks" target="_blank">“Build to learn” rather than “learn to build.”</a></li>
</ol>
<p>These thoughts have translated into the following decisions:</p>
<ol>
<li>Keep the upward and downward interfaces of the OS kernel idealistically simple – This means:
<ol type="a">
<li>The architecture platform on which the OS is implemented is kept simple to understand and program, yet capable of supporting virtual memory, interrupt driven disk/IO, time sharing, exception handling, demand paging etc.</li>
<li>The application programming interface (<a href="http://exposnitc.github.io/os_spec.html#collapse1" target="_blank">API</a>) (and the application binary interface <a href="http://exposnitc.github.io/abi.html" target="_blank"> (ABI) </a>) provided by the OS are kept simple and minimal. </li>
</ol>
</li>
<li>The <a href="os_spec.html" target="_blank">OS specification</a> has been kept as simple as possible from the viewpoint of the OS programmer. The OS features are minimal, some of them being:
<ol type="a">
<li><a href="https://en.wikipedia.org/wiki/Cooperative_multitasking" target="_blank">co-operative multi-tasking</a> </li>
<li>a simple single-directory file system where processes can create, write, read and delete data files </li>
<li>provision for processes to share files and memory </li>
<li>primitives for interprocess communication (binary semaphores) and process synchronization (signal-wait) </li>
<li>support for multiple users</li>
<li>demand-paged memory management </li>
</ol>
</li>
<li>The OS code has to be completely written by the student with no built-in code given, except for a bootstrap ROM code and code implementing an <a href="abi.html#library">application level library interface</a>. The programming support has been kept minimal to avoid high level programming tools hiding too many low level issues from the OS programmer. Essentially, the student has to do “low level programming” on a “high level hardware".</li>
<li>The system is designed to help the student appreciate the functioning of a “sufficiently complex” operating system and <b>not</b> to help him/her gain experience with real operating systems programming. The architecture, the OS, the API, ABI etc. are all different from any of the existing real systems or standards in use, but designed to make the task of programming the OS as simple as possible.</li>
</ol>
<hr style="border-color:black;border-width:1px">
<p>Since the operating system kernel is a software that forms a layer between the hardware and the application program, the first major hurdle that a student faces while writing an OS is in understanding the complexities of the underlying hardware.</p>
<p>The eXpOS package simplifies this by providing a hypothetical simple-to-program hardware abstraction – the <a href="arch_spec.html" target="_blank">XSM Machine</a>. What makes XSM simple is that its memory words can store an arbitrary string or a number. This means that data formatting – one of the major technicalities while working with machines - is simplified. Further simplifications include the assumption that each disk block fits into exactly one memory page etc. The OS code can be written by programming the machine using a simple to learn <a href="support_tools-files/spl.html" target="_blank">SPL language</a> (which is just an enriched XSM assembler). </p>
<p>The second interface of the OS is its upward interface – the interface to application programs. This interface, called the application binary interface (<a href="abi.html" target="_blank"> ABI </a>), defines the low level system call interface between the application and the OS, the virtual address space model for an application, the format of executable files etc. The ABI too is kept minimal. It is easy to load executables into the memory. Only small programs are permitted. Parameter passing between applications and the system calls is also extremely simple.</p>
<p>The eXpOS <a href="abi.html" target="_blank"> ABI </a> is too primitive to support application programs in the C programming language. Hence we provide a separate language (called <a href="support_tools-files/expl.html" target="_blank">ExpL</a>) using which applications can be created and compiled. The ExpL compiler given to the student supports the eXpOS high level application program interface (<a href="os_spec.html#collapse1" target="_blank">API</a>). We note here that, implementing an ExpL compiler for the eXpOS ABI on the XSM machine would be an instructive exercise for an undergraduate compiler design laboratory. (See <a href="https://silcnitc.github.io">ExpL compiler project</a>.)</p>
<p>We are of the view that insisting the student to work with real systems diverts his/her attention to the details of various “formats, standards and interfaces" which often comes in the way of appreciating the underlying principles of OS design. eXpOS separates concerns by providing minimal interfaces that are just sufficient to achieve the required functionality.</p>
<p>The development methodology suggested is to start from scratch with a simple bootstrap loader. Routines for handling the timer, disk and I/O devices shall be added next. A simple program loader that can load and execute applications from the disk can be written at this point. Single process operation will be possible at this stage. Following this, modules to support multi-tasking, Interprocess communication and process synchronization can be added. A file system can now be built on top of this structure. Multi-user support may be added next and finally full scale virtual memory management with swapping and demand paging shall be implemented. (A final stage adding support for multiprocessor operation is also intended.) The <a href="Roadmap.html"target="_blank">roadmap</a> guides the student systematically through these stages, asking him/her to follow the links and learn the concepts relevant to the OS modules developed in each stage.</p>
<hr style="border-color:black;border-width:1px">
<p>There are two aspects associated with the design and implementation of each major component of an OS. – 1) A Policy and 2) An implementation Mechanism.</p>
<p>For example, the OS may specify a policy that each process is allowed it's own logical address space starting from 0 to a particular limit. Paging is a hardware mechanism that allows the OS to implement the policy. As another example, child processes inheriting open file instances from its parent process is a policy. The mechanism used by eXpOS to implement the policy is to keep a shared file seek position in an open file table. </p>
<p>The pedagogical strategy followed here is to keep policies excessively simple so that the student can easily implement the policy, once the implementation mechanism is understood. For instance, in this project, size of the address space of a process is fixed by the OS, the file system does not have a directory structure and so on. To quickly prepare the students for the implementation, we provide detailed tutorials on various implementation mechanisms (like hardware paging) necessary to implement the policies. Our belief is that once the student completes the implementation of a simple policy using a particular mechanism, she will be in a position to visualize the implementation of more sophisticated policies that uses similar mechanisms without actually going through another implementation project. </p>
<p>It is our belief that the experiment will provide the student with a feel for how the OS modules for process management, memory management, file management, device management, inter-process communication, process sychronization, demand paging and user management can be glued together to form a functional operating system. An appreciation for the Operating System's hardware interface, application interface and run time library linkage is also intended.</p>
<p>We had tried our best to ensure that the spirit of the subject matter is not lost. However there have been compromises. The multi-user support, the file system and device handling are very primitive. Address space of a process is small and cannot expand at run time. Going further in these directions would make it difficult for the project to be completed in a semester. Some of these extensions are not “in principle” hard, once the basic OS is built. However topics such as pre-emptive multitasking, fault tolerance, system security etc. are beyond the scope of this project.</p>
<hr style="border-color:black;border-width:1px">
<p>The project presumes that the student has undergone a basic sophomore course in computer organization and data structures and has either completed or is currently undergoing a theory course in operating systems. The project does not require the student to be familar with the principles of compilers. It is not expected that the student has a high level of proficiency in programming or computer hardware. The required background on paging hardware, interrupts, runtime stack of application programs etc. are provided as reading material at appropriate places in the project roadmap. The parameter passing convention of ExpL as well as the system call interface are pretty simple so that students will have no serious difficulty in extracting parameters inside system calls and sending back return values to the application, despite not having undergone a compiler design course.</p>
<p>It must be emphasized that the project by no means a replacement to a theory course in operating systems,
but is only designed to suppliment it. </p>
<p>eXpOS evolved from an earlier version (called <a href="http://xosnitc.github.io/" target="_blank">XOS</a>) which was successfully used for undergraduate instruction at the department of Computer Science and Engineering, NIT Calicut. eXpOS extends XOS with multiuser support, cooperative multitasking, interrupt based disk transfer and interprocess communication facility. Both these platforms were developed by teams of undergraduate CSE students of NIT Calicut through a series of undergraduate major projects. <!--Maintenance and user support for the system are being provided by a team of volunteers through a <a href="https://groups.google.com/forum/#!forum/xos-users" target="_blank">user's mailing list</a>-->.</p>
<h3>Authors</h3>
<!-- <p>XOS/eXpOS was contributed by the following student groups in National Institute of Technology, Calicut from 2010 onwards under the guidance of Dr. K Murali Krishnan ([email protected]).
<br/>
<!-- <span style="color:red">Disclaimer:</span> The reports provided below may contain errors that are not corrected.
</p>-->
<p>
The content in the website and the documentation has been authored in the Department of Computer Science and Engineering, <a href="http://nitc.ac.in" target="_blank">National Institute of Technology, Calicut</a> under the guidance of Dr. Murali Krishnan K. The project's activity started in the year 2010 and is currently under progress. Below is a list of co-authors and contributors to the project. The work evolved from an earlier version of the project called the <a href="https://xosnitc.github.io" target="_blank">XOS project</a> under the guidance of Dr. Murali Krishnan K.
</p>
<div class="panel-body">
<!--2019-->
<div class="panel-group" id="accordion">
<div class="panel panel-default">
<div class="panel-heading">
<h4 class="panel-title">
<a >2018-19</a>
</h4>
</div>
<div >
<div class="panel-body">
<table class="table table-bordered" style="text-align: center;">
<tr class="info">
<th style="text-align: center;"><span class="fa fa-group" style="color:black"></span> Group Members</th>
</tr>
<tr>
<td>Arun Joseph, Rohith Vishnumolakala</td>
</tr>
</table>
</div>
</div>
</div>
</div>
<!--2018-->
<div class="panel-group" id="accordion">
<div class="panel panel-default">
<div class="panel-heading">
<h4 class="panel-title">
<a >2017-18</a>
</h4>
</div>
<div >
<div class="panel-body">
<table class="table table-bordered" style="text-align: center;">
<tr class="info">
<th style="text-align: center;"><span class="fa fa-group" style="color:black"></span> Group Members</th>
</tr>
<tr>
<td>Kandhala Naveena, Navaneeth Kishore, Sumedha Birajdar</td>
</tr>
</table>
</div>
</div>
</div>
</div>
<!--end of 2018-->
<!--2017-->
<div class="panel-group" id="accordion">
<div class="panel panel-default">
<div class="panel-heading">
<h4 class="panel-title">
<a >2016-17</a>
</h4>
</div>
<div >
<div class="panel-body">
<table class="table table-bordered" style="text-align: center;">
<tr class="info">
<th style="text-align: center;"><span class="fa fa-group" style="color:black"></span> Group Members</th>
</tr>
<tr>
<td>Akhil S, Karthika Aravind</td>
</tr>
<tr>
<td>N Ruthvik, Thallam Sai Sree Datta</td>
</tr>
</table>
</div>
</div>
</div>
</div>
<!--end of 2017-->
<!--2015-->
<div class="panel-group" id="accordion">
<div class="panel panel-default">
<div class="panel-heading">
<h4 class="panel-title">
<a >2015-16</a>
</h4>
</div>
<div >
<div class="panel-body">
<table class="table table-bordered" style="text-align: center;">
<tr class="info">
<th style="text-align: center;"><span class="fa fa-group" style="color:black"></span> Group Members</th>
</tr>
<tr>
<td>Anjana Babu, Christin V Jose, Kurian Jacob, Leny W V</td>
</td>
</tr>
<tr>
<td>Aleena Thomas, Reshma Sreekumar, Reshma Thomas</td>
</tr>
<tr>
<td>Nunnaguppala Surya Harsha, Vishnupriya Matha</td>
</tr>
</table>
</div>
</div>
</div>
</div>
<!--end of 2015-->
<!--2014-->
<div class="panel-group" id="accordion">
<div class="panel panel-default">
<div class="panel-heading">
<h4 class="panel-title">
<a >2014-15</a>
</h4>
</div>
<div >
<div class="panel-body">
<table class="table table-bordered" style="text-align: center;">
<tr class="info">
<th style="text-align: center;"><span class="fa fa-group" style="color:black"></span> Group Members</th>
</tr>
<tr>
<td>Kruthika Suresh Ved, Sikha V Manoj, Sonia V Mathew</td>
</tr>
<tr>
<td>Aswathy T Revi, Subhisha</td>
</tr>
<tr>
<td>Gautham R Warrier, Glen Martin, Govind R</td>
</tr>
</table>
</div>
</div>
</div>
</div>
<!--end of 2014-->
<!--2012-->
<div class="panel-group" id="accordion">
<div class="panel panel-default">
<div class="panel-heading">
<h4 class="panel-title">
<a >2012-13</a>
</h4>
</div>
<div>
<div class="panel-body">
<table class="table table-bordered" style="text-align: center;">
<tr class="info">
<th style="text-align: center;"><span class="fa fa-group" style="color:black"></span> Group Members</th>
</tr>
<tr>
<td>Shamil C M, Sreeraj S, Vivek Anand T Kallampally</td>
</tr>
</table>
</div>
</div>
</div>
</div>
<!--end of 2012-->
<!--2011-->
<div class="panel-group" id="accordion">
<div class="panel panel-default">
<div class="panel-heading">
<h4 class="panel-title">
<a >2010-12</a>
</h4>
</div>
<div >
<div class="panel-body">
<table class="table table-bordered" style="text-align: center;">
<tr class="info">
<th style="text-align: center;"><span class="fa fa-group" style="color:black"></span> Group Members</th>
</tr>
<tr>
<td>Ajeet Kumar, Albin Suresh, Avinash, Deepak Goyal, <br/>Jeril K George, K Dinesh, Mathew Kumpalamthanam,
Naseem Iqbal, <br/>Nitish Kumar, Ramnath Jayachandran, Sathyam Doraswamy, <br/> Sumesh B, Yogesh Mishra</td>
</tr>
</table>
</div>
</div>
</div>
</div>
<!-- end of 2011-->
<!-- Technical Contributors -->
<div class="panel-group" id="accordion">
<div class="panel panel-default">
<div class="panel-heading">
<h4 class="panel-title">
<a >Technical Contributors</a>
</h4>
</div>
<div>
<div class="panel-body">
<table class="table table-bordered" style="text-align: center;">
<tr>
<td>Shajahan Fariz, Nikhil Sojan</td>
</tr>
</table>
</div>
</div>
</div>
</div>
</div>
<h3>License</h3><br>
<a rel="license" href="http://creativecommons.org/licenses/by-nc/4.0/"><img alt="Creative Commons License" style="border-width:0" src="img/creativecommons.png" /></a><br><br>
<p>eXpOS by Dr. Murali Krishnan K, Department of Computer Science and Engineering, National Institute of Technology, Calicut is licensed under a <a href="http://creativecommons.org/licenses/by-nc/4.0/">Creative Commons Attribution-NonCommercial 4.0 International License</a>. Based on a work at <a href="https://github.com/eXpOSNitc/">https://github.com/eXpOSNitc</a></p>
<h3>Acknowledgement</h3>
<p>We thank GitHub for providing the free for use platform on which this tutoring system has been hosted. We also thank an uncountable collecton of individuals who have supported the work in one form or the other.</p>
</div>
</section>
<!-- END dashboard main content-->
</div>
</div>
<!-- END Page content-->
</section>
<!-- END Main section-->
</div>
<!-- END Main wrapper-->
<!-- START Scripts-->
<!-- Main vendor Scripts-->
<script src="vendor/jquery/jquery.min.js"></script>
<script src="vendor/bootstrap/js/bootstrap.min.js"></script>
<!-- Plugins-->
<script src="vendor/chosen/chosen.jquery.min.js"></script>
<script src="vendor/slider/js/bootstrap-slider.js"></script>
<script src="vendor/filestyle/bootstrap-filestyle.min.js"></script>
<!-- Animo-->
<script src="vendor/animo/animo.min.js"></script>
<!-- Sparklines-->
<script src="vendor/sparklines/jquery.sparkline.min.js"></script>
<!-- Slimscroll-->
<script src="vendor/slimscroll/jquery.slimscroll.min.js"></script>
<!-- Store + JSON-->
<script src="vendor/store/store%2bjson2.min.js"></script>
<!-- ScreenFull-->
<script src="vendor/screenfull/screenfull.min.js"></script>
<!-- START Page Custom Script-->
<!--[if lt IE 8]><script src="js/excanvas.min.js"></script><![endif]-->
<!-- END Page Custom Script-->
<!-- App Main-->
<script src="app/js/app.js"></script>
<!-- END Scripts-->
</body>
<!-- Mirrored from themicon.co/theme/beadmin/ by HTTrack Website Copier/3.x [XR&CO'2014], Fri, 29 Jan 2016 16:47:29 GMT -->
</html>