-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.xml
571 lines (571 loc) · 62.3 KB
/
index.xml
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
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>IMI Showtime</title>
<link>https://htw-imi-showtime.github.io/staging/</link>
<description>Recent content on IMI Showtime</description>
<generator>Hugo</generator>
<language>de-de</language>
<atom:link href="https://htw-imi-showtime.github.io/staging/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Challanges</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m5-mov.io/challanges/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m5-mov.io/challanges/</guid>
<description>Ideation Struggles The extensive ideation phase challenged the team as each member brought different perspectives, which led to difficulties in agreeing on a unified vision for mov.io. Uncertainty about the most appropriate technology required thorough research to make an informed decision. In addition, each team member brought unique insights, requiring additional effort to synthesize ideas and define key features, which impacted the initial stages of project build. Learning Curve of New Technologies Incorporating a range of new technologies, each assigned to a specific team member, presented a multi-faceted challenge.</description>
</item>
<item>
<title>Features</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b2-makesign/features/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b2-makesign/features/</guid>
<description>Features Using Makesign, you can project your own pictures, posters and GIFs on a screen and manage your content with an easy-to-use interface at any time. Create slideshows, choosing how long each of the images are being displayed. For dynamic displays, such as the dashboard, where you can see what tool is booked for how long, you can simply create a website and connect it with the system. The projection runs via a Raspberry Pi, which means you can connect them to basically any screen you have lying around and give them a new life.</description>
</item>
<item>
<title>Features</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b1-peek/features/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b1-peek/features/</guid>
<description>Features Visualisation through Charts Each Key existing in the documents of your collection receives their own chart window. In it, all the values of that key from the documents will be displayed in an aggregated way. Depending on the type of the key that aggregation may be in form of a pie chart, bar chart or list. That gives you a quick overview of the existing values and their occurrences.</description>
</item>
<item>
<title>Features</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b4-hypnobuddy/features/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b4-hypnobuddy/features/</guid>
<description>Dos And Don&#39;ts Guide Introducing our Dos and Don&rsquo;ts Guide: a specialized feature designed exclusively for parents in the Hypno Buddy app. This guide, created by therapists and linked directly to the patient, offers practical tips for daily life, categorizing advice to address common challenges. Unlike resources for children, parents access personalized recommendations, ensuring relevance to their unique situation. The feature, derived from therapist interviews, reflects a concise suggestion to enhance the overall effectiveness of the therapeutic process.</description>
</item>
<item>
<title>Features</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b5-smartlibrary/features/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b5-smartlibrary/features/</guid>
<description>Features Keyword extraction:
Moodle Course: By reading keywords from course names, course descriptions and keywords added by the educators we remove common words, which are stored in a blacklist, such as &ldquo;a,&rdquo; &ldquo;an,&rdquo; etc. (Functionality and blacklist sourced from beliefmedia.com). SmartLibrary constructs SQL queries from the extracted keywords to read material names and links associated with the keywords from the database.
Crawler: We built a crawler which can extract learning material names and keywords from the HTML code of websites such as Coursera.</description>
</item>
<item>
<title>Features</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b7-ar-interaction-city/features/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b7-ar-interaction-city/features/</guid>
<description>Communication Wi-Fi To ensure that our hardware can communicate smoothly in the same network, we use a Raspberry Pi as a WLAN hotspot. This ensures an uninterrupted connection and enables our devices to work together optimally.
MQTT Communication takes place via MQTT, an open network protocol for machine-to-machine communication. The Arduino uses the MQTT protocol to send messages to the Raspberry Pi, which acts as an MQTT broker. At the same time, the HoloLens glasses subscribe to these messages to receive real-time information.</description>
</item>
<item>
<title>Features</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m3-lep/features/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m3-lep/features/</guid>
<description>Efficient automated semester planning With just a few clicks, faculty staff can effortlessly generate a complete schedule for each course of study throughout the entire semester. Taking into account factors from module duration and rhythm to teacher&rsquo;s mandatory events, availability, and preferences, LEP utilizes Timefold to makes sure everything fits together well, making planning simple and hassle-free. Role-Based UI for seamless collaboration Say goodbye to mailing back and forth spreadsheets!</description>
</item>
<item>
<title>Features</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m5-mov.io/features/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m5-mov.io/features/</guid>
<description>Interactive WebApp Engaging Virtual Collaboration
Step into a world of seamless collaboration with our Interactive Web - App, an engaging and responsive platform designed to facilitate user interaction in a virtual environment. Our focus is on creating a dynamic space that encourages effortless collaboration and enhances the overall user experience.
Virtual Office Replicating Physical Office Online
Bring the essence of a physical office into the digital realm with our Virtual Office.</description>
</item>
<item>
<title>Future</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m5-mov.io/future/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m5-mov.io/future/</guid>
<description>As we look to the future of mov.io, our vision goes beyond a simple virtual office platform - we envision a dynamic and customisable ecosystem that truly adapts to the individual preferences and needs of our users.
Unleash personalisation A key aspect of our future plans revolves around providing users with an unprecedented level of customisation. Imagine having the freedom to design and personalize your virtual office space, from room layout to overall aesthetics.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b2-makesign/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b2-makesign/process/</guid>
<description>Process At the beginning of the project, we had a kick-off meeting with Prof. Dr. Barne, our project supervisor, and Martin Holzhauer, our lead connection to the IDiA Makerspace. Martin explained his needs for the digital signage, which considers showing ads for the Makerspace and most importantly, the booking reservations of the IDiA booking website. To get a general idea on digital signage, we looked around the campus for already existing digital signage use cases for inspiration, as well as possible cases, in which it might be practical to implement.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b1-peek/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b1-peek/process/</guid>
<description>Process Since our project had a lot do to with displaying data so it&rsquo;s easy to understand, we first created a concept of what our application should look like in Figma. The user should be able to navigate the interface easily, without immediately being overwhelmed. To do that, we decided that the application should have a simple login interface and once logged in, the user should be presented with only the necessary options first, navigating deeper into the interface as needed.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b7-ar-interaction-city/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b7-ar-interaction-city/process/</guid>
<description>Organization The project began with a kick-off meeting in which the basic project idea was explained and requirements defined. We also immediately set weekly meeting times that fit into everyone&rsquo;s schedule. In the weeks that followed, we collected ideas for implementation and entered them as issues in our issue tracker, set up the individual parts of the project and started implementing solutions. In the weekly meetings, we informed each other about the project status and discussed our next steps.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m4-gamingforthefuture/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m4-gamingforthefuture/process/</guid>
<description>Initial Meetings Discussed the project with the product owners to identify the core problem related to water scarcity in Brandenburg. Received relevant documents from Rebecca for further understanding. Communication and Iteration We engaged in back-and-forth communication with product owners to refine the project details every week. Flow Charts Developed flow charts to map out the game. Then we created initial prototypes and designs using Figma to visualize the project. Programming We programmed mostly in Unity.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m5-mov.io/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m5-mov.io/process/</guid>
<description>Research At the start of our development journey, we devoted a significant amount of time to in-depth research. Our goal? To get inside the user&rsquo;s world, to understand the challenges they face on a daily basis, whether in a traditional office or in the rapidly evolving landscape of remote working. We dug deep to uncover the pros and cons and shed light on the finer details of their working environment.</description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b2-makesign/techstack/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b2-makesign/techstack/</guid>
<description> Communication Zoom Whatsapp Signal Discord Organization Github Google-Docs Programming Bootstrap Javascript Ruby on Rails Rubymine Shell Ubuntu Visual Studio Code CSS Design Figma Utility Docker </description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b4-sempy/techstack/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b4-sempy/techstack/</guid>
<description> Projektmanagement Miro Github Discord Whatsapp Design / Styling CSS Bootstrap Miro HTML Chromeextension JavaScript Backend Python OpenAI API YouTubeAPI Flask </description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b1-peek/techstack/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b1-peek/techstack/</guid>
<description> Communication Discord Zoom Planning Notion Figma Programming Visual Studio Code React NextJS ExpressJS GitHub Utility MongoDB Docker Image Sources https://es.logodownload.org/discord-logo/ https://es.logodownload.org/zoom-logo/ https://logos-download.com/40130-notion-app-logo-download.html https://es.logodownload.org/?s=figma https://logospng.org/logo-visual-studio-code/ https://logos-download.com/9747-react-logo-download.html https://creazilla.com/nodes/3244252-nextjs-icon https://www.mementotech.in/nodejs-development-company-rajkot.html https://logodix.com/github-resume https://www.kindpng.com/imgv/hhJbRxJ_mongodb-logo-png-transparent-png/ https://iconduck.com/icons/94225/docker-icon </description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b2-mobile-multitouch-multiplayer/tech-stack/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b2-mobile-multitouch-multiplayer/tech-stack/</guid>
<description>Project Management In our project toolkit, we used various tools to keep things organized and clear. Notion was our main hub, providing flexibility along with the helpful Education Abo Option. Google Apps, such as TaskBoard for daily tasks and Calendar for sprint scheduling, helped us stay on course easily.
To see our progress visually, we created a lively Miro board connected to our Gantt Chart, adding color and energy to our project tracking.</description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b2-mobile-multitouch-multiplayer/tech_stack/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b2-mobile-multitouch-multiplayer/tech_stack/</guid>
<description>Project Management In our project toolkit, we used various tools to keep things organized and clear. Notion was our main hub, providing flexibility along with the helpful Education Abo Option. Google Apps, such as TaskBoard for daily tasks and Calendar for sprint scheduling, helped us stay on course easily.
To see our progress visually, we created a lively Miro board connected to our Gantt Chart, adding color and energy to our project tracking.</description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b4-hypnobuddy/techstack/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b4-hypnobuddy/techstack/</guid>
<description> Projektmanagement Miro Github Discord Zoom Whatsapp Design / Styling Figma SCSS &amp; CSS Bootstrap Frontend TypeScript React Vite Backend NodeJS Express JS TypeScript Mongo DB Passport JS DevOps &amp; Deployment Docker Github Actions Jest (Unit Testing) Cypress (End-to-End Tests) Firebase Terraform Google Cloud Platform </description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b7-ar-interaction-city/technology/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b7-ar-interaction-city/technology/</guid>
<description>Organisation and Communication We used Mattermost for our internal communication and for issue tracking.
Mattermost Development HoloLens To develop the AR/XR App that is running on the HoloLens 2 we used Visual Studio (Code) and Unity with MRTK2.
Programming Language: C# Raspberry The Raspberry Pi runs the Debian Raspberry Distribution and is the communication middleware. It serves as the MQTT broker and the Wi-Fi hotspot that the Arduino and HoloLens connect too.</description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m4-gamingforthefuture/techstack/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m4-gamingforthefuture/techstack/</guid>
<description> Tech Stack For this project we used mainly the Unity Engine to develop the game. Other programs that we used were Figma,Photoshop. Sometimes we had to use Blender as well. Coding was done in Rider or Visual Studio. Music was produced with Fl Studo and Garageband. Discord and Zoom were used for communication.
Tech Stack </description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m5-mov.io/techstack/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m5-mov.io/techstack/</guid>
<description> Organization GitLab NX Gather.town Figma &amp; FigJam Zoom Frontend Vue3 Nuxt3 TailwindCSS PhaserJS WebRTC Backend Express Socket.IO MongoDB </description>
</item>
<item>
<title>Terminology</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m1-somethinar/terminology/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m1-somethinar/terminology/</guid>
<description>Terminology Even though we&rsquo;ve spent a lot of time working with extended reality, we sometimes find ourselves questioning the precise terms used in this field. So, we thought it couldn&rsquo;t be different for you and decided to create a brief guide to some of the most frequently used terms in the world of XR: Virtual Reality (VR) Virtual Reality is a fully immersive digital environment where the user is completely surrounded by a computer-generated world.</description>
</item>
<item>
<title>Challenges</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b2-mobile-multitouch-multiplayer/challenges/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b2-mobile-multitouch-multiplayer/challenges/</guid>
<description>Getting to Grips with Unity Our journey into game development kicked off with Unity, and it was a learning curve. Understanding the ropes of this platform required time and effort, especially as we shifted from conventional programming mindsets. Yet, the more we dived in, the more we discovered Unity&rsquo;s flexibility and the wealth of pre-packaged tools it offered, turning our initial challenges into stepping stones for growth. Mastering Multitouch In our quest to make games accessible to mobile players, we encountered the challenge of implementing multitouch functionality.</description>
</item>
<item>
<title>Future</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b7-ar-interaction-city/future/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b7-ar-interaction-city/future/</guid>
<description>Future Our project is very open and creates a basis for extended reality. You can consider incorporating new interactions, such as switches or touch panels, or changing the platform and running the project on a tablet or VR glasses. New use cases can also be devised and tested. This project could be used very well in industry for maintenance work on machines and establish communication from the machine to the goggles.</description>
</item>
<item>
<title>Gameplay</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b2-mobile-multitouch-multiplayer/gameplay/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b2-mobile-multitouch-multiplayer/gameplay/</guid>
<description>Bringing Bobola to Life It all started with a sweet idea - a cute main character, and you, the player, saving it. No time to waste, so we jumped into Unity, made our main character, Bobola, and got into coding. Urgency was our guide to keep things moving.
Bobola&#39;s Story To make the game more engaging, we introduced falling objects to save Bobola. Originally, we planned to use coconuts, but we stumbled upon spike shields in the Unity Asset Store.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b4-hypnobuddy/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b4-hypnobuddy/process/</guid>
<description>Our development journey can be broken down into distinct phases, each contributing to the evolution of our vision. Let&rsquo;s explore the key milestones that shaped our project from its inception to the current stage. Preparation: Setting the Foundation Before diving into the technicalities, our team initiated the project by agreeing on a concrete problem within the realm of therapy that we aimed to solve. We defined major responsibilities, sharing our preferences and experiences to foster effective collaboration.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b5-smartlibrary/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b5-smartlibrary/process/</guid>
<description>Process We dedicated initial time to conceptualising the idea for the plugin, exploring its potential impact and benefits. This involved learning from Moodle Academy about building Moodle plugins and creating first drafts to outline key functionalities.
With a clearer vision, we strategically divided the overall idea into smaller, manageable tasks. Each task was designed to contribute to the overarching goal of the plugin.
Adopting agile methodologies, we embraced a collaborative and iterative approach.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m1-somethinar/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m1-somethinar/process/</guid>
<description>Collecting ideas At the beginning of our project, we had a clear goal in mind: to create a game using the Meta Quest 3 headsets provided by HTW, with a focus on multiplayer elements and mixed reality features. To get our project off the ground, we started with some hands-on exploration. We tested various games that were compatible with the Quest 3, and we even took a trip to Cosmic.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m3-lep/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m3-lep/process/</guid>
<description>Research In the project&rsquo;s initial phase, we conducted thorough research to establish a robust foundation for our web application. This involved exploring diverse technology stacks, evaluating programming languages, databases, and frameworks. We studied similar applications for inspiration and best practices. The implementation of timetable and schedule-solving algorithms was a key focus, with a careful assessment of existing solutions. We directly engaged with the planning team, gaining insights into manual planning methods and specific requirements.</description>
</item>
<item>
<title>Challenges</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m3-lep/challenges/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m3-lep/challenges/</guid>
<description>UX-UI Design In the initial stages of development, one key challenge our team faced was designing a user interface (UI) that effectively accommodates the input of constraints and preferences from teachers. None of us is a professional UX-UI designer, therefore, creating an appealing and simple UI for admin or teachers to specify their requirements posed a significant hurdle, as it required striking a balance between complexity and user-friendliness. We undertook several brainstorming sessions ensuring that the UI could be used efficiently without overwhelming the user.</description>
</item>
<item>
<title>Gameplay</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m1-somethinar/gameplay/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m1-somethinar/gameplay/</guid>
<description>Put your headset on and enter another world Pop on the Meta Quest headset and jump into a different world that&rsquo;s full of fun and surprises. You&rsquo;ll find yourself surronded by a virtual forest behind your own walls where you can explore, discover, and just have a good time with your friends. It&rsquo;s not just about playing; it&rsquo;s about stepping into a whole new place that feels as real as your sourroundings.</description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b5-smartlibrary/techstack/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b5-smartlibrary/techstack/</guid>
<description> Tech Stack Our tech stack consists of the following tools &amp; technologies: </description>
</item>
<item>
<title>Challenges</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m1-somethinar/challenges/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m1-somethinar/challenges/</guid>
<description>Integrating Meta SDKs with Unity Integrating the Meta XR All-in-One SDK from Oculus wasn&rsquo;t as seamless as we hoped it would be. The setup process for this package was complex and sometimes inconsistent. We were required to adhere to a strict implementation with limited flexibility for customization.
Additionally, the SDK tends to generate a lot of debug messages in the console, which are often unnecessary and can hide more critical information.</description>
</item>
<item>
<title>Future</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b5-smartlibrary/future/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b5-smartlibrary/future/</guid>
<description>Future NLP Integration:
As part of our ongoing development, we are planning to extract keywords from learning materials on Moodle by converting PDF Files with educator’s learning materials into searchable text using a PDF Reader Library. Subsequently, we analyse the text for keywords using Natural Language Processing. This comprehensive approach ensures that the SmartLibrary plugin not only remains cutting-edge but also addresses diverse content formats, including PDF materials.</description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m3-lep/techstack/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m3-lep/techstack/</guid>
<description>App Development Java &amp; Spring Boot The backbone of our back-end, chosen for its powerful suite of features that simplify the development of stand-alone applications with minimal configuration.
MongoDB Our NoSQL database of choice, allowing for flexible data schema and efficient, scalable storage of application data.
TimeFold Integrated as the core engine for intelligent and automated scheduling, ensuring optimal allocation of resources and efficient timetabling.
ReactJS &amp; TypeScript Our core frontend framework, enabling us to build a dynamic, interactive user interface with type-checking for a reliable and scalable application.</description>
</item>
<item>
<title>Future</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m3-lep/future/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m3-lep/future/</guid>
<description>Consideration of further Rhythm Types In our current version, we&rsquo;ve handled regulations dealing with the most common rhythms, ensuring LEP factors in weekly and biweekly module planning for time collisions as well as special constraints.
We understand that exceptions, demand more consideration and code restructuring in future to enhance adaptability. Especially one-time events like introductions at the start of semester have to be handled differently as well as unique faculty-specific rhythms like 3x6, where the module starts slightly delayed in the semester, initially five times every two weeks and then ends on a single day during the penultimate month of the semester.</description>
</item>
<item>
<title>Future</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m4-gamingforthefuture/future/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m4-gamingforthefuture/future/</guid>
<description>Future Prospect: Add visualisation of biodiversity aspects Further development of different levels Improvement of tile influence algorithm Further implementation of localization Gameplay improvement
Where we’re at: Currently, Gaming for Future only contains one level for presentation purpose Algorithm for influence of each biome tile is developed Achieved our goal, which is to emphasize the crucial issue of water scarcity E-Mail collector is implemented Available only in 2 languages</description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m1-somethinar/tech-stack/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m1-somethinar/tech-stack/</guid>
<description>VR Headsets Oculus We used the Meta Quest 3 VR headsets and the Oculus software with Unity for running and testing our application. Game Engine Unity Unity provided the core framework for developing our game, offering both 2D and 3D capabilities essential for our project. Networking Photon Fusion 2 We chose Photon Fusion 2 for its handling capabilities of multiplayer game synchronization and networking. XR Interactions Meta XR All-in-One SDK The Meta XR All-in-One SDK was our key asset for implementing immersive XR interactions in our game.</description>
</item>
<item>
<title>Future</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m1-somethinar/future/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m1-somethinar/future/</guid>
<description>Further Potential of our Game During the initial stages of our game development, we brainstormed numerous ideas that, due to the fact that we spent a lot of time working on the colocation, couldn&rsquo;t be realized in the current version. This section highlights some of these concepts to showcase the underlying potential and future directions our game could take. Collecting upgrades and special skills One idea we have is to introduce a system where players can collect upgrades and special skills throughout the game.</description>
</item>
<item>
<title>Features</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b4-sempy/features/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b4-sempy/features/</guid>
<description>Features SEMPY-Button on the idealo Website. Our SEMPY Button offers a relaxed shopping experience that provides customers with recommendations based on the information from the three major platforms: idealo, Amazon, and YouTube. Whether the customer is interested in products like a &ldquo;Victorinox Huntsman&rdquo;, an &ldquo;MSR Hubba Hubba 2 NX&rdquo;, or &ldquo;Apple AirPods 3&rdquo;, the SEMPY-AI Tool caters to the customer&rsquo;s individual needs.
SEMPY-modal on the idealo Website. We take information from idealo, YouTube and Amazon and give them to the OpenAi to process and summarize them.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b1-infinite-zoom/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b1-infinite-zoom/process/</guid>
<description>Process The first step into our project was deciding on a game engine to create it with. After evaluating various options, we chose Godot, an open-source software that supports both its own programming language, GDScript, and C#. Our team used both languages.
Once the technical decisions were made, we all worked in parallel. Some of us started by focusing on developing the mechanics for a zoom effect in a 3D environment, while others concentrated on implementing smooth player motion.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b4-sempy/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b4-sempy/process/</guid>
<description>Process Pipeline of data processing. At the beginning of the project, there was a brainstorming phase where we wanted to define how our project should look like at the end of the semester. Initially, we thought of having a tool where customers could have a conversation on the idealo website and ask everything about the product. We took inspiration from Perplexity AI, ChatGPT, and similar AI tools.
After a long discussion, we concluded that we would generate the output of the OpenAI API and place it on the website.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b5-pam/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b5-pam/process/</guid>
<description>Process The Project was both a technologically tricky undertaking, and a means for us to learn how programming projects will work in the future, with a large focus on Agile Development and SCRUM-style Progress management. We started by setting up a regular Scrum Schedule. Sprints were undertaken on a bi-weekly basis, with remote progress meetings every second week between the sprints, regularly on Wednesdays. We started off by examining the original site, and taking a look at the programming language that had been chosen for us.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/master/m1-gaming-for-future/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/master/m1-gaming-for-future/process/</guid>
<description>Initial Meetings The three of us, who had worked on the simulation last semester, provided the new team members with a brief introduction to the codebase and detailed information about water scarcity, our algorithms, and other essential aspects. Communication and Iteration We held weekly Scrum meetings with product owners to iterate on and refine project details, working in sprints to ensure continuous progress and alignment with our goals. Programming Workflow We managed our Source Code using the Gitflow Workflow and GitLab.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/master/m3-cognicity/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/master/m3-cognicity/process/</guid>
<description>Research As the very first step of our research, we read studies and articles on the topic of cognitive skills and how they can be tested to get an idea of what cognitive skills there are and how they could be measured. We also performed a market analysis to see what existing games with a similar focus are out there and what we could learn from them. Simultaneously, we already collected ideas for possible minigames we could implement to help enhance specific cognitive skills and researched possibilities to motivate our users to keep training.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/master/m4-orgxtract/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/master/m4-orgxtract/process/</guid>
<description>Defining our Problem To understand the problem better, we took a deep dive into the composition of organizational charts of German authorities. Every organizational chart not only looked different but also did not follow the same structure. The only thing they had in common was their format: PDF. We had a lot of discussion with the Open Knowledge Foundation about their objective to make these organizational charts machine-readable. Their answer was straightforward: To make research easier and, above all, faster.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/master/m5-capsearch/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/master/m5-capsearch/process/</guid>
<description> Process Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla facilisis neque id vulputate malesuada. Quisque dignissim finibus urna sed sagittis. </description>
</item>
<item>
<title>Challenges</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/master/m4-orgxtract/challenges/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/master/m4-orgxtract/challenges/</guid>
<description>Large Amounts of Data According to the Federal Office of Administration, there are a total of 966 federal authorities and institutions in Germany (Statista, 20.07.2024). However, there are many more, as the statistics do not include the offices at state level. One of the challenges of the project was to create a tool that would fit as many different organizational charts as possible in order to capture as much data as feasible.</description>
</item>
<item>
<title>Features</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b1-infinite-zoom/features/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b1-infinite-zoom/features/</guid>
<description>Features Zoom Effect We have used different implementations to visualize this effect. In some scenes, the objects are scaled up while the camera stays static; in others, the camera moves forward as the objects keep in their position.
Transitions When one scene is finished, the game transforms you into a new one, creating an endless loop.
Gameplay In this game, the player starts with three lives. Colliding with an obstacle decreases half a heart from their health.</description>
</item>
<item>
<title>Features</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b5-pam/features/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b5-pam/features/</guid>
<description>Features Completely Updated Codebase The original PAM was written in Springboot/Vaadin. The new PAM is written in React/Typescript, with usage of Figma for the design amongst other tools. Of course, this meant re-working the Tool from the ground-up in order to get all the old features working, before adding new features down the line. *
New Design The original PAM was not as appealing to the eye as it could be.</description>
</item>
<item>
<title>Features</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/master/m1-gaming-for-future/features/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/master/m1-gaming-for-future/features/</guid>
<description>Features Supervised tile based gridmap interactions Map interactions are controlled and supervised in order to restrict specific player interactions, removing some of the previous sandbox-aspect of the game.
Ground water level sensitive game winning conditions Player actions directly influence groundwater levels. These influence changes are computed by respecting a data-table though and built to try and mimic somereal-life behavior in the environment.
Reviving species Such objectives are displayed in the form of quests and can be achieved in the game by modifying the biomes configuration on the map and applying the right configurations and some other hidden conditions.</description>
</item>
<item>
<title>Features</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/master/m5-capsearch/features/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/master/m5-capsearch/features/</guid>
<description>Features Roles Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla facilisis neque id vulputate malesuada. Quisque dignissim finibus urna sed sagittis.
Game-Flow Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla facilisis neque id vulputate malesuada. Quisque dignissim finibus urna sed sagittis.
Voting Systems Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla facilisis neque id vulputate malesuada. Quisque dignissim finibus urna sed sagittis.</description>
</item>
<item>
<title>Gameplay</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/master/m2-food4future/gameplay/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/master/m2-food4future/gameplay/</guid>
<description>Gameplay You can manipulate the light-conditions, the temperature, the pH-value and the salinity of the water the algae should grow in. Keep an eye on the status of your plant with your score and the indicator on the floating monitor within all stages. If you want to learn more about the parts needed to do this kind of research, you can click on the small icons with an “i”. Those will open small boxes with text that will let you know more.</description>
</item>
<item>
<title>Process</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/master/m2-food4future/process/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/master/m2-food4future/process/</guid>
<description>Process The first thing we thought about within the brainstorming for this project was: •	What do we want to communicate?
•	Who is the target audience?
•	How can we target this audience? We answered those questions by communication with the product owners of the food4future-project. Food4Future (f4f) is a joint project funded by the German Federal Ministry of Education and Research (BMBF) as a part of the “Agricultural Systems of the Future” programme.</description>
</item>
<item>
<title>Story</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/master/m2-food4future/story/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/master/m2-food4future/story/</guid>
<description>Story In our AR-Game environment the “No land”-Scenario takes place. The area available for food production is decreasing. You are part of a team responsible for the indoor cultivation of algae. Therefore, you can experience all three important stages of the research necessary to grow the best algae for your country.</description>
</item>
<item>
<title>Workflow</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/master/m2-food4future/workflow/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/master/m2-food4future/workflow/</guid>
<description>Workflow As we are working in a group of four, we must use git (githHub) as our Version Control System. As our game engine we choose Unity, because it should be easier to work with as a beginner. To create the 3D-Models we used Blender and the build-in solutions provided by Unity itself. As our app only deploys on Android yet, we also used smartphones and tablets to test the application.</description>
</item>
<item>
<title>Features</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/master/m4-orgxtract/features/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/master/m4-orgxtract/features/</guid>
<description>Python Library The library contains primitives for extracting PDFs and detects shapes and words. It includes semantic analysis of organizational charts. The library can be used in your Python projects. It can be customized to your needs for your organizational charts by providing your own datasets. Command Line Tool The command line tool is designed to convert PDF files into JSON files. This main feature offers a simple user interface to quickly extract data from individual or multiple files.</description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b5-pam/techstack/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/bachelor/b5-pam/techstack/</guid>
<description>Tech Stack We used the following technologies in our Project: Future As this is a project on a limited-time basis, we are not planning on adding new features. However, we are going to add enough comments and documentation so that the next group to pick it up and try to improve on it will have an easier time. Future improvements to PAM would include Syntax Investigation of the diagrams, more in-depth filtering, perhaps even a social media share function.</description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/master/m1-gaming-for-future/techstack/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/master/m1-gaming-for-future/techstack/</guid>
<description>Tech Stack Overview Our project utilizes a diverse tech stack to support various aspects of development, design, 3D modeling, music production, and communication.
Development: We leverage Unity Engine for robust game development, integrated seamlessly with JetBrains Rider and Visual Studio for efficient coding and version control through GitLab.
Design: Graphic and UI design is powered by industry-standard tools including Adobe Photoshop and Adobe Illustrator, along with collaborative platforms like Figma and Mural for design iterations and team collaboration.</description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/master/m5-capsearch/techstack/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/master/m5-capsearch/techstack/</guid>
<description>Tech Stack Hugo offers a couple of options to include diagrams right in the source code, see https://gohugo.io/content-management/diagrams/
Here&rsquo;s a mermaid example: (note the hasMermaid = true parameter in the front matter!)
classDiagram Animal <|-- Duck Animal <|-- Fish Animal <|-- Zebra Animal : +int age Animal : +String gender Animal: +isMammal() Animal: +mate() class Duck{ +String beakColor +swim() +quack() } class Fish{ -int sizeInFeet -canEat() } class Zebra{ +bool is_wild +run() } Future &amp; A M S i o i q f b B x u j o e a ( - x d r a &gt; e f R &gt; c o C n u o b ( n r ) ) d n e e J d r o s i n N o R D t o i u a a n g d d l o i t n e D i a g o n a l s C V u e r r v t e i d c a l n o t A N C : o u l d r r i A a / I v n s i n e e h s t d - e - t r l B i h i i s i o n ' s r e q n .</description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/master/m4-orgxtract/techstack/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/master/m4-orgxtract/techstack/</guid>
<description>Organization Github for code collaboration and distribution Trello for task organization Figma for visualization prototyping Core Python Python was selected due to its status as the most prominent programming language for data science. Given the extensive range of available packages, it proved to be the most effective language for our problem.
PyMuPDF The PyMuPDF library was employed for the extraction of data from PDF documents, as it is the most high-performance Python library for this purpose.</description>
</item>
<item>
<title>Future</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/master/m4-orgxtract/future/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/master/m4-orgxtract/future/</guid>
<description>Open Data Formats For now, the PDF files are only converted into JSON Files. Developing the project further, integrating more open data formats (RDF, CSV, etc.) would be an option to create more possible use cases. Integration with External Tool The Technologiestiftung Berlin has developed an organizational chart tool that makes it easy to create organizational charts in a browser. The foundation has developed a JSON format called orgjson. Files in this format can be uploaded via their web interface.</description>
</item>
<item>
<title>ws23</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/debug/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/debug/</guid>
<description></description>
</item>
<item>
<title>ss24</title>
<link>https://htw-imi-showtime.github.io/staging/ss24/project_overview/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ss24/project_overview/</guid>
<description>This is the Project Metadata Overview - Back to Index</description>
</item>
<item>
<title></title>
<link>https://htw-imi-showtime.github.io/staging/ws23/master/m4-gamingforthefuture/review/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/master/m4-gamingforthefuture/review/</guid>
<description>Für alle Projekte: bitte überprüfen, ob alle Bilddateien notwendig sind und sich nicht doch noch verkleinern lassen. (und es ggfs. Auch tun) die Texte nochmal durchgehen und straffen. Bei Team reicht z.B. wir waren 5 IMI-Master: Namen und Bilder. (evtl. Noch Aufteilung von Verantwortlichkeiten, wenn Sie nicht woanders stehen) M4 Sehr schöne Seite!
Dateigrössen alles ok.
wenn Sie wollen, könnten Sie prüfen, ob sich die Größe der Bilder weiter reduzieren lässt, z.</description>
</item>
<item>
<title>Challenges</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b4-hypnobuddy/challenges/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b4-hypnobuddy/challenges/</guid>
<description>Challenges: User Management: Balancing Complexity and Simplicity The intricacies of managing users across three categories—therapists, patients, and parents—demanded a delicate balance. Based on therapists&rsquo; recommendations, we opted to allow patients and parents to share the same account, simplifying the user experience. However, creating a secure yet straightforward connection between therapists and patients posed a unique challenge. To streamline this, we implemented connection codes, enabling therapists to effortlessly initiate and secure connections with their patients during the first therapy session.</description>
</item>
<item>
<title>Contact</title>
<link>https://htw-imi-showtime.github.io/staging/contact/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/contact/</guid>
<description>The IMIxShowtime is a showcase of the term-long practical projects in the International Media and Computing Bachelor&rsquo;s and Master&rsquo;s programs. It takes place every term on the Friday of the last week of lectures.</description>
</item>
<item>
<title>Features</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b6-avatavr/features/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b6-avatavr/features/</guid>
<description>The VR Testing Environment One goal of our project was to construct a virtual test environment where the interaction between a user and the instructor could be examined. The challenge consisted of creating such an environment while not making it distracting enough to turn the focus away from the character that has to be evaluated. For a majority of our testers this was the first time experiencing a surrounding in Virtual Reality Scene 1 Introduction inside the Apartment In this scene the player is greeted by the instructor, and asked to point out some different uses of electric current in a regular household.</description>
</item>
<item>
<title>Future</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b4-hypnobuddy/future/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b4-hypnobuddy/future/</guid>
<description>As we reflect on our current achievements, we envision a future where our web application evolves into an essential tool for diverse forms of mental therapy. Here are key areas where we see potential for improvement: Therapy Session Calendar Streamlining Appointment Management
To streamline the therapeutic process, we plan to incorporate a comprehensive Therapy Session Calendar. This feature would empower therapists and clients to create or request new appointments directly within the app.</description>
</item>
<item>
<title>IMI-Showtime via Zoom</title>
<link>https://htw-imi-showtime.github.io/staging/zoom-help/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/zoom-help/</guid>
<description>1. Install or update Zoom If you do not have the Zoom client installed yet, you can get it here:
Windows | Other platforms
If you already have the client installed, please make sure it is up to date. 2. Join the Zoom session Simply follow this link: https://htw-berlin.zoom.us/j/97320821203
3. Switching rooms To switch from the main session into breakout rooms you first need to click on the „Breakout Rooms“ button (1) and then click „Join“ for the desired room (2) and confirm with „Yes“ (3).</description>
</item>
<item>
<title>Important Dates</title>
<link>https://htw-imi-showtime.github.io/staging/dates/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/dates/</guid>
<description>After Showtime is just before the next Showtime - upcoming events:</description>
</item>
<item>
<title>Imprint</title>
<link>https://htw-imi-showtime.github.io/staging/imprint/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/imprint/</guid>
<description>Diese Seite präsentiert Praxisprojekte der Studiengänge Internationale Medieninformatik Bachelor und Internationale Medieninformatik Master der HTW Berlin und ergänzt diese Webseiten.
Redaktionelle Verantwortung und verantwortliche Ansprechperson Studiengangssprecher der Studiengänge Internationale Medieninformatik (Bachelor &amp; Master)
Prof. Dr. Barne Kleinen
HTW Berlin, Fachbereich 4
Wilhelminenhofstr. 75A
12495 Berlin
barne.kleinen#64;htw-berlin.de
https://www.htw-berlin.de/impressum/
Telefon: +49 30 5019 - 3738
Urheberschutz und Nutzung Die Urheber räumen Ihnen ganz konkret das Nutzungsrecht ein, sich eine private Kopie für persönliche Zwecke anzufertigen.</description>
</item>
<item>
<title>Privacy Policy</title>
<link>https://htw-imi-showtime.github.io/staging/privacy-policy/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/privacy-policy/</guid>
<description>Es gilt die Datenschutzerklärung der HTW Berlin.
Diese Website verwendet keine Cookies und speichert keine Informationen, die über die üblichen Server-Logs der Webserver unter https://htw-berlin.de/ und https://github.com/ für https://htw-imi-showtime.github.io/preview/ und https://htw-imi-showtime.github.io/staging/ hinausgehen.</description>
</item>
<item>
<title>Project Archive Overview</title>
<link>https://htw-imi-showtime.github.io/staging/archive/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/archive/</guid>
<description></description>
</item>
<item>
<title>Projects</title>
<link>https://htw-imi-showtime.github.io/staging/projects/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/projects/</guid>
<description>This term there are 5 bachelor&rsquo;s and 5 master&rsquo;s projects:</description>
</item>
<item>
<title>Schedule</title>
<link>https://htw-imi-showtime.github.io/staging/schedule/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/schedule/</guid>
<description>There will be brief project presentations with a quick Q&amp;A in the morning (very brief presentations, the odd times are real, we might even be a bit quicker than this) and a project fair in the afternoon.
Ort: H 001 / Campus Wilhelminenhof</description>
</item>
<item>
<title>Showtime Website History</title>
<link>https://htw-imi-showtime.github.io/staging/hugo/history/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/hugo/history/</guid>
<description>For now, this is a gitinfo tryout:
(see https://gohugo.io/methods/page/gitinfo/)
GitInfo: Gitinfo: AbbreviatedHash: 2ef6516 AuthorDate: 2024-10-10 AuthorEmail: [email protected] AuthorName: Barne Kleinen CommitDate: 2024-10-10 Hash: 2ef6516c335437878f052a6ccbdd4240671b8878 Subject: winter date </description>
</item>
<item>
<title>Tech Stack</title>
<link>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b6-avatavr/tech-stack/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://htw-imi-showtime.github.io/staging/ws23/bachelor/b6-avatavr/tech-stack/</guid>
<description>The Oculus Headsets Thanks to the &ldquo;Institut für Kultur und Informatik an der HTW Berlin&rdquo;, which provided us with access to cutting-edge Oculus Headsets. The Quest 2 and Quest Pro, equipped with hand sensors, offered a seamless tracking experience, eliminating the need for external scanning setups. While these headsets proved to be revolutionary, navigating through app testing during the development phase presented its own set of challenges.
Oculus Quest App Meta Developer Hub Building the VR Environment Due to the implementation of the OpenXR Library into the Game Engine Unity, we were able to develop an app that is able to be played on most of the VR Headsets available.</description>
</item>
</channel>
</rss>