It's useful to either clone a full git history or one commit in
depth. One for cloning an existing (welcome screen) and one
shallow clone for our examples repo which is massive now!
This probably could become useful later on. It resolves the issue
of our examples being huge now.
We introduce C# examples to EDI.
Also the icon data/extra/examples/images/mono-runtime.png, which
is based on Faenza is released under the GPLv3 license (included).
The author, who goes by madmaxms or Marcus has no e-mail contact
information. His works can be found on Github at:
https://github.com/madmaxms.
Thanks very much for such a lovely icon for our Mono/C# templates.
The examples.git repo is getting RATHER large. However it is
demonstrating here that the UI can lock if we don't use a
separate thread here. Also we need some indication something
is happening, so let's use a progressbar.
This needs some more work but for now it's better behaviour.
In the vain of every other EFL application and Enlightenment,
let's start adding an insane amount of settings [sic]. In
sincerity, people like or don't like it, let's make it an
option.
This existing test is far too slow (though more accurate). On
FreeBSD and OpenBSD we have strcasestr. Am happier to use this
for the sake of "usability". Keep the code around for reference.
This slight change to the API allows the user (when prompted) to
open the settings panel, access to the specific settings tab of
interest. Therefore a prompt for missing user information,
will open the settings panel at the project section of settings.
This disables the initial highlighting on the settings
window. Cosmetically gets rid of the initial hidden
rectangle focus. If a user presses tab, focus and selection
works as normal.
When changing window alpha ensure the settings window
remains on top. Previously an alpha change would lose
the settings window when enabling alpha. Also add
some documentation.
In the settings panel after selecting the font
and then returning to the main settings window,
white artifacts polluted the widget. We need to
delete this object.
When there is user information missing or a change required in
settings, display a dialogue with the information and an added
button to open the "Settings" window.
When there is user information missing or a change required in
settings, display a dialogue with the information and an added
button to open the "Settings" window.
First, make sure the project stores user/email for SCM (again!). Also
allow user to change the user/email > once. Add a check to
stash (from menu) for credentials also.
This allows us to change the remote user and email more than once.
Also it ensures that
Alastair Poole
Alastair Poole
Andy Williams