Joined July 2023
24 Photos and videos
✨Sneak Preview✨ WebForge 1.3 will introduce, for the first time on iOS, a stepping debugger for NodeJS! Add breakpoints to files or use the debugger keyword and step through your code. Browse active call frames, and inspect properties. All running locally. Join the beta to try it now: testflight.apple.com/join/Lt…
2
140
Coming Soon! We've been working hard on improving the NodeJS plugin, and we're proud to say the next update will add support for @vite_js, running entirely on-device! This brings many upgrades to child processes, adds WebAssembly, and adds native Esbuild support. Just to name a few! We'd also like to say, after stepping through Vite and Esbuild almost line-by-line during this process - wow - amazing work by these projects!
18
2,182
Won't be long now #node #nodejs
5
198
WebForge v1.1 is well underway - first beta submitted for review this morning. This update includes a SQLite database editor, JSHint customization, and file templates. Coming soon!
1
1
751
SQLite plugin coming along well! Properly shows results and allows you to run any query you like. We have a few more convenience features to add and then it's off to our wonderful beta testers. What features would you like to see?
1
106
Working on a SQLite database plugin that will allow you to easily inspect and edit database files, right alongside other project files. Coming soon but more work to be done - tough to get right for all platforms! #buildinpublic
2
97
One the the improvements we've made to v1.0.1 is PHP thread safety. It sounds great, yes, but what is it? A quick explanation: WebForge features a built-in webserver to serve your projects to the built-in browser (your own little world...). Some traditional webservers are multi-process, creating a new process for each request. This keeps everything (memory, resources, etc) nicely separated. However, iOS apps are restricted to one process, so this approach is not an option. The good news is, apps can (and very frequently do!) use multiple threads. We built the WebForge webserver therefore to be single-process, but multi-thread, creating a new thread for each request. While this allows requests to be handled concurrently, it presents a problem when you have a library that uses global resources (like PHP), as threads don't have the same resource separation as processes. You therefore run into conflicts between requests. At best you leak information between requests, at worst you crash. Enter PHP ZTS (Zend Thread Safety). This option allows PHP to separate it's global resources in a thread-safe way, providing the separation needed to operate in a single process, multithread environment. With v1.0.1 we've enabled PHP ZTS and implemented it in the PHP plugin. This means scripts can execute concurrently ex. multiple PHP-powered images in a page, or a script requesting another using cURL (another thing we added!), without leaking data or crashing the app. Just one more step to the best option for PHP development on iOS.
4
93
🎉 WebForge IDE is now available! 🎉 Thank you to everyone who followed our announcement, participated in the beta, and helped us launch the newest (and best!) web development IDE for iOS. Now, on to v1.1! apps.apple.com/us/app/webfor…

1
3
8
2,233
Clone, checkout, code, commit. Clone, checkout, code, commit. Clone, checkout, code, commit.
2
61
👀
2
85
Public beta now open! Join our TestFlight to get early access to WebForge and help influence development. testflight.apple.com/join/Lt…
1
1
1,816
We're finally on the verge of a public release! We're rolling out a new beta today that comes with a good deal of polishing, all thanks to an unexpected cause: We wrote a user guide! Writing this guide was something we've been avoiding, but we're sincerely glad we finally tackled it. Here's a brief story about the perks of using your own product and the value of creating a user guide: As we're nearing the end of our release cycle, we had been procrastinating on writing a user guide. As developers, we're not naturally drawn to writing technical documentation, and let's be honest, it's not our favourite task. We found ourselves thinking, "Who needs a user guide anyway? Our product is intuitive enough!" But clarity never hurts. So, we got to work and started writing. We're so thankful we did! We wrote the user guide in HTML, providing us with a perfect opportunity to use our own product. This hands-on use helped us identify several bugs, all of which we promptly fixed, and led us to implement many small but hugely useful improvements to the code editor. These are aspects often overlooked until you step into the shoes of an end-user. Beyond the hands-on experience, writing a user guide has another benefit: it forces you to walk through your product, step by step, explaining every detail. This process exposes quirks and bugs, and inspires better solutions. Whether the guide will be used we can't say (especially because we don't use any analytics frameworks #datanotcollected), but writing it was an invaluable exercise that improved the product greatly. We hope you enjoy the beta!
1
150
New beta out today! This beta introduces #JSHint support! #WebForge will analyze your JavaScript files and display notices and warnings right in the editor. These are also included in the "Warnings" panel, giving you a project-wide view of potential issues. #WebDev #iPad #iPhone
2
240
A new week and a new beta! This update massively improves WebForge's syntax highlighting. Faster, more accurate, and better support for multi-language documents. Take a peek and sign up for beta access! #WebForge #WebDev #iOS #iPad #iPhone
123
New Beta out today! This beta adds pop-out Inspect Browser, so you can use and inspect your projects full-screen. DM us your email address or send a message to support@pdyn.net for beta access!
2
109