A list of puns related to "Integrated Development Environments"
I'm curious of what options exist for managing a development environment for a production SharePoint form that uses the SharePointIntegration feature. I haven't seen any official change management strategy from MSFT so I'm leaning on Reddit here for any suggestions.
Is the best way so far to just clone the list and literally copy + paste the screens to the second PowerApp enabled list?
I am currently in programming classes and one class suggests downloading netbeans as a Java IDE. However, I am using a computer I am not an administrator for. Is there a way to get access to a Java IDE without downloading one, perhaps through a web version? or an ios app?
A desktop environment is a development environment except windows and widgets are the files and the user's inputs are the lines of code. A desktop environment should be malleable to change in a similar way that the contents of the DOM (Document Object Model) of a web application can be easily changed. A web developer does not need to re-compile source code to change how an application appears.
If applications were designed to separate:
the decision of what widgets should be displayed given application state
deciding what data each widget should display
deciding which widgets should be displayed together (logical groupings such as 'menubar', 'toolbar')
deciding how to lay these widgets out (ordering, orientation)
deciding how detailed these widgets will be (responsive design)
Then the desktop environment and the user can override parts of the above behavior of the application without damaging the internal state of running applications.
a user could select an interesting region of a complex interface and 'send it to the notification area' or 'promote it to the title bar so that they can cut and splice the user environment how they like. This would be provided by the environment - not specifically coded. (How can I display a live screenshot of a piece of another application?)
the user can interrogate and inspect the underlying data a widget is displaying and add behavior to it
right-click a 'disk usage' indicator and select 'monitor' and create a notification when disk usage reaches a threshold. The desktop environment is smart enough to know it is not the widget itself that is being monitored but the underlying data the widget is displaying.
Example: A configuration file
- A simple visualization of a configuration file is a plain text editor.
- The next layer may be a tree structure to navigate the blocks of the file.
- The next step would be to provide proper widgets for every value.
- The next step may be wizards to generate certain blocks of the configuration file.
- The next step may be to provide a dashboard and interpretation of what the configuration
file is doing from a high level. Such as a nginx dashboard with icons for proxying. (representational computing and data views)
Interfaces are written to visualize and edit representations.
Writing interfaces to interact w
I just installed Python to automate some stuff. I have experience with R and I’ve always used rstudio with it. What is a good equivalent for Python?
Let me know if you want a beta tester account.
A desktop environment is a development environment except windows and widgets are the files and the user's inputs are the lines of code. A desktop environment should be malleable to change in a similar way that the contents of the DOM (Document Object Model) of a web application can be easily changed. A web developer does not need to re-compile source code to change how an application appears.
If applications were designed to separate:
the decision of what widgets should be displayed given application state
deciding what data each widget should display
deciding which widgets should be displayed together (logical groupings such as 'menubar', 'toolbar')
deciding how to lay these widgets out (ordering, orientation)
deciding how detailed these widgets will be (responsive design)
Then the desktop environment and the user can override parts of the above behavior of the application without damaging the internal state of running applications.
a user could select an interesting region of a complex interface and 'send it to the notification area' or 'promote it to the title bar so that they can cut and splice the user environment how they like. This would be provided by the environment - not specifically coded. (How can I display a live screenshot of a piece of another application?)
the user can interrogate and inspect the underlying data a widget is displaying and add behavior to it
right-click a 'disk usage' indicator and select 'monitor' and create a notification when disk usage reaches a threshold. The desktop environment is smart enough to know it is not the widget itself that is being monitored but the underlying data the widget is displaying.
Example: A configuration file
- A simple visualization of a configuration file is a plain text editor.
- The next layer may be a tree structure to navigate the blocks of the file.
- The next step would be to provide proper widgets for every value.
- The next step may be wizards to generate certain blocks of the configuration file.
- The next step may be to provide a dashboard and interpretation of what the configuration
file is doing from a high level. Such as a nginx dashboard with icons for proxying. (representational computing and data views)
Interfaces are written to visualize and edit representations.
Writing interfaces to interact w
Please note that this site uses cookies to personalise content and adverts, to provide social media features, and to analyse web traffic. Click here for more information.