Replies: 4 comments 15 replies
-
|
It might make more sense to choose some specific components to bundle into one project with a size estimate. For example, BrowseBox FileBox together for a 90 hour project. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @rikedyp |
Beta Was this translation helpful? Give feedback.
-
|
hey, hi! @rikedyp @sloorush how can i understand the problem statement better, and how many components are we looking for? |
Beta Was this translation helpful? Give feedback.
-
|
hey guys ! like I am new to open source so can someone assist me where to start? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Description:
EWC (Everywhere Window Create) is an emulation of Dyalog's highly successful object library for Windows Win32 GUI applications. While the original is limited to Windows Desktops, EWC allows the creation of web applications and cross-platform desktop or mobile applications using a combination of APL code on the server and JavaScript/React on the client side.
The EWC client can run in any mainstream browser or via the Chromium Embedded Framework on platforms that support it. When running on a single-user machine (typically via CEF), there are a number of classes available to the Windows developer that are not currently by supported JavaScript because access to local resources is restricted. Examples include BrowseBox, FileBox, FontPicker, Printer Selection and Configuration dialogs. These classes necessarily require development on both the APL and the JavaScript sides - prior APL knowledge is not required.
The task is to implement as many as possible of these classes using either existing EWC components (Button, Edit, Combo, ListView, etc) or by implementing new ones, and APL code that will work under Linux, Microsoft Windows and Apple MacOS, to provide EWC users with cross-platform versions of these objects.
The EWC development team will be available for mentoring and to help with any necessary enhancements to EWC to support this work.
Required:
Expected outcomes:
New EWC classes that can be used in APL applications, with documentation and examples.
Technologies involved:
APL, EWC, JavaScript, React, HTML, CSS.
Beta Was this translation helpful? Give feedback.
All reactions